[MDAWG25]

Originally Posted by ekapalka

Hello! Can someone please direct me to the section of the rules dealing with on-board computers (not coprocessors)? We've been considering using an ODROID for onboard Vision Processing, but is we can use a computer rinning Windows, that would be so much better. (I'm not completely sure if we can, I just saw someone mention it in another thread.) Thanks!

A couple different rules would be a concern here.

R11
The total cost of all items on the ROBOT shall not exceed $4000 USD. All costs are to be determined as explained in Section 4.1.3: Budget Constraints. Exceptions are as follows:
A. individual fasteners, adhesives, and lubricants, that are less than $1 each and
B. Kit of Parts (KOP) items
Teams should be prepared to disclose to Inspectors the cost of any non-KOP item and the total cost of the ROBOT.
Per T7, teams must be prepared to display a Bill of Materials (BOM) to Inspectors during Inspection. The BOM may be displayed in either printed or electronic form.

R12
No individual item shall have a value that exceeds $400 USD. The total cost of COMPONENTS purchased in bulk may exceed $400 as long as the cost of an individual COMPONENT does not exceed $400.

R34
The only legal source of electrical energy for the ROBOT during the competition, the ROBOT battery, is one of the following 12VDC non-spillable lead acid batteries:
A. MK Battery (P/N: ES17-12) or
B. EnerSys (P/N: NP 18-12)

Exception: Batteries integral to and part of a COTS computing device or self-contained camera are also permitted (e.g. laptop batteries), provided they’re only used to power the COTS computing device and any peripheral COTS USB input devices connected to the COTS computing device and they must be securely fastened to the ROBOT.

You might need to build a custom circuit.

R54
Custom circuits shall not directly alter the power pathways between the ROBOT battery, PD Board, motor controllers, relays, motors, or other elements of the ROBOT control system (including the power pathways to other sensors or circuits). Custom high impedance voltage monitoring or low impedance current monitoring circuitry connected to the ROBOT’S electrical system is acceptable, if the effect on the ROBOT outputs is inconsequential.

This is the rule you are mainly concerned with.

R55
ROBOTS must be controlled via one (1) programmable National Instruments cRIO (P/N: cRIO-FRC or cRIO-FRCII), with image version FRC_2013_v47.

There are no rules that prohibit co-processors, provided commands originate from the cRIO to configure, enable, and specify all operating points for all power regulating devices. This includes Jaguar motor controllers legally wired to the CAN-bus.

R56
One (1) D-Link wireless bridge (P/N: DAP-1522), hardware revision B, is the only permitted device for communicating to and from the ROBOT during the MATCH.
Hardware revision A, distributed in 2011 and 2012, is not legal for 2013. Teams participating in the Irael Regional may use hardware version Rev A or Rev B.

R58
Ethernet-connected COTS devices or custom circuits may connect to any remaining Ethernet port but must not transmit or receive UDP packets using ports 1100-1200 with the exception of ports 1130 and 1140.

R62
No form of wireless communication shall be used to communicate to, from, or within the ROBOT, except those required per R56 and R61 (e.g. radio modems from previous FIRST competitions and Bluetooth devices are not permitted on the ROBOT during competition).

R72
All outputs from sensors, custom circuits and additional electronics shall connect to only the following:
A. other custom circuits,
B. additional COTS electronics,
C. input ports on the Digital Sidecar,
D. input ports on the Analog Breakout Board,
E. the RS-232 port on the cRIO,
F. the Ethernet network connected to either Port 1 or Port 2 of the cRIO,
G. the CAN-bus if and only if all Jaguar motor controllers on the CAN-bus are wired in full compliance with R68 and R69, or
H. the sensor inputs on the Jaguar motor controller.

Custom circuits and additional electronics are allowed to utilize the Port 2 Ethernet bus on the cRIO-FRC and/or the CAN-bus to communicate between devices. Note however, that the ROBOT must be controlled by the cRIO (see R55). Thus, any additional devices on the Ethernet or CAN-bus must not provide command signals that do not originate from the cRIO.

R74
Any decorations that involve broadcasting a signal to/from the ROBOT, such as remote cameras, must be approved by FIRST (via e-mail to frcparts@usfirst.org) prior to the event and tested for communications interference at the venue. Such devices, if reviewed and approved, are excluded from R62.

These rules govern on-board processors of any type. As long as they abide by these rules and you provide documentation for any question that may arrise, you will be fine.

You can use any type of operating system, windows, linux, android, etc.

My team uses an on-board processor with an Intel I-3 running Windows 7 and RoboRealm. We use a Kinect to do realtime vision tracking, if you have any questions about our setup, you can send me a PM or post in this thread