Post by gordonkeller360 on RS232 Communication in CODESYS Control RTE V3 ^{CODESYS Forge talk (Post)}
Hi -- Did you have any luck porting this over to RTE? I have a similar situation, where I am using CAA SerialCom and it works fine with Control Win, but I can't open the port when using in RTE. Any advice helps. Thanks!
Last updated: 2026-03-14

Post by pernockham on Gateway in China - "Gateway not connected" ^{CODESYS Forge talk (Post)}
Finally sorted (unit in China). The problem was related to dns-setting of the gateway/host. Connection (also inside china) tested/works.
Last updated: 2026-03-18

Post by timvh on USB Game Controller with Raspberry Pi ^{CODESYS Forge talk (Post)}
I'm not sure it will work, but you could try it with the CmpCharDevice library. You could create a function block that looks something like this: As input for the filename, you have to use your Linux device, e.g.: '/dev/input/event0' '/dev/input/by-path/platform-button@23-event' Off course you must also pass the pointer to the memory where the data can be written to and the size (count in number of bytes) of the buffer. FUNCTION_BLOCK FB_CharDevice VAR_INPUT szFilename: STRING; pbyBuffer : POINTER TO BYTE; udCount : UDINT; END_VAR VAR_OUTPUT iState : INT := 0; nrBytesRead : DINT; END_VAR VAR xInit : BOOL := TRUE; dFlags: DINT := CmpCharDevice.ACCESS_MODE.O_RDONLY + DINT#4000; // see details for flags: http://linux.die.net/man/2/open, + DINT#4000 is for non-blocking hDevice: CmpCharDevice.CmpCharDevice_Implementation.RTS_IEC_HANDLE := -1; Result : CmpCharDevice.CmpCharDevice_Implementation.RTS_IEC_RESULT; END_VAR IF xInit THEN hDevice := CmpCharDevice.CDOpen(szFilename, dFlags ,Result); // if it would not succeed, the result is -1 (Invalid handle) IF hDevice <> 16#FFFFFFFF AND Result = 0 THEN iState := 5; END_IF xInit := FALSE; END_IF IF iState = 5 THEN nrBytesRead := CmpCharDevice.CDRead(hDevice, pbyBuffer, udCount, Result); ELSE nrBytesRead := 0; END_IF Make sure you close the connection properly, maybe by overwriting the default FB_Exit method of the FB: // Clean up device IF hDevice <> 16#FFFFFFFF THEN __TRY CmpCharDevice.CDClose(hDevice,Result); __CATCH ; __ENDTRY iState := 0; END_IF
Last updated: 2026-05-01

Post by totorovic on Ladder editor bug with 3.5.21.20 ^{CODESYS Forge talk (Post)}
The update via CODESYS Installer fails (admin mode). Anyway I am switching all my POUs from Ladder to ST because Ladder cannot be used like this.
Last updated: 2026-06-02

Post by eschwellinger on Linux ARM64 Deploy Fail - Index out of range ^{CODESYS Forge talk (Post)}
I would check the version of the deloy tool using the CODESYS installer. Sure manually installing works too, but woukd nice to know if there is a problem. Currebt version is 4.21.0.0 of the deploytool.
Last updated: 2026-07-01

Post by hhermsen on Codesys v3.5.22.10 - Internal error:System.AggregateException...Value cannot be null...Parameter name: expLValue ^{CODESYS Forge talk (Post)}
I pinpointed down 4 possible causes for this compiler error: Bare/empty statements (;) standing alone inside an IF/CASE branch — just removed two instances. The optimizer that tries to inline/replace expression statements may choke when a statement has no actual assignment to extract. A VAR_IN_OUT parameter used directly as a FOR loop's own control variable (FOR X := X TO Y DO) General deep-nesting complexity — every one of my decode routines has the same shape (IF busy THEN ... FOR loop containing nested CASE/IF chains ... END_IF), and the crash trace consistently shows for loop → sequence → ifst → sequence → ifst → sequence regardless of the code change. This raises the possibility that it's not one specific statement but a structural depth/complexity limit in SP22.x's compiler optimizer — which would mean no small code change fixes the issue. Only restructuring to reduce nesting depth, or downgrading the compiler will. Something entirely outside my library files — which cannot not ruled out since the exact stack trace was triggered by a Visualization object, in a totally different codebase. This means the same crash signature can come from unrelated causes. IMHO cause 3 seems the most probable one..
Last updated: 2026-07-11

Post by eschwellinger on CODESYS Control for Raspberry Pi 5 - "Hardware version or firmware version not supported" on Rev 1.1, persists across multiple runtime versions and OS images ^{CODESYS Forge talk (Post)}
you need to wait for the 4.22.0.0 release which will fix this problem
Last updated: 2026-08-10

Post by eschwellinger on CAN TX regression in Control for Raspberry Pi 4.21.0.0 with CAN API library (RX works, TX silently fails) ^{CODESYS Forge talk (Post)}
seems to be an accident but there is a workaround in the Configfile: [CmpSocketCanDrv] AsyncSend=1 and will be solved with 4.22.0.0 Release
Last updated: 2026-08-17

Post by reinier-geers on Read own network device name ^{CODESYS Forge talk (Post)}
Hi. When i scan for devices on the network i get names of the devices. Is there a command to get device name in my programm ? i found : DED.GetDeviceNameString( DED.GetRoot() ); but then i get his name in the programm. not his name in the network.
Last updated: 2026-09-17

Post by tcarlbom on codesys sp20 opcua not working ^{CODESYS Forge talk (Post)}
hi, anyone else having trouble with opc ua in codesys sp20? i get Error 'BadIdentityTokenInvalid' was returned during ActivateSession i have tried both windows x64 runtime and linux runtime. i have created a completely new codesys project for this. in each of them i have only added the symbol configuration and selected one tag. i have tried several opc ua client, like ua expert, nodejs and python. all return Error 'BadIdentityTokenInvalid' was returned during ActivateSession so the problem must be the opc ua server.
Last updated: 2024-07-03

Post by sercan on Does G75 work when SMC_NCInterpreter is used? ^{CODESYS Forge talk (Post)}
When a G75 command is received in a SoftMotion+CNC project, SMC_NCInterpreter does not generate any error commands, but the command does not continue execution! There is information about SMC_NCDecoder in the documentation of the G75 command. Is this command only supported by SMC_NCDecoder? Can the G75 command be used with SMC_NCInterpreter? Forexample: G75 ; RUNNING G01 X$Settings.X$ Y$Settings.Y$ Z$Settings.Z$ ; - G75 ; - G01 X100.0 Y200.0 Z300.0 ; -
Last updated: 2025-05-09

Post by sercan on Does G75 work when SMC_NCInterpreter is used? ^{CODESYS Forge talk (Post)}
When a G75 command is received in a SoftMotion+CNC project, SMC_NCInterpreter does not generate any error commands, but the command does not continue execution! There is information about SMC_NCDecoder in the documentation of the G75 command. Is this command only supported by SMC_NCDecoder? Can the G75 command be used with SMC_NCInterpreter? Forexample: G75 ; RUNNING G01 X$Settings.X$ Y$Settings.Y$ Z$Settings.Z$ ; - G75 ; - G01 X100.0 Y200.0 Z300.0 ; -
Last updated: 2025-05-09

Post by sercan on Does G75 work when SMC_NCInterpreter is used? ^{CODESYS Forge talk (Post)}
When a G75 command is received in a SoftMotion+CNC project, SMC_NCInterpreter does not generate any error commands, but the command does not continue execution! There is information about SMC_NCDecoder in the documentation of the G75 command. Is this command only supported by SMC_NCDecoder? Can the G75 command be used with SMC_NCInterpreter? Forexample: G75 ; RUNNING G01 X$Settings.X$ Y$Settings.Y$ Z$Settings.Z$ ; - G75 ; - G01 X100.0 Y200.0 Z300.0 ; -
Last updated: 2025-05-09

Post by sercan on Does G75 work when SMC_NCInterpreter is used? ^{CODESYS Forge talk (Post)}
When a G75 command is received in a SoftMotion+CNC project, SMC_NCInterpreter does not generate any error commands, but the command does not continue execution! There is information about SMC_NCDecoder in the documentation of the G75 command. Is this command only supported by SMC_NCDecoder? Can the G75 command be used with SMC_NCInterpreter? Forexample: G75 ; RUNNING G01 X$Settings.X$ Y$Settings.Y$ Z$Settings.Z$ ; - G75 ; - G01 X100.0 Y200.0 Z300.0 ; -
Last updated: 2025-05-09

Post by sercan on Does G75 work when SMC_NCInterpreter is used? ^{CODESYS Forge talk (Post)}
When a G75 command is received in a SoftMotion+CNC project, SMC_NCInterpreter does not generate any error commands, but the command does not continue execution! There is information about SMC_NCDecoder in the documentation of the G75 command. Is this command only supported by SMC_NCDecoder? Can the G75 command be used with SMC_NCInterpreter? Forexample: G75 ; RUNNING G01 X$Settings.X$ Y$Settings.Y$ Z$Settings.Z$ ; - G75 ; - G01 X100.0 Y200.0 Z300.0 ; -
Last updated: 2025-05-09

Post by hickan on safety cpu cannot go online ^{CODESYS Forge talk (Post)}
Hi! I am using abb ac500 in automation builder v2.7 I have a problem with a new project. In the normal mode I have no problems, but in safety mode i cannot go online. I get 'Communication Error (#0) Logout Performed' message. I have tried changing the adress (level 1) in communication parameters. I tried 0.0.0.0.0 and 0.1.0.0.0 and 1.1.0.0.0 but it did no difference. What do you think could be causing this? Thanks!
Last updated: 2025-07-08

Post by fleaplc on CPU + EtherCAT redundancy ^{CODESYS Forge talk (Post)}
Hi all, for a new project I'm looking for a redundant controller with EtherCAT fieldbus I/O. Actually I'm using Beckhoff and it works great! but there's not a solid redundancy yet... Does someone get experience for industrial application (not raspberry) for a redundant Codesys system? If yes please share some info (CPU / OS type, bus, number of managed I/O,... and especially feeling feedback (stability, bugs, performance)... Every suggestion is kindly appreciated!! Fabrizio
Last updated: 2026-01-27

Post by rita56re on Temu Coupon Code $100 off➧ [act892435] for First-time Users ^{CODESYS Forge talk (Post)}
New users can enjoy a fantastic $100 discount on orders over $100. Use the code [act892435] at checkout to receive your $100 off Temu coupon. This offer is available for a limited time only, so don't miss out! Exclusive Deals: • Extra 30% off for new and existing customers, plus up to 90% off on select items. • Temu coupon codes for new users: [act892435] • Temu discount code for new customers: [act892435] • Temu $100 coupon code: [act892435] Special Promotions: • Temu $20 coupon code: [act892435] • Verified Temu coupon code August 2024: [act892435] • WORKING,,$100 OFF** TEMU COUPON CODE|!act892435! Temu new customer offer: [act892435] • Temu discount code 2024 UK: [act892435] • $100 off coupon code Temu: [act892435] • 100% off any order: [act892435] • $100 off Temu code: [act892435] Amazing Bundles and More: • Shoppers can take advantage of numerous discounts and deals with the Temu Coupon Bundle [act892435]. • Temu coupon $100 off for new customers: [act892435] will save you $100 on your order. • Temu coupon code 80% off: [act892435] • Free Temu codes 50% off: [act892435] • Temu coupon $100 off: [act892435] • Temu buy to get $39: [act892435] • Temu 129 coupon bundle: [act892435] • Temu buy 3 to get $99: [act892435] Exclusive Savings: • $100 Off Temu Coupon Code: [act892435] • Temu $100 Off Coupon Code: [act892435] • Temu Coupon Code $100 Bundle: [] • Free Gift On Temu: [act892435] • Temu $40 Off Coupon Code: [act892435] • Temu $100 off coupon code for existing users: [act892435] Get the Most Out of Temu: • Yes, Temu offers a $100 off coupon code [act892435] for first-time users. You can get a $100 bonus plus 30% off any purchase at Temu with the $100 Coupon Bundle if you sign up with the referral code [act892435] and make a first purchase of $100 or more. • For existing users, Temu Coupon code [act892435] can get up to 50% discount on products during checkout. • Temu Coupon Codes for Existing Customers: [act892435]
Last updated: 2024-10-26

Post by risele on dynamic modbus devices ^{CODESYS Forge talk (Post)}
Have the same issue: I'm making a test setup for modbus devices testing and calibration. One is run for every possible address, and it starts with minimal request: if the device is found, it continue to work with it, otherwise it's set to Disabled temporary. Those state machines are running under FOR cycle, and disabled are just skipped. Every instance have its own timer for not running too frequently and a start delay, so the actual requests are separate in time. I also check not for a single error, but have some timer to allow one-two timeouts. The small program disables and re-enables devices temporary (manually, since i could not iterate over MB devices). VAR Reset:ARRAY[1..GVL_MB.MD_COUNT] OF R_TRIG; i:INT; END_VAR {IF hasconstantvalue(GVL_MB.MD_COUNT, 1, >= )} i:=1; MD_1.Enable:=GVL_MB.MDPortsEnable[i]; Reset[i](CLK:=GVL_MB.MDPortsEnable[i]); MD_1.xReset:=Reset[i].Q; {END_IF} {IF hasconstantvalue(GVL_MB.MD_COUNT, 2, >= )} i:=2; MD_2.Enable:=GVL_MB.MDPortsEnable[i]; Reset[i](CLK:=GVL_MB.MDPortsEnable[i]); MD_2.xReset:=Reset[i].Q; {END_IF} There is also program to re-enable devices periodically. METHOD ScanBus VAR_INPUT END_VAR VAR j:INT; (*block auto scanning if calibration is running for any device since it's data-reach process that should not be interrupted with modbus timeouts *) CalibrationBusy:BOOL:=FALSE; END_VAR CalibrationBusy:=FALSE; FOR j:=1 TO GVL_MB.MD_COUNT DO CalibrationBusy:=CalibrationBusy OR MD_Calibrate.AutoTesters[j].xBusy; END_FOR; IF CalibrationBusy THEN RETURN; END_IF tBusScanSchedule(IN:=(NOT tBusScanSchedule.Q), PT:=tBusScanPeriod); IF (NOT tBusScanDelayer.Q) AND (tBusScanSchedule.Q OR (NOT xFirstScanPerforemed)) THEN xBusScanBusy:=TRUE; MissingCounter:=0; xFirstScanPerforemed:=TRUE; FOR j:=1 TO GVL_MB.MD_COUNT DO (* MD_Calibrate is main calibration program. Identifiers - is array of State machines mentioned above Phase_Faulted is a state of Identifiers where I'm sure device is missing on the bus *) IF MD_Calibrate.Identifiers[j].state=eStateMDIdentifier.Phase_Faulted THEN MD_Calibrate.Identifiers[j].Rescan(); MissingCounter:=MissingCounter+1; END_IF END_FOR END_IF tBusScanPauser(IN:=tBusScanDelayer.Q AND (MissingCounter>0),PT:=tBusScanDelay*MissingCounter); xBusScanBusy:=tBusScanPauser.Q; xFirstScanPerforemed:=xFirstScanPerforemed OR tBusScanPauser.ET>=tBusScanPauser.PT; Also the GUI have buttons for each address possible that re-enables the device if required.
Last updated: 2026-02-13

Post by brandonje on [Error] IoDrvEtherNetIP Library with Weintek ^{CODESYS Forge talk (Post)}
I'm using weintek and Codesys V3.5 SP22 when I try to charge an ethernetIP device show me this error: ------ Build started: Application: Device.Application ------- Typify code... [ERROR] cip object, 4.9.0.0 (codesys): TCPIP_Interface: C0231: Expression of type 'BOOL' expected in this place [ERROR] cip object, 4.9.0.0 (codesys): TCPIP_Interface: C0077: Unknown type: '(_pPhysicalLink^._xLinkState <> CmpSysEthernet.OperStatus.SYSETH_OPERSTAT_Up)' [ERROR] cip object, 4.9.0.0 (codesys): TCPIP_Interface: C0077: Unknown type: 'CmpSysEthernet.OperStatus.SYSETH_OPERSTAT_Up' [ERROR] cip object, 4.9.0.0 (codesys): TCPIP_Interface: C0062: 'CmpSysEthernet.OperStatus' is no structured variable [ERROR] cip object, 4.9.0.0 (codesys): TCPIP_Interface: C0063: 'CMPSYSETHERNET, 3.4.3.0 (3S - SMART SOFTWARE SOLUTIONS GMBH)' contains no definition for 'OperStatus' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0046: Identifier '_diAdapterNumber' not defined [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: '_diAdapterNumber'' to type 'DINT' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: 'ADR(ethFrame.ethData)'' to type 'POINTER TO StructEthernetframe' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0077: Unknown type: 'ethFrame.ethData' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: 'ethFrame.udFrameLen'' to type 'ANY' [ERROR] cip object, 4.9.0.0 (codesys): SendEthFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): _OpenEthAdapter [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: '((driverInstance * 2) + 1)'' to type 'ANY' [ERROR] cip object, 4.9.0.0 (codesys): _OpenEthAdapter [TCPIP_Interface]: C0077: Unknown type: '(driverInstance * 2)' [ERROR] cip object, 4.9.0.0 (codesys): _OpenEthAdapter [TCPIP_Interface]: C0077: Unknown type: 'driverInstance' [ERROR] cip object, 4.9.0.0 (codesys): _OpenEthAdapter [TCPIP_Interface]: C0046: Identifier 'driverInstance' not defined [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0231: Expression of type 'BOOL' expected in this place [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'SIZEOF(ethFrame.ethData)' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'ethFrame.ethData' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0018: 'ethFrame.udFrameLen' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: 'ADR(ethFrame.ethData)'' to type 'POINTER TO BYTE' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'ethFrame.ethData' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [TCPIP_Interface]: C0201: Type 'SysEthernetFrame' is not equal to type 'SysEthernetFrame' of VAR_IN_OUT respectively REFERENCE 'ethFrame' [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0046: Identifier 'ethClose' not defined [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0018: 'ethClose' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0046: Identifier '_diAdapterNumber' not defined [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: '_diAdapterNumber'' to type 'DINT' [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0046: Identifier '_diAdapterNumber' not defined [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0018: '_diAdapterNumber' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0046: Identifier '_stName' not defined [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0018: '_stName' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0046: Identifier '_stDescription' not defined [ERROR] cip object, 4.9.0.0 (codesys): _CloseEthAdapter [TCPIP_Interface]: C0018: '_stDescription' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): AddressConflictDetection [TCPIP_Interface]: C0231: Expression of type 'BOOL' expected in this place [ERROR] cip object, 4.9.0.0 (codesys): AddressConflictDetection [TCPIP_Interface]: C0077: Unknown type: '(_pPhysicalLink^._xLinkState = CmpSysEthernet.OperStatus.SYSETH_OPERSTAT_Up)' [ERROR] cip object, 4.9.0.0 (codesys): AddressConflictDetection [TCPIP_Interface]: C0077: Unknown type: 'CmpSysEthernet.OperStatus.SYSETH_OPERSTAT_Up' [ERROR] cip object, 4.9.0.0 (codesys): AddressConflictDetection [TCPIP_Interface]: C0062: 'CmpSysEthernet.OperStatus' is no structured variable [ERROR] cip object, 4.9.0.0 (codesys): AddressConflictDetection [TCPIP_Interface]: C0063: 'CMPSYSETHERNET, 3.4.3.0 (3S - SMART SOFTWARE SOLUTIONS GMBH)' contains no definition for 'OperStatus' [ERROR] cip object, 4.9.0.0 (codesys): Recv [TCPIP_Interface]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): Recv [TCPIP_Interface]: C0046: Identifier '_diAdapterNumber' not defined [ERROR] cip object, 4.9.0.0 (codesys): Recv [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: '_diAdapterNumber'' to type 'DINT' [ERROR] cip object, 4.9.0.0 (codesys): Recv [TCPIP_Interface]: C0046: Identifier '_diAdapterNumber' not defined [ERROR] cip object, 4.9.0.0 (codesys): Recv [TCPIP_Interface]: C0032: Cannot convert type 'Unknown type: '_diAdapterNumber'' to type 'DINT' [ERROR] memory block manager, 3.5.21.30 (codesys): ObjectRetain [Disposable]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] memory block manager, 3.5.21.30 (codesys): ObjectRelease [Disposable]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [LLDP_Management]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [LLDP_Management]: C0201: Type 'SysEthernetFrame' is not equal to type 'SysEthernetFrame' of VAR_IN_OUT respectively REFERENCE 'frame' [ERROR] cip object, 4.9.0.0 (codesys): SendFrame [LLDP_Management]: C0201: Type 'SysEthernetFrame' is not equal to type 'SysEthernetFrame' of VAR_IN_OUT respectively REFERENCE 'ethFrame' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0032: Cannot convert type 'Unknown type: 'ADR(frame.ethData[0])'' to type 'POINTER TO BYTE' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'frame.ethData[0]' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0032: Cannot convert type 'Unknown type: 'SIZEOF(frame.ethData)'' to type 'UDINT' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'frame.ethData' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0018: 'frame.udFrameLen' is no valid assignment target [ERROR] cip object, 4.9.0.0 (codesys): CreateFrame [LLDP_Management]: C0077: Unknown type: 'SysEthernetFrame' [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Receive [UcmmReceiver]: C0448: Operator '__COMPARE_AND_SWAP' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Send [UcmmReceiver]: C0448: Operator '__COMPARE_AND_SWAP' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Enqueue [UcmmQueue]: C0448: Operator '__COMPARE_AND_SWAP' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Enqueue [UcmmQueue]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Enqueue [UcmmQueue]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Dequeue [UcmmQueue]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Dequeue [UcmmQueue]: C0448: Operator '__COMPARE_AND_SWAP' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] iodrvethernetip, 4.9.0.0 (codesys): Dequeue [UcmmQueue]: C0448: Operator '__XADD' is not supported by your current target. At least runtime system version 3.5.14.0 is required. [ERROR] asynchronous job manager, 5.0.0.0 (codesys): ExtendAsync [FactoryBase]: C0448: Operator '__COMPARE_AND_SWAP' is not supported by your current target. At least runtime system version 3.5.14.0 is required. Compile complete -- 71 errors, 0 warnings Build complete -- 71 errors, 0 warnings : No download possible
Last updated: 2026-08-20

Post by bernd on Version 3.5.19.40 probleme bei FUN mit _to_ im Name ^{CODESYS Forge talk (Post)}
Hallo, ich habe von Version 3.5.19.0 auf 3.5.19.40 hochgerüstet, jetzt bekomme ich bei allen FUNs die "to" im Namen haben einen Fehlermeldung. Oft in der OSCAT.LIB verwendet. Gleiche Meldung wenn ich einen FUN neu anlege. Sobald ich das to weglasse z.b. nur "t" ist der Fehler weg. Programm ist unverändert. Fehlermeldung: Typ.... wird nicht unterstützt. Hat jemand das gleiche Problem? Bzw. wo liegt das Problem? Bzw. nutzt jemand das SP4 und bei ihm kommt der Fehler nicht? Läuft bei mir auf Rasperry. Beispiel: DT_TO_SDT -> Fehlermeldung Typ DT_TO_SDT wird nicht unterstützt. DT_T_SDT -> Übersetzung Fehlerfrei
Last updated: 2023-11-09

Post by riccardo on Codesys SP19 patch 4 ^{CODESYS Forge talk (Post)}
Hallo everyone, I am working on new PLC of Weidmueller that uses Codesys SP19. I made the upgrade at the Patch 4 coming from patch 0. Unce made the upgrade everything is working well in the progect except the web visu user menagent. In the new version, when I perfom the login, I cannot use the keyboard of the device; the window where to digit the user name and password opens, the buttons "OK" and "Cancel" work but the system doesn't allow to put input from the device keybord, the mouse behaves as it is an image. If I active the virtual keypad or numpad it works otherwise nothing. I am wondering if it is a bug of the new package or if I must set something else. Thanks in advance, Riccardo.
Last updated: 2023-11-27

Post by dawidr on Best practices for querying multiple MODBUS devices ^{CODESYS Forge talk (Post)}
Hi! What are the best practices for querying multiple Modbus devices? Single PRG or maybe multiple PRG (so basically multiple thread) per each Modbus device. In my current implementation I'm using single PRG and I'm utilizing FbMbMasterMultiQuerySerial and WagoAppPlcModbus.FbDigitalTwinMbSlaveDevice in eCockpit with PFC200. I've the timer with 2 seconds delay there and it was working fine for single device. But now I have three Modbus devices and for two of them I need to run 2/3 queries to get data from all registers. I noticed that the delays for getting the data from the Modbus devices is much bigger right now.
Last updated: 2024-07-31

Post by davidbo on RPI can system operation like rm in a shell have an impact on a Task cycle time ^{CODESYS Forge talk (Post)}
I have noticed that a rm file1.txt command on a shell has an impact on the cycle time for a TASK writing to file2.txt. Seen in the Monitor fane of the Task configuration Furthermore if a TASK makes a system call like rm, its cycle time increases of course but it seems to have an invisible impact on other TASKs too. I have a TASK for handling communication over the CANbus (SPI) where it stops sending "Heartbeats" for many seconds when another TASK does a system rm. Why is that not seen on the Monitor fane? Is even codesyscontrol paused when system calls are made? The CPU load is about 30-40%
Last updated: 2024-09-23

Post by jacobwago on v3.5 SP19 - Modbus TCP Devices - Channel Limit? ^{CODESYS Forge talk (Post)}
Hello, I have experienced the same issue as described above but for the Modbus Serial configurator. Looking for a solution. In v3.5 SP19 Patch 7 the Modbus Serial Master Slave configurator has a "virtual" limit of 10 channels. In v3.5 SP18 Patch 5 this virtual limit does not exist. I can successfully copy back and forth from 18 to 19 with out any build error. However, this is not a good solution for our customers. What is even more confusing is that the IoDrvModbus library is the same version (4.3.0.0) for both SP18 and SP19. Please help in providing a fix to the virtual channel limit of 10 in SP19. Thanks,
Last updated: 2024-09-29

Sort by relevance or date