mondinmr

My mistake! Now is an external package. I found in installer. Sorry

What happened to Python? I’ve just installed version 3.5.21.3 of the CODESYS development environment. I’m coming from 3.5.19.5. What happened to Python scripting! We rely heavily on it for the automatic generation of thousands of lines of code! It seems absurd to me that such an important feature has been removed!

Good morning, I’ve been using the Collection library for a long time, mostly with Stack, LinkedList, and List. From your examples I was able to manage the different factories, even for custom elements. Now I need a hashtable, but with this object I’m running into a lot of random access violations. If I append something inside FB_Init after constructing the hashtable, it crashes, even though the list was already created. If I only create the hashtable in FB_Init and append afterwards, it usually works....

Good morning, I’ve been using the Collection library for a long time, mostly with Stack, LinkedList, and List. From your examples I was able to manage the different factories, even for custom elements. Now I need a hashtable, but with this object I’m running into a lot of random access violations. If I append something inside FB_Init after constructing the hashtable, it crashes, even though the list was already created. If I only create the hashtable in FB_Init and append afterwards, it usually works....

We need to use two CIFX 50E-DP cards in two Linux PCs running CODESYS for Linux SL (the machines are x86). Has anyone experienced any issues? Do these cards work reliably under Linux?

Double message sorry

I noticed something strange in the trace: one of the variables (specifically parts.servoFeeder.m_pathGen.m_acPos) is showing an absurd or unrealistic value—something around 4E+18. However, when I check the same variable in the watch window, it shows a normal and expected value (around 506). Do you know why there is this discrepancy between the trace and the watch? Could it be a bug in the trace tool? Thanks in advance!

I noticed something strange in the trace: one of the variables (specifically parts.servoFeeder.m_pathGen.m_acPos) is showing an absurd or unrealistic value—something around 4E+18. However, when I check the same variable in the watch window, it shows a normal and expected value (around 506). Do you know why there is this discrepancy between the trace and the watch? Could it be a bug in the trace tool? Thanks in advance!