Post by s1ack on Wago PFC200 Ethernet / IoDrvEthernet Issue? ^{CODESYS Forge talk (Post)}
It's suspected that the CPU loading is the Linux Kernal in the Wago PFC200 dealing with IGMP multicast traffic (@ 250 uSec) from inverters on site. The inverters use the ethernet network and IGMP to synchronize, the customer removed the switch that shipped with the system, and thus removed IGMP Snooping that was plug-and-play within the provided switch.
Last updated: 2025-01-24

Wago PFC200 Ethernet / IoDrvEthernet Issue? ^{CODESYS Forge talk (Thread)}
Wago PFC200 Ethernet / IoDrvEthernet Issue?
Last updated: 2025-01-24

Post by ph0010421 on Help with __SYSTEM.VAR_INFO ^{CODESYS Forge talk (Post)}
thanks...I changed to I POINTER which is perfect.
Last updated: 2025-01-26

Help with __SYSTEM.VAR_INFO ^{CODESYS Forge talk (Thread)}
Help with __SYSTEM.VAR_INFO
Last updated: 2025-01-26

Post by trusty-squire on Help with __SYSTEM.VAR_INFO ^{CODESYS Forge talk (Post)}
Not knowing exactly what you want to accomplish, you can try to use VAR_INPUT MyVar: POINTER TO BOOL; END_VAR MyVar contains the address of your referenced variable, and MyVar^ dereferences it allowing you to access the value. If this doesn't meet your needs, could you add more detail on what you are trying to accomplish?
Last updated: 2025-01-26

Post by fless on Help with __SYSTEM.VAR_INFO ^{CODESYS Forge talk (Post)}
to get the address just use ADR( ) variables defined in a VAR_IN_OUT block are references pointing to the passed variables. VAR_IN_OUT MyVar: bool; END_VAR VAR adrMyVar: __XWORD; END_VAR adrMyVar := ADR(MyVar);
Last updated: 2025-01-26

Post by kumareasu on Raspberry Pi 5 ^{CODESYS Forge talk (Post)}
Linux ARM SL is ready for Rapsberry pi5 now ?
Last updated: 2025-01-27

Post by eschwellinger on Raspberry Pi 5 ^{CODESYS Forge talk (Post)}
you could use either the PI package or Arm / Arm 64 SL packages on the PI
Last updated: 2025-01-27

Post by chrisdeloglos on Network Variables not updating ^{CODESYS Forge talk (Post)}
Thanks for the comment. I'm using Weidmueller UC20-WL2000-AC's and changing the broadcast address to match the current subnet this worked for me as well!
Last updated: 2025-01-27

Network Variables not updating ^{CODESYS Forge talk (Thread)}
Network Variables not updating
Last updated: 2025-01-27

Post by winki on Opaque NodeId in the OPC UA server ^{CODESYS Forge talk (Post)}
Hello, I have the same Issue !!!
Last updated: 2025-01-27

Post by eschwellinger on No source code available for this object ^{CODESYS Forge talk (Post)}
first i would try to update to 4.18.0.0 (latest) SoftMotion version and try if same problem still occure.
Last updated: 2025-01-28

Post by mystx on No source code available for this object ^{CODESYS Forge talk (Post)}
hello It is any solution to use this fb in application other pou?
Last updated: 2025-01-28

Post by bertcom on STRING conversions to DWORD ^{CODESYS Forge talk (Post)}
Good afternoon. I want to communicate with a Domino Industrial Printer using its Codenet protocol. The printer wants a series of Hexadecimal characters with no spaces or '00' characters. Because of that i chose the option to make the prefix and subfix for my code in a string. I have variable data in another string. With a complete program of a lot of CONCAT functions i eventually get the format of code that the printer accepts ( tested it with the hercules tool). Hercules String : 1B4F513030311B7532626C61636B04 The problem is : Codesys adds automatically 'code' to the code to show it is a string. Codesys string : '1B4F513030311B7532626C61636B04' The printer does not understand this. My idea is to convert the string datatype to an LWORD. I have no idea how to do this. I random types in STRING_TO_DWORD, as return i get 0. That didn't worked. Also on internet the explenations around string converting in codesys are very limited. If there in anyone who can explain me how to do it, i would appreciate it a lot ! Thank you!
Last updated: 2025-01-29

Post by trusty-squire on STRING conversions to DWORD ^{CODESYS Forge talk (Post)}
I don't fully understand the issue, but if the encoding is a problem you can try testing with WSTRING datatype instead of STRING. https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_datatype_wstring.html
Last updated: 2025-01-30

Post by bertcom on STRING conversions to DWORD ^{CODESYS Forge talk (Post)}
@trusty-suire, The problem is not encoding. The problem is that codesys ands ' ' to the string. And the printer can't handle these character.
Last updated: 2025-01-30

Post by bertcom on STRING conversions to DWORD ^{CODESYS Forge talk (Post)}
@trusty-suire, The problem is not encoding. The problem is that codesys ands ' ' to the string. And the printer can't handle these character.
Last updated: 2025-01-30

EtherCATStackLibrary - CmpSysEthernet Unaufgelöste Referenz ^{CODESYS Forge talk (Thread)}
EtherCATStackLibrary - CmpSysEthernet Unaufgelöste Referenz
Last updated: 2025-01-31

Post by z3r091 on EtherCATStackLibrary - CmpSysEthernet Unaufgelöste Referenz ^{CODESYS Forge talk (Post)}
Guten Morgen, ich habe ein Problem mit dem Lesen von IO Link Geräten. Wir nutzen einen Festo IO-Link Master den ich mittels der Funktionen ETC_ADS_IoLinkRead und ETC_ADS_IoLinkWrite lesen und schreiben möchte. Dazu implementiere ich die Bibliothek EtherCATStackLibrary 4.6.1.0. Hier geht schon das erste Problem los. Diese Bibltiothek möchte eine weitere Bibliothek nutzen, die "CmpSysEthernet". Diese muss ich über die Platzhalter manuell auf "SysEthernet 3.5.19.0" linken. Dann sind erstmal keine Fehler mehr vorhanden und das Projekt lässt sich übersetzen. Beim oder vor dem laden in die (Eckelmann) Steuerung, bekomme ich dann aber Fehler über unaufgelöste Referenzen, über Funktionen aus der SysEthernet Bibliothek (siehe Screenshot). Hat da jemand eine Idee oder Lösung?
Last updated: 2025-01-31

Post by rmaas on STRING conversions to DWORD ^{CODESYS Forge talk (Post)}
Hi, The '' characters in Codesys are there only to indicate it is a STRING type. They are not actually added to the string, maybe you are adding them unintentionally in the concat function? You can send your data from Codesys to Hercules to verify... Another option is to send the data as an array of bytes instead of a string, with every byte representing 1 ASCII character. https://www.ascii-code.com/ This way you are 100% sure Codesys is not adding any unwanted characters.
Last updated: 2025-01-31

Post by dkugler on STRING size and reading STRING with Modbus ^{CODESYS Forge talk (Post)}
Last updated: 2025-01-31

STRING size and reading STRING with Modbus ^{CODESYS Forge talk (Thread)}
STRING size and reading STRING with Modbus
Last updated: 2025-01-31

Post by bertcom on STRING conversions to DWORD ^{CODESYS Forge talk (Post)}
Hi rmaas, Do you have any explenation how to send it to Hercules? Thank you!
Last updated: 2025-02-01

Post by timvh on STRING conversions to DWORD ^{CODESYS Forge talk (Post)}
I guess that the printer expects to receive an array of byte values. So where it is described that it expects to receive: Hercules String : 1B4F513030311B7532626C61636B04 it actually expects to receive an array of bytes with the values 1B,4F,51,30,30, etc. So what you can do is create an array of bytes and assign the byte value to each item in the array: VAR abyToSend : ARRAY[0..99] OF BYTE; END_VAR abyToSend[0] := 16#1B; // ASCII Escape character, hexadecimal representation uses 16# as prefix abyToSend[1] := 16#4F; // ASCII 'O' abyToSend[2] := 16#51; // ASCII 'Q' abyToSend[3] := 16#30; // ASCII '0' // you can do the rest yourself // maybe could be created a lot smarter, but gives you an indication how to handle this. Then with the serial communication (or TCP/IP?) you can send a message with the reference to the array (abyToSend) and the number of bytes to send (15 bytes for the string you gave as example).
Last updated: 2025-02-02

Post by runtimevictor on virtual plc vPLC configure nics ^{CODESYS Forge talk (Post)}
Hello, When I add 2 nics in vPLC this happens to me..., why is it? If I just put one of the two NICs, the vPLC runtime instance starts running correctly...
Last updated: 2025-02-02

Sort by relevance or date