I am configuring my tracker FMC130 version 04.00.00 rev13.
My goal is to keep the device in Online Deep Sleep (or any other type of sleep is possible), but I want to remotely force it to wake up, get a GPS fix, and start send live data to the server. As far as I´ve read in the Wiki, this can be done via SMS command “on_demand_tracking X”.
I have configured Tracking on Demand in Data Acquisition. Per the wiki for this FW branch, I enabled an activation source by selecting DIN3 (even thoughDIN3 has no physical connection by wire), and mapped DIN3 in the I/O tab to High Priority and Operand: On Change to initialize the software module.
However, sending on_demand_tracking 1 or on_demand_tracking 2 via SMS while the device is ether in GPS sleep or Online Speep does not wake it (judging by the LEDs and no reaction). The device responds perfectly to standard text diagnostics (like getstatus and ggps), confirming cellular radio is awake, but the software tracking commands are ignored.
To answer your question regarding waking the device up to get new coordinates, there are a couple of key points to keep in mind regarding how sleep modes work:
First, the device automatically goes into sleep mode when no ignition or movement and other general conditions mentioned in the wiki are achived. If the vehicle is parked in the exact same location, there is no technical reason for the device to wake its GPS module up just to capture the same coordinates it already has.
Second, for the device to wake up from any sleep mode, it relies on specific hardware triggers. Different sleep modes offer different power-saving levels:
In GPS Sleep mode: The GNSS module turns off to save power, but GSM stays fully active.
In Online Deep Sleep mode: Same like GPS sleep but GSM part or GPRS part would be registered to network if it was opened before going into sleep mode and can send or receive SMS unless like GPS sleep it receives.
However, actually waking the unit from these sleep states requires one of these two events:
Movement is detected by the internal accelerometer (or your configured movement source).
The ignition source is physically turned on.
Regarding the On-Demand High Priority records not generating continuously:
The on_demand_tracking 2 command you are sending will only force one single high-priority record right at that moment. Because you have DIN3 configured as “On Change,” the device expects a physical state transition (going from 0 to 1, or 1 to 0) to trigger any subsequent high-priority events. If the wire is just sitting idle and the status isn’t physically changing, the device won’t create a continuous stream of records.
To get this working for future testing, you will need to connect DIN3 to an external trigger or switch and physically change its state to force those high-priority packets
So, how do I need to configure the softwage of the tracker to wake up from GPS Sleep or Online Deep Sleep mode and start sending data to the server by on_demand_tracking sms?
In Online Deep Sleep mode, the device can send and receive SMS commands, and based on this, on-demand tracking can be triggered. However, waking up the device depends on DIN1 status change or accelerometer movement detection.
For On-Demand Tracking, the following behavior is applicable:
If the On-Demand Tracking period is lower than the normal record acquisition period, only high-priority records will be generated during the tracking period.
If the On-Demand Tracking period is greater than the normal record acquisition period, low-priority records will be created according to the configured data acquisition settings, and high-priority records will be generated after the On-Demand Tracking period is completed.