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)
-   -   Addressing Universes on RDM: Manufacturer PID V ENDPOINT_TO_UNIVERSE (http://www.rdmprotocol.org/forums/showthread.php?t=1316)

Thierry Dupont November 20th, 2020 04:00 AM

Addressing Universes on RDM: Manufacturer PID V ENDPOINT_TO_UNIVERSE
 
Hello Everyone,

This is my first message, surely not the last one.
At Robert Juliat we are working on a new platform and we have an embedded node that can receive Art-Net and Sacn. Also we have one a classic DMX/RDM port.
We implemented RDM E1.20 + parts of E1.37-1/-2.

We have to address Universes by RDM for Sacn and Art-Net:
- Should we use a MANUFACTURER_PID or ENDPOINT_TO_UNIVERSE 0x0903 from E1.37-?
- For Art-Net could we use 0 to 32767 to address the universe?

Thanks

sblair November 20th, 2020 01:37 PM

Welcome to the forums Thierry.

I would suggest using the ENDPOINT_TO_UNIVERSE PID from E1.37-7. You will also want to support the ENDPOINT_LIST PID as well for controllers that may be expecting that before using the ENDPOINT_TO_UNIVERSE PID.

It's a been a long time since I've cracked open the ArtNet spec but I know the newer versions of it are using sACN underneath so it might work for the later versions of ArtNet.

We specifically didn't address use of ArtNet with any of the PIDs as we limited the scope to focusing on sACN as that is the direction everything has been moving towards.


All times are GMT -6. The time now is 03:23 AM.

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