v0.1.7

Changes

• Build using cargo-make to make it simpler between Linux and Windows
• LED Matrix Firmware
  • Add debug mode that will display sleep reason in sleep (Enable via command or on DVT module by DIP switch)
  • Separate firmware for EVT module with 10k LED resistor (instead of new 27k resistor)
  • Separate firmware for EVT module because DVT module has different LED layout
  • Update LED Layout for DVT changes
  • Disable SW9 in DVT since it isn't used and can cause noise if not connected
• Python Script/GUI
  • Fix snake game, broken in v0.1.6
  • Show firmware version
  • On launch, set brightness slider to module brightness

Hardware Compatibility

• Multiple LED Matrix firmware builds
  • ledmatrix_10k.uf2 (Hardware with 10k resistor, has firmware current limit)
  • ledmatrix_evt.uf2 (Hardware with 27k resistor, no current limit)
  • ledmatrix.uf2 (Latest Hardware - Aug 28)

Changing Sleep State

What can change the sleep state

• Hardware/OS triggers
  • SLEEP# pin
  • USB Suspend
• Software/Firmware Triggers
  • Sleep/Wake or other command via USB Serial
  • Idle timer

Both of the hardware/OS triggers change the sleep state if they transition from one state to another.
For example, if USB suspends, the LED matrix turns off. If it resumes, the LEDs come back on.
Same for the SLEEP# pin.
If either of them indicates sleep, even if they didn't change state, the module goes to sleep.
If they're active, they don't influence module state. That way sleep state can be controlled by commands and isn't overridden immediately.

The sleep/wake command always changes the state. But it can't be received when USB is suspended.
Any other command will also wake up the device.

The idle timer will send the device to sleep after a configured timeout (default 60 seconds).
The idle timer is reset once the device wakes up or once it receives a command.