47a8b40fdb
TREE(74): training modules, entity profiles, 2890 references, keyword indices SPROUT(42): knowledge pages, project docs, curated source material SEED(164): daily notes, raw session logs, unprocessed material Updated AUDIT_MANIFEST.json with growth classifications.
158 lines
5.7 KiB
Markdown
158 lines
5.7 KiB
Markdown
---
|
|
type: training-material
|
|
source: hawkcollective Google Drive
|
|
date: 2026-05-03
|
|
growth: tree
|
|
---
|
|
|
|
# Electrical Level 3
|
|
|
|
Electrical Level 3
|
|
Specialty ports, Troubleshooting & Fault Codes
|
|
|
|
2890 The Hawk Collective
|
|
|
|
|
|
FRC Robot Wire Guide
|
|
|
|
Power
|
|
Distribution
|
|
Board
|
|
|
|
PDB - Trouble Lights
|
|
Lights should always match except in Bootloader Mode
|
|
|
|
Robot Rio - Ports - CAN
|
|
CAN connector is the communications backbone of the robot. We use CAN to communicate to the PCM, Motor controllers, and PDB. The newer versions of the RIO have the color names printed on them.
|
|
Green = LOW
|
|
Yellow = HIGH
|
|
|
|
Robot Rio - Ports - I2C
|
|
I2C = Inter Integrated Circuit
|
|
A two wire communication system, similar to CAN. Hundreds of devices can be connected to this port with only 2 data wires as long as each device has a unique address.
|
|
Rio = Master I2C Device = Slave 12C
|
|
4 pins
|
|
Ground - Power(3.3v) - System Clock - System Data
|
|
Research Usage
|
|
|
|
Robot Rio - Ports - RS-232
|
|
Also known as UART. This is a basic Serial Communications system. Relatively slow communications, but very universal.
|
|
3 pins
|
|
Ground - Receive - Transmit
|
|
Research Usage
|
|
|
|
Robot Rio - buttons
|
|
Reset =reboots the FPGA and Processor in the Rio when the button is held down for 5 seconds.
|
|
User = Button that can be accessed in the code.
|
|
Not debounced
|
|
|
|
Research Usage
|
|
|
|
Robot Rio - Ports - SPI
|
|
Serial Parallel Interface - Port with the ability to talk in parallel to multiple devices on a common network. Each Chip Select # pin enables the individual device (4 devices). While the pins on the left side of the socket are shared amongst all the devices.
|
|
SCK = System Clock
|
|
MOSI = Master Out Slave In
|
|
MISO= Master In Slave Out
|
|
Research Usage
|
|
|
|
Robot Rio - MXP
|
|
Research Usage
|
|
Expansion port- Accepts speciality designed circuit boards that expand the functionality of the Rio. Screw points used to secure the expansion board.
|
|
|
|
Robot Rio -Lights - RSL
|
|
Mimics the RSL light showing connection status.
|
|
|
|
Robot Rio -Lights - Mode
|
|
Shows the current mode of the robot.
|
|
Off = Outputs disabled
|
|
Solid Green = Outputs enabled - Autonomous
|
|
Solid Yellow = Outputs enabled - Teleoperation
|
|
Solid Red = Outputs unknown, undetermined, test mode
|
|
|
|
Robot Rio -Lights - Comm
|
|
Shows the communications status of the robot.
|
|
Solid Red = No Code
|
|
Blinking Red = E-Stop was activated
|
|
Solid Green = Active, Driver station connected.
|
|
Any Yellow = Reserved
|
|
|
|
|
|
Robot Rio -Lights - Comm
|
|
Shows the current Communications of the robot.
|
|
Off = Off
|
|
Blinking Yellow = Radio Booting as AP
|
|
Solid Yellow = Radio is Active as AP
|
|
Blinking Green = Radio Booting as Bridge
|
|
Solid Green = Radio is Active as Bridge
|
|
Any Red = Reserved
|
|
|
|
Robot Rio -Lights - Status
|
|
Shows the current Self test status of the boot process.
|
|
2 blinks = Probably failed upgrade.
|
|
3 blinks = Safe mode
|
|
4 blinks = Multiple crashes without reboots. Probably out of memory.
|
|
Regular blinking / solid on = Irrecoverable crash (call NI).
|
|
|
|
|
|
Robot Rio -Lights - Power
|
|
Shows the current Communications of the robot.
|
|
Off= voltage outside normal range.
|
|
Solid Green = No faults
|
|
Solid Red = One or more voltage rails are shorted or overcurrent
|
|
Blinking Red = Over 16v applied to Rio outputs disabled
|
|
Solid Yellow = Brownout Under 6 volts outputs disabled
|
|
|
|
General Troubleshooting
|
|
When confronted a problem on the robot, unskilled technicians will jump from device to device. They often prioritize the devices that they are most comfortable with to least. By achieving Level 3 status you will develop a new skill for troubleshooting.
|
|
Troubleshooting procedures:
|
|
1) Mentally isolate the subsystem.
|
|
2) Check the “trouble / signal lights” for a clue.
|
|
3) Start closest to the affected device (motor, solenoid, sensor).
|
|
Have Programmers check the code for this item while you are doing the hardware side.
|
|
4) Check all input sources on that device. (power,signal,air)
|
|
Look for loose/poor/weak/broken connections/ bad crimps / solder joints.
|
|
5)Move up the substem, branching and checking at each point. Until you reach a known good item.
|
|
->Know good items are devices that connect to multiple devices, and the other devices are still functioning.
|
|
|
|
|
|
2890 Trouble Protocols
|
|
When troubleshooting a subsystem.
|
|
Call out “ Im Troubleshooting _________” (pneumatics/ electrical/ drive drain)
|
|
A second person who has any level certs in that area will “hover” and assist.
|
|
The primary person will verbalize what they are checking and what they are thinking.
|
|
The secondary will listen and only speak up if a step/subsection/trouble spot was missed.
|
|
|
|
(If no certified secondary is available a mentor will step in)
|
|
|
|
Resolving Problems
|
|
Once a probable defective device has been identified:
|
|
1)Quick swap identical item, Communicate the swap with all the Subsystem Leads so they can make all necessary changes while the swap is occurring.
|
|
2) As soon as the device has been swapped, check it, check it again, and then check it again.
|
|
If hardware fixes are not resolving the problems:
|
|
-Communicate with the lead programmer all actions taken by the hardware team.
|
|
|
|
Talons
|
|
|
|
Talon LED Codes
|
|
|
|
Pneumatic
|
|
Control
|
|
Module
|
|
|
|
|
|
PCM Status LEDs
|
|
|
|
PCM Status LEDs
|
|
|
|
To Achieve Electronic Technician Level 3
|
|
Read this presentation and memorize the memorize the fault light codes for Rio, PCM, Talons.
|
|
Find the slides marked with “Research Usage”. Research one instance of another team/device using this port.
|
|
Take the Pretest for Electronics Technician Level 3
|
|
Schendle an in person test with a Electronics Trainer for level 3.
|
|
|
|
Next-Electronic Technician Level 4 - Trainer
|
|
Assist in each lower level training procedures least twice with guidance from Mentor/System Lead
|
|
Participate in updating / upgrading tests / training materials.
|
|
Retake all 3 Q&A Pre-test/test in a single supervised sitting lasting no more than 1 hour.
|
|
|