Mine has done that on occasion, I'm yet to pinpoint the cause though.Usually its fine but every now and then, for no real reason it'll do that.

Good to know I'm not alone. Misery loves company.

It's not a big issue to my (yet) but it does make me restart ARC sometimes so I can get control of that script again.

Stopping is when it's stopping. You've asked the script to stop using a control command. If the script you asked to stop is doing something, it will be in stopping state until it stops.

Imagine driving toward an intersection and the light turns red. When you press the brake, you don't stop to a halt - instead you begin stopping... Eventually you stop.

I'm guessing Dave has the same issue as me on this but it will say stopping for what seems like forever (well, until I close ARC), I've left it for a good 20-30 minutes before and it's never stopped. I haven't found the cause and when I try to force the issue to happen it doesn't... When I figure out how to replicate the error I'll give more details but as of now all I know is that sometimes it will be forever "stopping" but no idea why.

It happens with ControlCommand and manually clicking stop in my experiences. I guess it's when it's in the middle of doing something like a loop or moving a servo or something but honestly I have no idea.

If you can replicate or provide your project then I can take a look

Rich is correct. Just to clearly it more; the actions the script are running when the stop command is issued (from whereever) will stop. However the Start/Stop button on the control window where that script resides will show "Stopping" and stay that way till I restart ARC. While "Stopping" is showing on the Start/Stop button I cannot operate it. However I can get into the control through it's settings button and change things.

In my project this will happen every time to the "Radar Rutine 1" control after the Init Script runs and it cant connect to my 3 EZB's because they are off or out of Bluetooth range. Not sure why that "Radar Rutine 1" control is effected at start up as the only thing that calls it is a script in the Speech Recognition control (I think).

It does happen to other controls sometimes also and other then the example given above seems random to me. Cant find the common event that causes it.

Here's my project (sorry, it's a little messy. I need to clean it up a bit and start using the Script Manager):

B9RobotControl.EZB

Thanks for offering to look into this, Dave Schulpius

Have you used the Flow control under Scripting to view where "Radar Rutine 1" is being controlled from?

OK, after looking at my Script Flow chart I see that "Radar Rutine 1" is called by the "Kill" script with a command: ControlCommand("Radar Rutine 1", ScriptStop) That "Kill" script is called by the Init Script at ARC start up and stays running as a loop looking and waiting for a switch to close.

Could it be that if a control is not running and a stop command is sent to that control it will keep showing "Stopping" on the Start/Stop button. would it also hold that button hostage trying to stop a script that is already stopped?

Just thinking it through here. Dave Schulpius

If this is happening mostly due to Bluetooth not connecting, then use the IsConnected() function after the connection attempt.

Now, just to make sure... Does your version have an IsConnected() EZ-Script command? To be honest, my brain is quite a mess right now and i'm not sure how recent that command is. It might just be in my beta version lol

Yes EZ-Script has IsConnected()

I know all about brains being in a mess, that's why I've never pinpointed this issue with my projects - working on so many projects and scripts has it's downsides... I don't even know which projects of mine have had this error.

No, sorry DJ. I don't think it has anything to do with connecting to the EZB board. Quite simply, It seems to happen when either I or a script tries to stop another script that is not running.

Ya know a stiff shot of Jack Daniels will straighten out your head (or maybe there was too much of it last night?).

Interesting , I concur with Dave and Rich having the same issue, again not knowing what causes it , other then a long running script, possibly ( anecdotalable ) to do with the VR. Long before I received my EZ board and was playing with the EZ software and NOT trying to connect it was "not stopping"...I just cant recall which Script I was running at the time arrgh