12-05-2006 03:45 PM
12-07-2006 12:53 PM
I'm still pretty new to LabVIEW, so forgive me if this question is obvious.
In the NXT Toolkit, there is a block called "NXT_RotationSensor.vi" I'd like to use that, but I want it to output a signed count, instead of a count +direction.
So, if I add this output to the VI, how will it affect other things? Will it affect anything else?
Next, if I don't change the block, and want to send an NXT-G block I've made based on the "normal" NXT_RotationSensor.vi to someone who has the DBU installed, will I have to include the block?
12-07-2006 03:32 PM
02-12-2007 05:09 AM
I have done some programming making a rotationcount_regulator for the motors and the NXT. It works fine. When I use the "Edit/Create SubVI"-function it doesn´t work any more and I don´t get any errormessages. I have done a mass compile and I´m using version 8.20. I would like to include the two VI´s in this message but I do not know how to do that. Any help with this problem is welcome.
02-12-2007 10:04 AM
I would like to include the two VI´s in this message but I do not know how to do that. Any help with this problem is welcome.
Below the edit window where you compose the message, is a field for attachments. Click the browse button and select your attachment. To add another, click on "add additional attachments" until you have two browse buttons. etc.
Be aware that these fields clear whenever you preview the message and you have to attach them again. Thus, you should add the attachments as a last step right before posting.
02-13-2007 01:33 AM
02-16-2007 04:38 PM
I tried your VIs and wasn't able to immediately identify a problem. That being said, I also didn't have your sub-VI there with which to test the higher level VI. Attaching that sub-VI would allow me to try the whole thing out from my end, too, to see if I can determine a problem.
Another solution to this question might be the following:
You could write a program on the NXT that listens for a particular mailbox, then send strings to that mailbox from the PC. The NXT could then respond with an action based on the message received (ie. start a motor with one message, stop it with another). Just another approach that might work! Unfortunately, there isn't a straight interface (with the direct commands) to the synchronization function in the firmware that the 'motor distance' function employs for its work.
I'd be interested to hear how things work out!
02-19-2007 01:21 AM
Thanks for your help. The sub-VI´s that I use are the ones included in the LEGO toolkit for LabVIEW. They also have a lot of sub-VI´s "inside" so I can´t attach them all to this message unfortunately. If you could install that toolkit and try, I would be greatful.
To bad to hear that there isn´t a straigth approach to the "motor distance"-function with the online commands. I have tried to use the "Tacho Limit" variable but I can´t access the flag "Tacho Limit" and the PID controls. Do you know why this isn´t possible? Is this function just forgotten or is it not possible? Due to the possible samplerate it should be possible. Please pass this request on to your colleuges responsible for the NXT toolkit.