I use Linux serial ports to complete data communication, serial interface is configured to parity checking, once every 62 bytes read, I need to know how to judge the data transmission in the process of calibration error happened? Hope the great god grant instruction!

CodePudding user response:

Taobao, a logic analyzer, 20 or 30 and into, do hardware of data transmission, not this thing, really bad debugging, testing the sender and the receiver respectively, which is easy to find the problem, it is easy to find where data is wrong,

CodePudding user response:

I also want to do that, but the customer requires a byte checksum error is 62 bytes of the packets lost all don't, so I just want to know whether the calibration error occurred, thank you for your answer!

CodePudding user response:

refer to 1st floor to the scarecrow to reply:

taobao a logic analyzer, 20 or 30 and into, do hardware of data transmission, not this thing, really bad debugging, testing the sender and the receiver respectively, which is very easy to find the problem, it is easy to find data, are

I also want to do that, but the customer requires a byte checksum error is 62 bytes of the packets lost all don't, so I just want to know whether the calibration error occurred, thank you for your answer!

CodePudding user response:

Try the custom agreement, without the physical check client data, if the data at the sending wrong, how to do?

CodePudding user response:

The

refer to the original poster weixin_42214206 response:

I use Linux serial ports to complete data communication, serial interface is configured to parity checking, once every 62 bytes read, I need to know how to judge the data transmission calibration error occurred in the process? Hope the great god grant instruction!

You said this parity checking is a serial port standard protocol verification (physical), to determine your data error, plus one byte of calibration transfer process,

CodePudding user response:

Communication Mscomm control have a err,

CodePudding user response:

Hardware configuration that parity checking, this is set on the level of transmission, software level can read does this error, parity, overflow of these errors are interrupted, software level can receive messages,