Let's decode Post #23, where your software is trying to read N150:321.
10 02 01 00 0F 00 B1 00 A2 02 96 89 41 00 10 03
10 02 Start of Transmission
01 Destination
00 Source
0F Command 0x0F
00 Status
B1 00 TNSW
A2 Function 0xA2
02 Data size = 2 bytes
96 Data File Number = 0x96 hex = 150 decimal
89 Data File Type = Integer
41 Data File Element = 0x41 hex = 65 decimal
00 Data File Sub-Element
10 03 End of Transmission
So there's a problem looking us in the eye. We think we're requesting N150:321, and the actual command going out over the wire is reading N150:65.
What do the values 321 and 65 have in common ?
321 decimal = 0x141 hex
65 decimal = 0x41 hex
It looks to be that the Automated Solutions software is converting the decimal value for the Element Number, but not accounting for the possibility that it's two bytes, and just taking the first byte.
So we know what's going wrong with some of your data reads.
The first unexplained issue is the Elements between 251 and 255 not being read correctly.
Could you capture the AS software reading N150: 251, 252, 253, 254, 255 ?
You guys are moving too fast for me today.... I'll go look at the Write captures now.