Skip to Content

KO Command – Low Power Mode / Sleep

Configure the system’s power saving mode to optimize battery life.


What is it for?

UseDescription
🔋 Battery savingReduces consumption when vehicle is off
😴 Sleep modeTurns off GPS/GSM after inactivity period
Ultra low consumptionExtreme mode that even turns off CPU
Scheduled wake-upConfigure periodic wake-up cycles
🚗 Auto wake-upActivates by movement or input changes

How it works

KO defines four power states. The device steps down only while IGN is disconnected, and returns to FULL ON as soon as ignition is connected or there is activity on the digital inputs.

StateWhat stays onHow it is enteredHow it is exited
FULL ONEverything: CPU, modem and GPSIGN connected, with KO mode enabled
RESTCPU and modem; GPS already turned off by its own counter (cccc)dddd seconds after IGN OFFIGN ON or input change
TOTAL SLEEPCPU only: modem and GPS offbbbb minutes after entering rest, or immediately with SKO+IGN ON or input change
KO++ (ultra low consumption)Nothing: even the CPU turns off and rules are frozenBy command only: SKO++Movement, inputs or scheduled time

cccc and dddd run in parallel from IGN OFF; bbbb only starts counting once the device has entered REST. With default values (SKOE072002400240) the GPS turns off and the device goes to rest after 4 minutes, and sleeps completely 12 hours later.

In TOTAL SLEEP and in KO++ the modem is off: the device is not online and receives no commands until something wakes it up. Anything that has to happen on wake-up must be configured beforehand, in a rule.


Syntax

ActionCommandResponse
ConfigureSKOabbbbccccddddRKO...
QueryQKORKOabbbbccccddddeeeeffffgggg

Parameters

ParameterDescriptionDefault
aE = enabled, D = disabledD
bbbbMinutes for TOTAL SLEEP from REST0720
ccccSeconds to turn off GPS from IGN OFF0240
ddddSeconds for REST from IGN OFF0240
eeeeCounter minutes for TOTAL SLEEP (read only)-
ffffCounter seconds to turn off GPS (read only)-
ggggCounter seconds for REST (read only)-

Direct Actions

CommandAction
SKO+😴 Force TOTAL SLEEP (if IGN is disconnected)
SKO-🔄 Restart service, turn on GPS and GSM
SKO++⚡ Force ULTRA LOW CONSUMPTION (includes CPU)

⚠️ Ultra Low Consumption Mode (SKO++): the CPU turns off, so the device goes offline and the rule engine is frozen. With a bare SKO++ it wakes up on movement detection (impact sensor / G-force) or on digital input activity; the extended variant also allows scheduling wake-up by time. On its way back it fires KO04+.


Associated Triggers

The KO module exposes five signals (KO00 to KO04) that can be used as a rule trigger (TRG=) or as a condition (CND=). As with any signal, + is the rising edge (the signal becomes 1) and - the falling edge.

SignalIs 1 when…TypeTypical use
KO00The device is in TOTAL SLEEP: the bbbb rest minutes expired and modem and GPS were turned offLevelKO00+ = it just fell asleep
KO01The device is at REST: the dddd seconds since IGN OFF expired, but not yet the bbbb minutes toward total sleepLevelIntermediate stage; drops to 0 when it moves to TOTAL SLEEP
KO02The device is FULL ON: IGN connected with KO mode enabledLevelKO02+ = the vehicle started
KO03KO mode is enabled (SKOE...)LevelAs CND=KO03, to gate rules on low power mode
KO04The device just woke up from KO++ (ultra low consumption)PulseThis is the wake-up trigger: TRG=KO04+

The wake-up one is KO04+. States KO00-KO03 describe where the device sits inside the classic KO cycle, which never turns the CPU off. KO04 is different: it is the only one that reports the device came out of KO++, where the CPU was off and rules were frozen. It is the hook to turn back on whatever ultra low consumption left off, or to open a working window on wake-up.

States and triggers

Three things the diagram does not show:

  • The GPS turns off on its own cccc seconds after IGN OFF, without changing the state.
  • SKO+ forces the jump to TOTAL SLEEP immediately, without waiting for the counters.
  • KO++ is entered with the SKO++ command from any state, not only from FULL ON.

Any activity on the digital inputs while IGN is disconnected reloads the three counters and turns the modules back on, same as SKO-.

Examples with KO04+

>SRLD4E;TRG=KO04+;ACC={STD10R00300}< // on KO++ wake-up: 5 min awake window >SRLE1E;TRG=KO04+;ACC={SSSBTHPWR11}< // on wake-up: turn BLE back on

KO04+ is a pulse: it fires once per wake-up. If you need several actions when leaving KO++, put them all in the same rule — ACC accepts several chained { } blocks — instead of splitting KO04+ across two rules: the second one may miss the pulse.


Extended Ultra Low Consumption Mode

Variant of ultra low consumption mode that allows configuring periodic wake-up.

Extended Syntax

ActionCommandResponse
ConfigureSKO++aaaabcdefgRKO++...
QueryQKO++RKO++aaaabcdefg

Extended Parameters

ParamDescriptionValues
aaaaTime to wake upSeconds (0000 = never). Prefixes: m = min, h = hours
bWake up by movement1 = yes, 0 = no
cWake up by inputs1 = yes, 0 = no
dCellular modem1 = on, 0 = off
eGPS module1 = on, 0 = off
fInternal source1 = on, 0 = off
gExternal source 3.3V1 = on, 0 = off

Examples

Enable basic low power mode

>SKOE072002400240< // Enable KO: 720min sleep, 240sec for GPS off and rest >RKOE072002400240;ID=037883;*5A<

Force total sleep

>SKO+< // Force sleep mode (requires IGN=0) >RKOK;ID=037883;*5A<

Low consumption cycle with periodic reports

>SRL01E;TRG=GPS+;ACC={GBR00L}< // On GPS acquisition, generate report >SRL02E;TRG=BU-;ACC={SKO++0060001000}< // On buffer empty, enter KO++ mode

In this example:

  • When GPS position is obtained → generates BR type 00 report
  • Once buffer is downloaded → enters ultra low consumption mode
  • After 60 seconds → automatically wakes up and repeats the cycle

Compatibility

💾Firmware v1.08.00
SPLegacy
ULLegacy
MTLegacy
C3Legacy
C5Legacy
💾Firmware v1.00.00
SP-IOT
SM-IOT
ZE-IOT
Last updated