Q597 - Laptops for Drivers Station part of your 30lbs withholding allowance

I just read Q597 and the GDC’s answer.

Q597
Does modifying the software (ex: uploading code, installing a new operating system, etc.) on a COTS computing device make it classified under a “fabricated item” (such as a motor with leads added)? And thus, would a COTS computing device therefore be included in the 30lb withholding allowance when brought in to an event?

Answer
Yes, loading software intended to be used for use in competition would make the item no longer in an “unaltered, unmodified state” which is a requirement for it to be a COTS part.

So here is what I take away from this.

  1. So now we have to purchase a new laptop for the driver’s station every year? Even if we re-image the system it is still not in an “unaltered, unmodified state”.

  2. A 10lb laptop is now part of the 30lb withholding allowance.

  3. Since the laptop is now a fabricated item, there is a $400 limit on the price.

  4. How many teams didn’t place the laptop in the bag with the robot?

If you didn’t bag your laptop, think about this.

  1. Just turning on a laptop and signing on changes the device and it is no longer in an “unaltered, unmodified state”, So you’ll have to do all the system installs at the events.

  2. If you go to multiple events, will you need a new laptop for each?

I really think the GDC missed the boat on this question. I agree that physically modifying a laptop means it is a fabricated device, but installing the driver’s station software?

Not advocating breaking this rule, but…

Your drivers station is not part of your robot. It doesn’t matter if any part of the drivers station is COTS.

If you were using a secondary processor on your robot, and it used custom software stored on a chip or hard drive on the device, writing the software onto the device alters it from as purchased condition, and it’s no longer COTS. Take a Raspberry Pi as an example. As I recall, the software for a Pi is stored on an SD card. You could bring spare Pi’s without counting them towards the weight allowance. But a pre-written SD card would count. If you mounted the Pi in an case, the assembly of the case and the Pi would also count as a fabricated assembly, as the act of assembling them means both the Pi and the case are no longer in their as-purchsed condition.

Your Driver Station is not, and never has been, part of your robot. You don’t get the driver station laptop inspected. You don’t weigh your laptop.

I am certain this question was clearly in regards to putting computing devices on-board the robot, such as a Raspberry Pi for vision. While a Pi by itself is clearly a COTS part, a Pi configured with software to detect vision targets is not.

RTFM

Guess we need to get our micro SD cards weighed. :o

The Driver’s Station is not part of the Withholding Allowance…

I think it was the question phrasing that causes some confusion here.
If you have a COTS computing device, the term is only used in reference to an on-board robot COTS computing device.

That puts the question into the “can I work on my robot outside of the bag” department.
And the answer to that is, only up to 30 lbs worth.

I’ll stipulate that the question probably was asked about placing a device on the robot. However neither the question nor the answer makes this clarification.

Regarding tickspe15, I have read the manual, many times. Again I’ll point out that the question and the answer makes no reference as to whether the COTS device is part of the robot or the control system.

1 Like

I believe that this rule would not apply to the driver station computer since it’s not part of the robot. However, the RoboRIO is part of it. FIRST has just set back teams $400 every year. Also, if any of you guys liked those Talon SRX motor controllers, you have to buy new ones of those every year. And changing brake/coast on a not overpriced motor controller means that those are fabricated items as well.

There is a rule (R13D) that may protect these, but it appears to mostly apply to adding connectors. (Are these complicated systems an electrical device? They use electricity, but cross the line into “electronic”)

The manual itself clarifies this in the very rule (R21) that defines the WITHHOLDING ALLOWANCE:

Items exempt from this limit are:
A. the OPERATOR CONSOLE,

Which the DS device is part of.

According to the Glossary: (emphasis mine)

ROBOT
an electromechanical assembly built by the FIRST® Robotics Competition
Team to perform specific tasks when competing in FIRST®
STEAMWORKSSM. The ROBOT must include all of the basic systems required
to be an active participant in the game – power, communications, control,
BUMPERS, and movement. The ROBOT implementation must obviously follow
a design approach intended to play FIRST STEAMWORKS

You clearly missed some parts of the manual:

Just perform a factory reset on your CRIO and Talons on kickoff day.

And just for good measure, from the glossary:

OPERATOR CONSOLE
the set of COMPONENTS and MECHANISMS used by the DRIVERS and/or
HUMAN PLAYER to relay commands to the ROBOT

This includes the DS laptop.

  1. No, the driver station is not part of the ROBOT, and R13 applies only to physical ROBOT elements, specifically excluing the driver station.
  2. No, the driver station is not part of the ROBOT, and the withholding allowance (R21) only covers items “to be used to repair and/or upgrade their ROBOT.”
  3. No, the driver station is not part of the ROBOT. R10 specifies the total cost of the ROBOT, while R11 and R12 imply that it’s the ROBOT only (although these could be made clearer).
  4. Probably every team, because the driver station is not part of the ROBOT.
  5. The driver station is not part of the ROBOT, so you don’t have to worry about changing it.
  6. No, because the driver station is not part of the ROBOT.

Anyone else see a pattern here? :stuck_out_tongue:

In many cases, like with the RoboRIO or motor controllers, you can easily take them back to a COTS state after modifying them. You just have to return them to the state they were in when you received them. When you upload new software or firmware to them, you’re essentially doing just that. You are removing the part that changed it and adding a new part that changed it.

That said… Really? You’re going to nitpick on this in order to cost your team money and hassle? Has anyone EVER had an inspector ask them if they modified software or code on their roboRIO or speed controller prior to the season? Has anyone EVER had an inspector hassle them on installed software on a roboRIO that they carried in outside of their bag?

Well… not until this Q&A.

I’ve had more than a few… shall we say eager inspectors trying to find anything they could to call something :slight_smile:

How much does a Bit weigh? A Gigabyte?

If you bag your robot with a battery, and make the breaker accessible without having to unbag the robot …

Before you unbag, you turn on the robot and deploy the new code …

Well, I guess I’ll chime in as the person that asked this question.

My intent when asking was focused towards co-processors like used for robot vision, but this apparently has other implications around other control system components. I asked mainly because when we bagged we didn’t bag our co-processor so we could use it on our second robot. However, since we installed Ubuntu and all our vision stuff we wanted to know if it was part of witholding.

Didn’t realize it would cause such a stir!

I was more pointing out that this clarification does technically make this the situation. As you said, inspectors won’t call people out on it and it’s totally unenforceable. (since there’s no physical change made to the item, part of the reason that calling them “fabricated” items doesn’t work in the first place) I also fully expect them to change this next year, potentially expanding R13D to all control system components, since basically no team is going to actually keep buying these parts.

Technically you can do all you want with it and then reimage it before you bring it to competition, and then reinstall everything after if you don’t have the weight for it.