nicolson
Canada
Asked
— Edited
Since the EZ revolution updates, EZ builder keeps freezing each time it connects to the robot. It would either take a very long time to run a program or freeze to the point of disconnecting the robot. Because of this the robot is no longer operational. Has anyone experienced this issue? Here is a link to one of the programs:
https://www.dropbox.com/s/yiyc39p2ye1vy5z/ProxyNewServo.EZB
It works fine before connecting, but as soon as the connects it keeps freezing.
A "Dbug " script would be very helpful! Whats happening with the Blue led and the red Bluetooth led? have you tried a different Digital port? Also what Version are you running ...just a few questions!
for now...
Both LEDs work fine, I am using EZ b version 3. I run ARC on a windows 8 samsung tablet.
Hey hey
don't blame innocent little ARC! It's working for a billion other people. Revolution updates don't affect the v3 users. As for the lockups, we should first look at your program. Second, we can look at Windows - as windows is usually the culprit. Mostly the software is affected by virus scanners and other Helper type software that do more harm than good.
I'll take a look at your project when I'm in front of a PC sometime this weekend
You may also try to run ARC as the administrator.
A Cheap Bluetooth dongle caused freezes for me... Replaced it with a more expensive one and haven't had a freeze since... Never mind, just realized you have built in Bluetooth....
Make sure you have the Microsoft Bluetooth stack.(driver)
Sorry DJ! I didn't mean to blame ARC. I am well aware that it's the best robot control platform in the world. And thank all of you guys for your prompt support. Later after work I'll try your suggestions and let you know what happen
@nicolson Well, that was interesting! I opened your script with an extra EZ-B I had and after connection, it spoke "That was refreshing" and then sure enough, ARC froze. I'm running Windows 8 on a desktop with ARC 2.7.14 (the latest as of today), I don't have any other issues with ARC or this EZ-B.
I don't fully understand everything your script is doing, but you do have a lot going on. Was this a script that worked fine then without any changes caused the issues? Or did you make modifications and then it caused this issue? Can you run a prior version of your script without issue?
My best guess is its something in the startup routine that windows does not like. Perhaps the speech routines? Could you explain what the scripts does at startup?