Post by rmaas on Fieldbus has lost synchronicity ^{CODESYS Forge talk (Post)}
Hi, On a gantry system with 2 axis i am getting the following error: SMC_DI_FIELDBUS_LOST_SYNCRONICITY This happens random, sometimes it happens every 5 minutes and sometimes no error for 2 hours... The Setup: - Using codesys 3.5 SP20 with all latest libs... - Kontron AL Pi-Tron CM4 with Preempt realtime patch (Raspberry Pi 4) - Codesys runtime 4.11.0.0 (single core) - CODESYS Control for Raspberry Pi SL licensed - Softmotion + CNC + Robotics licensed - 2x Leadshine EL8-EC400 servo drives - Axis group for a 2-axis T-Gantry Ethercat network wiring: Ethercat master softmotion -> Beckhoff EK1100 -> Servo drive #1 -> Servo drive #2 Ethercat Cycle time = 4ms Max Jitter = 140~150 What i have tried so far: - changed the sync offset from 20% to 30% - changed ethercat task priority from 1 to 0 Running tasks: - Ethercat tast: Prio = 0, Interval = 4ms - Main task: Prio = 1, Interval = 8ms - Visu task: Prio = 31, Interval = 100ms - Softmotion planning task: Prio = 15, Freewheeling - 3 other default tasks that were created by AC_Persist Motion fb's are called in the ethercat task... Does anyone have an idea how to fix this? Any help is greatly appreciated!
Last updated: 2024-04-11

Post by xnoop on MBTCP Slave configuration ^{CODESYS Forge talk (Post)}
Hello, I use Codesys 3.5 SP18 Patch 4 (64 bit) My Codesys project is composed of several dozen of Modbus TCP Slaves. I want to configure each of them by define : - Modbus TCP Slave Configuration : Name, IPAddress, port - Channels - Mapping I can't afford to configure manually and I need to find automatic way What possibilities does the Codesys offer? 1. I know it possible to use python script to create Modbus TCP Master and Slave. But I don't find anyway to create Channels and Mapping through the API 2. I 've tested to set mapping with file.csv on a Modbus Tcp Slave, but no way to import channels definition from file 3. I 've tried to use PLCOpenXml file. For example I 've create a project with an Ethernet device. I've exported it in PlcOpenXml file. After delete the Ethernet device, I've imported the PlcOpenXml file without success. I've tried the same by creating Modbus TCP Slave. Could you help me to find to good way ? Thanks
Last updated: 2024-06-19

Post by megasilver on Cannot download program to CR1074 – Version mismatch error ^{CODESYS Forge talk (Post)}
Hello, I am having a problem downloading my application to an ifm CR1074 using CODESYS. When I try to download the program to the controller, I get the following errors: [FATAL ERROR] Version mismatch at: 'KEYBOARD_SET_MAPPING' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'SYSCFG_SPLASH_SET_SPLASH_SCREEN_VISIBLE' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'SYSTEM_IO_BACKLIGHT_SET_CURRENT_BACKLIGHT_BLOCKING' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'SYSTEM_IO_BACKLIGHT_SET_CURRENT_BACKLIGHT' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'KEYBOARD_RESET_LEDS_BLOCKING' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'KEYBOARD_SET_LED_COLOR' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 [FATAL ERROR] Version mismatch at: 'SYSCFG_DEVINFO_GET_KEYBOARDS_INFO' Requested version: 2.0.0.12 Implemented version: 3.4.0.0 The controller is running an OS version that should be compatible with CODESYS 3.5 SP16, and I am using the latest available ifm/ecomatDisplay package for this OS version. Therefore, I do not think this is simply a CODESYS or OS compatibility issue. It looks like the application expects system functions with version 2.0.0.12, while the controller implements version 3.4.0.0. Could this be caused by an incorrect or outdated library, device description, package installation, or a mismatch between the libraries used in the project and the libraries installed on the CR1074? What would be the correct way to identify which component is requesting version 2.0.0.12 and how can I resolve this version mismatch? Thank you for your help.
Last updated: 2026-08-21

Post by acc00 on Redundancy Codesys Runtime, Synchronization ^{CODESYS Forge talk (Post)}
Hi, I’m currently testing the Codesys Redundancy application with 2 Raspberry Pi, with the idea is of using in my project 2 Wago PFC200 and 1 Ethercat Master with 2 Remote IO. After I configure the redundancy, and one Pi is Active and the other is Passive, if I disconnect the Ethernet cable of the Active, the Passive become Standalone, which is good, but the problem is the following: -When I recover the Ethernet connection, both stay Standalone. They will NOT Sync until I do it manually in the Codesys environment. How to make the synchronization automatically? -If both Pi/PLC stays Standalone, who is managing the IO? (Ethercat and Serial) I have done a test with an Modbus Slave, where I am sending a counter that increase every second. And I see that when both PLC are standalone, they both keep an active connection with the Slave, and both write values. This does not seem good, since according to this in my project both PLC would try to control the IO at the same time. Note: The Codesys have an option (greyed out, not possible to select) which says “Auto Sync”. What is the purpose, and why I’m not able to select it? I'm using Codesys Control for Rapsberry Pi 64SL Runtime in my test environment (2xRaspberry Pi 4), with the idea of using Codesys Control PFC 200 Runtime in my project (2xWago PFC200 and 1 Ethercat Master with 2x Wago 750-354 Ethercat Fieldbus Coupler). Using the last Codesys 3.5 version (SP19 PAtch 5). I'd appreciate a lot any help on this questions!
Last updated: 2024-01-22

Symbol Configuration ^{CODESYS Forge talk (Thread)}
Symbol Configuration
Last updated: 2023-08-29

Loading a file ^{CODESYS Forge talk (Thread)}
Loading a file
Last updated: 2016-03-14

PLCHander header files ^{CODESYS Forge talk (Thread)}
PLCHander header files
Last updated: 2010-02-23

Library creation error ^{CODESYS Forge talk (Thread)}
Library creation error
Last updated: 2017-11-06

Dynamic function call ^{CODESYS Forge talk (Thread)}
Dynamic function call
Last updated: 2007-06-29

Numerical Keypad ^{CODESYS Forge talk (Thread)}
Numerical Keypad
Last updated: 2013-05-23

Bug Please Fix!!!! ^{CODESYS Forge talk (Thread)}
Bug Please Fix!!!!
Last updated: 2009-10-10

Button ^{CODESYS Forge talk (Thread)}
Button
Last updated: 2011-06-11

void pointer ^{CODESYS Forge talk (Thread)}
void pointer
Last updated: 2014-08-25

webvisu ^{CODESYS Forge talk (Thread)}
webvisu
Last updated: 2012-06-13

Doubt in ADR ^{CODESYS Forge talk (Thread)}
Doubt in ADR
Last updated: 2009-03-17

PLCHandler example request ^{CODESYS Forge talk (Thread)}
PLCHandler example request
Last updated: 2009-04-13

Gateway protocol ^{CODESYS Forge talk (Thread)}
Gateway protocol
Last updated: 2019-02-04

General Data Transmission ^{CODESYS Forge talk (Thread)}
General Data Transmission
Last updated: 2012-08-05

Signal generator RMP_B ^{CODESYS Forge talk (Thread)}
Signal generator RMP_B
Last updated: 2011-01-31

Frequency Measurement ^{CODESYS Forge talk (Thread)}
Frequency Measurement
Last updated: 2018-07-10

private messages ^{CODESYS Forge talk (Thread)}
private messages
Last updated: 2012-06-08

MODBUS TCP Slave ^{CODESYS Forge talk (Thread)}
MODBUS TCP Slave
Last updated: 2017-10-31

Version 2.3.9.50 changes ^{CODESYS Forge talk (Thread)}
Version 2.3.9.50 changes
Last updated: 2016-06-27

Printing Error ^{CODESYS Forge talk (Thread)}
Printing Error
Last updated: 2014-11-04

Alarmtable, colorencoding ^{CODESYS Forge talk (Thread)}
Alarmtable, colorencoding
Last updated: 2016-03-17

Sort by relevance or date