Silent install for CODESYS 64 3.5.19.0 ^{CODESYS Forge talk (Thread)}
Silent install for CODESYS 64 3.5.19.0
Last updated: 2024-09-12

cant install runetime on 750-8202 ^{CODESYS Forge talk (Thread)}
cant install runetime on 750-8202
Last updated: 2024-10-01

Post by toby on Ethercat Servo Setup ^{CODESYS Forge talk (Post)}
Hi everyone, so a little update to this, I've come back to this project in the new year, and got it working. Yeah!, However, now with the new licensing setup, I need a new SoftMotion license, but it doesn't seem to be compatible with the previous Raspberry Pi SL license. Has anyone had any luck with Raspberry Pi and SoftMotion_Lite? Specifically the licensing of such? My customers new installation needs to be rebooted every 30min which is causing headaches! Another option is to not use the SoftMotion function blocks, and control the EtherCat amplifier directly, but I'm not sure how to do so. Does anyone have a specific example project of how to control a servo without the use of the SoftMotion function blocks? Thanks everyone for any assistance rendered. It's very much appreciated! Toby
Last updated: 2024-01-10

Post by timvh on Profinet fault with codesys control V3 - Receive packet error ^{CODESYS Forge talk (Post)}
Are you using the Control Win SL (installed together with the development environment of CODESYS)? If yes, you might want to consider using the CODESYS RTE instead. This has real-time capabilities (running on separate core(s)). But to be able to use this, you have to install the CODESYS Ethernet driver for your network interface to be able to let the RTE access the network port also in realtime. See: https://store.codesys.com/en/codesys-control-rte-sl-bundle.html https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_windows_rts_v3.html PS, I haven't tested this myself yet, but you could try to use the SetCommunicationState method of the Profinet controller to see if you can reset and start the bus communication: result := PN_Controller.SetCommunicationState(eRequestedState := DED.DEVICE_TRANSITION_STATE.START); PS, if you are located in the Netherlands or Belgium, we could also provide the license(s) for you.
Last updated: 2024-02-28

Post by timvh on Profinet fault with codesys control V3 - Receive packet error ^{CODESYS Forge talk (Post)}
Are you using the Control Win SL (installed together with the development environment of CODESYS)? If yes, you might want to consider using the CODESYS RTE instead. This has real-time capabilities (running on separate core(s)). But to be able to use this, you have to install the CODESYS Ethernet driver for your network interface to be able to let the RTE access the network port also in realtime. See: https://store.codesys.com/en/codesys-control-rte-sl-bundle.html https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_windows_rts_v3.html PS, I haven't tested this myself yet, but you could try to use the SetCommunicationState method of the Profinet controller to see if you can reset and start the bus communication: result := PN_Controller.SetCommunicationState(eRequestedState := DED.DEVICE_TRANSITION_STATE.START); PS, if you are located in the Netherlands or Belgium, we could also provide the license(s) for you.
Last updated: 2024-02-28

Post by mavitia on Application based license problem - Modbus TCP ^{CODESYS Forge talk (Post)}
raspberry pi is running ubuntu, so it has the codesys control for linux arm 64 bit, IDE is 3.5.19, both were installed last week from the latest versions online, im currently out of the PC but will upload some evidence ASAP
Last updated: 2023-12-18

Post by mavitia on Issue with TargetVisu on Codesys Control Win ^{CODESYS Forge talk (Post)}
anyone else running into the same issue: perform a repair install on the runtime, that should fix it without affecting license.
Last updated: 2024-02-02

Post by paulpotat on Can't open license manager with raspberry CM4 ^{CODESYS Forge talk (Post)}
Do someone have any information on this topic ? We tried several different CM4 boards without success, and we cannot install the licenses we bought anymore... Isn't CodeSys supposed to support CM4 Raspberry pi ?
Last updated: 2024-10-15

Post by elektron785 on Dongle von Linux-Modul (ARM64) nicht erkannt ^{CODESYS Forge talk (Post)}
Die Ausgabe bei lsusb ist im ersten Post im Bild usb.png zu sehen - der Dongle wird als WIBU Systems CmStick erkannt. Um Codesys als Soft-PLC darauf zum laufen zu bekommen habe ich das Addon Codesys Control for Linux ARM SL installiert und mir einen Docker gebaut mit den Dateien: codesyscontrol_linuxarm64_4.10.0.0_arm64.deb und codemeter-lite_7.60.5625.503_arm64.deb Wenn ich den Docker ausführe sind die beiden Programme ja inbegriffen und Codemeter sollte eigentlich die Erkennung des Dongles sicherstellen. Gibt es eine Möglichkeit festzustellen, dass Codemeter korrekt ausgeführt wird?
Last updated: 2024-09-05

Post by winki on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
For small project, I would like to use my industrial computer as a PLC + Industrial Computer. Like that I can save the cost of one PLC. That why I am using Codesys on Linux. With the nic it is not working. I already set the IP adress with /etc/network/interfaces. Can it comes from there ? looking to "Control Linux SL" docuemntation it should work with rtu.
Last updated: 2024-10-23

Post by rossanoparis on Clarifications regarding the appropriate runtime system to use ^{CODESYS Forge talk (Post)}
Hallo all I would appreciate some clarifications regarding the appropriate runtime system to use. I've been using 'KUNBUS CPUs' and 'CODESYS Control for Raspberry Pi MC SL' for the last 4 years. Recently, there have been some changes in the CODESYS licensing policy. [ https://store.codesys.com/en/howto_applicationbasedlicenses ] My questions are mainly two: 1) If I need to start a new project using 'KUNBUS CPUs', which is the correct runtime system to use. 2) Old projects built using 'CODESYS Control for Raspberry Pi MC SL' should be updated to another RT system? Current RT systems ... a)CODESYS Control for Raspberry Pi MC SL b)CODESYS Control for Linux ARM SL c)CODESYS Virtual Control SL May I count on receiving an explanation to understand the differences among the runtime systems listed above? A detailed and well-organized answer would be greatly appreciated. Kind regards Rossano
Last updated: 2024-09-23

Post by reinier-geers on License problem gateway ^{CODESYS Forge talk (Post)}
The hole setup is made by 3s. So its a comination of one not two. If Epis decide not to support extra licence whats then the funtion of providing an option with a single license ?? So the idee by 3s has a flod. Epis change the system to add the Stick. I send controller inc stick to Epis. On my software i can see the stick. An then you tel me i need a other license to use an license ?? Makes completly no sense. Codesys should be flexible but is not. I tried Delta. But has no HMI and has its own Codesys ?? Why ?? Then i tried Crist. The block there own system by a password. But dont know the password and cant switch it off. At the end the want me to pay for support to solve ther own made problem. So i send it al back. The extra license is adviced by 3s . Now a few month later still no working solution.
Last updated: 2024-05-01

Post by eschwellinger on License problem gateway ^{CODESYS Forge talk (Post)}
I just try to help. Anyway it is a big difference if a Store SL runtime or an oem plc and licence is used. These licenses need to be activated on plc side - so you have dependencies to the version (CODESYS and Runtime Version) Did you ever ask Epis out for this situation? They should know which license fit to their device. Even they should know if the device is capable for Softmotion and see the requiremnts in the CODESYS store: Runtime 4.9.0.0 - how should this work with Epis 3.5.16.x? Anyway refund is not a problem.
Last updated: 2024-04-26

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 valenting on Problem with Licenced Software Metrics ^{CODESYS Forge talk (Post)}
Hi, I tried with another project, using codesys SP20 with the latest visualization installed, I can install the application on my device but it doesn't work I get an exception "invalid license metrics" and the app won't run See attached the metrics in project and allowed by license, and the logs What am I supposed to do ? Everything is in the newest version and the values are lower than allowed and nothing works...
Last updated: 2024-04-26

Post by dhumphries on Minimum system requirements for codesys control standard S ^{CODESYS Forge talk (Post)}
I'm working on a low cost project and I'm considering installing the Codesys runtime on a PC running Linux Debian instead of buying a PLC with a pre-installed runtime. For my needs the Control Standard S license should be capable of running some IO over ethernet/ip, and a webvisu. The PC I am considering has a AMD GX-424CC 2.4GHz processor (4 core/4 thread) and 4GB RAM. This may compare to a raspberry pi4, but I know an X86 processor doesn't directly compare to an ARM processor, and a processor can have a high clock speed but other factors like L2/L3 cache can influence the overall performance. I can't find any published specs for the processor and RAM requirements to run the Codesys Control runtime, does anybody have a link to the minimum system requirements or experience using devices that are at or below the minimum system requirements. A raspberry pi with the control for raspberry pi SL runtime license would be the lowest cost option, but the license is not for commerical use. This restriction is somewhat vague, can anybody clarify if this means I can use a raspberry Pi runtime for in-house automation, what about if I am selling an integrated system that uses a raspberry Pi as a controller?
Last updated: 2023-12-25

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

no synchronization via field bus(Raspberry Sl softmotion) ^{CODESYS Forge talk (Thread)}
no synchronization via field bus(Raspberry Sl softmotion)
Last updated: 2018-05-29

MQTT für CODESYS Control for PFC200 SL ^{CODESYS Forge talk (Thread)}
MQTT für CODESYS Control for PFC200 SL
Last updated: 2017-05-09

CODESYS Control for Raspberry Pi SL on Raspberry Pi 4b ^{CODESYS Forge talk (Thread)}
CODESYS Control for Raspberry Pi SL on Raspberry Pi 4b
Last updated: 2023-10-17

RaspberrPi 4 Compute Module: Runtime "SL" available? ^{CODESYS Forge talk (Thread)}
RaspberrPi 4 Compute Module: Runtime "SL" available?
Last updated: 2021-02-02

Problem mit CODESYS Control for Raspberry Pi SL, fehlende Bibliotheken? ^{CODESYS Forge talk (Thread)}
Problem mit CODESYS Control for Raspberry Pi SL, fehlende Bibliotheken?
Last updated: 2020-03-13

CODESYS Control for Raspberry Pi SL - Error in Ticket email ^{CODESYS Forge talk (Thread)}
CODESYS Control for Raspberry Pi SL - Error in Ticket email
Last updated: 2017-05-11

Why Codesys Raspberry SL not updated any more like 3.5.9.0? ^{CODESYS Forge talk (Thread)}
Why Codesys Raspberry SL not updated any more like 3.5.9.0?
Last updated: 2016-07-07

HMI SL - Runtime shutdown by on screen command ^{CODESYS Forge talk (Thread)}
HMI SL - Runtime shutdown by on screen command
Last updated: 2019-08-05

Sort by relevance or date