E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM General Implementation Discussion

RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product.

Thread Tools Search this Thread Display Modes
Old February 5th, 2014   #1
Junior Member
Join Date: Feb 2010
Posts: 7
Default new PID: comms_status_sc0

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
luiscolo is offline   Reply With Quote
Old February 6th, 2014   #2
Task Group Member
Join Date: Aug 2008
Posts: 369

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:
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

Reset All Counters

Such a mechanism could provide an automatic way to detect data communication link errors.
ericthegeek is offline   Reply With Quote


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -6. The time now is 02:40 AM.

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