FMC003: Never enters deep sleep mode

[wico]

Hi!

I am writing here in the hope to get some pointers.

I do have a couple of FMC003’s (with firmware 04.01.00.rev.12, but it happened with 03.x too) and they work fine, except of one thing: I am unable to put them into “deep sleep”.
Whatever I do, these devices indeed enter “on stop mode” and thats it. From this mode, they continue to report data and never enter “deep sleep”.

These are the relevant current settings:

— Under System —
Records Saving/Sending: Always

Sleep Mode: Deep Sleep
Timeout (min): 1439 ← this is 23h59min

— Under GPRS —
Open Link Timeout (s): 60

— Under Data Aquisition (On Stop) —
Min Period: 1800 ← this is 30min
Min Saved Records: 1
Send Period: 300 ← this is 5min

That means, at least to me:

1. I drive around and all works as expected. Then I park the car.
   Ignition off, no movement anymore.

2. The device goes after some time into the “On Stop” mode. This
   I can clearly verify as the update interval to my server is
   becoming 1800s (and not 5s as it is when driving). So far so good.

3. Now I assume the “Sleep Mode timeout counter” should start to count
   (1439min / 23h59min).

4. During that time, while counting, I still get updates on my server
   every 30min as expected.

5. The last update to my server should come in after ~23h30min (counted
   from the moment the device has entered “on stop mode”):

• Because at ~23h30min a new GPS data point will be stored (that
  makes the “saved records counter” to become 1). This is because
  every 30min a GPS record should get acquired according to the config.
• This triggers the sending of that records some little time later.
  This is because every 300sec it should sent if there is at least 1
  record.

6. After around 23h35min (± some minutes) there should be:

• All records sent
• NO record stored to be sent and no new record acquired
• All GPRS connections to the server are closed after their respective
  timeout

7. When now the “Sleep Mode timeout counter” has reached the 1439min
   (= 23h59min), all conditions to enter deep sleep should be met, or?

I have chosen this weird timeout (23h59min) to give the device plenty of time to sent the latest collected GPS data, close all sockets, calm down and be happy. The next data acquisition would happen after 24h, but that is 1 min after the “Sleep Mode timeout counter” should have kicked in to put the device into deep sleep.

What am I doing wrong?

As additional info, here is the “ruleset” from Teltonika combined with my status assumption:

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
FMC003 can enter deep sleep mode if ALL of these conditions are met:

a) FMC003 is configured in Deep Sleep mode and sleep timeout is reached;
→ yes

b) 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:
o After Position Fix - FMC003 time is synchronized with GNSS satellites
and GPS fix is obtained;
o After Time Sync - FMC003 time is synchronized over NTP, NITZ, or GNSS
satellites;
o Always - FMC003 will enter sleep mode without time synchronization and
GPS fix.
→ yes, I have set it to “Always”

c) Ignition (configured ignition source) is off;
→ yes

d) Movement is not detected by the accelerometer or configured movement source;
→ yes

e) Min. Record Saving Period (Data Acquisition Mode settings) must be
larger than Open Link Timeout parameter, so that FMC003 could close GPRS
link;
→ yes, 1800sec is larger than 60sec

f) The difference between Send Period (Data Acquisition Mode settings)
and Open Link Timeout must be more than 90 seconds, so that FMC003 could
close GPRS link within at least 90 seconds;
→ yes, 300sec minus 60sec is way more then 90sec

g) There are no SMS messages being received;
→ yes, there are no SMS

h) Data socket(s) are closed;
→ yes, I can verify that there are no open TCP connections on the server side

i) Data sending is not in progress;
→ yes, there should be no data sent in progress, device should be
“idle” for quite some time after the last sent

j) FOTA is not in progress.
→ yes, FOTA is disabled
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

That was a long description - sorry for that.

I am more than thankful for any hint. What am I doing wrong here?

Wico

[Ashutosh.Singh]

Hi,

Good Day,

Yes, this is quite a detailed message and appears to be well researched.

I have reviewed your configuration against the FMC003 requirements . While your logic for the GPRS timeouts is correct, there appears to be a conflict between your Sleep Timeout and your Data Acquisition settings.

Recommended Test:

1. Shorten the Sleep Timeout: Try setting it to 10 minutes for testing. This will allow the device to reach the timeout more quicker just to check if it is getting in sleep mode or not.
2. Double-check Ignition/Movement: Ensure that the configured Ignition source (e.g., Digital Input 1 or Voltage) is consistently showing ‘0’ , and that no vibration is detected by the accelerometer during that 10-minute window .

If any event (Ignition or Movement ) occurs during the timeout period, the counter will reset.** .

However, I suggest opening a support ticket , where we will be able to monitor the data if required and also review the configuration file in detail. For general reference, please see the observations below.

Thanks

Ashutosh S.

[wico]

Hej Ashutosh,

thank you for looking into this!

Short question: In case a sudden movement or ignition during the “on stop” mode would be detected, the device will go into “on move” mode - or not? You wrote that the device would still remain in “on stop” mode? Is that correct?

I am confused.

Martin

[Ashutosh.Singh]

Hi,

Good Day,

Apologies for the line stating that the device will be in stop mode; I have edited it now.

Actually, the stop mode switching is dependent on the movement source. In case it is the accelerometer, if any movement is detected, the device will switch to Move mode.

However, I was explaining that the sleep mode exit depends on either of the conditions, such as ignition or movement source. If any of the sources is true, the counter would reset. That is why I suggested checking with lower timeout values like 10–15 minutes so that we can test whether the device is going into sleep mode or not.

Thanks

Ashutosh S.

[wico]

Hej,

yes - ok, now confusion cleared
I will try with a short sleep timeout and we will see - when I find the time to do this.

Thank you!

Martin