On time, I have no problem with Lego Toolkit.
Mass compiler checked, Ok.
All examples run. Ok
This is the toolkit that all Legowalker need for total control! Yeah.!
My plataform: Win Xp, Labview 8.0, AMD sempron 1.8 Ghz, 512 RAM
For the moment I have no idea concerning your BT-problem, but let me try to propose a solution for your Direct Command question.
If you have a look on the sensor and motor VIs you'll find that they have an NXT Object Input and a corresponding output. If you want to send many commands to your NXT (also in a loop), the idea is that you connect the NXT object output of one VI to the input in the next command vi (like one does most of the time with the error cluster, too). In this way you also define the order in which the commands are executed. The NXT object output of the last command VI inside the loop (which is now the end of a "command chain") should be connected to the input on the single Destroy NXT Object outside of the loop. So you end up with many commands, but with one single "Create NXT object" before and "Destroy NXT Object" behind the loop.
The passing of the NXT object through the loop should be done using a shift register - in case one of the VIs inside the loop changes the NXT object. (As far as I know this is not the case, but I think it's better style, and the overhead should be neglectable.)
Hope I was able to make the idea of "chaining" the commands clear - otherwise I'll try my best in another iteration ;-)))
Message Edited by UlfM on 12-17-2006 05:30 PM