Any significant power changing event in meshtastic should be tagged with a powermon state transition.
If you are making new meshtastic features feel free to add new entries at the end of this definition.
GPS is actively trying to find our location
See GPSPowerState for more details
Generated
from enum value: GPS_Active = 2048;
LED_On
LED_On
Generated
from enum value: LED_On = 128;
Lora_RXActive
Lora_RXActive
Generated
from enum value: Lora_RXActive = 32;
Lora_RXOn
Lora_RXOn
Generated
from enum value: Lora_RXOn = 8;
Lora_TXOn
Lora_TXOn
Generated
from enum value: Lora_TXOn = 16;
None
None
Generated
from enum value: None = 0;
Screen_Drawing
Screen_Drawing
Generated
from enum value: Screen_Drawing = 512;
Screen_On
Screen_On
Generated
from enum value: Screen_On = 256;
Vext1_On
Vext1_On
The external Vext1 power is on. Many boards have auxillary power rails that the CPU turns on only
occasionally. In cases where that rail has multiple devices on it we usually want to have logging on
the state of that rail as an independent record.
For instance on the Heltec Tracker 1.1 board, this rail is the power source for the GPS and screen.
The log messages will be short and complete (see PowerMon.Event in the protobufs for details).
something like "S:PM:C,0x00001234,REASON" where the hex number is the bitmask of all current states.
(We use a bitmask for states so that if a log message gets lost it won't be fatal)
Any significant power changing event in meshtastic should be tagged with a powermon state transition. If you are making new meshtastic features feel free to add new entries at the end of this definition.
Generated
from enum meshtastic.PowerMon.State