Yesterday I had the basic driving robot with two large motors, but I could not get both motors running at the same time. I had the tank control programming block, with both motors set to 50% and when running the program both motors would start and one would continue spinning, but the other would stop after only 1 or 2 degrees of rotation.

First I thought it was a problem with the motor, so I replaced it with another motor from another set, but the problem remained. When I switched the ports it was the other motor that would not keep running. I tried different ports, changing the cables and restarting the brick but nothing helped. Checked the rechargeable battery to see if it was a power issue, but that was full. I did this in a class with several other EV3 sets using both large motors and none of the others had this problem.

I then used the programming block for a single large motor and tried both separately and that worked fine. But when I put two of those blocks after each other to start the motors sequentially again the second would not run after an initial click.

When I wanted to troubleshoot it further after I got home everything worked fine, which makes it even stranger. That also suggests it was not the battery box as mentioned in this post.

So I hope maybe someone has seen this before and can tell me why this happened and what to do should it happen again.


EDIT: I found the faulty EV3 (it was number 9, not number 6....). So I was able to do more troubleshooting. Attached a screenshot of the various programs I tried with comments.

It looks like port C is consuming more power than the other ports (motor runs at a significantly higher rpm). And this shuts down any motor running at the same time through one of the other ports. combining two of the other ports (e.g. A and D) works fine.

Any thoughts on how this can happen?

enter image description here


  • Hi jboss and welcome to Bricks.SE! Can you post a screenshot of your program, so that we can see what exactly is happening?
    – zovits
    Dec 19, 2019 at 9:10
  • I'm not 100% sure it was like this (it was yesterday and everything is removed and taken apart again) but it was the basic driving robot.
    – jboss
    Dec 19, 2019 at 11:34
  • Maybe try another battery pack? Dec 19, 2019 at 18:42
  • I tried another battery pack, no effect. I also tried resetting the brick, no effect. But when I used motor control from the menu on the brick itself I could run both B and C simultaneously.
    – jboss
    Dec 20, 2019 at 8:35
  • And another possible cause, I updated the firmware of the brick, but that also made no difference.
    – jboss
    Dec 20, 2019 at 8:46

2 Answers 2


Most people with port problems have port C failure. I had similar issue. In my case it was factory defect: SMD chip (U26 on board, see image and HW dev kit pdfs) was soldered with a twist and had two legs broken, but they touched the chip and sometimes signal was getting through. They are used for tacho input. So in some modes when it runs fullspeed it works OK (remote control or built-in motor control), but when it is required to turn for degrees or rotate with a given speed it just spins fullspeed without a stop since it does not getting tacho from the connected motor.

buggy board

I replaced the chip (74HC2G14GW-G) and now everything works fine. I don't think they solder chips by hands, so it could be some defective batch.

  • When I saw the same thing with another brick I figured out that the plastic shell is crushing the chip. It holds PCB right in the place of U26, which it right in the middle of the side. Bad engineering :( Had to remove the fixer. Nov 18, 2022 at 12:23

In the mean time Lego has confirmed that the brick was broken and replaced it.

  • Did this resolve an issue with driving motors as well?
    – Alex
    May 26, 2020 at 11:58
  • Cheers for the update jboss, glad you were able to get to the bottom of it, and LEGO replaced the faulty item. May 27, 2020 at 15:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.