• Support for “Jumbo Packets” (up to 39 bytes payload) to enable OC32 Message Tunneling, among other things
• OC32 Message Tunneling, which allows OC32 modules to be configured through the RM-x while Dinamo is active
• Registration and active monitoring of OC32 modules, similar to TM-H, TM44, UCCI-s, and PM32. Note The RM-x does not (yet) support OC32 eXtended Addressing, so for now, a maximum of 16 OC32 modules per system is supported.
• If an OM32 command is received from the PC intended for a registered OC32 module, this message is sent as an OC32 message. If an OM32 command is received for a non-registered module, it is sent as an OM32 message. The addresses for OC32 and OM32 overlap.
• OC32 feedbacks from registered OC32 modules are forwarded to the PC as an “Embedded Subsystem Response”
• Support for PM32 Version Identification (requires PM32 1.10 or higher)

Note: If you have OC32s in your system, the orange LEDs on them will now stay “constantly lit.” This is because RM-x 1.3 now continuously monitors the OC32s. Just as with TM44, TM-H, and UCCI-s, the rule for OC32 in a Dinamo system is now: red/orange = good.
If you want to see if there is actual communication with the relevant OC32, you can change the function of the green LED on the OC32 to “OC32 Message received.” This also gets rid of that annoying blinking right away.