New Programmer

[theboyer]

Now I'm trying to insert a process much like this which will set a servo to 90 activate a relay forward and then set both of them back to their natural position
but it seems to be running too fast and starving the drive system any pointers

[Alan Anderson]

Originally Posted by theboyer

Now I'm trying to insert a process much like this...

Unless we see what you're actually doing, we won't be able to give much in the way of help. Show us your code, not the example you're emulating.

[theboyer]

oh sorry yes here

[Greg McKaskle]

If you place the code into teleop, it will prevent teleop from running frequently enough. Try moving it to Periodic tasks.

Greg McKaskle

[Racer26]

I can't be the only LabVIEW developer that despises the use of the feedback node, can I? IMO, while feedback nodes *can* make a diagram cleaner, they actually make it *harder* to understand, as compared to using the equivalent shift register.

[theboyer]

I attempted this and it still says it is starving the drive loop

[Mark McLeod]

You can attach your vi's directly to a post.
Show us your Teleop.vi & Periodic.vi, and any other vi you might have added code to.

The code you posted looks fine as long as it's in Periodic Tasks.vi (it would not work in Teleop).

[Greg McKaskle]

I can't be the only ...

I also learned LV long before there were shift registers and in many ways prefer them, but I now use both, typically for different things. I really like the compare to last with a shift register, but otherwise typically use shift registers.

Greg McKaskle

[bvisness]

Originally Posted by Greg McKaskle

I also learned LV long before there were shift registers and in many ways prefer them, but I now use both, typically for different things. I really like the compare to last with a shift register, but otherwise typically use shift registers.

Greg McKaskle

I almost never use feedback nodes, but I find myself using feed forward nodes quite frequently. They make more sense to me because the flow of the code keeps moving forward. If I'm in a loop, though, I'll always use shift registers.

[Ether]

Originally Posted by bvisness

I almost never use feedback nodes, but I find myself using feed forward nodes quite frequently.

Is "feedforward node" generally accepted terminology for a feedback node that simply has the arrow direction changed to make the wiring cleaner? If so, it seems unfortunate. The function of the node remains the same regardless of arrow direction.

[RyanN]

Originally Posted by Ether

Is "feedforward node" generally accepted terminology for a feedback node that simply has the arrow direction changed to make the wiring cleaner? If so, it seems unfortunate. The function of the node remains the same regardless of arrow direction.

As far as I know, they're only called feedback nodes. Changing the direction doesn't change their functionality. It just makes the code 'flow' more smoothly sometimes.

[bvisness]

Originally Posted by RyanN

As far as I know, they're only called feedback nodes. Changing the direction doesn't change their functionality. It just makes the code 'flow' more smoothly sometimes.

I guess it's not technically called a feed forward node, but that's what I have come to call them for reasons that are unclear to me. I think one of our mentors called it that, and it stuck.

But it does go forward...so I think I'm gonna stick to the "feed forward" name.

[Greg McKaskle]

Rather than feed forward, how about previous value or delay by one or some name that explains its purpose rather than its appearance.

Greg McKaskle

[Racer26]

Originally Posted by Greg McKaskle

I also learned LV long before there were shift registers and in many ways prefer them, but I now use both, typically for different things. I really like the compare to last with a shift register, but otherwise typically use shift registers.

Greg McKaskle

@Greg McKaskle: I really like several of the changes that have come about since the birth of the idea exchange a couple years ago. Things like shrinking the boolean constant, changes to local variable graphics, integrated labels for structures, better alignment of vi.lib vi's I/O and so on.

For my non-FRC applications, I REALLY like the JKI string-based state machine template.

[theboyer]

Here are my tele op and periodic vis neither has much extra really