NXT motor not responding to buttons programmed to

[webby]

When we assign an NXT motor to port A and on Remote one use turn while pressed in one direction for button 7 and turn in the other direction for button 8 we have no problem in test. When we generate code, the motor either comes out in the vi as a tetrix motor or as an NXT motor in Port C. I tried just moving the cable to Port C, but not only did it not get a response it created alerts in the Remote Config window. We have some LabVIEW experience from FRC, so we went to the vi and tried to assign the motor we linked back to the schematic with configure and saved and generated, but it still did not work. Any ideas?

Thanks

[jerry_dcjx]

the code gennerated by lvlm will consider nxt motor as a dc motor, so you need to change it mannually in the program.

just replace the dc motor and break with the nxt motor block and the ports.

[webby]

Thanks so much. I am glad to know I am on the right track. I have tried to do as suggested, but where in the palletes the the "NXT" motors exist? Or do I need to download a special vi? Also our button case for the 2nd controller shoes "lego Motor" as the item of the VI, but it is not clear in that area ow I designate the ports. The robot does run correctly when we test it in the remote configuration portion. I have attached a doc with a scren shot of the code we are seeing. Thanks so much. https://docs.google.com/a/lakefentonschools.org/document/d/1kxljJ4SknIIPJVIh45WmXtzekh3SyuHjtAnvtywW...

[mathterizer]

Functions Pallet (right click), NXT I/O, Motor - is the Lego Motor vi

[webby]

Thanks, at least I am no longer worring that I have the wrong motor. But I still cannot make the Lego motor plugged directly into A on the block respond to any button. Getting desperate.

[mathterizer]

Post a screen shot of the part of the code that addresses this motor. Maybe it will be obvious if I can see it.

You say the motor works in test, so it doesn't sound like a hardware issue.

Some ot the software bugs are being resolved by ensuring your vi is an 'NXT target', saving, exiting, and restarting LV.

[webby]

https://docs.google.com/a/lakefentonschools.org/document/d/1kxljJ4SknIIPJVIh45Wm Xtzekh3SyuHjtAnvtyw... is a google doc with screen shots

and

[mathterizer]

Thanks for the screen shot. It's quite clear that Controller 1, Button 7 is still referencing a DC Motor. Don't be fooled by the software giving you the option of choosing a Lego Motor in this case (seems to be a bug).

The 'generate code' function is making some errors, and you have one here.

As Jerry said earlier you will want to replace that DC Motor block with the Lego Motor block found at the 'Functions Palette, NXT I/O, Motor' (alternative: rt click on the DC Motor block and choose Replace, All Palettes, NXT I/O, Motor) - This is the Lego Motor vi and the picture on it will look like a little LEGO motor (grey and orange).

You will then proceed to rt-click on each of the nodes of that block to 'create constants' that define what you are after. (ie. rewire it)

See the attached file below for a screen shot of a wired Lego Motor block.

You might like to try the ctl-H option of having the help files for each part of the code displayed as you explore the generated code. It's a great way for the kids to learn.

If you still need help, don't be afraid to ask.

[webby]

We have the Lego motor running while pressed. We had to create a blank robot and build it up without the FTC Arm and Gripper template. We are not sure why, but now we can copy that teleop into any project we create and it works. Thanks for all the help.

[mathterizer]

There is a patch that might make the 'generate code' function work properly, and resolve this issue.

https://decibel.ni.com/content/thread/19336?tstart=0

UPDATE: no dice. I tried a new 'generate code' after installing the patch and you still need to manually replace the block.

Further update: ESearl of NI assures me that we can actuallly run an NXT motor using the DC Motor block in the new 2012 release. I never thought to try. Thx ESearl.