FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

4167 questions

4739 answers

3460 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
720 views
in Vehicle tracking by anonymous

Hello guys,

We've been working with Escort DUBLE and TDBLE sensors with the bluetooh feature from Teltonika devices.

We are facing some problems using FMB920 with FW 03.27.07.Rev.00. The problem happens when we use Non Stop Scan Enable. Sometimes the tracker have the values of the sensors stucked with the same value for long times, as you can see in the images. I haven't found yet when does the bug stops happening, but if the Non Stop Scan is Disabled, it doesn't happen.

I really need this feature working because we are using DUBLE for some operations that sometimes happens faster than 30 seconds, so we need a short period for updates of the sensors and the only way is using non stop scan.

Bug:

Working fine:

Do you know what could be the cause? Connecting the sensors with the app from Escort, everything is fine, they're updating as usually, just the tracker stops updating properly.

by anonymous
Teltonika team, do you have any thoughts on this?

2 Answers

0 votes
by anonymous
Hi, have you tried disabling AFTER SCAN option on beacon list menu?
by anonymous

Hello,

Do you mean any of this options on the image?

by anonymous
Sorry, FMB920 has not the parameter i told you.

Try analyzing the messages on Wialon, are there any sensor parameters with a value of 3000? If yes put BEACON TIMEOUT option to 20 or 30 seconds.
by anonymous
Actually there isn't, the parameters just start a cicle repeating themselves for a long and undetermined period until they update again and start once again the cicle.
by anonymous

Hello Teltonika team,

I had the same problem happening these days in a unit. I'm sending attached the log file of the tracker.

Also, you can see the problem happening in the printscreen.

https://drive.google.com/file/d/1lZ_TE5wPINGrFkirX1NyuwGoBLpjCKtJ/view?usp=sharing

0 votes
by anonymous

Hello @Fernando Brochetto:

I am facing the exact same issue with the DUBLE, 30 seconds between scan is simply not enough to report data on a timely matter and/or correct telemetry from the sensor. I am just about to test "non stop scan" on an FMC130, I will let you know if it has the same issue that you are reporting on the FMB920.

Question to the Teltonika Team: Can you share pros and cons on using 30sec scan vs non stop scan? There is very little information regarding these two options and it is crucial for any bluetooth sensor pairing....maybe not important for fuel sensors but for angle/rotation/light presence / temperature it is crucial to read the information live...not every 30 sec. 

Regards

by anonymous
Hello @jcvillalobos

Thank you for supporting this topic. I opened a ticket with Teltonika, but they asked me to take the log of the devices. Unfortunately its a difficult process to do in the client we are facing these problems, so the only solution that helped me was to disable the non stop scan, although is not what we need.
by anonymous

I have tested an FMC130 configured with non-stop scan. Graph below is for RPMs (positive=RPMs to the right, negative=RPMs to the left. As soon as direction changes, tracker will report the change.

In the IO section I configured to high priority message and "operand: Change".

 

Hope it helps

by anonymous

Hello @jcvillalobos,

I tested with FMM130, the same problem has happened, soon or later, it happens again, thats why it is also difficult to send logs to Teltonika.

by anonymous
Can you send a picture of the IO settings tab? It may have to do with how each IO is configured.

Also what application are you using it for? angle, rotation? and what firmware do you have on the DUBLE?
by anonymous
ok just to keep updating....I have been using the sensor with the FMC130 for 3 weeks now and have had no issues with it, I´m guessing it has to do with IO configurations, let me know if you have any questions.

Regards
by anonymous

Hello @jcvillalobos, how many devices have you connected? Are they still with non stop scan activated?

I had devices (FMB920) that leasted for months working good with non stop scan activated, but soon or later the problem happened.

by anonymous
I currently have 4 in use, but since you say it happens after several months, I would have to keep running tests. I´ll continue to monitor my units and let you know.
by anonymous
Sure, could you send me your config file? I wanna check it if we use the same parameters.