Hi,

I am trying to use an old style Technic Motor with an EV3 project, but am having issues with motor only running in one direction reliably.



The code runs flawlessly when I use either an NXT or EV3 motor, but when I use a PowerFunctions or Technics Motor, the Motor will only run for a few milliseconds in the positive direction (direction = 100). The negative or Reverse direction (direction = -100) it works fine. Is this a RobotC 4.30 issue, or am I doing something wrong?

I trust someone can please help me get to the bottom of this?

I am pretty sure the EV3 does not officially support anything other than the NXT or EV3 motors, so it's not something we ever tested. It most likely has to do with the fact that it's not getting any kind of feedback from the non-existing encoders. It's not something we ever tested.

= Xander

Thanks Xander.

I assumed that was the issue, but it is very inconvenient when you don't need encoder feedback and weight is a major design constraint. Also cost comes into the equation as well, as even the new Medium EV3 Motors are very expensive to buy.

Using a Mindsensors GlideWheel for PF and RCX Motor is a way out, but they cost as much/more as a Medium EV3 Motor.

How difficult is including a non-Ecoder Motor type to RobotC, as I'm sure I won't be the last to want to use non-EV3/NXT motors in a project?