<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">Sounds ok. So long as that extra test is only run if gps is enabled in config, it won’t affect the Tesla cars (or others with gps on the can bus).</div><div dir="ltr"><br></div><div dir="ltr">Mark</div><div dir="ltr"><br><blockquote type="cite">On 28 Feb 2021, at 3:57 PM, Michael Balzer <dexter@expeedo.de> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Maybe we could switch the alert trigger to be "GPS speed valid and
> x while vehicle off / vehicle speed < y". Teslas don't
provide the GPS speed, but for all modem GPS users that could be
more reliable.<br>
<br>
The GPS speed could peak on a jump, but that should be easily
detectable as an invalid speed. We also could use a smoothed value.<br>
<br>
@all: to provide data on this, you need to set the log level for
"location" to verbose:<br>
<br>
<font face="monospace">config set log level.location verbose</font><br>
<br>
"CheckTheft" log messages will then be created for any location
change for more than 10m while parking.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 27.02.21 um 22:53 schrieb Michael
Balzer:<br>
</div>
<blockquote type="cite" cite="mid:e6cfecb9-5570-9020-a600-1c70a9e433d4@expeedo.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Heiko,<br>
<br>
that log excerpt was sufficient to now be sure we cannot do
anything about these false alerts. You can only raise your alert
threshold.<br>
<br>
This happened: your GPS location suddenly went off by 200m, stayed
there for a minute, then jumped to a position off by 900m, stayed
at that point for another minute, then went back to the original
park position.<br>
<br>
<font face="monospace">…<br>
2021-02-21 15:55:09.668 CET I (288729388) ovms-server-v2: Send
MP-0
L48.987923,12.216290,0,338.2,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 15:55:30.658 CET I (288750378) ovms-server-v2: Send
MP-0
L48.987923,12.216290,0,338.4,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 15:56:12.668 CET I (288792388) ovms-server-v2: Send
MP-0
L48.987923,12.216291,0,338.5,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 15:56:33.668 CET I (288813388) ovms-server-v2: Send
MP-0
L48.987923,12.216291,0,338.6,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 15:56:54.668 CET I (288834378) ovms-server-v2: Send
MP-0
L48.987923,12.216292,0,338.6,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 15:57:15.658 CET I (288855378) ovms-server-v2: Send
MP-0
L48.987923,12.216292,0,338.7,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 15:57:57.678 CET I (288897388) ovms-server-v2: Send
MP-0
L48.987923,12.216292,0,338.7,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 15:58:52.688 CET I (288952398) ovms-server-v2: Send
MP-0 L<b>48.987923,12.216293</b>,0,338.8,0,0,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
<br>
2021-02-21 15:59:09.668 CET I (288969378) ovms-server-v2: Send
MP-0 L<b>48.986771,12.213362</b>,310.5,72,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,6,1.4,0.0<br>
<b>→ first jump to 200m distance</b><br>
2021-02-21 15:59:13.678 CET I (288973388) ovms-server-v2: Send
MP-0
L48.986782,12.213336,310.5,68,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,4,1.8,0.7<br>
2021-02-21 15:59:34.668 CET I (288994388) ovms-server-v2: Send
MP-0
L48.986874,12.213301,0,62.4,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,4,1.8,0.0<br>
2021-02-21 15:59:55.668 CET I (289015388) ovms-server-v2: Send
MP-0
L48.986874,12.213300,0,63.8,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,5,1.6,0.0<br>
<br>
2021-02-21 16:00:24.378 CET W (289044098) location: CheckTheft:
flatbed.moved @<b>48.994774,12.209670</b> gpsmode=AN satcount=5
hdop=1.9 gpsspeed=0.0<br>
<b>→ second jump to 906m distance → alert</b><br>
2021-02-21 16:00:24.658 CET I (289044378) ovms-server-v2: Send
MP-0
L48.994774,12.209670,316.9,1925.6,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,5,1.9,0.0<br>
2021-02-21 16:00:37.668 CET I (289057388) ovms-server-v2: Send
MP-0
L48.994671,12.209748,316.9,1908.4,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,5,1.9,0.0<br>
2021-02-21 16:00:58.668 CET I (289078388) ovms-server-v2: Send
MP-0
L48.994465,12.209938,124.1,1876.5,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,6,1.3,1.1<br>
2021-02-21 16:01:19.668 CET I (289099388) ovms-server-v2: Send
MP-0
L48.994236,12.210092,124.1,1831.4,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,6,1.3,0.0<br>
<br>
2021-02-21 16:01:43.658 CET I (289123378) ovms-server-v2: Send
MP-0 L<b>48.987961,12.216274</b>,124.1,345.1,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AA,9,1.2,0.0<br>
<b>→ back to park position</b><br>
2021-02-21 16:01:53.658 CET I (289133378) ovms-server-v2: Send
MP-0
L48.987968,12.216249,124.1,346.3,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 16:02:01.668 CET I (289141388) ovms-server-v2: Send
MP-0
L48.987972,12.216249,124.1,346.4,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 16:02:22.668 CET I (289162388) ovms-server-v2: Send
MP-0
L48.987972,12.216251,124.1,346.7,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 16:02:43.668 CET I (289183388) ovms-server-v2: Send
MP-0
L48.987972,12.216255,124.1,347,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 16:03:04.668 CET I (289204388) ovms-server-v2: Send
MP-0
L48.987972,12.216256,124.1,347,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
2021-02-21 16:03:25.668 CET I (289225388) ovms-server-v2: Send
MP-0
L48.987972,12.216257,124.1,347,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0<br>
…<br>
</font><br>
<br>
Satellite count went down during that episode from 8 to 4, but the
fix wasn't lost and the HDOP was still excellent. 4 satellites
normally are sufficient for a good position, also when the alert
occured, a fifth satellite already had been locked.<br>
<br>
IOW, that looked exactly like an actual flatbed theft would have
looked.<br>
<br>
The only thing you can do is raise your theft alert threshold to,
say, 1000m. Or higher if these GPS jumps go beyond 1000m.<br>
<br>
It seems this is a glitch in the SIM5360 GPS receiver.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 27.02.21 um 19:57 schrieb
sharkcow:<br>
</div>
<blockquote type="cite" cite="mid:df8109f1-0e94-2419-fdf3-324d065eab62@gmx.de">Ah,
thanks for the tip (I had that on in the beginning but could'nt
make <br>
much of the logs so I'd turned it off meanwhile :-/) <br>
<br>
Here's a bit more log info. <br>
<br>
<br>
Am 27.02.21 um 17:57 schrieb Michael Balzer: <br>
<blockquote type="cite">Heiko, <br>
<br>
off-topic, but that's why I provide the email export feature
on my <br>
server. Simply tick the checkbox and set your desired export
time, and <br>
the server will send you a full data export zipped once per
day. <br>
<br>
That way you can always go gack in time to any point. <br>
<br>
Your log excerpt was a bit too narrowed down, please show a
few more <br>
messages with the "location" tag around the alert. <br>
<br>
Regards, <br>
Michael <br>
<br>
<br>
Am 27.02.21 um 17:41 schrieb sharkcow: <br>
<blockquote type="cite">I got one false theft alert a few days
back, but it seems the server <br>
logs aren't saved that long... :( <br>
<br>
relevant lines of console log attached. <br>
<br>
sharkcow <br>
<br>
<br>
Am 27.02.21 um 16:47 schrieb Michael Balzer: <br>
<blockquote type="cite">As the other thread got off-topic:
I'd still like to get forward <br>
regarding release 3.2.016. <br>
<br>
We identified three open issues: <br>
<br>
1. VW e-Up sometimes stays awake for 4-5 hours. <br>
2. Wifi AP connection is unstable with some devices. <br>
3. More frequent location flatbed theft false alerts. <br>
<br>
My current status on these is: <br>
<br>
1. …is probably not a bug on the OVMS but rather a real
behaviour of <br>
the e-Up performing an extended 12V trickle charge. <br>
2. …has only been reported by Steve Davies and seems (?)
to have been <br>
solved by the default scan timings – Steve? <br>
3. …seems to be a Heisenbug, i.e. hasn't had any reports
since we added <br>
extended logging. <br>
<br>
Is my status correct? If so, I think these should no
longer stop us from <br>
releasing 3.2.016. <br>
<br>
Regards, <br>
Michael <br>
<br>
-- <br>
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal <br>
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 <br>
<br>
<br>
_______________________________________________ <br>
OvmsDev mailing list <br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
<br>
</blockquote>
<br>
_______________________________________________ <br>
OvmsDev mailing list <br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
</blockquote>
<br>
-- <br>
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal <br>
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 <br>
<br>
<br>
_______________________________________________ <br>
OvmsDev mailing list <br>
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a> <br>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
<br>
<br>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
<span>_______________________________________________</span><br><span>OvmsDev mailing list</span><br><span>OvmsDev@lists.openvehicles.com</span><br><span>http://lists.openvehicles.com/mailman/listinfo/ovmsdev</span><br></div></blockquote></body></html>