T
As noted above I can not get any answer back from the analyzer. This is the third analyzer/Modbus connection I have worked with in the last 6 months and each is different (first was with Provox DCS and second an old Taylor system). Using a protocol analyzer I have monitered the DCS request and also using our analyzer communication software repeated the request. Nothing is different except for the CRC.
Data request
05 03 00 22 00 06
Analyzer address 05
Read holding register 03
Address start 35 - 00 22
Number of blocks 6 - 00 06
Rosemount CRC - 24 06 or 64 06 or 24 46 (switchs between the three with no apparent pattern)
Analyzer software CRC - 64 46
Also when we change the configuration parity it changes the data request and I thought that this would have nothing to do with the data request string??? DCS has parity settings of none, even, odd, mark or space. Space is the only setting that will generate the correct 05 03 00 22 00 06. None which is my normal default gives 85 83 81 ..... Ideas on this??
Any idea why the CRC would not match up when the rest of the string is the same? I am limited in my pc language skills but continue to learn more and more each day, so be kind to me.
Troy
Data request
05 03 00 22 00 06
Analyzer address 05
Read holding register 03
Address start 35 - 00 22
Number of blocks 6 - 00 06
Rosemount CRC - 24 06 or 64 06 or 24 46 (switchs between the three with no apparent pattern)
Analyzer software CRC - 64 46
Also when we change the configuration parity it changes the data request and I thought that this would have nothing to do with the data request string??? DCS has parity settings of none, even, odd, mark or space. Space is the only setting that will generate the correct 05 03 00 22 00 06. None which is my normal default gives 85 83 81 ..... Ideas on this??
Any idea why the CRC would not match up when the rest of the string is the same? I am limited in my pc language skills but continue to learn more and more each day, so be kind to me.
Troy