Software Wago I O Check 3 42
Gifford Brickley
I/O modules are not configured using CODESYS, but rather the WAGO I/O-CHECK software. You can obtain a license key and the CD with the software from the following page: -i-o-check/p/759-920 (fee-based). If you do not have a CD drive, you can obtain the download version after your purchase upon request from WAGO Support (sup...@wago.com).
I have a Wago PLC running runtime PFC200 V4.4 from Codesys. After a random amount of time 0 - 5 hours, the PLC goes into stop mode and I lose connection to the PLC from Codesys. I can still ping the PLC, but I can not reconnect to the PLC with Codesys. After power cycle the PLC goes back into run mode and then I can reconnect to it with Codesys.
its not licensing, the license is activated. the log file does not show anything. i will take a screenshot of the log file if it happens again. Keep in mind I need to power cycle the PLC to get connection back. Not sure if the log file is cleared on power cycle.
Hi
I have had the same thing happen - It will be the Runtime shutting down for some reason. In my case it was due to reaching too high cpuload, which causes the runtime to stop. A lot of OPC UA traffic was taxing the CPU too much, so I eventually had to upgrade to a more powerful model.
You can take a look at /tmp/codesyscontrol.log (will not survive a reboot) which may give you some hints, or /var/log/
If the cause is the same, high cpuload, you can check this by typing 'plcload' in the PLC Shell, or watching 'top' in a shell.
thanks for the feedback. My CPU is running average at 90%, and the visu takes around 2-3 seconds to respond. If I load a tab/frame in the visu, the PLC hits 100%. It just baffles me that the logfiles does not survive a reboot, since that is the go to file for debugging things like this....
Check the CODESYSControl.cfg.
Here you can specify where the log output is written to, so you can also let it write to file. Please regard the numbering, because it should be kept in order (0, 1, 2, etc).
Weakaura is as safe as any wow addon. The import strings you get from wago.io are already scanned for possible problems by wago itself, and you can check the custom code on a weak aura before importing it.
LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
For this test, I used the second edition of CEI and I work from the bottom to up. Creating your data model is really easy. You can choose your logical device, logical node, data object, data atribute and choose the prefix and suffix. Example for MMXU :
The tool allows you to export .icd files and import .scd files. It does not include configuration tools for the 61850 substation and that's great! This facilitates the handling of the tool. You can quickly check your control blocks and data set from the LD0 -> LLN0. obvious :-)
There are two ways to subscribe to Goose Wago: First, you choose the control block that you want to listen into .scd (this can be difficult in large projects). For the second option, if like me you create your upstream communication with a 6180 engineering tool, you can directly import the goose link to this receiver via the Ext.Ref tag.
So basically I can start using these addresses without writing any code to transfer these to the S7-300 CPU because this is a slave and the Master is the S7-300 CPU but i have seen in the VFD which are slave they use DPRD_DAT and DPWR_DAT to transfer data .
what S7-300 cfg you have, to which DP interface on Master side you have this Wago connected? Now try compile all download and test that. I had many similar prj also with Siemens ET200L PB DP I/O stations and connected to 315-2DP port via only GSD file, defined I/O and all working perfectly.
Each Profibus-DP slave can occupy a maximum of 244 bytes OUT and 244 bytes IN with the master, so if you use every available I/O per slave you will exchange 1464 bytes input and output. Your CPU has a digital area of 16, 834 (bits)inputs and outputs, and an analog range of 1024 channels (words). So you have plenty of available room for these slaves.
If the HMI is from Siemens, it acts as a Master Class 2 over Profibus, not as a slave, and it manages its data exchange with the CPU 315 outside of these master-slave considerations. If it is not from Siemens, check whether it is a slave on Profibus-DP, then you can add a cyclic number of bytes to the Profibus exchanges, which I doubt will cause problems.
So you can go ahead with this project without too much anxiety. And if you still have doubts, build a hardware configuration with your CPU, central rack I/O modules and Profibus-DP slaves with their own I/O modules.The HWConfig editor will warn you if you try to exceed the amount of data you want to exchange with the master.
It is then your choice whether to use direct I/O addressing for your remote I/O modules (over Profibus-DP), you then use them as if they were part of your central rack; or you can choose SFC15/14 to read each block of data from a slave as a single consistent unit. It makes no difference for I/O modules (for some drives there are requirements to use SFC15/14).
Each Profibus-DP slave can occupy a maximum of 244 bytes OUT and 244 bytes IN with the master, so if you use every available I/O per slave you will exchange 1461 bytes input and output. Your CPU has a digital area of 16, 834 (bits)inputs and outputs, and an analog range of 1024 channels (words). So you have plenty of available room for these slaves.
b1e95dc632