Updated 2026-10-08

1. Decode something you already have

Open the decoder and paste any of these:

• A hex string from an RSU's message store (the rsuMsgRepeatPayload column of an SNMP walk), from a vendor console, or from an ODE log. Spaces, colons and 0x prefixes are fine.
• A base64 payload from a Kafka topic or a REST API.
• A whole captured frame: an Ethernet frame with EtherType 0x88DC, an IEEE 1609.3 WSMP frame, or an IEEE 1609.2 secured PDU. The decoder peels each layer and shows what it found.
• XER (XML) or JSON if you are converting from another tool.

The result has four parts. The headline card names the message, its ID, size and the layers that were removed. The summary translates raw units into plain values: tenths of microdegrees to coordinates, 0.02 m/s to mph, TimeMark tenths of a second to clock time, ITIS codes to phrases. The map draws MAP lanes, TIM regions, RSM paths, BSM path history and SDSM detected objects. The JSON and XER tabs are the full decode, field by field, in the names the standard uses.

If a decode fails, the message tells you where: a payload that starts 00 14 but stops early is a truncated BSM; a payload that decodes as the wrong type usually has the wrong messageId; a frame from a 2016-era device may use fields that the 2024 dictionary renamed.

2. Create a message

Open the creator and pick a template. Each one is a realistic, validated example: a BSM with path history, a SPaT with four signal groups, a MAP with ingress and egress lanes and connections, a work-zone TIM and a speed-limit TIM, a J2945/4 Road Safety Message for a lane closure, a PSM, an SRM and SSM pair for transit priority, an SDSM with detected objects, an EVA and an RTCM correction.

Edit the quick fields (position, timing, codes) or the JSON itself, then Encode / Validate. The portal checks every range, size and enumeration against the standard before it hands you bytes; a constraint error names the field and the rule. The output is the UPER hex you would store on an RSU, plus base64, the readable summary and the map, so you can confirm the geometry before you broadcast it.

3. Register an RSU and push

Create a free account, open My RSUs, and add a device: a name, the agency, vendor and model, its location, its IP address and SNMPv3 credentials. Credentials are encrypted at rest and each account only sees its own devices. Test connection reads the system description and RSU identity so you know the credentials and the firewall are right before you push anything.

From the creator, Push to my RSU writes the encoded message into the RSU's store-and-repeat table with the PSID, channel, interval and delivery window you choose, as described in the NTCIP 1218 push guide. The push log keeps the SNMP response for troubleshooting.

4. When to call us

The portal is free and will stay free. ITS Roads earns its keep when an agency wants the work done for it: SCMS enrollment and certificate renewals across a fleet, SPaT and MAP generation and verification against CTI 4501, TIM and RSM programs tied to work-zone data, FCC licensing, OmniAir readiness, NTCIP 1218 conformance testing, and 24/7 monitoring of the RSUs, the security subsystem and the backhaul with the agency's existing enterprise tools. Contact ITS Roads to scope a managed service.