Piston Tracing/Debuging


#1

Is there a link to read about the trace function? What colors mean? what does the commented numbers that appear at the right of some rows mean? etc. etc.

Can you do breaks, steps when debugging?

And while talking about debuging, is there any way to manually trigger a device for testing purposes? Instead of having to stand up to trigger a motion device simulate the motion from webcore?

I know I know… lots of questions :blush:


#2

this seems like a question for @Robin :slight_smile:


#3

Post up an example that you are familiar with and I’ll explain the trace colors. In short though green is true and red is false. Blue shows on anything that was triggered/activated/evaluated.

Commented numbers are to help with the logs. So when it says canceling condition 9… you can see what it is referring to in the code.

Not sure about the breaks and steps for debugging.

Yes you can use simulated devices and then trigger those from the ST app. To do this go to ST IDE and click my devices. Add a new device. Fill out the required fields. Then for the drop down find simulated motion/contact/switch/etc. Thrn make sure you include them into webcore like when you first installed all your devices.

Now from the ST app you just have to click the device to use it


#4

Oh OK. So the trace is in fact real-time? I can trigger the pistons and watch it as it happens.

Im liking webcore more and more.

Thanks


#5

Correct trace is real time


#6

Great. Thanks