Excluding the impact of chipset performance and host processing capability, the primary reason in-vehicle network cameras tend to exhibit greater latency than analogue HD cameras is due to the image encoding, decoding, and transmission processes. To enhance video smoothness and transmission stability, network cameras typically buffer a number of image frames prior to encoding — a step that inevitably introduces some delay.

In practical testing, we used ONVIF standard tools to assess the latency of our 30 fps network cameras. The results indicated an average latency of approximately 180 ms. It is worth noting that, in real-world applications, overall latency can also be influenced by the decoding capabilities of the host system and the performance of the display unit.

Taking into account the demands of the in-vehicle environment, a latency of under 300 ms is generally regarded as acceptable. This ensures a satisfactory balance between real-time responsiveness and system stability.

In the production of vehicle-mounted exterior cameras, many small and medium-sized manufacturers face challenges in achieving stable and high-quality waterproof performance. To address waterproofing issues, some have adopted potting (glue-filling) techniques, which offer a relatively simple process to achieve consistent water resistance in the short term. However, we do not recommend the use of potting-type cameras for the following reasons:

1. Limited Stability of Waterproof Adhesives

Exterior vehicle cameras operate in complex and harsh environments, often exposed to extreme temperatures, UV radiation, and high humidity. Under these conditions, the waterproof adhesive tends to degrade over time—leading to issues such as cracking, softening, or becoming brittle—which seriously compromises the camera’s waterproof performance and lifespan.

2. Electrical Performance Issues Caused by Adhesive Impurities

The potting process can introduce trace amounts of moisture or impurities into the adhesive, potentially affecting the camera‘s electrical properties. This may lead to uncontrollable issues in areas such as EMC (electromagnetic compatibility) and power consumption, reducing the overall stability and reliability of the device.

3. Difficult Maintenance and Repair

Once the adhesive has cured, potting-type cameras are nearly impossible to disassemble. If a failure occurs, the device is essentially irreparable and must be scrapped. This makes potting-type cameras more suitable for low-cost, disposable applications, rather than environments that require high reliability and serviceability.

4. Higher Long-Term Costs

Although potting-type cameras may have a slightly lower upfront cost, their failure rate increases significantly over time. Over a 5-year usage period, the total cost of ownership for potting-type cameras often exceeds that of structurally waterproof cameras. In fact, structurally waterproof models can offer up to 40% lower long-term costs—excluding the potentially high maintenance and service expenses.

This phenomenon is called power frequency interference, which is a problem with exposure frequency. Please check whether your camera is set to the correct exposure mode, such as whether 50HZ/60HZ is correct and whether the exposure time is too short.

There are many reasons why the camera has no image, mainly power supply problems, network problems and parameter problems. Please follow the following operations to confirm the fault and repair or replace the device.
1. First check whether the network cable and power cable are connected properly.
2. Block the photosensitive sensor, confirm whether the infrared light is turned on normally, and confirm that the device is powered normally.
3. Use the configuration tool to search and check whether the search is normal.
4. Check the IP network segment in the search tool to see if it is consistent with the network segment of the network environment.
5. Confirm that the device is added correctly.
6. Confirm that the backend can correctly support the encoding method and resolution of the camera.

The above phenomenon is mainly caused by port errors. Remember to check whether the port is correct. The default IPC port is 80