|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
[FTC]: [FTC]: eliminating the Motor Configurator (LabVIEW)
I'm not a fan of the Motor configurator. It is cumbersome and makes it difficult to move files from one computer to another. An alternative is to directly address the motor and servo vi's with a 4 digit integer as follows:
1st digit: NXT port. Valid values are 1-4 2nd digit: Controller position in daisy chain. Valid values are 1-4 with a value of 1 meaning the controller closest to the NXT. 3rd digit. Motor port on the controller. Valid values are 1 and 2. 4th digit. Motor direction. Valid values are 0 and 1. e.g. 2310 means NXT port 2, third controller in the daisy chain, motor port 1 on the controller, direction 0. Servos are addressed in the same fashion: 1st digit: NXT port. Valid values are 1-4 2nd digit: Controller position in daisy chain. Valid values are 1-4 with a value of 1 meaning the controller closest to the NXT. 3rd digit. Servo port on the controller. Valid values are 1-6. 4th digit. Valid values are 0 and 1. This value is ignored but is still necessary as a place holder. See the attached file for an example. You can also right click on one of your configurations and choose "edit items" for more insight. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| [FTC]: Faster LabVIEW motor .vi's | aklego | FIRST Tech Challenge | 3 | 08-12-2010 16:48 |
| [FTC]: Bluetooth Problem with LabView/FTC Controller Station | James Dowd | FIRST Tech Challenge | 8 | 27-10-2009 10:40 |
| [FTC]: Tips page on using FTC Encoders with LabVIEW | PhilBot | FIRST Tech Challenge | 7 | 27-01-2009 14:00 |
| [FTC]: First problem with FTC and LabView.....? | PhilBot | FIRST Tech Challenge | 5 | 07-11-2008 10:36 |
| [FTC]: FTC Servo-Motor Problem with Labview | dnhansen | FIRST Tech Challenge | 1 | 26-10-2008 00:43 |