Frequently Asked Questions

Battery not charging

*Important: As mentioned in tutorials, software terms of use, and box instruction insert, the battery of your robot must be charged before use. This must be the first thing you do before assembling and using your new EZ-Robot. Additionally, do not disregard the "My battery is low" message. Power down the robot when you hear this message. The battery saver was engineered to maintain battery longevity. There are in-depth details regarding care for your EZ-Robot in the tutorials of the learn section.

The smart microprocessor LiPo charger included with your ez-robot will provide diagnostic information to help identify problems. Your smart LiPo charger may flash all three red LEDs in a certain pattern to notify you of what the problem might be. All lessons within the robot tutorials section are important, including this Battery Tutorial. We highly recommend reviewing all lessons for your robot as well as the Battery Tutorial. Below is an overview of the smart LiPo charger diagnostic light patterns...

  1. All LEDs repeat flashing red once, and stopping for 1 second. This means that your battery is connected improperly. Make sure the battery cable fits properly into the charger and is plugged into the port on the right side of the charger.
  2. All LEDs repeat flashing red twice, and stopping for 1 second. This means that your charger encountered an overload or a short circuit. Check your charger and battery cables and make sure that they are in good condition. If any cables are exposed please Contact Us.
  3. All LEDs repeat flashing red four times, and stopping for 1 second. This means that the voltage of a single cell is too high or too low. This is most likely due to leaving your robot powered on for an extended period while the low voltage battery warning was playing. This will over discharge the battery and cause problems like this. If you have this problem you can either try re-balancing the cells at a local hobby store, or purchase a new battery.
  4. All LEDs repeat flashing red six times, and stopping for 1 second. This means that there is a 300mv difference between the voltage of the two cells. This is can be due to leaving your robot powered on for an extended period while the low voltage battery warning was playing. This will over discharge the battery and cause problems like this. Another cause of this issue is a manufacturer defect.

    If you receive this error, wait 30 minutes for the battery to cool down and try charging again.

    If that does not work, remove the EZ-B v4 from the robot and try charging the battery again.

    If the error persists perform the following steps:

    1. Open EZ-Builder
    2. Turn on robot (With nothing connected to the ez-b) (Ignore the battery is low warning for now)
    3. Connect to the robot's WiFi on your computer
    4. Connect to the robot with EZ-Builder
    5. Click the project tab
    6. Press Add Controls
    7. Under the General category, press EZ-B v4 Info
    8. Read and record the "Input voltage" value
    9. Turn off your robot to prevent further battery damage
    10. Contact Us and report the input voltage.
*Note: Damaged LiPo batteries due to neglecting the instructions, tutorials and terms of use do not qualify for warranty replacement. Replacement batteries may be purchased from our store here. To maintain LiPo battery life, be sure to not drain the battery by respecting the battery saver monitor. Follow the directions provided to you in the software's terms of use, website tutorials, and the included instruction sheet.
Return to Top


Roli not moving

There are trouble-shooting lessons for each robot in their respective tutorials & lessons. The Roli robot lessons includes a detailed procedure to help diagnose incorrect wiring connection issues. If the Roli tracks are not moving, perform these diagnostic steps:

  1. Ensure that you are using the latest Roli project included in the latest EZ-Builder installation. EZ-Builder can be downloaded here.
  2. The H-Bridge wires may not be connected correctly to the EZ-B v4. Check the cable connections to the EZ-B v4. See this tutorial lesson for more information.
  3. The wires inside the Roli chassis may be connected incorrectly to the motor or H-Bridge Motor Driver. There is a diagnostic procedure to verify correct wired connections by clicking here for the HBridge Motor Diagnostic Lesson.
  4. All EZ-Robots contain an internal fuse for electrical short protection against fire. The fuse may have been damaged by accidental wiring mishaps. The fuse may be checked by clicking here

Return to Top


Robot not moving correctly or falling over

Incorrect, or "weird" movements with your EZ-Robot can be attributed to a few issues:

  1. Improperly oriented servos. This means the robot servos are connected backward, reverse or in the wrong place. Consult the build instructions for your robot to ensure the servo motors are in their correct place and in the proper orientation.
  2. The servos have not been calibrated or are misaligned. The bracket on each servo should be aligned from the manufacturer to be flat at 90 degrees. In chance that the servo bracket is misaligned, the robot will not have correct joint positioning. Consult the servo calibration procedure for your robot in the Learn Section.
  3. Servo wires are connected to incorrect ports on the EZ-B v4. Each servo has a wire which connects to the EZ-B v4, if the wires are connected to the wrong ports, the robot will move the incorrect joints. To correct this scenario, visit the building procedure for your robot and check the wiring.
  4. Incorrect servo profile or no servo profile loaded for the robot. Some robots, such as JD, require a servo profile to accurately align the servos for high precision movements. If a servo profile was not created, created incorrectly, or not loaded, the robot will fall over or function incorrectly. This can be resolved by visiting the Servo Profile step within the tutorial for your robot in the Learn Section.
The steps below may fix your problem.
First, make sure that your robot is built correctly. Make sure that all of the servos are oriented properly. Compare with the assembly instructions either online

JD Assembly Instructions (Online)

SIX Assembly Instructions (Online)

Roli Assembly Instructions (Online)

or in EZ-Builder in the appropriate example project. Make sure your robot looks exactly like the one in the assembly instructions.

If your robot is still moving incorrectly you need to fine tune your servos. Since not all servos are perfect out of the box, you need to create a servo fine tune profile for your robot configuration. See this tutorial on how to fine tune your servos. This tutorial may apply to all robots, not just JD.
Return to Top


JD locking up, freezing or disconnecting

Antivirus or Firewall Software is the number one connection issue. There are many reports of connection issues with PCs running Antivirus or Firewall Software, such as AVAST, McAfee, Norton or Norton Internet Security. If your PC has Antivirus or Firewall software installed, please disable or uninstall it.

In addition to the tips provided in Robot not moving correctly, issues with JD may be due to the RGB LED eyes not being plugged in correctly or having a loose connection. Ensure that the eyes are plugged into the EZ-B v4 correctly. You can also try plugging the eyes into one of the three i2c ports.

A sign that a connection to the RGB Eyes is causing a disconnect is identifiable when the RED LED on the EZ-B v4 glows continuously and the EZ-B v4 require a power cycle before it accepts another connection. If your JD disconnects and you believe it may be the RGB Eyes, look at the EZ-B v4 and see if the RED LED is glowing.

If resetting the connector of the RGB Eyes fails to work, there is a chance that the connector inside of JD's head for the RGB Eyes may be loose. To check it, use a Philips screw driver and carefully separate JD's head and check the plug on the eyes PCB. Make sure that the wire is not squished or pinched when reassembling the head.

When JD is powered on, the RGB Eyes should initialize with their bootup sequence of blue and white. If the RGB Eyes in JD do not glow when power is switched on, they are either not connected or the cable is damaged and require replacement.

Lastly, to identify if the RGB Eyes are damaged or the cable is damaged, there is one additional diagnostic step. Disconnect the RGB Eyes from the JD's EZ-B v4 and delete the RGB animator control from the JD project. If JD runs correctly after doing so, Contact Us for support regarding a replacement cable for your RGB LED eyes.

More on the red LED topic can be found here.
Return to Top


Servo stop working

A robot servo may have been damaged and/or burnt-out for a few reasons. The following points are common issues that lead to damaged servos. For additional information about how servos work, we highly recommend following the provided Servo Tutorial in the learn section by clicking here.

EZ-Robot servos are designed to fail if there the load is too high. This is no different than you, as a human, attempting to hold yourself in positions that strains muscles. A servo giving out is the same as a muscle giving out. The safety release of a servo is inside itself, to prevent damage from affecting other components, such as the EZ-B or battery.

  1. Improper calibration will cause servos to humm/buzz while holding the robot's default standing position. Ensure the latest EZ-Builder software and EZ-Robot project is loaded for the robot. Also, ensure the calibration process has been executed and the correct saved calibration file is loaded. An incorrect calibrated robot increases the chance of servo failure.
  2. Moving a servo when something is obstructing it from moving. When a servo is given a command to move but it is unable to physically move into the desired position (e.g. telling JD to move his claw to 180 degrees) will damage the servo. Servos do not have a method of reporting that they are unable to move.
  3. High amount of stress/weight can damage servos. The concept is similar to the first point, as weight prevents the servo from moving, this will damage the internals of the servo. The heavier the load, or the further the load is away from the servo, the more stress there will be on the servo. If you are experiencing damaged servos, consider lightening the load.
  4. Putting strain or pulling the servo cable will result in the cables fraying or breaking which will result in a short circuit. A short circuit is protected by the EZ-B fuse, but will still create a burning smell and the heat may melt the plastic housing of the servo. To prevent this, make sure servo cables are loose and not bent at sharp angles.

Return to Top


Order Shipment stuck at a certain step

For convenience, your EZ-Robot order shipment is split into 4 steps:

Step 1 of 4) Awaiting Review - If your order is stuck at this step it is usually because we haven't gotten to it yet. If your order has been in step 1 for more than 3 days, please Contact Us under the Sales & Orders category and we will make sure it gets moving.

Step 2 of 4) Processing Order Details - If your order is stuck at this step it is usually because it contains a pre-order item or an item that is out of stock. Pre-order/Out of stock items on the shop page have red text underneath them stating so. If your order does not contain any of these items and has been in step 2 for more than 1 week please Contact Us under the Sales & Orders category and we will make sure it gets moving.

Step 3 of 4) Preparing Order - If your order is stuck at this step, again, usually because it contains a pre-order item or an item that is out of stock. Pre-order/Out of stock items on the shop page have red text underneath them stating so. If your order does not contain any of these items and has been in step 3 for more than 1 week please Contact Us under the Sales & Orders category and we will make sure it gets moving.

Step 4 of 4) Shipped - If your order is in this step, but you have not received your shipment please check the status of your shipment by inputting the tracking number (The tracking number can be found in your profile under Order History and then by clicking on the order you would like to track. The tracking number should be listed beside Shipping) into DHL's tracking system. If you notice something strange such as the item being returned to the sender or being delivered and signed for even though you have not received it, please Contact Us under the Sales & Orders category and we will help solve the problem.

Return to Top


Jerky movements or disconnecting from WiFi

Your robot may have jerky movements or the WiFi may be disconnecting for one of two reasons. Jerky movements are almost always caused by WiFi saturation (view wifi saturation below). The first, being due to WiFi/Frequency saturation in your area. The second can be caused by the power pin of the EZ-B becoming loose and requires adjusting. It is also important to consider the computer it dropping WiFi, not the robot. Lastly, if this robot is a JD, consider checking the RGB Cable connections to ensure they are secure and refitted. There is a FAQ on this page regarding the RGB cable for JD.

EZ-B Red LED Stays On

The highest cause of WiFi disconnects is when the EZ-B red LED stays on. This is an error that an i2c device has lost connectivity or is not found. This will happen if your project is configured to use to an i2c device that is not connected to the EZ-B (i.e. RGB Eyes, 4-in-1 Sensor, etc.) or the cable connecting to the i2c device is faulty or loose. If the red LED stays lit and a disconnection occurs, this is exactly the issue. Simply identify which devices are or should be connected to the i2c ports based on the project configuration. More on the Red LED topic can be found here

Power Pin Adjustment

The power pin may require adjusting on the EZ-B and body of the robot. This occasionally can occur after prolonged use or repeated insert/removal of the EZ-B. While this is a very rare occurrence, a tutorial has been created to simplify the process. You can identify if the power pin needs to be adjusted because the EZ-Robot reboots by making the startup chime sound rather than a disconnect sound. The power pin adjustment tutorial can be viewed here.

WiFi Saturation

If your robot is making an unexpected disconnect sound during use, rather than a startup chime sound, then you may be suffering from WiFi interference. WiFi networks use specific frequencies which have been defined for public consumer/home use. Because there are only so many frequencies available, home devices share the same frequency. These range from wireless speakers to microwave ovens. This list of WLAN channels are legally allowed wireless local area network channels using IEEE 802.11 protocols, mostly sold under the trademark Wi-Fi. The 802.11 workgroup currently documents use in five distinct frequency ranges: 2.4 GHz, 3.6 GHz, 4.9 GHz, 5 GHz, and 5.9 GHz bands. If your EZ-Robot is suffering from disconnects or WiFi latency issues, consider disconnecting radio transmission appliances in your home. Also, do not run a microwave oven while using the EZ-Robot, as these are common causes for WiFi interference. There is a community forum thread on this topic here. You can download WiFi Info to identify WiFi channels by clicking HERE.

Things To Consider

  • When the connection to the robot drops, does it reboot or disconnect? The difference is in the sound that is made. A reboot will play the startup sound. A disconnect will play a disconnect sound. If a startup sound is heard, this is generally caused by overloading the communication channel -or- by a loose power pin. If the power pin is secure, then consider the data channel. If your project is custom, post on the community forum for assistance and share your project. Someone will help you get up and running!
  • Have you tried different WiFi channels? Perhaps the WiFi channel in question is saturated by other wifi devices. Log on to the EZ-B Web Server and change the WiFi channel. Use WiFi Info to identify channels, it is available for download HERE.
  • Are you using the latest EZ-Builder? We are always making improvements to the software with new features and stability.
  • Lastly, you can always share the project and we can take a look to see if there is something in the project that is causing the disconnect. You can share a project by using the ATTACH FILE button to the right of the forum entry form when editing in the forum. Once you select the file, press the UPLOAD FILE button. That will add the file to your message. Post it in this thread and we'll take a look!

Return to Top


No Audio from EZ-B

The question about not having audio from the EZ-B requires a few diagnostic steps to identify the issue.

No Startup Chime - Can Connect from EZ-Builder

As demonstrated in the Learn Tutorials, the EZ-B v4 will emit a friendly startup chime when switched on. The startup sequence involves the flashing of the status led and the startup chime. If the startup chime is not heard, we must now identify if a connection from EZ-Builder either via Mobile or PC can be made to the EZ-B? If a connection can be made and the EZ-B v4 operates normally, but without audio, then the issue can be easily repaired with a Phillips head screw driver. The speaker of the EZ-B v4 is pressure fit against the case and the PCB. Two springs emerge from the speaker which make a connection to the exposed pads on the bottom of the EZ-B main board. Use a portion of these instructions to separate the plastic chassis from the EZ-B with the 4 screws. Very gently use a pair of small plyers or tweezers and extend the springs a very small amount. Also use a q-tip and rubbing alcohol to clean the speaker pads on the bottom of the EZ-B main circuit board. Re-assemble and your speaker should be operating.

No Startup Chime - Unable To Connect from EZ-Builder

Likely that the EZ-B v4 main board (bottom PCB) has been damaged. If the comm board (top PCB) was damaged, the speaker would verbally inform you of a communications error. Instead, the bottom board is not responding - also, confirm that there is no red LED during startup. The lack of red LED during startup means the bottom board main chip is damaged.

In the likely hood of a damaged main board PCT, you can either replace the bottom board, or replace the entire EZ-B v4. The bottom board can be damaged by a few ways:

  • Static charge is an enemy of electronics. The ez-b v4 took over a year of development and has been designed to withstand as much static charge via grounding and isolation resistors on the signal pins. The ez-b v4 has additional hardware that you will not find on any other micro controller which protects against static charge. However, even with all these preventions, there are still incidents where static will damage the controller. Because this occurrence is rare and also incredibly random, it's difficult to diagnose and isolate an incident responsible.
  • Shorting the pins accidentally. We all make mistakes, and sometimes the power pin is shorted against a signal pin accidentally. This can happen if connecting a servo or sensor and the pins bend and connect. Or this can happen if a screw driver touches the pins. Or even if any conductive surface touches the ez-b v4 pins briefly. All servos and sensors use the same power pin arrangement of Ground, Voltage, Signal (GVS for short). This arrangement puts the power pin in the center of the two, which means it can short either way. If it shorts to GND, the fuse will blow. If it shorts to Signal, the EZ-B main controller will blow. To purchase a EZ-B v4 PCB separately can be requested by contacting us directly.

"Communication Error" - Verbal Message

If the EZ-B v4 startup does not make the startup chime, and verbally speaks of a communication error after powered on for 10 seconds, the top PCB (comm board) has been damaged. The top PCB of the EZ-B v4 is the communication board which contains the WiFi and Web Server. When the bottom board is unable to communicate with the top board, it will inform you with a verbal message out of the speaker. To purchase a EZ-B v4 PCB separately can be requested by contacting us directly.
Return to Top


Red Light Stays On EZ-B and Disconnects

The red LED on the EZ-B is an activity indicator. When the LED is illuminating, that means there has been a data packet received and the EZ-B is processing the packet commands. If the LED stays on, the EZ-B is still processing the command. Normally, a command is processed in milliseconds, which is why the LED flickers when the robot is in use. When the LED stays lit, a command is taking too long to process and will timeout the connection.

The primary reason for the red LED staying on (processing error) is when there is trouble connecting to an i2c device. i2c devices are the eyes of JD, an 4-in-1 sensor, or an RGB 8x8, etc.. Verify the i2c devices are connected and are successfully powering on with the robot.

If you are attempting to run a project which communicates with i2c devices that you do not have connected to the EZ-B, the red LED will stay illuminated and a disconnection will occur. You have two options: 1) Connect the appropriate i2c device to the EZ-B, or 2) Remove the i2c control/script from the project.


Return to Top


Additional FAQs, Diagnostics and Assistance

The EZ-Robot philosophy is focused on sharing knowledge and information from individual experiences. We have prepared detailed step-by-step lessons for the EZ-Robot flagship products in the Learn Section. These important lessons are constantly evolving with updated information based on customer experiences shared with us in the Community Forum. If you have a question, feel free to search the Community Forum or ask a question on the Community Forum to receive assistance by other experienced customers.

"We are only as strong as we are united, as weak as we are divided". The User Tutorial Section enables ez-robot users to create tutorials to share knowledge and experiences. Have you learned something knew about EZ-Robot? Share it by creating a step-by-step User Tutorial and participate in helping others.

Return to Top