Quote:
Originally Posted by dickswan
The LabVIEW toolkit for NXT compiles your program into a object file for execution on the NXT. It does not warn you about the lack of floating point.
|
The NXT terminal won't let you download the program unless you have the 1.21 firmware installed. So no chance of running incompatible code.
I'm not getting any consistency on the tests I do with different programs and on different computers and NXT's.
I absolutely saw a large response delay with the Floating Point Joystick processing in place, that went away when I just deleted it and used a wire to bypass the code. I did this several times .
However, based on your post I did some time tests on the JS code, and sure enough it runs VERY fast.
So I ran the original code on a NXT WITHOUT a motor controller attached and it runs like lightning.
So... something in the I2C protocol, or interface code, interracting with the FP code? Maybe interrupts are disabled?
Anyway, since the developer has said that there is a bug, I'm loath to worry about it any more until we see an update. Hopefully he will post something about the underlying bug so we can say "oh, yeah... that explians it" (hint, hint)