Answered: VEXU <VUR7a> Additional Microcontroller

[capow08]

Are your previous responses to this Q&A question from Skyrise valid for the Nothing but Net season?

There is NO restriction on sensors and additional electronics used for sensing and
processing except as follows:
a. Sensors and Electronics MUST be connected to the VEX ARM® Cortex®-based
Microcontroller, and can only be connected via any of the externally accessible ports.
b. Sensors and Electronics CANNOT directly electrically interface with the VEX motors, motor
controllers, or solenoids.
c. The additional Sensors and Electronics may only receive power from any of the following:
i. Directly from the VEX ARM® Cortex®-based Microcontroller via any externally
accessible port.
ii. From an additional VEX 7.2V Robot Battery or from a VEX 9.6V Transmitter Battery
(only one (1) additional battery can be used for sensor power.)

Specifically, the intent is to use a separate microcontrollor board (Arduino, RPi, etc.) between the Cortex and a set of custom sensors.

The main purpose of this additional microcontroller board would be to interface with sensors that would otherwise not be available to use with the Cortex. In addition, the microcontroller board would filter and perform computations on the sensor data that would otherwise be impossible or extremely difficult to implement on the Cortex (such as Kalman filters, particle filters, or a SLAM process).

The microcontroller board would only perform calculation on the sensor data and output the results to the Cortex. If it were removed or disconnected, the robot would continue to function and drive, although in an impaired manner. The significance of this is that the Cortex remains the “master” controller and is not simply a motor driving slave to the additional microcontroller board.

[Karthik]

@capow08

Are your previous responses to this Q&A question from Skyrise valid for the Nothing but Net season?

Specifically, the intent is to use a separate microcontrollor board (Arduino, RPi, etc.) between the Cortex and a set of custom sensors.

The main purpose of this additional microcontroller board would be to interface with sensors that would otherwise not be available to use with the Cortex. In addition, the microcontroller board would filter and perform computations on the sensor data that would otherwise be impossible or extremely difficult to implement on the Cortex (such as Kalman filters, particle filters, or a SLAM process).

The microcontroller board would only perform calculation on the sensor data and output the results to the Cortex. If it were removed or disconnected, the robot would continue to function and drive, although in an impaired manner. The significance of this is that the Cortex remains the “master” controller and is not simply a motor driving slave to the additional microcontroller board.

Yes, the previous ruling holds true for VEX U - Nothing But Net.