|
RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product. |
|
Thread Tools | Search this Thread | Display Modes |
February 5th, 2014 | #1 |
Junior Member
Join Date: Feb 2010
Posts: 7
|
new PID: comms_status_sc0
Hello!
In order to obtain more information about communications integrity, I propose a PID to request errors in Null Start Code packets, i.e., in normal DMX transmission. Tipically: frame errors that aren't breaks. Due to the reason that are the most frecuently packets sent through the link, errors will be rapidly discovered and this PID will provide a real mechanism to test the integrity of the link. Thank you to all, regards, Luis Bolster |
February 6th, 2014 | #2 |
Task Group Member
Join Date: Aug 2008
Posts: 375
|
This is something I'd also like to see. In addition to Framing Errors, a "Comms Status Extended" PID could use the SIP Mechanism defined in E1.11 to validate the checksum for NSC packets.
Something like: GET: NSC Packet Count NSC Min Length NSC Max Length NSC Checksum Errors (using the Previous Packet Checksum from the SIP) SIP Packet Count Text Packet Count UTF-8 Packet Count Framing Error Count SET: Reset All Counters Such a mechanism could provide an automatic way to detect data communication link errors. |
Bookmarks |
Thread Tools | Search this Thread |
Display Modes | |
|
|