Can you explain why you need both setPower and setSpeed for the same motor? How are you using them?
We are using the setPower method to calibrate some of our motors, without using an extra sensor. For example, we are running the motor with very low power, such that it stops when there is too much resistance and at the same time we monitor the motors tachocount to see if it has moved. If the tachocount has not changed for X consecutive readings, we conclude that the motor is at a specific position and then resets the tachocount to have the same starting position for each run. We are using setSpeed when operating the motor, to operate it at different speeds dependent on how accurate we need the movement to be.
gloomyandy wrote:At a push you could probably re-create the old motor class by sub-classing NXTRegultedMotor and adding a setPower method that first disables the regulator and then sets the power on the port...
I will try that today, to see if that is possible to use. I tested the NXTMotor class yesterday as well, but I could not get the motor to move at all. My code was basically instantiating the NXTMotor, setting the power and calling the forward method, which should be the simplest way of getting a motor to run. However, it did nothing at all.
gloomyandy wrote:There is no way to move the i2c code back to 0.8.5 without a lot of work, so I don't think that is going to happen, sorry...
That is understandable - thank you for considering how much effort it would require! We will try to rewrite our code to see if it can work on the snapshot version.
By the way, I simply love the new menu system with all the fancy graphics - it feels so much more intuitive and complete! Good job!