E1.20 RDM (Remote Device Management) Protocol Forums

E1.20 RDM (Remote Device Management) Protocol Forums (http://www.rdmprotocol.org/forums/index.php)
-   RDM General Implementation Discussion (http://www.rdmprotocol.org/forums/forumdisplay.php?f=4)
-   -   RDM & DMX frames multiplexing (http://www.rdmprotocol.org/forums/showthread.php?t=1080)

DavidR November 19th, 2010 10:59 AM

RDM & DMX frames multiplexing
Hi All,

I'm new in this forum and although I have browsed the FAC, I didn't find an answer to my question.

RDM specification mention a lot of timing values for RDM frames, but doesn't really explain how to multiplex DRM & DMX frames.

Suppose the controller is sending DMX (typically during a crossfade) at a rate of 25 (up to ~48 according to DMX512A specs) cycles/second. How the controller shall insert RDM frames and manage reception of anwsers (and possibly timeouts)?

In other words I'm wondering if there is some gidelines or whitepaper about the rules on this matter?



sblair November 19th, 2010 12:17 PM


Good question! Section 3.1.2 specifies the timing values for packet spacing between Null Start Code frames and RDM frames as well as RDM Discovery frames. These timings are the only requirements in how you handle interleaving between the packets.

As long as you follow these requirements you are then free to interleave in whatever makes the most sense for your product.

In general, a number of products will do a 1-1 interleave of DMX NSC, RDM Request/RDM Response, DMX NSC. With that type of 1-1 interleave you can still maintain about 26HZ refresh rate of the NSC packets.

There are many tricks and optimizations you can do based on your application and need. For example, if you are in the middle of doing an active crossfade, you may choose to reduce or eliminate the frequency you send RDM messages in the background in order to maintain a higher refresh rate during the crossfade.

At the same time, if you are doing something more intensive with RDM and your DMX values aren't changing then you can dramatically throttle back the number of DMX NSC packets you are sending and mostly just send RDM packets. Your only real requirement is to send an NSC packet at least 1/second to keep the signal alive so the devices don't go into a "loss of signal" scenario. The rest of the messages could all be RDM traffic at that point.

Hope this helps shine some light on it for you.


DavidR November 20th, 2010 04:10 AM

Hi Scott,

thank you for this quick answer, this is exactly what I expected.

Best Regards,


All times are GMT -6. The time now is 11:56 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2021, vBulletin Solutions, Inc.