Filling pneumatic system in queue?

[jojoguy10]

Hi all!

We're trying to find a rule that says anything about starting up the robot and running the compressor to fill up our pneumatic air tanks. We are using an on-board compressor.

Thanks!

[JohnM]

That is completely okay. My team did all last year too, and I think we plan on doing it this year too.

[Daniel_LaFleur]

Originally Posted by JohnM

That is completely okay. My team did all last year.

This years rules =/= last years rules.

That said, it is legal to pre-charge your tanks before going on to the field.

[rich2202]

Most teams use an extra battery in the que to pre-charge.

[mackenzieg]

My team did this last year. I'd suggest bringing a battery with you in queue to fill the tanks, then switch to a new battery right before the match starts.

____________________
Mackenzie Glaser
Team 1261

[IndySam]

When we get back to the pits we do whatever repairs and updates we need to do with the last match battery still in the bot. Before we go out to queue we charge the pneumatics with that battery and then install a new one.

If your system is leaking enough to require a recharge while in line after precharging in the pits you need to work on the pneumatic systems to eliminate leaks.

As a caveat, we have been know when running late to perform the fill and battery change in the queuing line instead of in the pits.

[cgmv123]

Originally Posted by rich2202

Most teams use an extra battery in the que to pre-charge.

Originally Posted by mackenzieg

I'd suggest bringing a battery with you in queue to fill the tanks, then switch to a new battery right before the match starts.

Note that you still have to use the control system to fill the tanks; you can't just connect a separate battery directly to the compressor.

[Ether]

Originally Posted by Daniel_LaFleur

=/=

Here ya go: ≠ :-)

[rich2202]

"<>" also works.

[Ether]

Originally Posted by rich2202

"<>" also works.

!=

[GeeTwo]

Originally Posted by Daniel_LaFleur

=/=

Or from some other infix languages I've used over the years:

~= (MATLAB)
.ne. (FORTRAN)
-ne (Bourne Shell)
/= (Ada)

[Christopher149]

Originally Posted by GeeTwo

Or from some other infix languages I've used over the years:

~= (MATLAB)
.ne. (FORTRAN)
-ne (Bourne Shell)
/= (Ada)

And JavaScript has !== in addition to !=.

[Sohaib]

This is legal provided you don't break any other rules in the process. I imagine this year during the time you assemble your robot, you could charge your tanks. (Provided it is safe to do so.)

[EricH]

Originally Posted by Sohaib

This is legal provided you don't break any other rules in the process. I imagine this year during the time you assemble your robot, you could charge your tanks. (Provided it is safe to do so.)

Nuh-uh. You're on the field, putting your robot together, it's either off or disabled. The compressor only runs when the robot is enabled. And tethering up is illegal.

Now if you're changing from one Transport Configuration to another within the same volume, sure, knock yourself out, because you're in queue for that. (Just don't leave Transport Configuration to do that.)

[rich2202]

Originally Posted by EricH

Nuh-uh. You're on the field, putting your robot together, it's either off or disabled. The compressor only runs when the robot is enabled. And tethering up is illegal.

Tethering is only illegal on the field (violation of G9). There is no prohibition on tethering in the que. One rule to be careful of: Don't move the robot out of transport configuration while in the que (Q299).