PLC connect communicate with Masterpact Schneider
Now I have an other PLC connect installed in a virtual machine on a 800XA Ver.6.0. And then, I am not able to establish the same communication !
Is there any difference beetwin the 2 versions?
Answers
There is no feature degradation in PLC Connect from SV 5.0 to SV 6.0. In fact, in SV 6.0, there are a lot of new functionalities on top of existing functionalities in SV 5.0.
So, you are using Modbus TCP/IP protocol for communicating Masterpact Schneider to PLC Connect.
One problem with Schneider modules is that they won’t respond to the query if a single register is polled. I would ask you to address 2 registers in PLC Connect. Eg. instead of using the address HR40017, use address as HRA016,REAL which addresses 2 registers to access floating point values. i.e., it polls 40016 and 40017.
If this doesn’t help, further troubleshooting would be required.
What Communication Parameters have you set?
What address have you set?
What Quality do you get when you subscribe for live data?
Do you get good communication if you use some 3 rd party software like ModScan?
Did you try incremental deploy? (Perform Deploy while SHIFT key is pressed).
Refer Modbus log file (PlcModbusTCPDriver) for errors in PLC Connect Log Files folder from the following Location:- C:\OperateITDataXXX\AdsServer\Service Group Data.
You can share the PLC Connect log files folder for analysis, or contact your Regional Support Center for assistance.
Add new comment