CODESYS Control Win SL Soft PLC

Fieldbus Integration: From Configuration to Troubleshooting

CODESYS Control Win SL supports multiple mainstream fieldbuses from the factory at no additional cost (some protocols require installation of Npcap). The following is the complete support list and configuration points:

The protocol role requires Npcap. Typical application common faults

CANopen manager/device is not distributed I/O, drive control baud rate is inconsistent, terminal resistance is missing

EtherCAT main station is motion control, high-speed IO network card is not compatible (requires Intel PRO/1000 series)

EtherNet/IP scanner/adapter communication with Rockwell PLC package timeout set improperly

J1939 device has no vehicle/engine data address conflict

Modbus TCP master/slave is a universal SCADA connection port 502 intercepted by a firewall

Modbus serial master/slave, old instrument level conversion error (RS232/485)

PROFIBUS DP master station, Siemens system integration, GSD file missing, terminal resistance error

PROFINET controller/device does not match Siemens I/O exchange data device name

Sercos III main station is a high-end motion control ring network disconnection

4.1 EtherCAT Configuration Troubleshooting Example

Phenomenon: After the EtherCAT master station scans, some slave stations display abnormal "Op" status or experience periodic communication interruptions.

Steps:

Confirm that the Npcap driver has been installed correctly and that the network adapter is not occupied by other applications (such as Wireshark).

In the CODESYS device tree, right-click on the EtherCAT master → "Append Device" → select the correct slave XML description file (provided by the slave vendor).

Check physical wiring: Use a cross test wire to connect the PC to the first slave station and observe the slave station indicator light. If the LED "L/A" does not flash, try replacing the network card.

Network card compatibility: CODESYS Control Win SL has poor support for Realtek network cards (prone to frame loss), and it is recommended to use Intel PRO/1000 or PCIe network cards based on Intel chips.

Set task cycle: EtherCAT data refresh should run in a separate high priority task, typically with a cycle of 1-4ms. If the task cycle jitter exceeds ± 20%, the Windows timer resolution needs to be increased (using timeBeginPeriod call or automatically optimized through CODESYS).

4.2 PROFINET device name malfunction

PROFINET IO devices are identified by device names rather than IP addresses. If CI871 or third-party slave cannot connect:

Use PST (Primary Setup Tool) or CODESYS's built-in "PROFINET Device Scan" function to read the current device name.

In the CODESYS configuration, set the "Device Name" to be exactly the same as the slave entity (case sensitive).

If the factory settings are restored from the site, the name needs to be reassigned.

4.3 Modbus TCP connection rejected

In most cases, it is due to the Windows Firewall blocking port 502. Solution:

Add an inbound rule in the control panel for 'CODESYS Control Win SL.exe' to allow TCP port 502.

Or temporarily shut down the firewall for testing (non production environments only).

License management: Avoid two-hour interruptions

5.1 License Types

CODESYS Control Win SL adopts a single device license and can be bound to:

Software container: Bind with the hardware fingerprint (network card MAC, hard disk serial number, motherboard UUID) of the target PC, permanently valid. After replacing the hard drive or network card, reactivation is required.

CODESYS Key (USB hardware dongle): Simply plug it into any PC for easy mobility and temporary replacement.

Order information: Product number 2302000003, purchased through CODESYS Store.

5.2 Activation Process

Install the runtime system on the target PC and obtain the 'Container ID' (displayed in the CODESYS Control Win SL control panel).

Log in to the CODESYS Store, enter the activation code obtained at the time of purchase, and submit the container ID.

Download the license file (. crypto) and import it into the runtime system (via web interface or local file).

Restart the runtime service and confirm that the 'License Info' display is valid.

5.3 Common License Malfunctions

Possible causes and solutions for the fault phenomenon

Still showing that the demo mode license file has not been loaded. Check if the file path contains Chinese or spaces; Re import using the 'Manage License' tool

After activation, it prompts "mismatched" hardware fingerprint change (such as replacing network card). Contact CODESYS support to regenerate container ID

USB dongle not recognized, missing driver installation CODESYS Key driver (located in installation directory Drivers)

The license validity period is shorter than expected. If you purchase a subscription version (annual fee), renew it annually, or purchase a permanent version

Tip: When deploying redundant systems, it is necessary to purchase independent licenses for each PC (redundancy options require additional fees, see the next section).

Product option: Expand the boundaries of soft PLC

CODESYS Control Win SL offers multiple charging options, significantly expanding its application scope. Here are the four most commonly used: