Hi all,

Could you please take a look at the attached picture? It's a snapshot of the debugger window. Strangely it gives me a = 20 but the speed of motorA should be 0 then. I've no idea about it.

It seems like the motor is reporting the last non-zero speed it was given. I'm looking into this issue now.

Thanks!

Hi guys,

Do you have any update for this problem?

I've never read from the motor[] array; I've only ever written to it. I usually just use global variables (or, sometimes, another array) in my program to keep track of motor values, and then update motors each frame, rather than actually checking the value in motor[]. What happens if you use a different motor port? It doesn't seem to be acting strangely with motorB and motorC.

Strange.

Ah!

Maybe only "int's" can only be imputed int a motor?

This issue should be resolved in ROBOTC 3.54.

Thanks!