About nickH

I think you are mixing to things here. There are two ways to test your bundle.  You can install the snap on a real or on a virtual ctrlX CORE. Here you would set the scheduler configuration manually in the webinterface and add your callable. Here you can take a look at the trace logs in the logbook and check if your callable works like you would expect. But you can't hit any breakpoints here. You can debug your bundle inside your build environment. For this type of debugging you don't need a ctrlX CORE or ctrlX CORE virtual! Here you don't have a webinterface for the scheduler. To add a configuration here you would need to insert a configuration for the scheduler like you will find in our samples (solutions/activeConfiguration/scheduler). Hint: This is the same kind of configuration you can also find in the app data of a ctrlX CORE. So you could also download the app data of a ctrlX CORE when you did the debugging type 1 and bring it to the build environment for the type 2.  ... View more

Hello KangZahihao,  Regarding your first question:  The ctrlX COREvirutal is not real time capable. The times you are measuring are not really meaningful. If you want to measure cycle times you would have to do that on a real ctrlX CORE. Also the scheduler on the ctrlX COREvirtual runs in debug mode, because of that. And also the Hardware Watchdog is disabled.    Regarding your second question: No unfortunately I don't know any other way to trace your internal values while running on the ctrlX CORE.   Best regards,  Nick ... View more