PyBricks
- EV3 Color Sensor Mode Switch Latency
- Delay between different Infrared Sensor modes
- OSError when using MultiProcessing in PyBricks
- NXT viability
EV3Dev
- LEGO EV3 UART sensors return stale values after mode switch
ValueError: invalid literal for int() with base 10: ''when using InfraredSensor in Threading- similar: GyroSensor angle for GYRO-ANG sometimes returns empty string instead of integer
- related: Device objects not thread safe
- possibly related: sensors stop working
- Threading error when 2 Threads may control the same Motor. Errors encountered in EV3Dev2 with different error messages on MicroPython vs Python3. No such errors encountered in EV3Dev(1) and PyBricks.
MicroPython
Other
- Broken EV3 Motors:
-
Mr. Hino:
- Solving the Broken LEGO Mindstorms EV3 Motor Issue
- The Continued Mystery of the Broken Motor Port
- Elias Malak: Thank you for the video Mr. Hino. This cleared a lot of things up. If you change the brick, the same problem will occur. If you change the motor that was slow, the same problem will occur. If you switch the ports between b and c, the problem will still occur. However, if you change the motor that is fast, the problem will be fixed. What's happening is that your motor that is going fast has a broken encoder which is why in port view, it does not read anything. When the makers of the ev3 programming programmed the software, they made it so that the brick keeps adding power to the motor that does not show any rotations or degrees so that it can try to "move", because in the brick, it thinks the motor isn't moving at all since the encoder(tracker) is broken, therefore if you change the motor that is going fast, your problem will be resolved. Let me know if this fixes your problem? Thanks, Eli.
-
SOLUTION: use the Device Browser in EV3Dev to manually set the mode/status of the motor from "No Motor" to "Tacho Motor"
EV3Dev