Difference between revisions of "Template:FMB Sleep modes"
(Added CAN and OBD behaviour for Deep Sleep and Online Deep Sleep under the condition that the page has variable CAN set.) |
|||
Line 42: | Line 42: | ||
[[Image:Deep_Sleep_.gif]] | [[Image:Deep_Sleep_.gif]] | ||
− | Please note that power saving depends on two configurable parameters: ''Send Period'' and ''Minimum Record Saving Period'' in "X on Stop Mode". When records are sent successfully in deep sleep mode, open link timeout counter will be skipped and {{{model|FMM6YX}}} will enter deep sleep mode immediately.<br />Because a lot of functions are disabled in deep sleep mode following I/O elements are disabled from records that are generated in this mode: GSM Signal, GNSS Status, GNSS PDOP, GNSS HDOP, GSM CellID, GSM Area Code, Active GSM Operator{{{txt_IO|, Trip Odometer, Total Odometer, Speed, Fuel Rate GPS, Fuel Used GPS}}} and ICCID. | + | Please note that power saving depends on two configurable parameters: ''Send Period'' and ''Minimum Record Saving Period'' in "X on Stop Mode". When records are sent successfully in deep sleep mode, open link timeout counter will be skipped and {{{model|FMM6YX}}} will enter deep sleep mode immediately.<br />Because a lot of functions are disabled in deep sleep mode following I/O elements are disabled from records that are generated in this mode: GSM Signal, GNSS Status, GNSS PDOP, GNSS HDOP, GSM CellID, GSM Area Code, Active GSM Operator{{{txt_IO|, Trip Odometer, Total Odometer, Speed, Fuel Rate GPS, Fuel Used GPS}}} and ICCID. |
+ | |||
+ | {{#if: {{{CAN|}}} | In this mode, OBD, CAN and Eventual I/O activity is disabled. Records that are generated while the device is sleeping will not contain data from these sources, Parameter AVL IDs will also be excluded from the records. | }} | ||
{{{model|FMM6YX}}} can enter deep sleep mode if ALL of these conditions are met: | {{{model|FMM6YX}}} can enter deep sleep mode if ALL of these conditions are met: | ||
Line 78: | Line 80: | ||
In this mode, the device works as in deep sleep mode, but without deregistering from the GSM network. GSM part stays powered so this increases power consumption. In this mode, the device should send/receive SMS and make/accept calls. It does not close the GPRS context if one was previously opened. | In this mode, the device works as in deep sleep mode, but without deregistering from the GSM network. GSM part stays powered so this increases power consumption. In this mode, the device should send/receive SMS and make/accept calls. It does not close the GPRS context if one was previously opened. | ||
+ | {{#if: {{{CAN|}}} | In this mode, OBD, CAN and Eventual I/O activity is disabled. Records that are generated while the device is sleeping will not contain data from these sources, Parameter AVL IDs will also be excluded from the records. | }} | ||
[[Image:Online_Deep_Sleep_.gif]] | [[Image:Online_Deep_Sleep_.gif]] |
Latest revision as of 13:22, 8 August 2024
There are four sleep modes: GPS sleep, Deep sleep, Online Deep sleep, and Ultra Deep-sleep mode.
Video Demonstration
Here is a visual demonstration of the sleep modes and how they they affect the device.
GPS Sleep mode
FMM6YX is able to go into GPS sleep mode if such mode is enabled.
Sleep mode timeout starts counting when the device is in STOP mode. After timeout is reached and all conditions for GPS sleep mode are met, the device goes into sleep mode.
When in GPS sleep mode, FMM6YX turns the GPS module off and continues making new periodic records. As a result power usage decreases, in turn saving vehicle battery.
FMM6YX will enter GPS sleep mode if ALL of these conditions are met:
- FMM6YX is configured to work in GPS Sleep mode and sleep timeout is reached;
- Device time must be synchronized with GPS satellites. From Firmware 03.18.15 version, this condition depends on the “Records saving/sending without TS” parameter:
- After Position Fix - FMM6YX time is synchronized with GNSS satellites and GPS fix is obtained;
- After Time Sync - FMM6YX time is synchronized over NTP, NITZ, or GNSS satellites;
- Always - FMM6YX will enter sleep mode without time synchronization and GPS fix.
- Movement is not detected by the accelerometer and configured movement source;
- Ignition (configured ignition source) is off;
- There are no SMS messages being received.
![]() |
On Firmware version older than 03.18.15, the device time has to be synchronized with GNSS satellites and GPS fix has to be obtained in order for the device to enter GPS Sleep mode. |
FMM6YX exits GPS sleep mode if ONE of following conditions is true:
- Movement by accelerometer or configured movement source is detected;
- Ignition (configured ignition source) is turned on.
Deep Sleep mode
While in deep sleep mode, FMM6YX sets the GNSS receiver to sleep mode and turns off GSM/GPRS module (hence it is not possible to wake up the device via SMS). Despite records with the last known coordinate being saved and sent to the AVL server (GSM/GPRS module is turned on to send data and then it is turned off), power usage is decreased to save the vehicle's battery.
Please note that power saving depends on two configurable parameters: Send Period and Minimum Record Saving Period in "X on Stop Mode". When records are sent successfully in deep sleep mode, open link timeout counter will be skipped and FMM6YX will enter deep sleep mode immediately.
Because a lot of functions are disabled in deep sleep mode following I/O elements are disabled from records that are generated in this mode: GSM Signal, GNSS Status, GNSS PDOP, GNSS HDOP, GSM CellID, GSM Area Code, Active GSM Operator, Trip Odometer, Total Odometer, Speed, Fuel Rate GPS, Fuel Used GPS and ICCID.
FMM6YX can enter deep sleep mode if ALL of these conditions are met:
- FMM6YX is configured in Deep Sleep mode and sleep timeout is reached;
- Device time must be synchronized with GPS satellites. From Firmware 03.18.15 version, this condition depends on the “Records saving/sending without TS” parameter:
- After Position Fix - FMM6YX time is synchronized with GNSS satellites and GPS fix is obtained;
- After Time Sync - FMM6YX time is synchronized over NTP, NITZ, or GNSS satellites;
- Always - FMM6YX will enter sleep mode without time synchronization and GPS fix.
- Ignition (configured ignition source) is off;
- Movement is not detected by the accelerometer or configured movement source;
- Min. Record Saving Period (Data Acquisition Mode settings) must be larger than Open Link Timeout parameter, so that FMM6YX could close GPRS link;
- The difference between Send Period (Data Acquisition Mode settings) and Open Link Timeout must be more than 90 seconds, so that FMM6YX could close GPRS link within at least 90 seconds;
- There are no SMS messages being received;
- Data socket(s) are closed;
- Data sending is not in progress;
- FOTA is not in progress.
![]() |
On Firmware version older than 03.18.15, the device time has to be synchronized with GNSS satellites and GPS fix has to be obtained in order for the device to enter Deep Sleep mode. |
FMM6YX exits deep sleep mode if ONE of following conditions is true:
- Movement by accelerometer or configured movement source is detected;
- Ignition (configured ignition source) is turned on.
Online Deep Sleep mode
In this mode, the device works as in deep sleep mode, but without deregistering from the GSM network. GSM part stays powered so this increases power consumption. In this mode, the device should send/receive SMS and make/accept calls. It does not close the GPRS context if one was previously opened.
Conditions to enter online deep sleep mode are the same as entering deep sleep mode. FMM6YX exits online sleep mode if ONE of following conditions is true:
- Movement by accelerometer or configured movement source is detected;
- Ignition (configured ignition source) is turned on.
Ultra Deep Sleep mode
Conditions to enter ultra deep sleep mode, where GPS and GSM modem are turned off and device functions are suspended for maximum battery saving, are the same as entering deep sleep mode.
FMM6YX exits ultra deep sleep mode only when DIN1 or movement are detected by accelerometer. Movement source and Ignition source configuration is not taken into account in this case.