new PID: comms_status_sc0 - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · February 6th, 2014

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.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

February 6th, 2014	#1
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	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.