Adding a prg to a task via python script ^{CODESYS Forge talk (Thread)}
Adding a prg to a task via python script
Last updated: 2018-09-17

Forward a VAR_IN_OUT to a sub block :?: ^{CODESYS Forge talk (Thread)}
Forward a VAR_IN_OUT to a sub block :?:
Last updated: 2012-02-01

How to start a video on a Raspi's HDMI output ? ^{CODESYS Forge talk (Thread)}
How to start a video on a Raspi's HDMI output ?
Last updated: 2022-10-13

MC_Home of a master axis while a slave is geared? ^{CODESYS Forge talk (Thread)}
MC_Home of a master axis while a slave is geared?
Last updated: 2021-05-31

Any way to access a variable via a string? ^{CODESYS Forge talk (Thread)}
Any way to access a variable via a string?
Last updated: 2017-12-04

Converting a program into a function block ^{CODESYS Forge talk (Thread)}
Converting a program into a function block
Last updated: 2016-05-30

read and write a file to a raspberry folder ^{CODESYS Forge talk (Thread)}
read and write a file to a raspberry folder
Last updated: 2020-11-01

Saving a GVL to a file ^{CODESYS Forge talk (Thread)}
Saving a GVL to a file
Last updated: 2019-12-20

Extract a memory adress from a string value ^{CODESYS Forge talk (Thread)}
Extract a memory adress from a string value
Last updated: 2016-12-06

Create a FB for a continuous loop ^{CODESYS Forge talk (Thread)}
Create a FB for a continuous loop
Last updated: 2014-03-25

Adding a Softmotion License to a Weintek HMI ^{CODESYS Forge talk (Thread)}
Adding a Softmotion License to a Weintek HMI
Last updated: 2025-10-17

Importing a library overrides parameters of a referenced library ^{CODESYS Forge talk (Thread)}
Importing a library overrides parameters of a referenced library
Last updated: 2026-05-04

Post by baltzer on ICertificateVerifier.VerifyCertificate doesn't appear to override an ERR_CERT_HAS_EXPIRED rejection in TCP_Client.Upgrade() ^{CODESYS Forge talk (Post)}
Follow-up: working workaround found (routing TLS outside CODESYS) For anyone finding this thread later with the same problem (a third-party device presenting a self-signed and/or expired certificate that ICertificateVerifier/udiVerificationMode won't let you connect through) - we never got a working fix within NBS itself, but found a practical workaround worth sharing. Approach: run a local TLS-terminating proxy on the same host as the CODESYS runtime, and have CODESYS talk plain, unencrypted TCP to it instead of connecting to the remote device directly over TLS: CODESYS --plain TCP--> 127.0.0.1:<port> --stunnel/TLS--> <remote device>:<port> We used stunnel (client mode), with certificate verification explicitly disabled at that layer (verifyChain = no, verifyPeer = no) - a simple, well-documented one-line option, unlike anything we could get working inside NBS. Running it as a systemd service with Restart=always means it survives reboots and recovers automatically if the proxy or the remote device drops. On the CODESYS side, this required no changes beyond pointing TCP_Client at 127.0.0.1 instead of the device's real IP, and removing the TLSContext/ICertificateVerifier code entirely - the rest of our application-layer logic (framing, checksums, etc.) was completely unaffected, since none of that ever depended on where the TLS termination happened. Confirmed working end-to-end against a real device with an expired self-signed certificate, running on CODESYS Control for Raspberry Pi SL (Linux). We haven't yet set this up on Windows - stunnel does have Windows builds available, so the same general approach should be possible there too, but that combination isn't tested or confirmed by us at this point. Caveat: this only makes sense when the proxy and the CODESYS runtime are on the same trusted host (in our case, both on the same Raspberry Pi) - don't expose the proxy's plaintext side on a reachable network interface, since that would create an unauthenticated plaintext path to the device. The original question - whether there's a supported way to override an ERR_CERT_HAS_EXPIRED/self-signed rejection from within NBS's own TLSContext/ICertificateVerifier - remains open as far as we know. Still happy to hear from anyone who's solved that particular piece, since the workaround above is a practical detour rather than an actual answer to the original question.
Last updated: 2026-08-06

Post by robinluckey on IDE window handling bugs, windows diasppear, multi monitor setups ^{CODESYS Forge talk (Post)}
Codesys Windows (Main window as well as pop-ups) often appear outside of the viewable are in Windows when using multiple Monitors. This is exacerbated (happens more very often), when working on a notebook with different Monitor setups at different locations (which kind of is standard nowadays). The windows (not even the main Window) can not be recovered using standard short cuts like WIN + Arrow keys, alt + tab etc. The only way we found to recover the windows is by changing the Monitor positions in thew Windows Display Settings and than changing them back EVERY TIME a pop us is displayed. This makes using Codesys close to unbearable. All my colleagues face the same problem and do not have this problem with any other IDE. Please help.
Last updated: 2024-10-11

Post by pedegani on "Do you really want to perform" dialog boxes ^{CODESYS Forge talk (Post)}
I have the same annoying problem. The confirmation prompt for every single action appeared recently after an update from CODESYS 3.5 SP20 Patch 3 to Patch4, but I don't think it's due to this. Having to confirm every operation while debugging an application is a considerable waste of time and does not help at all to concentrate on development, not to mention that many times you miss the long-awaited event because you are busy looking for the 'yes' button to resume debugging or force a variable. Does anyone know how to disable the confirmation messages?
Last updated: 2025-02-14

Post by sushela on TEMU COUPON CODE 2024 [Oct 2024] ⇨ "[acq615756]",, 90% + 30% Discount ^{CODESYS Forge talk (Post)}
The Temu coupon codes acq615756 & acs546758 offer a $100 discount for customers in 2024. Applicable to both new and existing users. These codes can be used to save significantly on a variety of products available on the Temu platform. To redeem the discount, users should enter the code at checkout. This promotion enhances the shopping experience by providing substantial savings, making it an excellent opportunity for customers to explore Temu's diverse catalog while enjoying reduced prices. 2024 | TEMU Coupon Code ➞ ⦉{acq615756} & {acs546758 }⦊ "$100 Off" First order The TEMU coupon code acq615756 & acs546758 is are fantastic opportunities for shoppers in 2024 to save big on their online purchases. By using this exclusive code, you can enjoy a $100 discount on your first order. Additionally, the coupon offers a 50% discount on all orders, making it an unbeatable deal for those looking to maximize their savings. To take advantage of this offer, simply enter the code "acq615756" or "acs546758 " during checkout on the TEMU app or website. Temu Coupon Code $100 Off ⇒ {acq615756 } or {acs546758} For New and Existing Customers Temu is offering enticing coupon codes for both new and existing customers, allowing significant savings on purchases. The code acq615756 provides a remarkable $100 off for first-time users in 2024, making it an excellent opportunity to explore Temu's extensive product range. Additionally, the code acs546758 can be utilized by existing customers for further discounts, enhancing the shopping experience. Simply enter these codes at checkout to unlock your savings and enjoy a more affordable shopping spree on Temu. Temu 2024 Sign-Up Bonus Code [acs546758] The Temu sign-up bonus code "acs546758" offers an enticing opportunity for new customers in to enjoy significant savings on their first purchase. By entering this code during the checkout process, users can access exclusive discounts on a wide range of products available on the Temu platform. This promotion is designed to enhance the shopping experience for newcomers, making it a perfect time to explore Temu's diverse catalog while benefiting from substantial savings. To redeem this offer, simply apply the code at checkout and enjoy the benefits of being a new customer. 2024 Temu coupon "|"acq615756"| [acs546758 ]" for New Customers The Temu coupon code "|"acq615756"| [acs546758 ]" is a fantastic offer for new customers in 2024 , providing a discount of $100 on their first purchase. This code can be easily applied at checkout, allowing new users to enjoy significant savings on a wide variety of products available on the Temu platform. This promotion is designed to enhance the shopping experience for first-time buyers, making it an excellent opportunity to explore Temu's extensive catalog while benefiting from substantial discounts. Simply enter the code during checkout to take advantage of this offer. How to get TEMU Coupon code ᐅ |【acq615756】 || 【acs546758 】| To get Temu coupon codes, you can use the codes acq615756 and acs546758 for significant savings. The code acq615756 offers $100 off your first order, along with an additional 30% discount, making it an excellent choice for new customers. Meanwhile, acq615756 can be used for other promotions, potentially providing further discounts or cash back offers. Simply enter these codes at checkout to apply your savings and enjoy shopping at Temu's extensive online store. TEMU Coupon Code |"acq615756"| [acs546758 ] 2024 Free Shipping Who doesn't love free shipping? With the TEMU coupon code |"acq615756"| [acs546758 ], you can enjoy free shipping on your orders in 2024 . This offer eliminates the extra cost of delivery, making your shopping experience even more budget-friendly. Whether you're ordering a small item or a large haul, free shipping is always a welcome perk. TEMU Coupon Code |"acq615756"| [acs546758 ] 2024 for Free Items on the First Order First-time shoppers in 2024 have even more to look forward to. By using the TEMU coupon code |"acq615756"| [acs546758 ] on your first order, you can receive free items along with your purchase. This offer adds extra value to your initial shopping experience, making it even more rewarding. TEMU Coupon Code |"acq615756"| [acs546758 ] 2024 40% Off Looking for a significant discount? The TEMU coupon code |"acq615756"| [acs546758 ] in 2024 offers 40% off on select items. This substantial discount allows you to buy more while spending less, making it an ideal choice for those looking to maximize their savings. 2024 Temu coupon code 40 off "|"acq615756"| [acs546758 ]" for New & existing customers The Temu coupon code "|"acq615756"| [acs546758 ]" offers a discount of $40 for both new and existing customers in 2024 . This code can be applied during checkout to enjoy savings on a wide array of products available on the Temu platform. To redeem this offer, simply enter the code in the designated field at checkout. This promotion is a fantastic opportunity for all customers to enhance their shopping experience while benefiting from significant discounts on their favorite items. TEMU Coupon Code $100 Off {acq615756}: Get $100 Off + 40% Discount Unlock incredible savings with the TEMU Coupon Code [acq615756/ acs546758]! Get an exclusive $100 off on your first purchase, plus enjoy an additional 40% discount on selected items. This unbeatable offer is perfect for new users looking to maximize their savings. Simply apply the code at checkout to take advantage of these massive discounts and start shopping smart with TEMU today! TEMU Coupon Code |"acq615756"| [acq615756 ] 2024 50% Off For even greater savings, the TEMU coupon code |"acq615756"| [acs546758 ] provides a whopping 50% off on selected items in 2024 . This half-price offer is perfect for those big-ticket items you've been wanting to purchase but waiting for the right deal. TEMU Coupon Code |"acq615756"| [acq615756 ] For Free Finally, the TEMU coupon code |"acq615756"| [acs546758 ] can be used to access various free offers in 2024 . Whether it's free shipping, free items, or other promotional deals, this code opens the door to a range of cost-saving opportunities that can enhance your shopping experience. TEMU Coupon Code |"acq615756"| [acq615756 ] 2024 $100 Discount + 40%/50% Off For shoppers in 2024 , the TEMU coupon code |"acq615756"| [acs546758 ] is a must-have. It offers a $100 discount on your purchase, plus an additional 40% or 50% off selected items. Whether you're placing your first order or are a returning customer, this code provides incredible savings. Don't miss out—apply the TEMU coupon code|"acq615756"| [acq615756 ] at checkout to maximize your discounts and enjoy a more affordable shopping experience! TEMU COUPON CODE 2024 [Oct 2024] ⇨ "[acq615756]" or "[acs546758 ]",, 90% + 30% Discount Unlock incredible savings with Temu's exclusive coupon codes for 2024 this October 2024! Use code [acq615756] or [acs546758 ] to enjoy a massive 90% discount on selected items plus an additional 30% off on your purchase. These codes are perfect for both new and existing customers, helping you make the most of your shopping experience on Temu. Don’t miss out—grab these deals before they’re gone! Conclusion The TEMU coupon code |"acq615756"| [acs546758 ] in 2024 offers a versatile range of discounts and special offers, catering to both new and existing customers. Whether you're looking to save on your first order, get free shipping, or receive a significant discount, this code has something for everyone. Don't miss out on these incredible savings—use the TEMU coupon code |"acq615756"| [acs546758 ] on your next order and enjoy all the benefits it has to offer!​​
Last updated: 2024-10-26

Post by edvard-munch on How I can get "Done flag" for "Modbus Slave Channel"? ^{CODESYS Forge talk (Post)}
This is from 10 years ago, I know. But I have been using (SLAVE_DEVICE.iChannelIndex = CHANNEL_NUMBER) AND (SLAVE_DEVICE.xDone) I suppose that it shows xDone for the channel that shows up in the iChannelIndex at the same cycle? It seems to be working properly for two devices that I have been using it before But now I have another device and using two write channels, for one register each. One channel works properly and returns DONE flag When another channel is triggered, I see that it shows up in iChannelIndex, but flag DONE not received, but no Error for the channel. Also, when i check the register in the device it's evident that data has been transferred. Is this could happen sometimes with CODESYS, so DONE flag not received? Or this is a problem with a given device? With this certain register
Last updated: 2024-12-19

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 kevinrn on Github Actions CI/CD tasks - development topic ^{CODESYS Forge talk (Post)}
Hello community, I just want to inform you about our plans and the current status of automating the build process for CODESYS libraries. So it might be helpful for some people who are in the same situation. Background story: I am a software engineer at powerIO GmbH, normally I use high level languages for the products we develop and offer. Sometimes I work with my team on CODESYS libraries, which can also be found in the CODESYS store. Most of the time I spend with them on architecture tasks and tasks that are not directly related to our products. Every time I see the manual processes for releasing a library etc., I am very surprised about this time intensive process. Current situation: I know there has been a scripting interface for years. CODESYS Git was released a few years ago, but the scripting interface was only released a few months (weeks?) ago. We developed a pseudo-automated solution a few months ago, but it was all very hacky. So now there is a better Git implementation and also more modularization and installation options. For example, the CODESYS installer has a full CLI, which makes it very convenient to install CODESYS installations headless. Plans: I think it's the right time to develop a better automation solution. Most of our software projects are hosted on Github and we use Github actions very intensively for other software projects. Therefore, we have decided to use Github for our CODESYS library projects as well. Following tasks should be implemented in automation for CI/CD tasks: - Automated setup of CODESYS installation (Already released: https://github.com/marketplace/actions/setup-codesys-installation) - Checkout CODESYS libraries - Execute tests scripts - Sign CODESYS libraries - Extract Library documentation - Create CODESYS package - Sign CODESYS package Side Note: - This is mainly a side project, and we do not provide support for the CI/CD part. - This topic is here to help and also to get help from other software engineers. - This project and idea is not prioritized as I am currently the only one working on it and I hope it will help us and also others and increase productivity. - We are putting this out there as an organization, but priorities can change quickly and the CI/CD tasks I am developing are mostly done in my spare time. So please don't expect this to happen in a short time or even be fully completed. I would be very happy if some ppl will join the development process and might be open to discuss some technical details for this. I hope this topic is not to off-topic, but I think the CI/CD part is very important today and it can increase a lot of quality and push productivity. Thanks :)
Last updated: 2024-03-28

Post by alexschooneveld on OPC UA PubSub SL 1.3 — UADP WriterGroup with assigned PSS.SecurityGroup still publishes plaintext ^{CODESYS Forge talk (Post)}
I am currently investigating an OPC UA PubSub connection over UDP. When I don't use encryption, the publish and subscribe are working correctly. But with encryption it does not. Environment OPC UA PubSub SL 1.3.0.0 (namespace UADP) OPC UA PubSub Security 1.3.0.0 (namespace PSS) OPC UA PubSub Base 1.3.0.0 (namespace PSB, incl. PSS.SecurityGroup / PSS.CONFIG) Programmatic PubSub in a CFC: UADP.Configuration → UADP.Connection → UADP.writerGroup → UADP.writer → writerDataSet, plus a CyclicCall gated by xEnable. Goal: publish secured UADP, SignAndEncrypt, policy PubSub-Aes256-CTR. What I do (one-shot, before xEnable := TRUE): fbSecurityGroup.SetInitialValue( 'http://opcfoundation.org/UA/SecurityPolicy#PubSub-Aes256-CTR', PSB.SECURITY.SIGNING_AND_ENCRYPTION); stSecurityCfg := fbSecurityGroup.GetConfig(eErrorID => eError); // eError=NO_ERROR, udiEncryptionKeySize=32 eError := fbSecurityGroup.SetSecurityKeys(udiTokenId, ADR(abyKey), SIZEOF(abyKey), 2436001000); // eError=NO_ERROR, SIZEOF=68 // writerGroup.itfSecurityGroup := fbSecurityGroup -- set in the WriterGroup block's Parameters (a per-scan code write got overwritten) What I verified eError = NO_ERROR after both GetConfig and SetSecurityKeys; udiEncryptionKeySize = 32. Key length = 68 bytes (signing 32 ‖ encrypt 32 ‖ nonce 4). itfSecurityGroup is set via the WriterGroup's Parameters (so it isn't clobbered each scan). Init runs before xEnable (the writer doesn't run with xEnable=FALSE). The UADP.writerGroup FB exposes only itfSecurityGroup for security — no SecurityMode/MessageSecurityMode property. Result: the published datagrams are still plaintext — ExtendedFlags1 = 0x01 (security bit 0x10 clear), no security header: b1 01 29 00 0f 16 00 … (PublisherId 41, WriterGroupId 22, RawData, no security) Questions With UADP.writerGroup, is assigning a configured + keyed PSS.SecurityGroup to itfSecurityGroup sufficient to enable message security, or is there an additional step/property/method to switch the WriterGroup to SignAndEncrypt? At what point in the WriterGroup lifecycle is itfSecurityGroup read? Must it be assigned/keyed before xActive, and does the group need a stop→start to pick it up? Is there a required call order, and does SetSecurityKeys need to be called once or repeatedly? Should security be configured on the Connection/Configuration level rather than (or in addition to) the WriterGroup? Is there a working example of secured (SignAndEncrypt) programmatic UADP publishing with this library, or a known limitation in 1.3? How can I read back at runtime whether security is actually active (via itfDiagnostics or similar)? Additional information I can confirm that the consumer side works — i.e. a standard subscriber decrypts the same keys fine — so the keys/profile aren't the issue. The Wireshark capture of the published message is: 0000 b1 01 29 00 0f 16 00 df 0d bb 25 01 00 0e 00 1b ..).......%..... 0010 0e 00 00 00 00 00 00 00 ........
Last updated: 2026-06-22

Post by alexschooneveld on OPC UA PubSub SL 1.3 — UADP WriterGroup with assigned PSS.SecurityGroup still publishes plaintext ^{CODESYS Forge talk (Post)}
I am currently investigating an OPC UA PubSub connection over UDP. When I don't use encryption, the publish and subscribe are working correctly. But with encryption it does not. Environment OPC UA PubSub SL 1.3.0.0 (namespace UADP) OPC UA PubSub Security 1.3.0.0 (namespace PSS) OPC UA PubSub Base 1.3.0.0 (namespace PSB, incl. PSS.SecurityGroup / PSS.CONFIG) Programmatic PubSub in a CFC: UADP.Configuration → UADP.Connection → UADP.writerGroup → UADP.writer → writerDataSet, plus a CyclicCall gated by xEnable. Goal: publish secured UADP, SignAndEncrypt, policy PubSub-Aes256-CTR. What I do (one-shot, before xEnable := TRUE): fbSecurityGroup.SetInitialValue( 'http://opcfoundation.org/UA/SecurityPolicy#PubSub-Aes256-CTR', PSB.SECURITY.SIGNING_AND_ENCRYPTION); stSecurityCfg := fbSecurityGroup.GetConfig(eErrorID => eError); // eError=NO_ERROR, udiEncryptionKeySize=32 eError := fbSecurityGroup.SetSecurityKeys(udiTokenId, ADR(abyKey), SIZEOF(abyKey), 2436001000); // eError=NO_ERROR, SIZEOF=68 // writerGroup.itfSecurityGroup := fbSecurityGroup -- set in the WriterGroup block's Parameters (a per-scan code write got overwritten) What I verified eError = NO_ERROR after both GetConfig and SetSecurityKeys; udiEncryptionKeySize = 32. Key length = 68 bytes (signing 32 ‖ encrypt 32 ‖ nonce 4). itfSecurityGroup is set via the WriterGroup's Parameters (so it isn't clobbered each scan). Init runs before xEnable (the writer doesn't run with xEnable=FALSE). The UADP.writerGroup FB exposes only itfSecurityGroup for security — no SecurityMode/MessageSecurityMode property. Result: the published datagrams are still plaintext — ExtendedFlags1 = 0x01 (security bit 0x10 clear), no security header: b1 01 29 00 0f 16 00 … (PublisherId 41, WriterGroupId 22, RawData, no security) Questions With UADP.writerGroup, is assigning a configured + keyed PSS.SecurityGroup to itfSecurityGroup sufficient to enable message security, or is there an additional step/property/method to switch the WriterGroup to SignAndEncrypt? At what point in the WriterGroup lifecycle is itfSecurityGroup read? Must it be assigned/keyed before xActive, and does the group need a stop→start to pick it up? Is there a required call order, and does SetSecurityKeys need to be called once or repeatedly? Should security be configured on the Connection/Configuration level rather than (or in addition to) the WriterGroup? Is there a working example of secured (SignAndEncrypt) programmatic UADP publishing with this library, or a known limitation in 1.3? How can I read back at runtime whether security is actually active (via itfDiagnostics or similar)? Additional information I can confirm that the consumer side works — i.e. a standard subscriber decrypts the same keys fine — so the keys/profile aren't the issue. The Wireshark capture of the published message is: 0000 b1 01 29 00 0f 16 00 df 0d bb 25 01 00 0e 00 1b ..).......%..... 0010 0e 00 00 00 00 00 00 00 ........
Last updated: 2026-06-22

Post by struccc on Inheritence of struct, ^{CODESYS Forge talk (Post)}
Strangely reminds me to my struggles... Want to do something "Elegant", reusable, universal, practical... In CODESYS??? 🙃 First of all, before you get too deep into this: If you could find a way, to make a "universal" log entry object, containing the variable length data itself, you wouldn't be able to store them in an array, or access them like an array, or pass them by value as a type. (please correct me, if I'm wrong, incorrect, or not precise). Because... Basically you can't declare a type with variable memory footprint. This is a very deeply embedded characteristic of CODESYS, and all IEC 61131-3 systems, and it has many reasons behind. And yes, it is a very common trap / mistake, to forget about. So, with a log entry - I guess - it's pretty much the purpose: store data and metadata together, and then handle it in a uniform way. There are ways to handle this, really depends on what is the purpose. For example: 1. Entries with fixed length (Maybe it is not as evil as it looks for the first time. Depends on the situation, but definitely the fastest and easiest code) You can have your base object, with an internal, fixed length string or byte array variable. I would go with a string, and call it _Data.; And then you can make properties, like As_Bool, As_Int, As_Real... In the 'set' accessors, you can do like: pReal := ADR(_Data); // POINTER TO REAL As_Real := pReal^; In the 'get' accessors, evidently: pReal := ADR(_Data); // POINTER TO REAL pReal^ := AS_Real; Or, can use ANY type, if you are not obsessed with variable / property like access: 2. Fixed length, but nicer First, some disadvantage to any values: - You can only assign values with write access. No literals, constants, etc... - Can only be used as input variable of function or function_block - Therefore, stg you could reach: LogEntry.Initialize (stVariable|rVariable|iVariable|xVariable); Just a quick example (it's funny to play with ANY): Be careful it was not tested. I'm sure can be done better, please feel free to comment FUNCTION_BLOCK FB_LogEntry VAR_INPUT MsgClass : UDINT; // Like DEBUG, WARN, ERR... MsgCode : UDINT; // Like Errors.ERR_FAILED MsgTS : DT; // The timestamp END_VAR VAR _Data : STRING(80); // Our data container... _Descr : __SYSTEM.AnyType; // A standard descriptor for our data, containing TYPE_CLASS, address and size END_VAR METHOD SET_Value : BOOL VAR_INPUT anyValue : ANY; END_VAR VAR I : DINT; diSize : DINT; pStr : POINTER TO STRING; END_VAR // Check what did we receive in anyValue. diSize := anyValue.diSize; // We use constant __SYSTEM.TYPE_CLASS to identify the received data type CASE anyValue.TypeClass OF // Maybe we don't want to store references, pointers... and who knows what else... __SYSTEM.TYPE_CLASS.TYPE_REFERENCE, __SYSTEM.TYPE_CLASS.TYPE_POINTER : SET_Value := FALSE; // For the planned types we will be just fine. TYPE_CLASS.TYPE_BOOL, TYPE_CLASS.TYPE_INT, TYPE_CLASS.TYPE_REAL : SET_Value := TRUE; // Optionally string can be handled separately, maybe we have received STRING(255), but practically it is shorter than 80 bytes... TYPE_CLASS.TYPE_STRING : pStr := anyValue.pValue; diSize := MIN(anyValue.diSize, LEN(pStr^) + 1); // Get the actual size, and rewrite the received structure member diSize := MIN(SIZEOF(_Data), diSize); // Can chop down the received string to our length... SET_Value := TRUE; // Maybe want to play a little bit more here, to narrow down or convert datatypes, etc... // Or just reject any other datatype ELSE SET_Value := FALSE; RETURN; END_CASE // Fail, if the received value is still larger than our container... IF diSize > SIZEOF(_Data) THEN SET_Value := FALSE; END_IF // Here we should be ok, just set up the _DataType structure, and copy store the data IF SET_Value THEN THIS^._Descr.TypeClass := anyValue.TypeClass; // The typeclass is already filtered THIS^._Descr.diSize := diSize; // Set the (adjusted) size THIS^._Descr.pValue := ADR(_Data); // This will not change, just to be sure {IF defined (pou:SysMem.SysMemCpy)} SysMem.SysMemCpy(_DataType.pValue, anyValue.pValue, TO_UDINT(anyValue.diSize)); {ELSE} // An ugly replacement MemCpy FOR I:=0 TO diSize - 1 DO _Descr.pValue[I] := anyValue.pValue[i]; END_FOR {END_IF} // Otherwise, in case of failure maybe better set an empty value (overwrite the former data descriptor) ELSE THIS^._Descr.TypeClass := TYPE_CLASS.TYPE_NONE; THIS^._Descr.pValue := ADR(_Data); THIS^._Descr.diSize := 0; END_IF METHOD GET_Value : BOOL VAR_INPUT anyValue : ANY; END_VAR VAR I : DINT; END_VAR // We just have to serve the data, using the __System.AnyType structure received // Roughly we can say: IF anyValue.TypeClass = _Descr.TypeClass AND anyValue.pValue <> 0 // This should not be possible, already taken care of by Codesys (?) THEN {IF defined (pou:SysMem.SysMemCpy)} SysMem.SysMemCpy(anyValue.pValue, _DataType.pValue, TO_UDINT(MIN(anyValue.diSize, _Descr.diSize))); {ELSE} // An ugly replacement MemCpy FOR I:=0 TO MIN(anyValue.diSize -1, _Descr.diSize - 1) DO anyValue.pValue[I] := _Descr.pValue[I]; END_FOR {END_IF} // Just to make sure, that our string is terminated... IF anyValue.TypeClass = TYPE_CLASS.TYPE_STRING THEN anyValue.pValue[anyValue.diSize -1] := 0; END_IF GET_Value := TRUE; RETURN; END_IF // ... But can play more CASE anyValue.TypeClass OF TYPE_CLASS.TYPE_WSTRING : ; // Could do conversion TYPE_CLASS.TYPE_XSTRING : ; // Wow, I have to figure this out TYPE_CLASS.TYPE_PARAMS : ; // BTW, what is this, how to use? TYPE_CLASS.TYPE_ANYNUM : ; // ... END_CASE Be careful it was not tested. I'm sure can be done better, please feel free to comment 3. If you really want to do entries with variable size In a standard environment, it would be similar to the previous, except you dont have the container variable _Data, just use a pointer, practically _Descr.pValue At Initialize (SET_Value), you have to allocate the memory, would be easy with SysMem.SysMemAlloc - nowadays with SysMem.SysMemAllocData -, and you make sure to release it after use with SysMem.SysMemFreeData... SysMemAlloc was already hidden. The problem with this, that sooner or later your application will totally fragment the dynamic memory, and fail... So should look for some form of dynMaybe MemUtils.MemoryManager (I am not sure what is the status and the future of it). 4. You will end up by a LogEntry Factory ... 5. You could still have a look at this IEC Snippets BTW, Standard Codesys Logger is not a bad choice either. If you are really interested, I share some more code / library.
Last updated: 2025-03-09

Post by imdatatas on MC_CamIn did not work properly with SMC_FreeEncoder on SoftMotion 4.17.0.0 ^{CODESYS Forge talk (Post)}
Hello, I am facing a problem with the new Softmotion 4.17.0.0 version. Has anyone encountered a similar problem, what is the solution? I would be happy if you could share it. Problem description: -- "SMC_FreeEncoder" encoder axis is the master, -- The motor of the servo driver on the EtherCAT bus is the slave axis. -- When the MC_CamIn block executed, the InSync output is activated. However, although the master encoder axis position value changes, there is no movement in the slave servo axis! Test steps: 1-) EtherCAT servo axis installed, configured and motion test was performed with MC_Jog. No problem. 2-) Softmotion general axis pool > SMC_FreeEncoder was added and pulse amount configuration was performed. No problem. 3-) Incremental encoder actual count value was transferred to the "SMC_FreeEncoder.diEncoderPosition" variable as DINT under the ethercat task in every cycle and the encoder axis position value was observed. No problem. 4-) A simple CAM table with a 1:1 ratio was created under the project tree. (For example: Simply, when the encoder rotates 1 turn, the motor will rotate 1 turn.) 5-) The SMC_FreeEncoder axis enabled with MC_Power and brought to the StandStill state. 6-) The MC_CamTableSelect block was run with default input values ​​(all absolute) and only the Cam table name was specified. The Done output was seen successfully. No problem. 7-) The MC_CamIn block was activated with default input values ​​(absolute) and only the master encoder axis name, slave servo axis name, CamTableID input pins was specified and then "Execute" input set to TRUE. 8-) The InSync output information of the MC_CamIn block observed as TRUE. However, although the encoder axis value changed, the position value of the slave axis did not change at all, it did not move. It always remained at 0.0mm. 9-) When I repeated the same steps above, only changing the master axis to SM_Drive_Virtual instead of FreeEncoder and gave movement to the virtual axis, this time the slave axis moved successfully. However, when the same steps and operations are performed with the same IDE just downgrade SoftMotion version from 4.17.0.0 to 4.10.0.0, everything works normally and without problems as expected in MC_CamIn block with FreeEncoder master. (By the way, The used IDE version is Codesys V3.5 SP20patch3.) Best Regards Imdat
Last updated: 2024-11-11

Post by brell on Automatic xExecute NBS.TCP_write ^{CODESYS Forge talk (Post)}
I've recently started experimenting with CODESYS for a project and am fairly new to it. I'm currently working with Function Block Diagrams (FBD) to set up TCP communication between a server and a client, where the client is implemented as a Python script. Once the communication is established, my connection status changes to True, which is the expected behavior. My challenge arises with the TCP write module, which requires the xEnable_write flag to toggle between True and False. If xEnable_write remains True, the module only performs a single write operation. To address this, I introduced a falling edge trigger (F_TRIG), expecting it to help in toggling xEnable_write and it does, However, I've encountered an issue where in the beginning after connxion established I need to manually set xEnable_write to True for the system to work as intended. I'm looking for a way to automate this process so that xEnable_write becomes True automatically upon establishing a connection . Initially, I tried setting xEnable_write to True from the start, but this approach didn't work well since it left the flag permanently True, preventing further toggling. I also experimented with using a TON timer, but I faced similar issues. I am seeking a solution that automatically toggles xEnable_write between True and False after a connection is established, ensuring continuous write operations without manual intervention. Any advice or guidance on how to achieve this would be greatly appreciated."
Last updated: 2024-03-05

Post by jinlee on Reading Camera Feed in Codesys v3.5 webvisu web element browser ^{CODESYS Forge talk (Post)}
Hi guys, I have been trying to use web browser element in the visualisation to connect with my IP camera. From the past few weeks, I have not been successful of doing it. I thought it would be very easy to just connect to the ip address, but apparantly it is not. I am using WAGO PLC PFC200 and my PC as a webvisu. or else can you guys please advice me on which kind of camera should I use as a CCTV system in my project instead of IP Camera. Ideally, I want multiple web browser elements to browse my IP Cameras in one frame. Kind regards, Jin.
Last updated: 2024-09-16

Sort by relevance or date