Almost definitely related to the motor sensor. It's sending bad data (or no data) back to the brain brick which is why your program slows the other motor. I assume your program is not running each motor independently, but using tank mode or at least running them together as a pair somehow. The bad motor sends no data and the good motor gets slowed when the brain tries to keep the robot going straight.
We had it during our FLL Competition. Our Team ended up switching their motor 5 minutes before the end of the 3rd game. It would work and sometime not!
So I have had this issue show up on 3 more motors. All of the motors are part of the N3 batch. Two were 49N3 and one was 50N3. I didn't check the batch #'s on the motors in the video, since I wasn't aware of batch #'s at that time.
Anyone know to fix the broken motor? I have the same issue but 1 motor draws a little more power from the other one and makes more noise, while the other is slower and quieter. I noticed the problem after unplugging some wires out and putting them back in during the program running. I don't know if that might be the cause though, maybe a coincidence.
Both my EV3 large motors (both batch 24N3) failed in this way. I assumed this was just normal wear and tear and bought new ones, but maybe batch N3 really did have defects.
Lego has not gotten back to me. However, it seems to be a motor encoder issue. Lego just sent me a replacement motor and asked me to send them the malfunctioning motor.
I think the position encoder has stopped on the right motor and the brain is compensating what it thinks is a stall on the right by slowing the left down.
my motor have that broblem too i changed the battery to eneloop pro and it works normal try change the battery but now when i use the rac3truck program and delete the reset block, when i steer to a direction,it wont stop going and steering unless i close the program.
I had a similar issue, one motor was not rotating, tried different combinations and the problem was in the port, when using A and C was having strange behaviour, but when chanched to A and D all was suddenly working fine
Have you had problems with the brick itself? The programme works but the motor is not moving. I have also noticed my brick takes a long time to get started. Can anyone shed some light? I have only had this brick for less than 6 months.
I had this problem too, you have to open the motor and force the motor to spin with controlled power on the motor pins directly, I will post a video later
I think it would have been helpful to show us the actual program in correspondence with the hardware, so we could see if it was an issue with the software instead. Good video though, as it definitely appears to be a faulty motor haha
Bro Plz Respond Fast, Im Getting the prob with motors that even if i move my motor with my hand it feel hard to move it while sometimes its gud, whats the prob and how can I solve it plz fast, thank you
Thanks for the video - have spent days switching wires and motors! You've helped my team save a bunch of motors we thought were dead....
Almost definitely related to the motor sensor. It's sending bad data (or no data) back to the brain brick which is why your program slows the other motor. I assume your program is not running each motor independently, but using tank mode or at least running them together as a pair somehow. The bad motor sends no data and the good motor gets slowed when the brain tries to keep the robot going straight.
We have definitely had this issue! I will be sharing this with our FLL Teams. Sometimes a robot would go rogue and we could NOT figure it out!!
LWBE Robotics I am having this problem more and more. In fact, I had another motor go bad just yesterday.
We had it during our FLL Competition. Our Team ended up switching their motor 5 minutes before the end of the 3rd game. It would work and sometime not!
That is quite unfortunate. Luckily, this has not happened to any of our FLL team motors. It has only happened to my motors I use with my classes.
So I have had this issue show up on 3 more motors. All of the motors are part of the N3 batch. Two were 49N3 and one was 50N3. I didn't check the batch #'s on the motors in the video, since I wasn't aware of batch #'s at that time.
I know this is late but did you try to run the motors indepently if used in tank mode it runs each motor together
Anyone know to fix the broken motor? I have the same issue but 1 motor draws a little more power from the other one and makes more noise, while the other is slower and quieter. I noticed the problem after unplugging some wires out and putting them back in during the program running. I don't know if that might be the cause though, maybe a coincidence.
Thanks! I have been changing wires and motors to get it to work.
Both my EV3 large motors (both batch 24N3) failed in this way. I assumed this was just normal wear and tear and bought new ones, but maybe batch N3 really did have defects.
use data loging to check motor sensor values and others and display them on screen to figure out?
Lego has not gotten back to me. However, it seems to be a motor encoder issue. Lego just sent me a replacement motor and asked me to send them the malfunctioning motor.
I think the position encoder has stopped on the right motor and the brain is compensating what it thinks is a stall on the right by slowing the left down.
This is really good to know, did you get any warranty support from Lego?
Thanks! I was having this same issue and this solution worked
i have the same problem
but how to fix?
Amazing video! Keep up the good work! I also like LEGO
Hi Scott , we are facing same problem. What N3 batch mean? 2013 Year production?
my motor have that broblem too i changed the battery to eneloop pro and it works normal try change the battery but now when i use the rac3truck program and delete the reset block, when i steer to a direction,it wont stop going and steering unless i close the program.
I had a similar issue, one motor was not rotating, tried different combinations and the problem was in the port, when using A and C was having strange behaviour, but when chanched to A and D all was suddenly working fine
Same issue here. Contrary to the suggestion from Sweg, the wires are the same length and the problem still occurs. Any solution yet?
There is no solution other than calling customer service and having them replaced :(
Have you had problems with the brick itself? The programme works but the motor is not moving. I have also noticed my brick takes a long time to get started. Can anyone shed some light? I have only had this brick for less than 6 months.
I had this problem too, you have to open the motor and force the motor to spin with controlled power on the motor pins directly, I will post a video later
th-cam.com/video/y7SAVTklCzI/w-d-xo.html
Do you have batch number by any chance? I seem to have another similar issue
No I don't, but I can look into it. I have some other motors that are starting to show signs of this issue.
I think it would have been helpful to show us the actual program in correspondence with the hardware, so we could see if it was an issue with the software instead. Good video though, as it definitely appears to be a faulty motor haha
Thank you!
but how do you fix
Bro Plz Respond Fast, Im Getting the prob with motors that even if i move my motor with my hand it feel hard to move it while sometimes its gud, whats the prob and how can I solve it plz fast, thank you
May be motor is shortened inside? The same effect you can notice if you take simpe DC motor and connect his two wires.
program please
I have the exact same problem, how do you fix this?
Kyle n buy a new motor and replace the motor that sucks the power
Sorry, but Lego says the motors are worn out. It's a long story but you are better off replacing the motor.
We also face the same problem.
The longer the wire the slower the motor use same length motors
have the same proplem