Welcome to Synthiam!

The easiest way to program the most powerful robots. Use technologies by leading industry experts. ARC is a free-to-use robot programming software that makes servo automation, computer vision, autonomous navigation, and artificial intelligence easy.

Get Started
Asked — Edited

Freezing Ezb And Ez Builder ≫ I Have No Idea What Can I Do

Sometimes my EZB works correctly.
But sometimes the ARC freeze.

First you see in my video i start EZ Builder.
Then i start a script for smartarrange all Windows and tabs.
Then i start my robot.
When i use some RGB scripts and moving servos,
he lost the connection and the ARC freeze.

I can reproduce the error.
Start the robot, change a lot of RG an Servos to same time.

You see in the video at the first, the bugreport is functionally.

After freeze, the ARC cant closed and used.
He is complete out.

Is this a problem from my EZB, my computer or the EZ Builder?
I have no idea, what i can do.

Pls activate subtitles. i have wrote english in the german subtitles.
I hope for help.
Thanks to all.

A videa say more as 1000 words.


Upgrade to ARC Pro

Harnessing the power of ARC Pro, your robot can be more than just a simple automated machine.

You could add the Benchmark tool from the General section of the controls and try to send say 1000 commands from each of the 5 tasks. Watch the processor utilization. With that machine it should be pretty low. It will tell you how many requests per second the EZ-B is able to run at for each of these 5 tests. See if it locks up.

Another question is this... How are you connecting to the EZ-B from the computer? Are you connecting via your network or are you connecting directly to the wifi on the EZ-B. In any event, I would try to switch it and conduct your tests again. It might be an issue with the network card in the computer getting flooded or something like that. When the lockup occurs, does the wifi also disconnect and then reconnect?

One more questions is, are you using the EZ-B V4 or the EZ-B V4 1/2? You can tell by looking at the EZ-B. If you see the bottom of a silver chip just above the camera port then it is the 4 1/2. if you see nothing except the board, it is a 4.

Another thing actually... Make sure that the Camera and the I2C connector are plugged in well and are not getting pulled loose when doing your movements. I don't think this is the issue but it is worth a check.

These are just my thoughts based on what the video shows. I don't know for sure.
Thanks for the fast answer.
I try my best.

I have add benchmark and try the test with 1000 commands.
Read ADC took 00:00:16.6238631 to execute 1000 commands.
60.15 commands per second.

Set servo took 00:00:00.0836563 to execute 1000 commands.
11.953.67 commands per second.

Set servo took 00:00:00.0925681 to execute 2000 commands.
21.605.72 commands per second.

Set Digital took 00:00:00.3230272 to execute 1000 commands.
3.095.71 commands per second.

Read Digital took 00:00:15.9356775 to execute 1000 commands.
62.75 commands per second.

In the test 2, 3 and 4 i lost the connection after 5-10 seconds.
Test 1 and 5 was running complete.

First i was connected the EZB with my home network.
After the problems i have try direct the network from the ezb.
Actually Iam connected with the EZB directly in wpa2 and i have try 2 WLAN USB and
the WLAN from my Dell computer.

I use Win10 64bit.

I have the EZB 4/2

The Cables from the camera and the head are correct use.
I can reproduce this error with other servo too.
Those from the diagnostic tool are good.

Try to do the same thing with the camera turned off and see. What resolution do you have the camera set to in ARC?

I just saw the "In the test 2, 3 and 4 i lost the connection after 5-10 seconds." sentence. I missed it because I was looking at the numbers I guess.

Is the camera turned on when you run these tests?
Another thought is that maybe because the cables are bundled together, one cable may be causing interfering with the camera or I2C cable. You might try to unbundle them and see if it still happens.
When the software becomes unresponsive, is there a red led permanently lit on the ezb controller?
When i lost the connection in the benchmark tests,
my computer hold the Robots network and a green light is blinking on the EZB very fast.
I'm confused - does ARC freeze when benchmark test is run or when the project is run?

This post is regarding the project freezing ARC. My question about the red led staying permenantly lit is related to that question. Please answer the questions related to the post only, and we'll figure this out:)

Also, can you post your project so I can take a look?

I'm leaning toward 1 of 3 things...
1) the ezb v4/1 is not being able to process the commands quick enough. Solution: upgrade to /2 as suggested in your other duplicate post

2) the battery/power is browning out. However, I doubt that because you're not using very many servos

3) the rgb eyes in the humanoid head connection is lose and causing the i2c to lock up (which is in relation to the red led question)

So let's start with the red led question. If you can answer that, then we can move on to the others.
One more thing to look, that head moves around very fast and at all angles. Look for broken or loose wires around the head area going to be eyes.
First thanks to all for your great help.
Apologies for misunderstandings

Benchmark was unknown to me before this post.
I used it the first time.
In the test I lost only the connection.
ARC works here correctly and dont freeze.

Now to your question DJ Sures.

My once and actually project is EZRI.

When the ARC freeze, the robot freeze too.
The same blue light is shining for normaly connection.
The Robots network is connect with my computer,
but i cant connect to the EZB again.
I must turn off the robot.
ARC can only abort with taskmanager.

I have the EZB 4/2 from my JD bought in November.
Its exactly this version.
I have open this and see the silver chip.

Do you mean this upgrade for my EZB?

My battery is a 5400ah Lipoakku with 25c.
I think this is not the problem. ;)

I have open the head and checking the connections.
This is safe.

Is the using from the head to fast for the connection?
When i limit the speed for the ports (D6,D7) from the head in the "init",
the speed with this control from the handy is same as without limit.
So i must found a another way to control this.
Excellent - that answers the question and we now know what is causing it.

The EZ-B is actually locking up. The EZ-B can only lock up when i2c is disrupted. So, the easy fix is to verify the connections of the RGB LED Eyes. Follow these instructions...

1) Disconnect and remove the humanoid head from the robot

2) Use a number 2 Philips screw driver to take the humanoid head apart

3) Locate the RGB LED PCB

4) Disconnect the i2c cable from the PCB

5) Examine the cable to see if any wires are lose or pins bent. What you're looking for is to ensure the plugs on the end of the cable look securely fastened and nothing out of the ordinary

6) Firmly reconnect the i2c cable to the RGB LED Eyes

7) Re-assemble the humanoid head

8) Add the humanoid head back to your robot


Because the head is moving very rapidly with the servo control, the i2c cable connection is being disrupted. This is causing the EZ-B to lock up.

I also recommend adding a ServoSpeed() to the init of the humanoid head servos, much like how the JD project does.


# Init servos to starting position
Servo(d0, 90)
Servo(d1, 90)

# Init speed of servos
ServoSpeed(D0, 2)
ServoSpeed(D1, 2)

The JD project adds a ServoSpeed() to the humanoid head for multiple reasons:
1) slows down the servos to remove jerkiness and maintain visible camera image
2) prevents i2c cable from being pulled rapidly in different directions and loosening the connection which may cause ez-b to lock up

Also, you do not have a EZ-B v4/2 Comm Upgrade. The silver chip has nothing to do with the difference between versions. You have a COMM 1 EZ-B, not a COMM 2 EZ-B. Your EZ-B is the first version, which should be okay for your application. As i believe the i2c is the culprit.

User-inserted image

Here is your log file, which shows the COMM version. The EZ-B v4/2 Comm Upgrade has explicit details on how to check what version you have, which does not mention anything about "look for silver chip", because that's irrelevant to the version, as all versions have silver chips.


28.04.2017 07:37:14C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBScreen Resolution: 1600x900 (96x96 dpi)
28.04.2017 07:37:14C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBVersion: 2017.04.16.00
28.04.2017 07:37:40C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBAttempting connection on
28.04.2017 07:37:40C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBConnected to
28.04.2017 07:37:40C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBReports EZB v4 OS With Comm 1
28.04.2017 07:37:40C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBEZ-B v4 ID: 63-50-0-0-46-255-57-58-58-38-38-40
28.04.2017 07:37:40C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBSetting battery monitor voltage: 7
28.04.2017 07:37:40C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBSetting battery protection: True
28.04.2017 07:37:40C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBSetting i2c rate: 100000
28.04.2017 07:37:40C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBEZ-B voltage is 7.929577002
28.04.2017 07:37:40C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBEZ-B temperature is 25.28782105101315840C

However, i do not believe the limitation is the ez-b. It is the i2c, as i have previously stated in this response. So, t here is no reason to upgrade to a EZ-B v4/2 Comm Upgrade at this point. The EZ-B v4/2 Comm Upgrade is 40 times faster, which is good for DIY builders using lots of READ commands.
Thanks alot.
Wow, so a little cable and so much problems.
You are great.

I have disassemble the head.
Remove all cables and set new.

Now i have check my init.
I have already installed servospeeds in the init file.
The sleep command i have forgotten.

Then when i make AutoPosition with speed -1 so become the servos a reset.
I have found and fix this problem.

*stress* *stress* *stress*
Bah its so daisy.

Thanks to all for this great help.

This is a nice community.