AVS Forum Addicted Member
Join Date: Sep 2006
Mentioned: 56 Post(s)
Tagged: 0 Thread(s)
Quoted: 2993 Post(s)
I don't know what Integration Designer or RS232 Library Manager is, but that document has all the info anyone would need to write code to communicate with that device.
Basically take the Tx format and substitute the data values from the tables to build a command. I can't quite tell how the checksum is calculated from that document, but it's typically all the bytes they list XOR'd together.
I'm not sure how novice you are, but you'll need a pretty good understanding of binary, hex and boolean math to program any RS232 stuff from scratch. I typically take the contents of a spec like you have and put it in a spreadsheet, and build some formulas for the checksum byte so I know what my command strings should look like, so I can check my code using Hyperterminal on a loopback. Once I'm certain my program is sending the strings according to spec, I test on the actual device. I guess you could skip the Hyperterminal test if you wanted.
The hardest part for me is not sending commands but receiving them. So if you want feedback, the code around that is generally more complex since you have to detect the events, read your comm buffer, then parse and decode the data, then display it on your controlling device. That can be a significant coding effort.