new PID: last active port on splitter
 

Hello again!
Trying to provide a mechanism to know how the RDM net is phisically builded, I suggest a PID to ask a splitter wich port recieved the last message. Then, if you ping a device (perhaps with a status request or a mute command) you can subsequently ask the splitter wich was the last active port, and then you know where is the device phisically attached. Devices in the same port are presumibly in the same link. This idea relays on the assumption that a splitter has this a level of intelligeny to implement this capability and no transparent inline devices are present.
Thank you again, regards, Luis

During the initial brainstorming session there was a discussion of "Topology Mapping" PIDs, which is similar to what you are describing. Rather than "Last Active Port", PID the idea was to have a "GET UID Port" PID that would tell you what port a specific UID is attached to.

The problem with "Last Active Port" is that it can give in accurate results in a system with more than one controller generating requests (as you might find with an RDM Merger or E1.33 style system).

However, during the initial discussion, there seemed to be relatively little interest in Topology Mapping PIDs. Who else is interested in having such a feature?