Files
-
braking_io / braking_io.PcbDoc
-
braking_io / braking_io.SchDoc
-
braking_io / bus_filter.SchDoc
-
braking_io / connectors.SchDoc
-
braking_io / mcu.SchDoc
-
braking_io / power_24V.SchDoc
-
braking_io / power_5V.SchDoc
-
braking_io / power_7V.SchDoc
-
braking_io / pressure.SchDoc
-
braking_io / retro.SchDoc
-
braking_io / solenoid.SchDoc
-
braking_io / solenoid_drv.SchDoc
-
braking_io / telemetry_adc.SchDoc
-
braking_io / unity_gain_buffer.SchDoc
-
braking_io / watchdog.SchDoc
-
breakout_board / breakout_board.PcbDoc
-
breakout_board / breakout_board.SchDoc
-
breakout_board / connectors.SchDoc
-
main_io / adc.SchDoc
-
main_io / arduino_shield.SchDoc
-
main_io / batt_protection.SchDoc
-
main_io / battery_interface.SchDoc
-
main_io / beaglebone.SchDoc
-
main_io / bms_interface.SchDoc
-
main_io / bus_filter.SchDoc
-
main_io / can_uart.SchDoc
-
main_io / connectors.SchDoc
-
main_io / gpio.SchDoc
-
main_io / limit_switches.SchDoc
-
main_io / main_io.PcbDoc
-
main_io / main_io.SchDoc
-
main_io / misc_sensors.SchDoc
-
main_io / motor_controller_interface.SchDoc
-
main_io / power_12V.SchDoc
-
main_io / power_28V.SchDoc
-
main_io / power_5V.SchDoc
-
main_io / retros.SchDoc
-
main_io / RTC.SchDoc
-
main_io / shutdown_circuit.SchDoc
-
precharge / connectors.SchDoc
-
precharge / Contactors.SchDoc
-
precharge / indicator_light.SchDoc
-
precharge / precharge.PcbDoc
-
precharge / precharge.SchDoc
-
precharge / precharge_relays.SchDoc
-
resources / sample_design / power_3V3.SchDoc
-
testing_board / adc.SchDoc
-
testing_board / connectors.SchDoc
-
testing_board / current_source.SchDoc
-
testing_board / dac.SchDoc
-
testing_board / gpio.SchDoc
-
testing_board / mosfet.SchDoc
-
testing_board / pi.SchDoc
-
testing_board / power_5V.SchDoc
-
testing_board / relay.SchDoc
-
testing_board / serial.SchDoc
-
testing_board / testing_board.PcbDoc
-
testing_board / testing_board.SchDoc
Last update 3 years 11 months
by
Shelby Riggleman
README.mdPurpose
The Braking IO board (generically called Remote IO or RIO boards) are responsible for managing the sensors and actuators on each of the braking trays. Previously, we routed several dozen wire harnesses across the majority of the pod in order to connect to the pressure sensors and solenoids. This board reduces all of that routing into a single power harness, UART + Heartbeat cable and allows for more localized routing to each of the sensors and actuators on the tray. Eventually, there will be 2 of these boards on the pod; one for each braking tray
Requirements
- Mechanical:
- Board shall have at least four 4-40 mounting holes
- Board shall fit in the mechanical enclosure
- Bonus: Board shall contain at least three fiducals for potential automated assembly
- Connector Interface:
- Connectors shall be properly rated for voltage and current
- Connectors shall have a positive locking feature
- Connectors shall share a common pinout and be polarized
- connectors shall be kept to a minimum
- Bonus: System shall be designed for 1:1 harnesses in order to use off the shelf cable assemblies as much as possible.
- Bonus: Harness ID pin shall be added to each connector in order to detect if each cable is properly connected or not.
- Power:
- Fusing: Bus input shall be fused to protect against over-current events
- Telemetry: All rails shall have voltage and current sensing
- Filtering: Bus voltage shall be filtered
- Rails: 5V and 3V Rails shall be implemented
- Sensors:
- Pressure: Pressure telemetry inputs (8x) shall be configurable for both voltage and current output pressure transducers
- Temperature: Two configurable board mount or external temperature sensors shall provide temperature feedback
- Actuators:
- Solenoids: 8x solenoid driver circuits shall be implemented
- Bonus: Use the MPQ6610 instead of a traditional N-MOS driver to save on power
- Bonus: LEDs on each solenoid
- Watchdog:
- Board shall have a way to reset all solenoids in case of loss of heartbeat or UART connection from either the microcontroller or the primary flight computer
- MCU:
- Board shall be capable of sending telemetry, over UART, to the primary flight computer
- Board shall be capable of receiving commands to actuate different valves, over UART, from the primary flight computer
Info
- Schematic Designers @btobin @rcastle1
- Layout: @btobin
- Need-by-date: 10/1/2019