Post by rafaelbrito on Licensing info not available. ^{CODESYS Forge talk (Post)}
Hello, I'm having the same problem. I'm trying to license Codesys running in a Linux container, which I downloaded from the following link (https://hub.docker.com/r/hilschernetiotedge/codesys_control_sl_linux). The same error that you mentioned appears. Is there any solution?
Last updated: 2024-05-22

Post by yannickasselin on ControlWin 3.5.20.30 Issues ^{CODESYS Forge talk (Post)}
Hello, Trying to install ControlWin 3.5.20.30 on Windows 10 Enterprise 2016 LTSB and I always get this error about the gateway. 3.5.20.20 is working fine. Any ideas why? Thank you
Last updated: 2024-09-26

Post by gabor-n on PNIO Connect Parameter Error ^{CODESYS Forge talk (Post)}
Hello, I have the same issue, but with 2 Raspberry Pi3b+ in connection with Profinet. Has it been solved yet? Thank You all! Gabor
Last updated: 2024-10-08

Post by nano on PNIO Connect Parameter Error ^{CODESYS Forge talk (Post)}
please post your codesyscontrol.cfg and codesyscontrol_user.cfg in most cases there are misconfigs or missing entrys the reason. also the fact that in most cases codesys isnt running as rt-application on raspberry needs special eyes on
Last updated: 2024-10-10

Post by winki on Modbus TCP & RTU with Control for Linux SL ^{CODESYS Forge talk (Post)}
I do not have error anymore using nic with eth0 value. But my network it still 172.17.0.3 like the first picture.
Last updated: 2024-10-23

Post by andrax on CodeSys Raspberry pi I2C driver not found ^{CODESYS Forge talk (Post)}
Note: if you do not get any values. Check the correct wiring again. The board seems to be running and you have no error.
Last updated: 2024-11-07

Post by to-ke on Errors with VisuUserManagement library ^{CODESYS Forge talk (Post)}
Hallo zusammen, hi all, ich habe den gleichen Fehler. Auf einem Raspberry Pi geht der Fehler weg, wenn ich alles bereinige und dann vollständig übersetze. Wenn das Projekt im Codesys Development System wieder neu geladen wird ist der Fehler aber wieder da. Mit eine Win V3 x64 PLC kann ich den Fehler nur unterbinden wenn ich auf der HMI das VUM_Login einbinde. Dieses brauche ich aber nicht, da ich die HMI für das User Management selbst gestaltet habe. Das funktioniert auch. I have the same error. On a Raspberry Pi the error goes away if I clean everything and then compile completely. When the project is reloaded in the Codesys Development System, the error returns. With a Win V3 x64 PLC I can only prevent the error if I integrate the VUM_Login on the HMI. But I don't need this because I designed the HMI for user management myself. That works too. Anyone have an idea to fix this problem. Many thanks
Last updated: 2024-07-09

Post by alimans on Hex string ^{CODESYS Forge talk (Post)}
Hi kdkwhite, for Word you still can use suggested code by using a union structure and crack down your Word to two byte as bellow: TYPE CrackWordToByte : UNION InWord : WORD; OutBytes : ARRAY [0..1] OF BYTE; END_UNION END_TYPE then define your variable as this type: udInput : CrackWordToByte; now assign your Word variable input to InWord and send OutBytes[x] to the mentioned method: udInput.InWord := WordVariableInput; Input := udInput.OutBytes[x]; Regarding your question about the code: actually 48 is ascii code of "0" and while 65 is the ascii code of "A" so in above code 55 + 10 would be 65.
Last updated: 2023-09-20

Post by fpawlak on KNX SL on stock PFC200 firmware ^{CODESYS Forge talk (Post)}
Hi All. Is it possible to use CODESYS KNX SL on stock Wago firmware (Codesys version, not e!Cockpit). I have Wago 750-8212 with firmware 0.4.04.03(26). When I tried to run 'KNX SL' or even 'Device Reader', I have got [FATAL ERROR] Unresolved reference: 'CODEMGETCONTENTBYFIRMCODE3' [FATAL ERROR] Unresolved reference: 'CODEMGETCONTENTBYFIRMCODE2' [FATAL ERROR] Unresolved reference: 'CODEMGETCONTENTBYFIRMCODE2' What probbalby means that there is no running CodeMeter component on PLC. I have checked /etc/codesys3.d/CODESYSControl.cfg [CmpWebServer] WebServerPortNr=58080 [CmpSecureChannel] CertificateHash=86ccf31839a098ee32067179e26600f1bd6b36f8 [CmpUserMgr] AsymmetricAuthKey=a9d38381e75bbf1bbfc8749e97f536f68238a2ce So the question is if I can somehow add Codemeter to stock firmware? Or should I switched to CODDESYS Control for PFC200 SL or application-base runtime licence?
Last updated: 2024-05-23

Post by egau on Hard shutdown: no code on device after power on ^{CODESYS Forge talk (Post)}
Hi, thanks for the fast response :) Yes I Have a .err file. Sorry I forgot to upload it. It is a binary file though... "Runtime goes in exception before the shutdown ?" I think it goes into exception at the same time as the power is lost...
Last updated: 2024-10-03

Post by totorovic on CSVReaderInit returns error : INVALID_HANDLE ^{CODESYS Forge talk (Post)}
Hello, Can we please have some details about the error : INVALID_HANDLE? So we can try to avoid it.
Last updated: 2023-08-28

Communication error (#0), logout performed,please check if plc is connected ^{CODESYS Forge talk (Thread)}
Communication error (#0), logout performed,please check if plc is connected
Last updated: 2023-09-11

enabling OPC UA connectivity while using motion control SM3_basic library gives build error ^{CODESYS Forge talk (Thread)}
enabling OPC UA connectivity while using motion control SM3_basic library gives build error
Last updated: 2018-08-22

[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

Error 4709....Trends are not supported by the current target ^{CODESYS Forge talk (Thread)}
Error 4709....Trends are not supported by the current target
Last updated: 2012-04-02

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

Yellow triangle and bus not running error in Modbsu TCP master and Slave. ^{CODESYS Forge talk (Thread)}
Yellow triangle and bus not running error in Modbsu TCP master and Slave.
Last updated: 2021-12-07

what to do in case of a writing error to eeprom ^{CODESYS Forge talk (Thread)}
what to do in case of a writing error to eeprom
Last updated: 2020-11-26

OPC-UA errors in log, how do I interpret the error codes? ^{CODESYS Forge talk (Thread)}
OPC-UA errors in log, how do I interpret the error codes?
Last updated: 2021-02-05

Yellow triangle and bus not running error in Modbsu TCP master and Slave. ^{CODESYS Forge talk (Thread)}
Yellow triangle and bus not running error in Modbsu TCP master and Slave.
Last updated: 2021-12-07

Codesys v3.5 SP4 Patch 1 pbF: Internal error while opening archive with projects.open_archive() ^{CODESYS Forge talk (Thread)}
Codesys v3.5 SP4 Patch 1 pbF: Internal error while opening archive with projects.open_archive()
Last updated: 2021-06-08

"The identifier 'min' is not a valid IEC identifier" error, Profinet Controller configuration ^{CODESYS Forge talk (Thread)}
"The identifier 'min' is not a valid IEC identifier" error, Profinet Controller configuration
Last updated: 2023-04-03

Communication error(#0): logout performed after update Windows 7 to Windows 10 ^{CODESYS Forge talk (Thread)}
Communication error(#0): logout performed after update Windows 7 to Windows 10
Last updated: 2019-02-28

Generic CiA402 dirve AL Status read from slave address 1001 status 16#1A: Synchronization error ^{CODESYS Forge talk (Thread)}
Generic CiA402 dirve AL Status read from slave address 1001 status 16#1A: Synchronization error
Last updated: 2022-01-13

an item with the same key has already been added. Error ^{CODESYS Forge talk (Thread)}
an item with the same key has already been added. Error
Last updated: 2014-06-16

Sort by relevance or date