osu-uwrt / maelstrom_firmware Goto Github PK

Everything electrical and non-hardware

C 15.19% VHDL 0.99% HTML 0.91% Verilog 34.09% Tcl 10.87% Scheme 0.02% SystemVerilog 25.94% Python 1.51% JavaScript 0.08% TypeScript 6.91% Makefile 0.02% C++ 0.22% Processing 0.25% SCSS 3.00%

maelstrom_firmware's People

Contributors

Stargazers

Watchers

Forkers

c-fletcher leosato justbenj shmaugust blaine141 schmidt12 andrew-tian humanchuk1 yoonlee-lab mcdavid32 nissekl netouchmail

maelstrom_firmware's Issues

Temperature control

There is a thermostat-like control on the operator console. If the robot is more than capable of cooling itself, implement the thermostat feature. If not, always leave cooling on and change the control on the operator console to not look so thermostat-like

Error 16

Every once in a while a command will have an error 16 or it will occur while trying to initialize something. Seems to be I2C related

Watchdog Timer

The device sometimes fails. When it fails, that could entail that it stops receiving socket data, or code could stop, or it could just stop being able to send responses. We don't know. There is however a common idea in embedded systems of a watchdog timer. When there is an issue, the device restarts itself.

Implement a log

Make the copro log errors in a file so you can read it after you power down the robot

Rename repo

Change it to uwrt_firmware or maelstrom_firmware. Current name does not reflect the current status of the team and may be confusing

Include energy consumed

Integrate amperage to find how much energy each battery can provide. Also see the breakdown of what is consuming energy

Make copro have light reset

When there is a hard reset, it restarts the computers. Dont

Depth sensor error

Every once in a while the depth sensor will have an error. See if this is an issue. It just prevents the copro from updating depth every once in a while right now.

Program copro over network

Make the copro able to be programmed over network. There is some code to do it over ftp and some to do it over telnet

Copro timing analysis

Find some way to analyze what takes how much time on the copro. Is it being maxed out? what takes the longest? Is the sensor caching making things faster or slower?

Converter board ADC reads wrong

Converter board's logic level voltages are not reading correctly. The currents are not either. The current sensors may have been fried when the board was first powered on. Check into it. The battery balancer required a calibration for voltage readings but the current sensors always seemed to work. Check to see if it is still reading correctly

Implement warning lights

That status board is out of commission right now but the lights work. It also has warning lights on it, flashing red lights. Implement code to flash the lights in any warning condition (low battery, high temp) also maybe do something cool with the red green blue lights while the robot is running

Fix the readme

Include in the readme how to set up the copro and info about the code. @blaine141 will add how to build the website