Post by donm on Regarding trend storage access error ^{CODESYS Forge talk (Post)}
i have created a project which contain 30 trend and suddenly trend recording is not working. its showing an error 30437."Determination of root pages for recording did not work for 'screen', error:30437" how to solve this issue?
Last updated: 2024-05-27

Post by donm on trend storage access error ^{CODESYS Forge talk (Post)}
i have created a project which contain 30 trend and suddenly trend recording is not working. its showing an error 30437."Determination of root pages for recording did not work for 'screen', error:30437" how to solve this issue?
Last updated: 2024-05-27

Post by unusual-data on C0138: No matching 'FB_Init' method found for instantiation of VisuClientObjectMgr ^{CODESYS Forge talk (Post)}
you can try to disable "Visualization Manager - Settings - Support client animations and overlay of native elements " selection" It worked for me, thank you.
Last updated: 2025-12-18

Post by elektron785 on GPIO mit Codesys Virtual Control for Linux ARM64 SL ^{CODESYS Forge talk (Post)}
Hallo zusammen, ich möchte an einem Entwicklungsboard auf dem der i.MX 8M Plus von NXP aufgesteckt ist die vier zur Verfügung gestellten GPIOs als Ausgänge verwenden. Ich habe mir dazu die Readme-Datei des GPIO-Beispiels von "C:\Program Files\CODESYS 3.5.20.40\CODESYS\CODESYS Control SL Extension Package\4.14.0.0\Examples\GPIO" angeschaut Die Übersicht der verfügbaren GPIOs sieht folgendermaßen aus - wobei ich das auf die reduziert habe, die für mich von Interesse sind: gpiochip0: GPIOs 0-31, parent: platform/30200000.gpio, 30200000.gpio: gpio-0 (SODIMM206 ) gpio-1 (SODIMM208 ) gpio-2 ( ) gpio-3 ( ) gpio-4 ( |sd-vsel ) out hi gpio-5 (SODIMM210 ) gpio-6 (SODIMM212 ) gpio-7 (SODIMM216 ) gpio-8 (SODIMM218 ) gpio-9 ( ) gpio-10 ( ) gpio-11 (SODIMM16 ) gpio-12 (SODIMM155 |regulator-usb1-vbus ) out lo gpio-13 (SODIMM157 ) gpio-14 (SODIMM185 |regulator-usb2-vbus ) out hi gpio-15 (SODIMM91 )** Füge ich nun das GPIO (1 Bit)-Gerät in meinem Codesys-Programm hinzu funktioniert der Bus solange bis ich die Richtung in den GPIO-Parametern von "not used" auf "Output" stelle (siehe Bild gpio_parameter). Dann funktioniert nach Download der Bus nicht mehr. Gibt es noch eine andere Möglichkeit das zu steuern oder muss ich noch Einstellungen tätigen? Für die Zeile mit dem echo (export/unexport) aus dem Beispiel fehlen mir trotz sudo die Zugriffsrechte. "The Kernel Linux has deprecated GPIO user space SysFS. However, the kernel config CONFIGGPIOSYSFS is still enabled on Toradex's BSP to support customers using it in their legacy applications. You can check the configuration by running zcat /proc/config.gz | grep CONFIGGPIOSYSFS. For GPIO access from userspace, the new char device API, also known as libgpiod, must be used." Dies steht in der Verwendung der GPIOs - eine Ausführung des zcat-Kommandos liefert ein =y zurück.
Last updated: 2025-03-17

Post by spiessli on Raspberry Pi 4 with Legacy Drivers and Codesys 3.5.19 Patch 4 ^{CODESYS Forge talk (Post)}
Hi, I wanted to use the Adafruit Hat for the Raspberry and get acquainted with Softmotion using servos for RC models. This did work great with Codesys 3.5.19 Patch 1, but with Patch 4 and 5 i get errors. I suspect changes in the SoftMotion library have broken dependencies in the legacy drivers, might that be true? Thanks for any hint, spiessli Here the error log: ------ Übersetzungslauf gestartet: Applikation: Device.Application ------- Code typisieren... Code erzeugen... [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0032: Typ 'Unbekannter Typ: 'ConfigGetParameterValueLREAL(pParam, 0)'' kann nicht in Typ 'LREAL' konvertiert werden [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0046: Bezeichner 'ConfigGetParameterValueLREAL' nicht definiert [FEHLER] sm3_drive_servo, 4.6.0.0 (3s - smart software solutions gmbh): GetStandardConfigParams AXIS_REF_SERVO: C0035: Programmname, Funktion oder Funktionsbausteinstanz an Stelle von 'ConfigGetParameterValueLREAL' erwartet Übersetzung abgeschlossen -- 15 Fehler, 0 Warnungen : Kein Download möglich
Last updated: 2023-12-19

Post by micik on Using Codesys example problems ^{CODESYS Forge talk (Post)}
Hello to all, I'm totally new to Codesys, but I do have some PLC programming experience, mosty with Siemens TIA and STEP7. I have just installed Codesys 3.5. sp19 and I have downloaded example with Ethernet Rockwell 1734AENT. The example can be found here: https://forge.codesys.com/prj/codesys-example/rockwell-1734-c/home/Home/ After opening, I had to manually update devices (Device, Ethernet, IP Scanner, EthernetIP adapter). However, when trying to build the project, I get the following errors: [WARNING] CODESYS_EtherNetIP_Rockwell1734AENT: Library Manager [Device: PLC Logic: Application]: C0100: Library System_VisuElemXYChart has not been added to the Library Manager, or no valid license could be found [WARNING] CODESYS_EtherNetIP_Rockwell1734AENT: Library Manager [Device: PLC Logic: Application]: C0100: Library system_visuinputs has not been added to the Library Manager, or no valid license could be found [ERROR] iodrvethernetip, 4.4.1.0 (3s - smart software solutions gmbh): ServiceCycle [IoDrvEtherNetIP]: C0040: Function 'ProcessUpdateConfigurationQueue' requires exactly '1' inputs [ERROR] iodrvethernetip, 4.4.1.0 (3s - smart software solutions gmbh): IoDrvStartBusCycle [IoDrvEtherNetIP]: C0040: Function 'GenerateRandomUINT' requires exactly '2' inputs [ERROR] iodrvethernetip, 4.4.1.0 (3s - smart software solutions gmbh): Cyclic [GenericServiceUnConnected]: C0040: Function 'GenerateRandomUINT' requires exactly '2' inputs [ERROR] cip object, 4.4.1.0 (3s - smart software solutions gmbh): ForwardOpenService [ConnectionManager]: C0040: Function 'GetAssemblies' requires exactly '3' inputs [ERROR] iodrvethernetipadapter, 4.4.0.0 (3s - smart software solutions gmbh): ServiceCycle [IoDrvEtherNetIPAdapter]: C0040: Function 'GenerateRandomUINT' requires exactly '2' inputs [ERROR] iodrvethernetip, 4.4.1.0 (3s - smart software solutions gmbh): SetupStructuredIOMapping [RemoteAdapter]: C0040: Function 'MallocData' requires exactly '1' inputs [ERROR] iodrvethernetip, 4.4.1.0 (3s - smart software solutions gmbh): SetupStructuredIOMapping [RemoteAdapter]: C0040: Function 'MallocData' requires exactly '1' inputs Compile complete -- 7 errors, 13 warnings Build complete -- 7 errors, 13 warnings : no download possible! What could be the reason for this errors and how to rectify them? Thank you!
Last updated: 2024-02-01

Post by mondinmr on Unexpected behavior in cyclic encoder read method during INT overflow (wrap-around) ^{CODESYS Forge talk (Post)}
Hi everyone, I’m investigating a potential issue with a cyclic method we use for reading incremental encoders in our libraries. I’ve come across two implementations that, at first glance, appear to perform the same operation: motionUnit.vlPositionActualValue is UINT due strange encoder type. Version A METHOD PROTECTED cyclicReadField VAR_INST actPosFieldOld: INT; rI: INT; delta: INT; END_VAR rI := TO_INT(motionUnit.vlPositionActualValue); delta := rI - actPosFieldOld; m_actPosRaw := m_actPosRaw + TO_LREAL(delta); actPosFieldOld := rI; IF settings.velocityFeebackMapped THEN m_actVelRaw := TO_LREAL(motionUnit.velocityActualValue); END_IF Version B METHOD PROTECTED cyclicReadField VAR_INST actPosFieldOld: INT; END_VAR m_actPosRaw := m_actPosRaw + TO_LREAL(TO_INT(motionUnit.vlPositionActualValue) - actPosFieldOld); actPosFieldOld := TO_INT(motionUnit.vlPositionActualValue); IF settings.velocityFeebackMapped THEN m_actVelRaw := TO_LREAL(motionUnit.velocityActualValue); END_IF Both use INT and the same delta logic, so they seem equivalent. However, when an overflow (wrap-around) occurs, version A continues correctly as expected, while version B unexpectedly resets to -32768 without a clear reason. Has anyone experienced similar behavior or can shed light on what might be happening here? It almost seems as if the cast to LREAL is being applied before the calculation — but that would be illogical and potentially very dangerous in many situations! Thanks!
Last updated: 2025-05-13

Post by paro on Modbus Client Request Not Processed ^{CODESYS Forge talk (Post)}
Hi, Problem in your code is that you are not calling the ClientFb cyclic. Please look at the Example from CODESYS: https://forge.codesys.com/prj/codesys-example/modbus/home/Home/ Your code works if the client fb is called cyclic! IF NOT initDone THEN initDone := TRUE; // configure clientTcp clientTcp(aIPaddr:=Ethernet.IPAddress, uiPort:=502); // configure clientSerial clientSerial(iPort:=SysCom.SYS_COMPORT2, dwBaudRate:=SysCom.SYS_BR_115200, byDataBits:=8, eParity:=SysCom.SYS_EVENPARITY, eStopBits:=SysCom.SYS_ONESTOPBIT, eRtuAscii:=ModbusFB.RtuAscii.RTU); // configure clientRequestReadCoils_1 clientRequestReadCoils_1(rClient:=clientTcp, uiUnitId:=42, udiTimeout:=TO_UDINT(T#10MS)); // configure clientRequestWriteSingleRegister clientRequestWriteSingleRegister(rClient:=clientTcp, uiUnitId:=43, udiTimeout:=TO_UDINT(T#10MS)); // configure clientRequestReadCoils_2 clientRequestReadCoils_2(rClient:=clientTcp, uiUnitId:=44, udiTimeout:=TO_UDINT(T#10MS)); // configure clientRequestReadInputRegisters clientRequestReadInputRegisters(rClient:=clientTcp, uiUnitId:=44, udiTimeout:=TO_UDINT(T#10MS)); END_IF // call the client FB's clientTcp(); clientSerial(); // call client request FB's clientRequestReadCoils_1(rClient:=clientTcp, xExecute:=TRUE, uiStartItem:=2, uiQuantity:=3, pData:=ADR(aDataCoils_1[0])); // for more details see Example_TCP, especially ClientRequest control (xExecute, xDone, xError). IF clientRequestReadCoils_1.xDone THEN // get data from aDataCoils_1 ... END_IF clientRequestWriteSingleRegister(rClient:=clientTcp, xExecute:=TRUE, uiItem:=3, uiValue:=123); clientRequestReadCoils_2(rClient:=clientTcp, xExecute:=TRUE, uiStartItem:=2, uiQuantity:=3, pData:=ADR(aDataCoils_2[0])); clientRequestReadInputRegisters(rClient:=clientTcp, xExecute:=TRUE, uiStartItem:=16, uiQuantity:=3, pData:=ADR(aDataInputRegisters[0]));
Last updated: 2024-05-29

Post by lsislsis on Alarms Placeholder ^{CODESYS Forge talk (Post)}
Hello. When i put placeholders at "/etc/codesyscontrol/CODESYSControl.cfg" : [SysFile] FilePath.1=/etc/codesyscontrol/, 3S.dat IecFilePath.1=/proc/, cpuinfo IecFilePath.2=/proc/, iomem PlaceholderFilePath.1=/sys/devices/w1_bus_master1, $OneWire$ PlcLogicPrefix=1 PlaceholderFilePath.2=/data/persistence, $ac_persistence$ PlaceholderFilePath.2.Volatile=1 PlaceholderFilePath.2.View=1 PlaceholderFilePath.3=/data/alarms, $alarms$ PlaceholderFilePath.3.Volatile=1 PlaceholderFilePath.3.View=1 Where "Data" are my USB Flash. I take these attachment errors at run time. What i am doing wrong.
Last updated: 2024-10-15

Post by arvindkumar on Wago plc not going back to RUN Mode after Power failure ^{CODESYS Forge talk (Post)}
Hi im using wago pfc750-8207 plc and my programming software was codesys v2.3, im facing some issue in my plc after power failure my plc not going back to run mode sometimes, i did sourecode download, boot application created and still facing this issue, out of 10 power failure 8 times its going to run mode some time its missing to go run mode and only sys indication is in on condition Kindly please help me.
Last updated: 2023-12-15

Post by user0815 on Web Socket Client SL -Bibliothek Fehler ^{CODESYS Forge talk (Post)}
Hallo zusammen, ich hoffe ihr könnt mir weiterhelfen. Meine Codesys Version ist die V3.5 SP19 Patch 4 und die Zielsystemversion ist die 4.10.0.0 . Ich verwende Codesys ohne Lizenz. Ich probiere eine Verbindung über Web Sockets zwischen Node-RED und Codesys aufzubauen. Dabei kommt folgende Fehlermeldung und folgender Logeintrag. Ansonsten stehen keine Fehlermeldungen im Log. Ich weiß nicht wieso sich die demo mode Zeit nicht zurücksetzt beim neu starten der RUN-Time. Schöne grüße
Last updated: 2023-12-19

Post by timvh on Codesys SVN ^{CODESYS Forge talk (Post)}
If you use 3.5 SP10, then Git is not supported. SVN will work fine, but with this version you do need a USB key, because software licenses are not supported with this version. Off course you can work without SVN (or Git), but especially if you work with multiple developers on one project, it will save you a lot of time and you can keep track of all changes and improvements much easier. So how much is this worth to you?
Last updated: 2024-04-30

Post by bitwitch on Einheiten umrechnen, Numpad und Eingabegrenzen ^{CODESYS Forge talk (Post)}
Das Codesys-Objekt 'Einheiten umrechnen' wirkt auf timeVar (TIME) z.B. innerhalb eines Visu-Rechtecks und funktionier in den Grundfunktionen einwadfrei. Die Ausgabe der Std. von timeVar läuft. Beispiel: Bei t#3d2h10m wird wunschgemäß 74h (volle Std-Anzahl). Die Grenzüberwachung Max= 10 funktioniert nicht, da die Angabe scheinbar ms erwartet (arbeitet mit 10ms). Irgend wie muss man jetzt codesys davon überzeugen, dass auch für Min und Max die Einheitenumrechnerei wirken soll, wobei die Eingabe der Grenzen in Std erfolen muß. Hat jemad einen TiPPPPPPPPP?
Last updated: 2024-06-14

Post by janderson on OPC UA Server limitations, large array crashes runtime ^{CODESYS Forge talk (Post)}
What are the limitations of the OPC UA Server? I am trying to get data off my PLC that is acquired at high rates (~50k samples/s) so I am storing them in arrays and trying to get the arrays off the PLC. When I attempt to read a ~200k element array through OPC UA the server and runtime crashes (requiring tools -> update linux arm64 -> start runtime). Is there a better way to get highspeed data off? The ACDatalog library seems a bit irritating to use so I would prefer to go through OPC UA.
Last updated: 2023-08-23

Post by janber0206 on Gateway doesn't come online, regarding a working internet connection ^{CODESYS Forge talk (Post)}
Solved (see comment) Setup: Kunbus RevPi Connect+ (a raspberry based PLC) Codesys runtime package: 4.5.0.0 (raspberry, armhf) based on Codesys V3.5.18.20 Edge Gateway: 4.5.0.0 (edgearmhf,armhf) EN: The edge-gateway was added over a year ago to the automation server. I now need to make a few changes to the Codesys software, but the Pi is not showing as online in the Automation Server. Internet connection is established, I have remote access to the Pi via RealVNC. Anyone have an idea how I can solve this? Some screenshots added. DE: Ich muss nun ein paar Änderungen an der Codesys-Software vornehmen, aber der Pi wird im Automation Server nicht als online angezeigt. Die Internetverbindung ist hergestellt, ich habe über RealVNC Fernzugriff auf den Pi. Hat jemand eine Idee, wie ich das Problem lösen kann?
Last updated: 2023-10-26

Post by bahrt on Mapping GPIO and adding GPIO configurations ^{CODESYS Forge talk (Post)}
Hi I am about to configure ALL GPIOs on a Raspberry Pi 3 model B V1.2. It seems that I have limited understanding of why not all the IO’s become available with the corresponding mapped IO’s – the 'dwInUse' contains mapping of the inputs from GPIO0 to GPIO27. But 'dwInputs' are only showing GPIO0 to GPIO8 and GPIO15 as available inputs. These mentioned inputs work fine You will be able to watch the limited mapped IO activity here: https://drive.google.com/file/d/1zz4PBNBfRZBF2YkiJ2VQxw6L9MBVji7R/view?usp=sharing Can you please bring your best idea on why GPIO09 to GPIO14 and GPIO16 to GPIO27 state are zero in the dwInputs register? Thanks in advance. Best regards Andreas Bahrt
Last updated: 2023-11-16

Post by bahrt on Raspberry Pi GPIO mapping ^{CODESYS Forge talk (Post)}
Hi I am about to configure ALL GPIOs on a Raspberry Pi 3 model B V1.2. It seems that I have limited understanding of why not all the IO’s become available with the corresponding mapped IO’s – the 'dwInUse' contains mapping of the inputs from GPIO0 to GPIO27. But 'dwInputs' are only showing GPIO0 to GPIO8 and GPIO15 as available inputs. These mentioned inputs work fine You will be able to watch the limited mapped IO activity here: https://drive.google.com/file/d/1zz4PBNBfRZBF2YkiJ2VQxw6L9MBVji7R/view?usp=sharing Can you please bring your best idea on why GPIO09 to GPIO14 and GPIO16 to GPIO27 state are not active (at a fixed zero state) in the dwInputs register? Thanks in advance. Best regards Andreas Bahrt
Last updated: 2023-11-21

Post by orbis-tertius on 3.5 P20 hangs - no response ^{CODESYS Forge talk (Post)}
Is there anybody can help me with the same problem? I have to migrate created project in ver.3.5.17.0 32BIT with runtime 4.7.0 to ver.3.5.20.0 64BIT with runtime 4.7.11.0 due to the new license. All the libraries and dependencies are updaded and there are no any errors. The first compilation and loading to the controller is being compleated well. After this being done and if I am forced to change any values or change any code in the current project, another compilation will be freezed. This problem can be solved if pressed Build/cleen or cleen all. There is another method to solve this; if project is loaded with excluded object (Alarm Configuration), repeated compilations will be done well.
Last updated: 2024-06-27

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Post by jp23 on Unable to Connect to Modbus RTU Device ^{CODESYS Forge talk (Post)}
Hi all, I am attempting to use the Control Win V3 soft PLC to control a WAGO 750-315 remote I/O system via modbus RTU communication. I am struggling to connect to the device. I have been following this tutorial: https://www.youtube.com/watch?v=YlRfkESaNds I have setup my devices as shown in the images below. I have verified that my com port settings are correct as I am able to connect/control using modbus simulator software with these settings. I have also connected to a modbus master simulator program as instructed in the video, but the orange triangles will not go away. Additionally, I have updated my settings to 485 using the PLC shell. I have also set "always update variables" to enabled (1). Serial port, PCI-Bus, and modbus serial device status all show as "Not Running."
Last updated: 2024-08-26

Sort by relevance or date