Is This Normal Propeller Tool 2.4.1 Behavior?
CJMJ
Posts: 225
in Propeller 2
So I load a program on the P2 Edge. Everything is working fine, so I leave it running. I come back later to modify the code and the first thing I do by habit is press F7 "Identify Hardware..." to make sure I have the COM channel and my running program stops running. I obviously don't understand how this check is done, so for the old hands here, is this behavior normal? Just pressing F7 will kill a running program?
Comments
Yes, this is normal. Also if you remove your USB cable and plug it back-in that will cause Propellers both P1 and P2 to reset.
Yes, "identify hardware" reboots P1 and P2.
Yes, it has to reset it in order to have a conversation with it, to find out what it is.
Ok. Good to know. Thanks. I'll have to write that down somewhere.
Ultimaker Cura when started with Propeller 2 attached resets it periodically. Also any USB activity (switching on the USB printer) also resets a connected P2. Too many programs mess with USB connections... I think Cura searches for 3D printer connected on all possible ports and this resets P2.