Modbus TCP Driver Failure in 3.84 & 3.85

[DougLyons]

Archie,

I have not been able to make the ModbusTcpCom driver work with only a Digital Panel Meter for the 40001 register in version 3.84 or 3.85. I also tested registers 40002-40005 and these failed the same way.

The message at the top of the display shows the following:

INVALID VALUE RETURNED!Illegal Modbus Address

This happens regardless of what value I put into the registers.

Thanks for any help that you can provide.

[Archie]

The ModbusTCP driver was completely re-written in version 3.84, so I'm sure some bugs crept in. I have been testing with a Modbus simulator running on the same PC and it has been working. I will setup the simulator on another PC to see if it becomes a problem when running over a network.

[DougLyons]

Archie,

My testing was done using Modsim32 by Win-Tech Software on the same PC as the Advanced HMI.
The error has always been "Illegal Modbus Address" when using the DigitalPanelMeter.
For the BasicIndicator there mostly is no error, but the Bit values return incorrectly.
I am using Windows 7 in 64-bit mode.

Thanks very much.

[Archie]

I tried some testing with ModSim64 and I do get problems with version 3.85. I will go ahead and post version 3.86 because seems to be working. The difference is that 3.86 shares some common classes between ModbusRTU and ModbusTCP. It also ha sthe functionality of bit level addressing (e.g. 40001.0)

[Archie]

Version 3.86 is now posted. Try that version to see if it works.

[DougLyons]

Archie,

I have just tested the 3.86 version with only a ModbusTcpCom and DigitalPanelMeter with no success.
The error shows "Com Fail -- 20". I have attached an example of what I see.
I only tested address 40001. The attachment is named "3.84", but you can see the header shows "v3.86".

Thanks.

[Archie]

When I tried 40001 with ModSim64, it wouldn't work , but 40100 does

I normally do my testing with ModRSim  it seems easier to use and the data stream view is formatted better.

[Archie]

Are you using 127.0.0.1 for the IP address?

[DougLyons]

Archie,

I am using the IP address of the Ethernet connection on my Motherboard which is 172.16.52.111.
Normally I do not use the 127.0.0.1 at all.
I had just plugged my laptop into my docking station when I was having the problems though.
Now all of the above items are working just fine, so maybe I had something wrong.
It would be nice to get the bits working for the ModbusTcpCom driver though.
I have done some testing in 3.86 and it seems that I can use .0 and .1 but not any other bits.

I have attached a screen shot of what I am seeing when I try and use bit 2.

Thanks very much for your continued support.

[Archie]

I am using the IP address of the Ethernet connection on my Motherboard which is 172.16.52.111.
Normally I do not use the 127.0.0.1 at all.

This 127.0.0.1 would only be used when running the simulator on the same PC as the HMI, such as ModSim64 or ModRSim