• 4X corrosion protection (NEMA 250 clause 5.10)
• Gasket (NEMA 250 clause 5.14)
The RVSD shall be able to withstand a drop of up to 5 ft. (1.5 m) without compromising its functional and structural
integrity.
The RVSD enclosure shall include a connector that meets the MIL-C-26482 specification. The MIL-C-26482 connector
shall provide contacts for all data and power connections.
7.0 Power. The RVSD shall consume less than 9.5 W.
The RVSD shall operate with a DC input between 12 VDC and 28 VDC.
8.0 Communication Ports. The RVSD shall have an RS-485 port and an RS-232 port, and both ports shall communicate inde-
pendently and simultaneously.
The two simultaneous ports are necessary whenever simultaneous access to the RVSD is needed or redundancy is required. For example, two
ports are needed if event data and interval data must be collected at the same time. For an example of redundancy, the RS-232 port and
RS-485 port could each be connected to separate communications device to provide a backup means of communication in case a device fails.
The RS-232 port shall be full-duplex and shall support true RTS/ CTS hardware handshaking for interfacing with various com-
munication devices.
The RVSD shall support the upload of new firmware into the RVSD's non-volatile memory over either communication port.
The RVSD shall support the user configuration of the following:
• Baud rate
• Response delay
• Data push
• RS-232 flow control (RTS/CTS or none)
The communication ports shall support all of the following baud rates: 9600, 19200, 38400, 57600 and 115200 bps.
9.0 Data Protocols. The RVSD shall support three different data protocols for all lanes being monitored: interval (bin) data, event
(per vehicle) data, and real-time true presence data.
The RVSD manufacturer shall provide the data protocol document free of charge.
The interval (bin) data packet protocol shall support:
• Sensor ID
• A timestamp that records the year, month, day, hour, minute, and second of the end of time interval
• Total volumes of more than 65536
• Average speed values in either mph or kph
• Occupancy in 0.1% increments
• Volume in up to eight length-based user-defined vehicle classification bins
• Volume in up to 15 user-defined speed bins (bin by speed)
• Volume for both directions of traffic (bin by direction)
• Average headway in seconds
• Average gap in seconds
• 85th percentile speed in either mph or kph
The event (per vehicle) data packet protocol shall support:
• Sensor ID
SmartSensor HD
7
Need help?
Do you have a question about the SmartSensor HD and is the answer not in the manual?