page 34
TrafficXRoads: Guide
Node
–
Detection
time should always be 20% shorter than the minimum
detection FPS for the specific scene type.
Node
–
Processing
also includes the
configurable tracker time buffer.
Block
–
Processing
time should always be at least 50% shorter than the
set
Computational tick interval
. If that is not the case, the unit is
overloaded and is unable to evaluate the data quickly enough. It is
necessary to lower the number of analytics or reduce the number of
data outputs.
Reducing latency on the outputs
By latency on the output we mean the transfer of the information about a traffic event
from FLOW device to the controller. The best communication tool with the lowest latency
are the UDP sinks. Next is the SDLC interface utilizing convertors and last, the I/O module
(relay interface) namely:
UDP sinks: < 1 ms
SDLC including the convertor: ~ 1 ms / based on the convertor
IO module – relay interface: ~ 11 ms
For maximum reduction of the latency between the unit and the traffic
controller we suggest using UDP interface if the traffic controller is data
compatible with the FLOW device.
Conclusion
The latency is worsened by both image grabbing, communication between the camera
and the unit, in the image analysis and in the communication between the unit and the
traffic controller. With good system settings, many of the latencies can be significantly
reduced and a very low latency can be achieved (200 – 350 ms), in breakdown:
Camera: ~ 50 – 150 ms
Image transfer: < 10 ms (local network)
TrafficXroads: ~100 ms
Communication to traffic controller: < 1 ms (UDP, local network)
Lower latencies are achievable with the use of industrial cameras (even as low as 50ms).
Get in touch with us if that is something you would like to implement.
