Fatal Error when installing Wago CoDeSys version V2.3.9.61 ^{CODESYS Forge talk (Thread)}
Fatal Error when installing Wago CoDeSys version V2.3.9.61
Last updated: 2022-11-07

CoDeSys 2.3.9.11 - Pointers in Visualization Placeholders ^{CODESYS Forge talk (Thread)}
CoDeSys 2.3.9.11 - Pointers in Visualization Placeholders
Last updated: 2010-03-11

Accessing an External File from CoDeSys ^{CODESYS Forge talk (Thread)}
Accessing an External File from CoDeSys
Last updated: 2007-06-21

How to add a new device to CodeSys ^{CODESYS Forge talk (Thread)}
How to add a new device to CodeSys
Last updated: 2012-12-12

Uniop Etop 500 series programming with Codesys ^{CODESYS Forge talk (Thread)}
Uniop Etop 500 series programming with Codesys
Last updated: 2014-11-13

how to read a text file using codesys.. ^{CODESYS Forge talk (Thread)}
how to read a text file using codesys..
Last updated: 2007-06-25

codesys with epec controller and J1939 can communication ^{CODESYS Forge talk (Thread)}
codesys with epec controller and J1939 can communication
Last updated: 2009-12-10

CoDeSys Soft-PLC PLCWinNT for Vr 3.5 ^{CODESYS Forge talk (Thread)}
CoDeSys Soft-PLC PLCWinNT for Vr 3.5
Last updated: 2019-10-24

Use time of day with codesys ^{CODESYS Forge talk (Thread)}
Use time of day with codesys
Last updated: 2009-10-22

CANopen and CoDeSys Ver 2.3.8.4 memory managment ^{CODESYS Forge talk (Thread)}
CANopen and CoDeSys Ver 2.3.8.4 memory managment
Last updated: 2008-05-07

Moeller XV progeammer on Xsoft Codesys in Canada ^{CODESYS Forge talk (Thread)}
Moeller XV progeammer on Xsoft Codesys in Canada
Last updated: 2011-11-16

How to communicate 2 pcs that are using CODESYS ^{CODESYS Forge talk (Thread)}
How to communicate 2 pcs that are using CODESYS
Last updated: 2024-05-06

CANopen PDO Issue with Pressure Sensor in Codesys ^{CODESYS Forge talk (Thread)}
CANopen PDO Issue with Pressure Sensor in Codesys
Last updated: 2024-10-22

Noob in Codesys and IFM CR7506...Output stay active ^{CODESYS Forge talk (Thread)}
Noob in Codesys and IFM CR7506...Output stay active
Last updated: 2024-10-22

Post by fontrap on cmDongle Raspberry Pi issue ^{CODESYS Forge talk (Post)}
Hello mates, I'm working with CODESYS V3.5 SP20 on a Raspberry Pi and I use "Raspberry Pi MC SL" as device on the project. I've installed the Control Standard L (multicore) license on a Wibu System usb-Dongle (cmStick/4.50) that already had another license from another vendor. I follow the online activation procedure from CODESYS documentation. Raspberry Pi has already CodeMeter installed for the other license. When I plugin the dongle on Raspberry and start the Runtime from Raspberry Pi Update in CODESYS I receive the message that I'm on Demo mode because the license is missing. I double checked that the license is activated in the dongle, through the WebAdmin of CodeMeter and the second license runs properly without any issue. I have already try to change the dongle from HID to MSD device and backward but the the Runtime cannot recognize the Dongle. I have also try to stop and start the Runtime through CODESYS without success. Is there anything else I can do to fix this issue?
Last updated: 2024-04-22

Post by eurowolf on SoftMotionLight Lizenz nach Programmupdate weg ^{CODESYS Forge talk (Post)}
Hallo, auf einer Sabo MKS855.20 habe ich die SoftMotionLight-Lizenz installiert. Zur Programmierung nutze ich V3.5 SP16.0. Die im Projekt verwendete SML 4.7.0.0, SML_Drive_CAN_GenericDSP42 3.5.7.0, CANopen_Manager_Softmotion 3.5.16.0. In der Regel habe ich keine Probleme mit der SoftMotionLight, nur bei dieser Anlage ist es mir jetzt zum Zweiten mal passiert, das ich ein Programmupdate einspiele und die SML in den Demo-Modus wechselt. Die Lizenz ist doch auf der SPS gespeichert, warum wird dann behauptet, dass die SML im Demo-Modus arbeitet. Da ich z. Zt. beim Kunden vor Ort bin und dieser sich im Ausland befindet, benötige ich kurzfristig eine Lösung. Auf E-Mails bekomme ich leider keine Rückmeldung.
Last updated: 2024-05-14

Post by rossanoparis on Upgrading CODESYS runtime from v4.7 to v4.9 using a bash script leads to lose the licences stored in the soft container ^{CODESYS Forge talk (Post)}
System information - Controller: KUNBUS RevPi CONNECT-S - OS: Linux buster 32bit 5.10.103-rt62-v7l #1 SMP PREEMPT_RT armv7l GNU/Linux - CODESYS v3.5 SP19 Patch 2 I'm facing a problem related to codesys licences using a procedure based on a bash script. Such bash script detect the presence of new .deb files and install them on system. My automation solution don't allow to be maintained by dedicated personal, thus even the CODESYS runtime SW must be installed using an "automatic" procedure instead of using the CODESYS tool. remark I've been using the following procedure since the runtime v4.5 without any issue. Before installing the new runtime packages, I need to copy the file CODESYSControl_User.cfg (here attached) because of new section which is necessary to add in order to allow some folders to be written by CODESYS runtime v4.9 Up to now, this has been unnecessary, this is the main difference between my previos bash file and the new one. remark If I skip this action, everythings goes fine, but my CODESYS application can't work as it needs to access some folders on controller's file system. Process - Before the procedure: the licenses are OK (see attached file lic-01.png) - After the procedure: the new CODESYS runtime version is correctly installed, but the software container with v1.19 and all licences disappear (see attached file lic-02.png) This is the synthetic content of bash script I'm using. # Stop runtime sudo service codesyscontrol stop sudo service codesysedge stop # Move the new CODESYSControl_User.cfg file # New configuraton with folders declared sudo mv -f CODESYSControl_User.cfg /etc # Install runtime package echo N | sudo apt-get install -y --allow-downgrades codesyscontrol_raspberry_4.9.0.0_armhf.deb # Install edge gateway package echo N | sudo apt-get install -y --allow-downgrades codesysedge_edgearmhf_4.9.0.0_armhf.deb # Reboot controller sudo reboot Thanks in advance
Last updated: 2023-09-19

Post by rossanoparis on After un upgrade of "CODESYS Control for Raspberry Pi MC SL" from v4.7 to v4.9 SysFileOpen function stopped working ^{CODESYS Forge talk (Post)}
Hello at all. After un upgrade of "CODESYS Control for Raspberry Pi MC SL" from v4.7 to v4.9 SysFileOpen function stopped working. I'm not able to read or write files from the PLC application. Before this upgrade all worked fine. I've read this thread [ https://forge.codesys.com/forge/talk/Engineering/thread/3da9ded84e/ ] Despite I followed that indications I couldn't get my code working again. Perhaps I'm missing something or I didn't understand how to use placeholders at all. Is there a different syntax to use for "SysFileOpen" in order to use placeholders? Thanks in advance for your help. Information Compiler: CODESYS V3.5 SP19 Patch 2 Runtime: codesyscontrol 4.9.0 HW: KUNBUS RevPi Connect S Below the paths I want to access (The entire CODESYSControl_User.cfg file is attached) [SysFile] PlaceholderFilePath.1=/home/pi/hpca/bin, $hpcabin$ PlaceholderFilePath.2=/home/pi/hpca/cfg, $hpcacfg$ PlaceholderFilePath.3=/home/pi/hpca/logs, $hpcalogs$ PlaceholderFilePath.4=/home/pi/hpca/resources, $hpcares$
Last updated: 2023-08-22

Post by ewi04 on Git with visu ^{CODESYS Forge talk (Post)}
Hi, I have several problems with the git extension. Situation: I am working with Codesys v3.5 SP19 Patch 1 and Git V1.2.1.0. The remote repository is GitLab Community Edition v16.1.2. I am working on a project with one other person. Problems: 1: After each start of Codesys all of the visu pages are marked as modified. So we have to discard all changes first. Otherwise the history is not clean and the merge request becomes more complex. I tested it with a new project and only local. I made the observation, that a page is not marked as modified when it is committed a second time (after a restart of codesys). But this is necessary after every change of a page. However, since we are working in a team, it seems we are playing ping-pong and so all pages are marked as modified on each startup. 2: Each image pool causes a parent child conflict. Also in my local project. The only solution that I have found, is to ignore the issue. Does anyone have the same problems? I think it looks more like bugs. Thanks ewi04
Last updated: 2023-11-22

Post by arundara on Variable Sync Issue In Soft Plc Redundancy ^{CODESYS Forge talk (Post)}
Hello, I was trying to create a redundancy POC for our application where we read data from few modbus tcp devices. As there is a limitaion that modbus tcp device support only for single master device, we wanted to test how the variable sync happens in redundancy mode. For that i have used the redundancy sample code added a variable "b" under a condition. What i observed was while active controller is running, if passive controller is powerup, passive controller is able to sync all the data configured for redundacny. But after that the variable data which resided under a condition is not synching from active to passive controller. I have attached the image where i have highlighter the variable. Can some help me to understand how redundacny work in codesys soft plc and if there is a solution to sync variable which are under condition, please explain the same or suggestion to achieve the same. Hardware - Raspberry Pi (2 qty) Redundancy licence used - yes in both controllers. Codesys runtime - 4.9.0.0 Codesys software version - V3.5 SP19 if i have posted this question in wrong section, please do let me know in whcih section i have to post this question.
Last updated: 2023-12-01

Post by anlebr on Codesys Communication Manger - Required information model version exists in the model repository but is not found ^{CODESYS Forge talk (Post)}
Hi I am trying use the Codesys Communication Manager to set up an Opc ua server with a custom information model. As a start I am using the Boiler model available on Opc foundations github page. I am testing with a Wago CC100 and using Codesys V3.5 SP19 Patch 6. I get the following error: Communication Manager [Device: PLC Logic: Application]: The information model http://opcfoundation.org/UA/ is required by http://opcfoundation.org/UA/Boiler/ with a minimal publication date from 15/12/2023 but the device has only a model from 15/09/2021 installed. Probably the information model from 15/09/2021 is missing in the information model repository. The error message does not make sense to me. Should it not be “Probably the information model from 15/12/2023 is missing in the information model repository”? Anyway, both versions are available in the repository. How can I solve this?
Last updated: 2024-03-13

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

Sort by relevance or date