FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
12-20-2023 09:08 AM
Hello,
when debugging, there is always a big time delay between 2 steps since some time. If doing one step (F10) you have to wait 2...5 seconds or sometimes longer. If doing one cycle (F5) ist takes up to 10 seconds.
I don't know what happened. I've never experienced something in earlier times. In general, by pressing the key it jumps to the next line without time delay.
I reinstalled ctrlX Works v1.20.5 but it didn't change anything.
Clear / clear all doesn't help.
Can someone help? It's really annoying when debugging.
Solved! Go to Solution.
12-20-2023 12:43 PM
Hello alink,
could you please describe your case and the changes a bit to get an impression about the rootcauses. Otherwise its hard.
or leave some describing screenshots.
former version of PLCEng? Update of the same program done? Functional working and just the debugging w/o expected behaviour?
Changes on the Tasks can be neglected.
Bye and happy xmas.
12-20-2023 03:11 PM
an example:
Breakpoint at line 13
Doing one step (pressing F10) needs about 8 seconds (real life time)
Now in line 14
Doing one more step takes about 5 seconds (real life time).
Now in line 15
and so on....
Another example:
In line 13 there is read out the time -- seconds:
1st it is on 46 seconds
Doing 1 process step (F5) the seconds are on 54 seconds --> means it took 8 seconds long!
The task istself is set on 25ms
CtrlX is runnung without any issues in RUN. No time issues or corruptions or anything.
If beeing online with Engineering, no problem with online monitoring or anything.
Just when debugging. I don't know what happend. After updating on v1.20 (in November) there was no issue, but suddenly there is such a big time delay.
Happy Xmas
12-20-2023 04:02 PM
Hello alink,
would you mind to check without having the gvl published as symbol var to the datalayer? just an assumption from my side.
Bye, available next year again.
02-29-2024 08:13 AM
Are there any news? Is this still an issue? Or could you post a solution and close the topic?