Post by timvh on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
Most likely your IP address is set to 172.... because you use a VPN connection to your device. Probably best to use the other Ethernet interface for your modbus communication.
Last updated: 2024-10-24

How to use more 4 instances of CANopen/Profibus/Modbus with The application-based license CODESYS Control ^{CODESYS Forge talk (Thread)}
How to use more 4 instances of CANopen/Profibus/Modbus with The application-based license CODESYS Control
Last updated: 2023-11-02

Post by cavein on PFC100 Licensing fails ^{CODESYS Forge talk (Post)}
Hi, i have a similar problem. im using pfc200 4.5.0.0. There are two softcontainer and only one with license in it. every 1-2 hrs it will auto logoff. i tried the steps above but i dont find the /var/opt/codesys/.cmact_licenses i need help please.
Last updated: 2024-03-19

Post by paulpotat on Can't open license manager with raspberry CM4 ^{CODESYS Forge talk (Post)}
Update : The solution I mentionned in a previous post does not always work. Some Raspberry Pi CM4 still won't create the license container. I will open a support ticket.
Last updated: 2024-10-18

Post by ggis on Rasperry Control Debian 12 ^{CODESYS Forge talk (Post)}
From bash I usually see codesyscontrol.service as the runtime service. Taking a step back, I guess you used Tool > Update RaspberryPi SL interface to install the runtime: what does the info popup window tells you about your destination system?
Last updated: 2023-11-26

Post by dangjoris on raspistepper error after install ^{CODESYS Forge talk (Post)}
Ok with the new Release of SM3RaspiStepper 0.0.0.6 it is fixed. Everything works fine with CODESYS Control for Raspberry Pi SL 4.13.0.0 and CODESYS SDK 3.5.20.20
Last updated: 2024-09-30

Post by alexgooi on Codesys licensing explanation ^{CODESYS Forge talk (Post)}
Dear Forum, We are currently switching to a native Codesys controller, and I'm currently trying to determine the correct license. I have a question regarding the Modbus instances. With the Standard S license this is set to 4 (See picture). In our projects we are using a lot of communications to Modbus servers using a Codesys Controller, for this communication I'm using the ModbusFB library (supplied by 3S) (see picture). In my project I would like to use more than 4 instances of the ClientTCP FB. My question is, is this now capped at 4 possible connections with the standard S license. Or do these function blocks have a different relation with the license? Some clarity on this topic would be very welcome. Thank you in advance
Last updated: 2024-02-15

Post by rmaas on TargetVisu for Linux SL not starting ^{CODESYS Forge talk (Post)}
Hello, I am trying to get TargetVisu for Linux working but i am having some troubles. The problem is that after installation it is not starting automatically on boot and i cannot start it from the update Targetvisu tool. When i try i get the following error (see attached screenshot) The file /opt/codesysvisualization/scripts/codesysvisualization_start.sh is missing... Steps performed: - installed fresh Debian 12.7 on virtual machine - installed all required libraries as described here: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_target_visu_for_linux.html - then installed the TargetVisu for Linux SL 4.13.0.0 using the Codesys IDE Does someone know how i can fix this? Best Regards, Rinie
Last updated: 2024-10-02

Post by hfelek on TargetVisu for Linux Package on runtime 4.12.0.0 install error due to Qt dependencies. ^{CODESYS Forge talk (Post)}
I use V3.5.SP20 Patch 2 for development and my device with runtime is armv7l 32-bit arch
Last updated: 2024-08-27

Post by superjojo2002 on Licensing info not available. ^{CODESYS Forge talk (Post)}
I updated the docker container runtime to version 4.11.0.0. and build the container with this "Dockerfile" FROM arm64v8/debian:11.6 RUN apt-get update RUN apt-get install -y wget sudo unzip libusb-1.0-0-dev procps ENV CDS_VERSION "4.11.0.0" ENV EDGE_VERSION "4.11.0.0" ENV URL "https://store-archive.codesys.com/ftp_download/3S/LinuxARM64/2302000039/$CDS_VERSION/CODESYS%20Control%20for%20Linux%20ARM64%20SL%20$CDS_VERSION.package" ENV EDGE_URL "https://store-archive.codesys.com/ftp_download/3S/EdgeGatewayLinux/000120/$EDGE_VERSION/CODESYS%20Edge%20Gateway%20for%20Linux%20$EDGE_VERSION.package" RUN wget --output-document=/tmp/codesys.package $URL && \ unzip -p /tmp/codesys.package '*codemeter*.deb' > /tmp/codemeter.deb && dpkg -i /tmp/codemeter.deb && \ unzip -p /tmp/codesys.package '*codesyscontrol*.deb' > /tmp/codesys.deb && dpkg -i /tmp/codesys.deb RUN wget --output-document=/tmp/edge.package $EDGE_URL && \ unzip -p /tmp/edge.package '*arm64.deb' > /tmp/edge.deb && dpkg -i /tmp/edge.deb EXPOSE 11740 1217 11743 ENTRYPOINT ["/bin/sh", "-c" , "/etc/init.d/codemeter start && /etc/init.d/codemeter-webadmin start && /etc/init.d/codesyscontrol start && /etc/init.d/codesysedge start && tail -f /dev/null"] Now cmu -x" returns root@sensoredge-field-netfield-produktmanagment:/# cmu -x cmu - CodeMeter Universal Support Tool. Version 8.00 of 2023-Nov-28 (Build 5967) for Linux/ARMHF 64-Bit Copyright (C) 2007-2023 by WIBU-SYSTEMS AG. All rights reserved. But still CODESYS development system reports that it needs a dongle and when I click install that "value cannot be null. Parameter name: containerToLicenses" It seems that Codemeter is forced to look for a dongle instead of a CMsoftcontainer. Can you confirm that CODESYS licensing works also when CODESYS is installed in a Docker container?
Last updated: 2024-03-21

Post by starmaxou on How to download dependencies packages for CODESYS Control for Raspberry Pi SL ? ^{CODESYS Forge talk (Post)}
Hi everyone, I'm trying to install the CODESYS Control for Raspberry Pi SL package. The computer with CODESYS software is offline for security reasons. So, I downloaded the package on another computer and installed it manually. But this package has dependencies packages: CODESYS.Control SL Extension Package, V4.0.0.0 CODESYS.Control SL Deploy Tool, V4.10.0.0 As I said, the computer with CODESYS is offline. I cannot use the package installer to search for these packages. I did not find them in Codesys Store with another computer. Do you know where to find and download them? Thank you in advance for your help!
Last updated: 2024-05-30

Post by superjojo2002 on Licensing info not available. ^{CODESYS Forge talk (Post)}
I recognized that I have to start the two services "/etc/init.d/codemeter" and "/etc/init.d/codemeter-webadmin" in the docker container as well. If I do so, then the command "cmu -x" returns root@sensoredge-field-netfield-produktmanagment:/# cmu -x cmu - CodeMeter Universal Support Tool. Version 7.60c of 2023-Aug-09 (Build 5625) for Linux/ARMHF 64-Bit Copyright (C) 2007-2023 by WIBU-SYSTEMS AG. All rights reserved. So this time there is no indication any more that "Codemeter is not running". But still we are getting the error when using the license manager in CODESYS development system.
Last updated: 2024-03-21

Post by miodusy on CODESYS Control Standard S and Beaglebone ^{CODESYS Forge talk (Post)}
Hi, CODESYS Control Standard S + CODESYS Visualization L, CODESYS Control for Beaglebone 4.11.0.0, CODESYS V3.5 SP20 + (64-bit) I have problem that license manager say that this device is not supported when i try active whole license. When I select only runtime and communication it is go next step, but then I no have license on in Visualistion section, all of rest of software metric licese is ok(IO, Istances of com et, code size etc.). Thanks!
Last updated: 2024-05-11

Post by aliazzz on Unable to deploy Virtual Control SL on ARM64 (Raspberry Pi5) ^{CODESYS Forge talk (Post)}
Hi, I have successfully deployed "Virtual Control SL" on a few x86/64 machines now. However, I'd now like to deploy this to a Raspberry Pi (ARM64). To do this I prepared the Raspberry Pi5 with the following prereq's; * Minimal PREEMPT Debian * Latest Bootfirmware * full SSH access via non-root account * Podman * RedHat Cockpit with CODESYS LicensServer plugin up and running However, I can't seem to resolve copying the correct (deploy) Images as they wont show up in the CODESYS IDE I have added CODESYS Virtual Control for Linux SL and the CODESYS LicenseServer for Linux SL via the CODESYS installer on my DevBox. I open CODESYS > Tools > Deploy Control SL Next I enter the SSH targets IP and Credentials and for my RPi5 and it shows "Connected". In the next tab, Deployment, the dropdown box only shows one (1) image, which also is the incorrect CPU architecture. Only Virtual Control AMDx64 shows up (!?) while I expect to see the ARM64 based images for both Edge and Control. Has someone encountered this too? I'd like to hear other people experiences with Virtual Control deployment on ARM based architecture. attachment 1: AMD64 based deployment pulldown menu (correct images) attachment 2: ARM64 based deployment pulldown menu (incorrect images) regards,
Last updated: 2024-07-28

Post by hfelek on TargetVisu for Linux Package on runtime 4.12.0.0 install error due to Qt dependencies. ^{CODESYS Forge talk (Post)}
Hi, I am trying to make my runtime support TargetViso on 4.12.0.0 runtime. First when I tried to install package I got error due to missing libraries that are generated through qt-base. After compiling and installing related qt lib when I tried to install the package, I didnt get lib dependencies error but I got another error: [ERROR] The installed QT Version does not meet the minimum required version 6.4.2. Please install version 6.4.2 or higher and try again. When I check Qt version I get the following response QMake version 3.1 Using Qt version 6.5.0 in /usr/local/qt6/lib. I tried with Qt version 6.9.0 but that didn't help. Any idea on what coudl be the reason. When I looked for codesys related processes the related libraries were included within environment.
Last updated: 2024-08-27

Post by elektron785 on CAN-Bus in Demo-Version ^{CODESYS Forge talk (Post)}
Hallo, wie verhält es sich mit der Demo-Version und Datenübertragung z.B. via CAN-Bus. Der Bus läuft, das Device befindet sich im Zustand "Operational" aber es werden keine Daten von der Soft-SPS empfangen. Ich benutze aktuell eine nicht lizenzierte Version von CoDeSys Control for Linux ARM64SL. Normalerweise sollte die Demo-Version uneingeschränkt laufen - also kann ich davon ausgehen, dass es sich um einen Programmierfehler handelt oder ist die Feldbusfunktion ohne Lizenz doch in irgendeiner Form eingeschränkt verfügbar (außer dem 30 Minuten Limit nach Reboot)?
Last updated: 2024-02-06

Migration von "CODESYS Control for PFC200 SL" zu WAGO FW26 "CODESYS V3.5.19.2" ^{CODESYS Forge talk (Thread)}
Migration von "CODESYS Control for PFC200 SL" zu WAGO FW26 "CODESYS V3.5.19.2"
Last updated: 2023-11-23

Using ADAM-6200 with CODESYS Control for Raspberry Pi MC SL ^{CODESYS Forge talk (Thread)}
Using ADAM-6200 with CODESYS Control for Raspberry Pi MC SL
Last updated: 2021-03-21

[Error] HMI with CODESYS Control RTE SL does not show Pool images ^{CODESYS Forge talk (Thread)}
[Error] HMI with CODESYS Control RTE SL does not show Pool images
Last updated: 2022-06-21

CODESYS Control Win SL: Error Preparation was not successful: could not open network adapter ^{CODESYS Forge talk (Thread)}
CODESYS Control Win SL: Error Preparation was not successful: could not open network adapter
Last updated: 2023-05-19

Installing boot application to CodeSYS HMI SL without login through CodeSYS ^{CODESYS Forge talk (Thread)}
Installing boot application to CodeSYS HMI SL without login through CodeSYS
Last updated: 2021-01-05

Control RTE SL (for Beckhoff CX) on Windows Embedded Compact 7 ^{CODESYS Forge talk (Thread)}
Control RTE SL (for Beckhoff CX) on Windows Embedded Compact 7
Last updated: 2018-11-25

Support for Compute Module 4s (CM4s) with CODESYS Control for Raspberry Pi MC SL ^{CODESYS Forge talk (Thread)}
Support for Compute Module 4s (CM4s) with CODESYS Control for Raspberry Pi MC SL
Last updated: 2023-06-30

CODESYS Control for Raspberry Pi MC SL runtime failed to start ^{CODESYS Forge talk (Thread)}
CODESYS Control for Raspberry Pi MC SL runtime failed to start
Last updated: 2023-04-13

CODESYS Control for Raspberry Pi SL / SPI-Schnittstelle / Baudrate verändert sich ca. im 2-Sek-Takt ^{CODESYS Forge talk (Thread)}
CODESYS Control for Raspberry Pi SL / SPI-Schnittstelle / Baudrate verändert sich ca. im 2-Sek-Takt
Last updated: 2021-10-17

Sort by relevance or date