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 |
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. |
All times are GMT -6. The time now is 10:13 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.