Q: ClairEye-i video detector utilizes a vast amount of real-world traffic data, and the algorithm is embedded in the AI chip for real-time traffic data processing. Is the data sourced from projects in the local region? Is it suitable for the global market's traffic situations?

A: Our algorithm is trained using both standard and specific traffic datasets. The standard traffic data includes international traffic information, making it suitable for the global market. Our training also focuses on challenging visibility conditions, such as nighttime, dawn, and adverse weather conditions like dust, fog, rain, and snow. These conditions don't vary significantly from region to region.

Q: With a detection distance of up to 150m, how does the system manage with a small IR? How does it prevent blurring from headlights at night?

A: We utilize a starlight CCD (0.0001LUX) that doesn't require infrared fill light. To mitigate blurring, we employ Digital WDR technology, which effectively suppresses intense light.

Q: The ClairEye-i's power consumption is just 3W with both AI and an optical camera. This seems almost unbelievable. How is this achieved?

A: This is achieved by employing a low-power consumption processor and CCD.

Q: How many lanes can be covered simultaneously? 

A: It depends on the number of lanes the field of view can cover which will be related to the installation height and location. 

Q: How is the setup done? What type of communication is used?

A: Configuration is done through a web GUI, communicating via Ethernet.

Q: What about the I/Os?

A: We utilize an accessory box that serves as an Ethernet to IO converter for I/O output.

Q: API?

A: We offer both customized and default APIs.

Q: Many older controllers operate using I/Os, or RS485. However, this may require adaptation to fit specific controllers. Can you accommodate this?

A: We can provide a standard interface protocol. If the controller has its own interface protocol, we can also adhere to that.

For more information: https://bit.ly/440eYM7