Activity for SuperJojo2002
-
SuperJojo2002 posted a comment on discussion Runtime 🇬🇧
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"...
-
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...
-
If support for a containerized CODESYS runtime with a license isn't feasible, then I've considered an alternative approach: I've purchased and activated a "CODESYS Control Basic S" license on my Windows notebook, where I already have the Codemeter Control Center installed. Upon activation, I can see the CODESYS license as active on my notebook. Subsequently, I followed the instructions provided in this link (https://faq.codesys.com/display/CDSFAQ/How+to%3A+Setup+a+Wibu+Network+Server+Access+for+Licenses)...
-
I just want to highlight, that we intend to use the codesys runtime on an embedded device that has no possibilites to connect any dongle devices to. It is an edge IO-Link master with an 1.6GHz ARM computer running inside that has an embedded linux running and a Docker container engine: https://www.hilscher.com/de/produkte/edge-gateways-mit-container-management/edge-io-link-master
-
I just want to highlight, that we intend to use the codesys runtime on an embedded device that has no possibilites to connect any dongle devices to. It is an edge IO-Link master with an 1.6GHz ARM computer running inside that has an embedded linux runing and a Docker container engine https://www.hilscher.com/de/produkte/edge-gateways-mit-container-management/edge-io-link-master
-
I just want to highlight, that we intend to use the codesys runtime on an embedded device that has no possibilites to connect any dongle devices to. It is an edge IO-Link master with an 1.6GHz ARM computer running inside that has an embedded linux runing and a Docker container engine
-
I just want to highlight, that we intend to use the codesys runtime on an embedded device that has no possibilites to connect any dongle devices to. It is an edge IO-Link master with an 1.6GHz ARM computer running inside that has an embedded linux runing and a Docker container engine
-
I checked it using the very same docker container version like colleague moon and the command returned root@nt0001c02c5533:/# 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. Result: 0 CmContainer(s) listed. (CodeMeter not running) Please consider that we intend to license a codesys ARM64 SL in a docker container.
-
I checked it using the very same docker container version like colleague moon and the command returned root@nt0001c02c5533:/# cmu -x cmu - CodeMeter Universal Support Tool. Version 7.60b of 2023-Jun-15 (Build 5615) for Linux/ARMHF 64-Bit Copyright (C) 2007-2023 by WIBU-SYSTEMS AG. All rights reserved. Result: 0 CmContainer(s) listed. (CodeMeter not running) Please consider that we intend to license a codesys ARM64 SL in a docker container.