There are currently four connection strings defined, all of which are ethernet related. DMX delivered via RS-485 transmission is not defined. While it may be a bit illogical to use RS-485 DMX transmission if a network connection is also available for CITP communication, it is not disallowed.

A DMX E1.11 connection string should be added. Since a fixture/server is ignorant of "universe" and only has start "channel" information, the string would be something like "DMXE111/<channel>".

While "no system could use it to actually identify the DMX data in question", it will provide existing configuration information to the querying device. It would allow a control desk to identify a server configuration so the operator can manually patch the server, deciding manually how to assign and connect the DMX stream.

Granted, it is a bit ambiguous to have both an RS-485 connection and an ethernet connection, but it is physically possible and is not disallowed by any existing control specification. It is a situation that can exist for which there is no connection string.

If nothing else, it could serve as a diagnostic to alert the operator that a sever might need to be reconfigured to use some ethernet-based control stream.