Abel_Souza

My coworkers told me that this PLC did not have access authorization, but we need input PC IP on PLC to communicate, so it have access authorization setting. Now using IP setting configured on PLC its working well. Thanks!

Talking with my coworkers, this PLC don't have an access control list. Code working if a use two PCs and modbus examples on LabVIEW as a modbus server. When Ido this I can read with my code. Cheking with Wireshark, with PLC, the communication was disconnected before transfer any modbus packet. When running with two PCs I could see modbus packets on wireshark. My challage is how identify what cause this disconnection.

LabVIEW 2016 Modbus Communication with a PLC Siemens SIMATIC ET 200SP Windows 7 Ultimate Hi, When I run my code it return error 66 at Read Holding Registers function. I ran this code as a VI on the development virtual machine and as a *.exe on real machine, but received the same error. Try in another computer and receive the same error. As PLC code was developer by other programmer I ask him if this communication was working on his machine, he showed me a LAbVIEW code running with Modbus communication with the same PLC. He was using a LabVIEW 2013 with old Modbus Library, but I had taken his code and ran on my PC with LV 2016 and receive the same error on MB Ethernet MAster Query Read Holding Registers(Poly).vi. Also generate an exe file and run on my real machine and still receiving error 66. In all scenarios I can ping PLC and receive answers, but cannot read or write any data with LabVIEW. First picture is my code with LV 2016 VIs. Second picture is error message. Third one is the other programmer code with old Modbus Library. On the first code, if I remove Read Holding Registers VI and connct wires directly or put a property node to set any property it runs without errors. If change this function for any other modbus function return error 66. Any idea what I am doing wrong? Thanks in advance! ni_support.zip Comunicação CLP.vi Main_MB_2.vi