|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: old robot kicker question
well, the problem is that in the loop is a flat sequence, with 2 frames. the first is timed for either 500, 625, or 750 ms (depends on kicking power), and the second is always 500ms
i thought that by itself would server as timing enough... the power button has me confused... if this were digital electronics, all i would do is wire a nor gate to each reset of the flip-flop... but this isn't that any ideas? Last edited by ratdude747 : 21-03-2011 at 17:29. |
|
#2
|
||||
|
||||
|
Re: old robot kicker question
I think i fixed it.
I found in the function block menu flip-flops. i used those to set the 3 button system. being an electronics guy, i knew how to wire them to do what i wanted. I also moved the button/flip-flop section to the teleop.vi and clustered the kick boolean and the enum kick power to the periodic tasks.vi . i did it this way to make a future dashboard and/or autonomous project more modular. i attached the teleop and periodic halves of the kick code. (well, screenshots) edit- (not in pictures) i changed the cluster wire to a global variable. that way I can add it to my custom dashboard (I did, thanks to a tut. video), and if i want to do an autonomous demo, I can use the kicker without creating a conflict. Last edited by ratdude747 : 22-03-2011 at 00:30. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|