Hi Guys,
Again as a beginner in codesys i come with simple question:
I wanted to open WagoAppPLCModbus documetnation via Library Manager but i get error that says “Opening embedded objects of an unsingned library is not allowed due to security concerns.”
I would like to manage it to work properly. Thx in advance
Documentation for the WagoAppPLCModbus library can be found here:
https://www.wago.com/us/d/15960
Regards,
Mike
But Do you know if i can solve this error ? this is just security setting but how can i turn it off
Unfortunately CODESYS has blocked opening embedded objects of unsigned libraries due to security concerns. This was introduced with v3.5 SP17. You can access the library documentation from the link that @MikePsaltis included.
https://www.wago.com/us/d/15960
Regards,
Stephen
I got this documentation i am busy with it but one more thing:
I bought 879-9000 cummunication module as a gateway from RTU to TCP which wil say that i connected this module with eth cable to at this case CC100 (for test purpose) and A/B to RTU/RS-485 slave. How to configure the ehternet device and then master and server as by server codesys will ip adress for server/slave which i dont have cause it has only slve addres (in this case: 10).
This device supports Modbus TCP & Modbus RTU. Is the AB communicating with Modbus RTU, I thought this defaulted to DF1 protocol.
Thanks. I managed to get it working. I did it with communication configurator. First you need to add ethernet device and when u press browser he wil get the IP from the connected PLC. Then u need to add Master TCP, Slave TCP with IP adress of the gateway, then as last add Serial Slave with Unit ID. There is no need to set up the parity of baudrate 'cause it wil be done by the gateway.
It took me a while because i was testing it with module which was not working properly and i needed to send him back
This link no longer works. Can you please upload the pdf?
1 Like
Unfortunately, I could only get the e!Cockpit library which is almost 99% the same. It should have enough relevant information for integration purposes.
WagoAppPlcModbus.pdf (761.2 KB)
2 Likes
Hello, on my side I was able to get this one:
a2022006-en-WagoAppPlcModbus.pdf (2.3 MB)
Is it the same ?
3 Likes
Interesting. They cover the same library, but your copy is far more detailed than the one I attached. I would go with your copy.
Hi There, again problem with Modbus. I am using WAGO 879-900 to communicate/control Belimo valve (LR-24A-MOD) via modbus RTU. What’s really strange is that i can write to register 16x0000 (SetPoint of the valve) but i can’t read it. same for other registers os i can write to but cannot read any values. Can someone please help me with this one ?
It’s hard to be sure without seeing more code details, but I wonder if calling out the fixed address (i.e. %IW6) rather than the variable name means the compiler isn’t seeing the variable as “used” and therefore not updating?
Try changing the “always update variables” setting in the Modbus I/O Mapping to “enabled 2”
Hi, thx for your feedback. I have mapped the address en also changed setting to “enabled 2“ but without any positive result.
I see more clearly what you are doing now. I have never tried using the “Modbus_Slave_COM_Port” device nested under a “Modbus_TCP_Slave” before. I see that both devices allow you to specify Modbus channels for polling. Do you have the channels setup the same in both logical devices? I’m not sure if it is necessary, but I am guessing the interaction of those two logical devices with each other is the likely source of the issue.
I think so too, I did something simular with a Vega sensor and a Moxxa mgate.
You need to put the words from the serial communication into the words of the modbus TCP.
