Comments on: NXT LabVIEW Toolkit DirectCommand VIs http://nxtasy.org/2006/12/05/nxttoolkit-directcommand-vis/ LEGO Mindstorms NXT Blog Forums Community Downloads Tutorials Tue, 07 Oct 2008 05:03:09 +0000 http://wordpress.org/?v=2.0.4 by: UowNxt http://nxtasy.org/2006/12/05/nxttoolkit-directcommand-vis/#comment-2375 Fri, 15 Dec 2006 14:49:45 +0000 http://nxtasy.org/2006/12/05/nxttoolkit-directcommand-vis/#comment-2375 I want to use labview NXT Direct Commands to control my NXT . I connected PC and NXT through USB successfully, and also got the response form Sound Sensor. The sound level is used to specify the rotational distance of NXT motor in DEGREES, however I found that 'NXT Direct Commands >output>motor unlimited' can not accept a Degree input parameter. I try to modify these subVIs, add Degree and Break(?) parameters. It seem that Degree parameter can be defind (also worked),but it worked in a incorrect way. I read LabVIEW_for_NXT_Advanced_Programming_Guide, and try to add UpdataFlags for that VI. After analysis Motor Unlimited.vi in deep, I found that SendDirectCommand.vi can't be open,it's locked! So I have no idea about the structure of "Output Port Info". Can anybody help? I want to use labview NXT Direct Commands to control my NXT .
I connected PC and NXT through USB successfully, and also got the response form Sound Sensor.

The sound level is used to specify the rotational distance of NXT motor in DEGREES, however I found that ‘NXT Direct Commands >output>motor unlimited’ can not accept a Degree input parameter.

I try to modify these subVIs, add Degree and Break(?) parameters. It seem that Degree parameter can be defind (also worked),but it worked in a incorrect way.

I read LabVIEW_for_NXT_Advanced_Programming_Guide, and try to add UpdataFlags for that VI. After analysis Motor Unlimited.vi in deep, I found that SendDirectCommand.vi can’t be open,it’s locked! So I have no idea about the structure of “Output Port Info”.

Can anybody help?

]]> by: Greg McKaskle http://nxtasy.org/2006/12/05/nxttoolkit-directcommand-vis/#comment-2315 Tue, 12 Dec 2006 13:31:29 +0000 http://nxtasy.org/2006/12/05/nxttoolkit-directcommand-vis/#comment-2315 To simplify the play tone example, you can take advantage of LabVIEW's garbage collection and get rid of the Dispose. You can also take advantage of the error I/O wires. On error, the blocks will become no ops, meaning the case for handling a timeout isn't truly needed. (I don't have the toolkit in hand, but this is the way LabVIEW blocks normally operate with error I/O). That leaves three blocks, connect, create, play. There was nothing wrong with the example as presented, but as is often the case, it didn't take full advantage of the language features. Please don't take this as a LV vs Ruby volley. I like languages in general, and just wanted to level the comparison. Greg McKaskle To simplify the play tone example, you can take advantage of LabVIEW’s garbage collection and get rid of the Dispose. You can also take advantage of the error I/O wires. On error, the blocks will become no ops, meaning the case for handling a timeout isn’t truly needed. (I don’t have the toolkit in hand, but this is the way LabVIEW blocks normally operate with error I/O).

That leaves three blocks, connect, create, play.

There was nothing wrong with the example as presented, but as is often the case, it didn’t take full advantage of the language features.

Please don’t take this as a LV vs Ruby volley. I like languages in general, and just wanted to level the comparison.

Greg McKaskle

]]> by: Guy Ziv http://nxtasy.org/2006/12/05/nxttoolkit-directcommand-vis/#comment-2218 Wed, 06 Dec 2006 15:17:12 +0000 http://nxtasy.org/2006/12/05/nxttoolkit-directcommand-vis/#comment-2218 This is not NXT-G 2.0, rather it is a release of the LabView engine of NXT-G 1.0 to the public. This is not NXT-G 2.0, rather it is a release of the LabView engine of NXT-G 1.0 to the public.

]]> by: Tony Buser http://nxtasy.org/2006/12/05/nxttoolkit-directcommand-vis/#comment-2209 Wed, 06 Dec 2006 00:46:20 +0000 http://nxtasy.org/2006/12/05/nxttoolkit-directcommand-vis/#comment-2209 I've seen some interesting things you can do with labview and the graphs/gui instrument panel widgets, but that example to play a tone is pretty complicated compared to the same thing with ruby-nxt in 3 lines of code: require "nxt_comm" nxt = NXTComm.new nxt.play_tone(500,300) ;) I’ve seen some interesting things you can do with labview and the graphs/gui instrument panel widgets, but that example to play a tone is pretty complicated compared to the same thing with ruby-nxt in 3 lines of code:

require “nxt_comm”
nxt = NXTComm.new
nxt.play_tone(500,300)

;)

]]> by: Mr,M. http://nxtasy.org/2006/12/05/nxttoolkit-directcommand-vis/#comment-2207 Tue, 05 Dec 2006 22:39:49 +0000 http://nxtasy.org/2006/12/05/nxttoolkit-directcommand-vis/#comment-2207 How is it compared to NXT-G 1.0 ? Should i understand it as NXT-G 2.0 ? How is it compared to NXT-G 1.0 ?

Should i understand it as NXT-G 2.0 ?

]]>