|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: DIO not working in autonomous.
Greg,
We did use the execution highlighting and did not see any errors (a previous version of the code passed the error signal through so we could look at it). Phil, If you look at the datasheets, the GPIO lines have a 10K pullup resistor. I did verify with a multi-meter that this was the case and that closing and opening the switch made the voltage at the signal line do what we expected. I also verified that NONE of the signal lines (set as outputs) changed output voltage when expected, so I don't think we have a numbering issue. We also at one point added a switch to our Labview control panel and connected it to the LED and on-screen LED indicator. The on-screen indicator turned on and off just like expected, but the voltage didn't change on any of the GPIO signal lines. Thanks all for the great suggestions. I know there must be one of those "Duh" things that we are doing wrong somewhere, but I sure can't see it yet. Thanks, |
|
#2
|
|||||
|
|||||
|
Re: DIO not working in autonomous.
D'oh, I was reading your post on my iTouch and was sure you were talking about the Driver Station.. Must have been the prior post.
|
|
#3
|
|||
|
|||
|
Re: DIO not working in autonomous.
PROBLEM SOLVED!
As expected it was a hardware problem: Loose nut behind the keyboard (me). It was an indexing issue (0 vs. 1). We had the switch connected to DIO ch 1 (according to the numbers on the digital breakout board) whereas the code needs to use 0 to access that channel. Why couldn't they have numbered the breakout board starting at 0? I could have SWORN that we had run a test to check for this yesterday, but apparently not. I was 99.9% certain it had to be a programmer problem and (sheepish grin) I once again proved myself right. Thanks for all the suggestions. ![]() |
|
#4
|
||||||
|
||||||
|
Re: DIO not working in autonomous.
From your picture, the red dots at the inputs of your opens is the clue. Those are coercion dots, which means the data types didn't match, but LabVIEW took its best guess.
Those expect an enumerated type, but you wired them to a integer constant. The best way to get the enumerated type is the right click on the input and choose create constant. From there you can use the drop down menu to select which one you want (for example, DIO 1). When you do it that way, the numbering on the hardware and in LabVIEW match. |
|
#5
|
|||
|
|||
|
Re: DIO not working in autonomous.
Joe,
Thanks for the suggestion. This is yet another of those items where Labview will help you out, but we didn't know that it would or how to do it. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Camera Code not Working in Autonomous? | Mikesername | Programming | 6 | 28-01-2009 10:14 |
| IR Board Not Working (But NOT Fried) | itsme | Electrical | 2 | 18-02-2008 06:11 |
| Help Autonomous code not working | team550 | Programming | 5 | 14-01-2008 10:35 |
| Camera not working in autonomous | Roger | Programming | 9 | 09-03-2006 07:38 |
| Gyro not working in Autonomous? | kaszeta | Programming | 7 | 11-02-2006 01:28 |