Thread: I-5 cRIO?
View Single Post
  #6   Spotlight this post!  
Unread 20-06-2013, 13:57
tr6scott's Avatar
tr6scott tr6scott is offline
Um, I smell Motor!
AKA: Scott McBride
FRC #2137 (TORC)
Team Role: Mentor
 
Join Date: Dec 2007
Rookie Year: 2005
Location: Oxford, MI
Posts: 515
tr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond reputetr6scott has a reputation beyond repute
Re: I-5 cRIO?

Next year's rules have not been written, so no one knows.

Based on this year... probably not, or not as you intended. It could be considered a custom circuit or coprocessor, but then it can not control any motor controllers, or interface with the power pathways.

Quote:
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.
Expanding on Mark's R55 This is the blue box explanation.

Quote:
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.
If the I-5 has outputs, then you are bound to R72 (Blue box included)

Quote:
R72
All outputs from sensors, custom circuits and additional electronics shall connect to only the following:

other custom circuits,
additional COTS electronics,
input ports on the Digital Sidecar,
input ports on the Analog Breakout Board,
the RS-232 port on the cRIO,
the Ethernet network connected to either Port 1 or Port 2 of the cRIO,
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
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.
And I don't know what an I-5 cRio is but I have a suspicion if it is like most NI hardened processors, you will issues with the budget rules, particularly Rule 11.

Quote:
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.
__________________
The sooner we get behind schedule, the more time we have to catch up.