Germany
Asked — Edited

Freezing Ezb And ARC ≫ 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 ARC. 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 ARC? 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.


ARC Pro

Upgrade to ARC Pro

Join the ARC Pro community and gain access to a wealth of resources and support, ensuring your robot's success.

Germany
#9  

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.

PRO
Synthiam
#10  

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

Test

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.

Quote:

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 192.168.1.1 28.04.2017 07:37:40C:\Users\Stiko\Documents\EZ-Builder\My Projects\EZRI.EZBConnected to 192.168.1.1 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.

Germany
#11  

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.