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.
Hummzzzz, Well version 2014.2.21 runs the script, no modification needed and no freezing. CPU usage is staying around 5%. @Nicolson - I'd give the newest version a try.
@JustinRatliff I wasn't as fortunate: I tried the latest version but the problem persist.
Darn! confused Probably the only difference between my setup and yours is nothing is connected to my EZ-B. I know that on startup it looks for input from the PING sonar, battery monitor and collision sensors. Some servo routines activate. Voice recognition comes on I think.
Is the problem exactly the same, the app freezes? Or is it just extremely slow? Are you getting high CPU usage when you to go Task Manager? What is the last function that is preformed correct? Does it at least says "That was a good nap"?
The script execution is very very slow, to the point of disconnecting the robot, turning off the blue LED. Yes it says "that was a good nap". 49% percent cpu usage during startup.
It sounds like it's likely to be an issue with a script (or more than one).
Have you got a lot of scripts checking ADC ports quickly? Or a lot of scripts looping too quickly? This can increase the demand that ARC will have and cause an unresponsive computer.
Unfortunately the bluetooth connection can cause something of a bottleneck if you are trying to do too much at once.
Does this happen with all your ARC projects or just this particular project?
I loaded your project and it "kind" of worked for me on an EZ-B v4. However, I noticed it being really really really sluggish. Here are fixes I recommend...
There are 3 controls all using the same HC-SR04 Ping Sensor (radar Scanner, Ping Collision, Distance). There is no need for 3 of those - only use 1. Otherwise, you have a pile of communication requests for redundant queries. Your tablet may be a little slow processor as well, so all of those controls are using up CPU resources. Only use 1.
There is a script called "LightFlashing" and there is no delay. It simply toggles the digital port as fast as the CPU will run. That is going to use up 100% of the CPU. Put a short Sleep() in the loop - perhaps something like Sleep(1000) for a 1 second flash.
There are probably other things but those are the two that popped up right away. Fix those two things and you'll be fine.
I removed the radar scanners and fixed that one loop with a delay, here's the fix: AAProxyNewServo.EZB
How cool is that! @D(octor) J makes house calls
Take two EZB's and call me in the morning!