HW Implementation Remaining

Giant list categorized into a couple big buckets of HW functionality left to implement:

Has HAL Method, not in SC NT - Do these exist as HW capabilities?

Power

• 3.3V Rail Voltage
• 3.3V Rail Current
• 3.3V Rail Active
• 3.3V Rail Current Faults
• Get/Set Brownout Voltage

Counter

• SetCounterEdgeConfiguration - Remove this?
• ResetCounter - Implement HAL side offset per discussion in #129
• GetCounterPeriod - rateget updates in counter mode, periodget does not
• SetCounterMaxPeriod/GetCounterStopped - should we just implement this at HAL layer if we want to keep it?
• Class names at WPILib level are Tachometer and UpDownCounter (which no longer has ability to assign a down channel). Remove UpDownCounter?

DIO

• A whole bunch of PWM functions in here, axe these?
• A couple Pulse functions in here, axe these?

Serial Port

• There's no built in serial port. Axe these? Or is there a way to provide a friendly interface for devices that show up as USB Serial?

Has HAL Method, in SC NT, not in MRCLib

• Get CPU Temp

Has HAL Method, in SC NT, in MRCLib - just need to connect the dots

• Get Team Number

In SC NT, not in MRCLib or HAL - Do we want to expose any of these?

• CPU %
• ramAvail
• storage? (3 keys)
• faults subtable - what if anything here do we want to expose to user code?

Other

• GetAnalogValueToVolts/GetAnalogVoltsToValue - The math in these doesn't match what is in GetAnalogVoltage and these methods don't seem to be used? Can we get rid of them?

Start by comparing the HAL, SC NT, and MRCLib capabilities listed in the issue, along with the referenced WPILib classes. The unchecked items are unresolved design questions spanning power, counters, DIO, serial, system metrics, faults, and analog conversion. Done requires decisions on what to expose, remove, or connect, with each selected capability implemented and verified.