Getting Started with Codesys v3.5 and Wago PFC200 (750-8212)

 

 

Step 1: Search for Codesys v3.5 in any search engine.

Step 2: When you click on the link, it redirects you to following page. Click on the download button. It will redirect you to a new webpage with Codesys v 3.5 descriptions.

 

 

Step 3: Click on Open Page link, which open a new webpage.

Step 4: User can download the software along with dependencies as a bundle download or selecting individual dependency as per his/her requirement.

Step 5: Click on Codesys 3.5 setup file to initiate installation.

Once installation is complete, launch the Codesys to check if installation is correct.

After this, you have to install Wago Licensing, Wago Solution Builder, Wago codesys Download Server, Wago Device and Libraries which are downloaded in Step 4 as a bundle.

Step 6: Again Launch Codesys 3. Create a New Project from Basic Operations.

Create a standard project and then choose suitable Name and Location where you want to save the project file.

Once done, you have to select the Device and Programming Language from drop down menu.

          

I have selected 750-8212 as my PLC device and Ladder Logic Diagram as my programming language. You will see the device list only if Wago Device and Libraries are properly installed.

 

Selected target system is different from the connected device

Once you connect a Wago PFC 750-8212 device with PC and develop a ladder program, you will have to download the program into the PLC.

In some cases, it may display “selected target system is different from the connected device” error message. This happens due to firmware incompatibility between the codesys wago device library and PLC firmware. The user will have to update the firmware of the device in that case.

 

 

PLC Firmware update

In the softwares downloaded in Step-1, you will find Firmware also which needs to be uploaded to the PLC. The firmware can be uploaded using Wagoupload. WAGOupload is a stand-alone PC software for transferring, backing up and restoring PLC applications on WAGO 750 Series controllers.

Modbus and OPC comparison Table

 

Comparison between Modbus and OPC

Feature	Modbus	OPC (OLE for Process Control)
Definition	Communication protocol	Communication protocol and data exchange standard
Protocol Type	Serial and Ethernet-based	Can use various protocols, including TCP/IP
Topology	Master/Slave	Client/Server and Publish/Subscribe
Data Types	Limited data types (e.g., integers, floats)	Extensive data types (e.g., integers, floats, strings)
Complexity	Simple and lightweight	More complex and feature-rich
Flexibility	Limited flexibility in terms of data format	Highly flexible, supports complex data structures
Scalability	Suitable for small to medium-scale systems	Suitable for small to large-scale systems
Integration	Widely used in industrial automation	Common in industrial automation, more versatile
Interoperability	Interoperability may be limited	Emphasizes interoperability, supports multiple platforms
Vendor Neutrality	Generally vendor-neutral	Allows for vendor-specific implementations
Security	Basic security features	OPC UA provides advanced security features
Standards	Open standard, but various versions exist	Open standard with defined specifications (OPC UA)
Popular Versions	Modbus RTU, Modbus TCP	OPC DA (Data Access), OPC HDA (Historical Data Access), OPC UA (Unified Architecture)
Usage	Common in simple industrial systems	Used in a wide range of industrial automation scenarios

This table provides a high-level overview, and the choice between Modbus and OPC depends on specific project requirements and considerations.