Hi,
I am trying to communicate with a GE Micro-Versamax PLC.
My configuration is as follows:
- Digi SP one connected to the RS-485 port of the PLC
- Kepware Server using Modbus driver with "ethernet encopsulation" enabled
I am trying to communicate with the PLC and get most of my Tags defined in Kepware working properly.
Some of the Tags however does not work properly (all of them are registers). Their data is not updated and their condition is BAD.
When trying to diagnose the problem using Kepware diagnostic tool I receive the following line when trying to retrieve data from one of the bad registers:
17/12/2008 18:48:33:693 TX: 01 03 00 69 00 01 54 16
17/12/2008 18:48:33:771 RX: 01 03 02 7F FF FF D8 34
Which means the Kepware requests a single register (16 bit) starting at address 0x69. The answer though is 24 bit long (one and a half registers !?!).
This happens for all read requests for this specific register (and quite a few of its friends...).
When trying to use an HMI software like Cimplicity, I receive no error and the data is displayed perfectly.
I also tried using Modscan utility and got these results for the same register aforementioned:
TX: 01 03 00 69 00 01 54 16
RX: 01 03 02 7f ff d8 34
Which means the data I receive in Kepware is somehow distorted...
Anyone has a clue or experienced this kind of behaviour?
Thanks in advance,
Assaf
I am trying to communicate with a GE Micro-Versamax PLC.
My configuration is as follows:
- Digi SP one connected to the RS-485 port of the PLC
- Kepware Server using Modbus driver with "ethernet encopsulation" enabled
I am trying to communicate with the PLC and get most of my Tags defined in Kepware working properly.
Some of the Tags however does not work properly (all of them are registers). Their data is not updated and their condition is BAD.
When trying to diagnose the problem using Kepware diagnostic tool I receive the following line when trying to retrieve data from one of the bad registers:
17/12/2008 18:48:33:693 TX: 01 03 00 69 00 01 54 16
17/12/2008 18:48:33:771 RX: 01 03 02 7F FF FF D8 34
Which means the Kepware requests a single register (16 bit) starting at address 0x69. The answer though is 24 bit long (one and a half registers !?!).
This happens for all read requests for this specific register (and quite a few of its friends...).
When trying to use an HMI software like Cimplicity, I receive no error and the data is displayed perfectly.
I also tried using Modscan utility and got these results for the same register aforementioned:
TX: 01 03 00 69 00 01 54 16
RX: 01 03 02 7f ff d8 34
Which means the data I receive in Kepware is somehow distorted...
Anyone has a clue or experienced this kind of behaviour?
Thanks in advance,
Assaf