Open issues blocking release 3.2.016
As the other thread got off-topic: I'd still like to get forward regarding release 3.2.016. We identified three open issues: 1. VW e-Up sometimes stays awake for 4-5 hours. 2. Wifi AP connection is unstable with some devices. 3. More frequent location flatbed theft false alerts. My current status on these is: 1. …is probably not a bug on the OVMS but rather a real behaviour of the e-Up performing an extended 12V trickle charge. 2. …has only been reported by Steve Davies and seems (?) to have been solved by the default scan timings – Steve? 3. …seems to be a Heisenbug, i.e. hasn't had any reports since we added extended logging. Is my status correct? If so, I think these should no longer stop us from releasing 3.2.016. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
For the VW e-Up all is fine by me. The blocking by T26 as hypothetical protection for triggering the extended 12v charging is still in the code. That is, from my point of view, the way to go, as long is this behaviour is still not completely understood. Regards Chris Am Samstag, den 27.02.2021, 16:47 +0100 schrieb Michael Balzer:
As the other thread got off-topic: I'd still like to get forward regarding release 3.2.016.
We identified three open issues:
VW e-Up sometimes stays awake for 4-5 hours. Wifi AP connection is unstable with some devices. More frequent location flatbed theft false alerts.
My current status on these is:
…is probably not a bug on the OVMS but rather a real behaviour of the e-Up performing an extended 12V trickle charge. …has only been reported by Steve Davies and seems (?) to have been solved by the default scan timings – Steve? …seems to be a Heisenbug, i.e. hasn't had any reports since we added extended logging.
Is my status correct? If so, I think these should no longer stop us from releasing 3.2.016.
Regards,
Michael
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
I got one false theft alert a few days back, but it seems the server logs aren't saved that long... :( relevant lines of console log attached. sharkcow Am 27.02.21 um 16:47 schrieb Michael Balzer:
As the other thread got off-topic: I'd still like to get forward regarding release 3.2.016.
We identified three open issues:
1. VW e-Up sometimes stays awake for 4-5 hours. 2. Wifi AP connection is unstable with some devices. 3. More frequent location flatbed theft false alerts.
My current status on these is:
1. …is probably not a bug on the OVMS but rather a real behaviour of the e-Up performing an extended 12V trickle charge. 2. …has only been reported by Steve Davies and seems (?) to have been solved by the default scan timings – Steve? 3. …seems to be a Heisenbug, i.e. hasn't had any reports since we added extended logging.
Is my status correct? If so, I think these should no longer stop us from releasing 3.2.016.
Regards, Michael
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Heiko, off-topic, but that's why I provide the email export feature on my server. Simply tick the checkbox and set your desired export time, and the server will send you a full data export zipped once per day. That way you can always go gack in time to any point. Your log excerpt was a bit too narrowed down, please show a few more messages with the "location" tag around the alert. Regards, Michael Am 27.02.21 um 17:41 schrieb sharkcow:
I got one false theft alert a few days back, but it seems the server logs aren't saved that long... :(
relevant lines of console log attached.
sharkcow
Am 27.02.21 um 16:47 schrieb Michael Balzer:
As the other thread got off-topic: I'd still like to get forward regarding release 3.2.016.
We identified three open issues:
1. VW e-Up sometimes stays awake for 4-5 hours. 2. Wifi AP connection is unstable with some devices. 3. More frequent location flatbed theft false alerts.
My current status on these is:
1. …is probably not a bug on the OVMS but rather a real behaviour of the e-Up performing an extended 12V trickle charge. 2. …has only been reported by Steve Davies and seems (?) to have been solved by the default scan timings – Steve? 3. …seems to be a Heisenbug, i.e. hasn't had any reports since we added extended logging.
Is my status correct? If so, I think these should no longer stop us from releasing 3.2.016.
Regards, Michael
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Ah, thanks for the tip (I had that on in the beginning but could'nt make much of the logs so I'd turned it off meanwhile :-/) Here's a bit more log info. Am 27.02.21 um 17:57 schrieb Michael Balzer:
Heiko,
off-topic, but that's why I provide the email export feature on my server. Simply tick the checkbox and set your desired export time, and the server will send you a full data export zipped once per day.
That way you can always go gack in time to any point.
Your log excerpt was a bit too narrowed down, please show a few more messages with the "location" tag around the alert.
Regards, Michael
Am 27.02.21 um 17:41 schrieb sharkcow:
I got one false theft alert a few days back, but it seems the server logs aren't saved that long... :(
relevant lines of console log attached.
sharkcow
Am 27.02.21 um 16:47 schrieb Michael Balzer:
As the other thread got off-topic: I'd still like to get forward regarding release 3.2.016.
We identified three open issues:
1. VW e-Up sometimes stays awake for 4-5 hours. 2. Wifi AP connection is unstable with some devices. 3. More frequent location flatbed theft false alerts.
My current status on these is:
1. …is probably not a bug on the OVMS but rather a real behaviour of the e-Up performing an extended 12V trickle charge. 2. …has only been reported by Steve Davies and seems (?) to have been solved by the default scan timings – Steve? 3. …seems to be a Heisenbug, i.e. hasn't had any reports since we added extended logging.
Is my status correct? If so, I think these should no longer stop us from releasing 3.2.016.
Regards, Michael
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Heiko, that log excerpt was sufficient to now be sure we cannot do anything about these false alerts. You can only raise your alert threshold. 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. … 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 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 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 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 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 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 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 2021-02-21 15:58:52.688 CET I (288952398) ovms-server-v2: Send MP-0 L*48.987923,12.216293*,0,338.8,0,0,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0 2021-02-21 15:59:09.668 CET I (288969378) ovms-server-v2: Send MP-0 L*48.986771,12.213362*,310.5,72,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,6,1.4,0.0 *→ first jump to 200m distance* 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 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 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 2021-02-21 16:00:24.378 CET W (289044098) location: CheckTheft: flatbed.moved @*48.994774,12.209670* gpsmode=AN satcount=5 hdop=1.9 gpsspeed=0.0 *→ second jump to 906m distance → alert* 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 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 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 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 2021-02-21 16:01:43.658 CET I (289123378) ovms-server-v2: Send MP-0 L*48.987961,12.216274*,124.1,345.1,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AA,9,1.2,0.0 *→ back to park position* 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 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 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 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 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 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 … 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. IOW, that looked exactly like an actual flatbed theft would have looked. The only thing you can do is raise your theft alert threshold to, say, 1000m. Or higher if these GPS jumps go beyond 1000m. It seems this is a glitch in the SIM5360 GPS receiver. Regards, Michael Am 27.02.21 um 19:57 schrieb sharkcow:
Ah, thanks for the tip (I had that on in the beginning but could'nt make much of the logs so I'd turned it off meanwhile :-/)
Here's a bit more log info.
Am 27.02.21 um 17:57 schrieb Michael Balzer:
Heiko,
off-topic, but that's why I provide the email export feature on my server. Simply tick the checkbox and set your desired export time, and the server will send you a full data export zipped once per day.
That way you can always go gack in time to any point.
Your log excerpt was a bit too narrowed down, please show a few more messages with the "location" tag around the alert.
Regards, Michael
Am 27.02.21 um 17:41 schrieb sharkcow:
I got one false theft alert a few days back, but it seems the server logs aren't saved that long... :(
relevant lines of console log attached.
sharkcow
Am 27.02.21 um 16:47 schrieb Michael Balzer:
As the other thread got off-topic: I'd still like to get forward regarding release 3.2.016.
We identified three open issues:
1. VW e-Up sometimes stays awake for 4-5 hours. 2. Wifi AP connection is unstable with some devices. 3. More frequent location flatbed theft false alerts.
My current status on these is:
1. …is probably not a bug on the OVMS but rather a real behaviour of the e-Up performing an extended 12V trickle charge. 2. …has only been reported by Steve Davies and seems (?) to have been solved by the default scan timings – Steve? 3. …seems to be a Heisenbug, i.e. hasn't had any reports since we added extended logging.
Is my status correct? If so, I think these should no longer stop us from releasing 3.2.016.
Regards, Michael
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
OK, thank you for taking the time to analyze this, Michael! Am 27.02.21 um 22:53 schrieb Michael Balzer:
Heiko,
that log excerpt was sufficient to now be sure we cannot do anything about these false alerts. You can only raise your alert threshold.
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.
… 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 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 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 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 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 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 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 2021-02-21 15:58:52.688 CET I (288952398) ovms-server-v2: Send MP-0 L*48.987923,12.216293*,0,338.8,0,0,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0
2021-02-21 15:59:09.668 CET I (288969378) ovms-server-v2: Send MP-0 L*48.986771,12.213362*,310.5,72,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,6,1.4,0.0 *→ first jump to 200m distance* 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 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 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
2021-02-21 16:00:24.378 CET W (289044098) location: CheckTheft: flatbed.moved @*48.994774,12.209670* gpsmode=AN satcount=5 hdop=1.9 gpsspeed=0.0 *→ second jump to 906m distance → alert* 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 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 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 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
2021-02-21 16:01:43.658 CET I (289123378) ovms-server-v2: Send MP-0 L*48.987961,12.216274*,124.1,345.1,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AA,9,1.2,0.0 *→ back to park position* 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 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 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 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 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 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 …
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.
IOW, that looked exactly like an actual flatbed theft would have looked.
The only thing you can do is raise your theft alert threshold to, say, 1000m. Or higher if these GPS jumps go beyond 1000m.
It seems this is a glitch in the SIM5360 GPS receiver.
Regards, Michael
Am 27.02.21 um 19:57 schrieb sharkcow:
Ah, thanks for the tip (I had that on in the beginning but could'nt make much of the logs so I'd turned it off meanwhile :-/)
Here's a bit more log info.
Am 27.02.21 um 17:57 schrieb Michael Balzer:
Heiko,
off-topic, but that's why I provide the email export feature on my server. Simply tick the checkbox and set your desired export time, and the server will send you a full data export zipped once per day.
That way you can always go gack in time to any point.
Your log excerpt was a bit too narrowed down, please show a few more messages with the "location" tag around the alert.
Regards, Michael
Am 27.02.21 um 17:41 schrieb sharkcow:
I got one false theft alert a few days back, but it seems the server logs aren't saved that long... :(
relevant lines of console log attached.
sharkcow
Am 27.02.21 um 16:47 schrieb Michael Balzer:
As the other thread got off-topic: I'd still like to get forward regarding release 3.2.016.
We identified three open issues:
1. VW e-Up sometimes stays awake for 4-5 hours. 2. Wifi AP connection is unstable with some devices. 3. More frequent location flatbed theft false alerts.
My current status on these is:
1. …is probably not a bug on the OVMS but rather a real behaviour of the e-Up performing an extended 12V trickle charge. 2. …has only been reported by Steve Davies and seems (?) to have been solved by the default scan timings – Steve? 3. …seems to be a Heisenbug, i.e. hasn't had any reports since we added extended logging.
Is my status correct? If so, I think these should no longer stop us from releasing 3.2.016.
Regards, Michael
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
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. 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. @all: to provide data on this, you need to set the log level for "location" to verbose: config set log level.location verbose "CheckTheft" log messages will then be created for any location change for more than 10m while parking. Regards, Michael Am 27.02.21 um 22:53 schrieb Michael Balzer:
Heiko,
that log excerpt was sufficient to now be sure we cannot do anything about these false alerts. You can only raise your alert threshold.
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.
… 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 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 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 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 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 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 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 2021-02-21 15:58:52.688 CET I (288952398) ovms-server-v2: Send MP-0 L*48.987923,12.216293*,0,338.8,0,0,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0
2021-02-21 15:59:09.668 CET I (288969378) ovms-server-v2: Send MP-0 L*48.986771,12.213362*,310.5,72,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,6,1.4,0.0 *→ first jump to 200m distance* 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 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 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
2021-02-21 16:00:24.378 CET W (289044098) location: CheckTheft: flatbed.moved @*48.994774,12.209670* gpsmode=AN satcount=5 hdop=1.9 gpsspeed=0.0 *→ second jump to 906m distance → alert* 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 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 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 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
2021-02-21 16:01:43.658 CET I (289123378) ovms-server-v2: Send MP-0 L*48.987961,12.216274*,124.1,345.1,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AA,9,1.2,0.0 *→ back to park position* 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 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 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 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 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 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 …
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.
IOW, that looked exactly like an actual flatbed theft would have looked.
The only thing you can do is raise your theft alert threshold to, say, 1000m. Or higher if these GPS jumps go beyond 1000m.
It seems this is a glitch in the SIM5360 GPS receiver.
Regards, Michael
Am 27.02.21 um 19:57 schrieb sharkcow:
Ah, thanks for the tip (I had that on in the beginning but could'nt make much of the logs so I'd turned it off meanwhile :-/)
Here's a bit more log info.
Am 27.02.21 um 17:57 schrieb Michael Balzer:
Heiko,
off-topic, but that's why I provide the email export feature on my server. Simply tick the checkbox and set your desired export time, and the server will send you a full data export zipped once per day.
That way you can always go gack in time to any point.
Your log excerpt was a bit too narrowed down, please show a few more messages with the "location" tag around the alert.
Regards, Michael
Am 27.02.21 um 17:41 schrieb sharkcow:
I got one false theft alert a few days back, but it seems the server logs aren't saved that long... :(
relevant lines of console log attached.
sharkcow
Am 27.02.21 um 16:47 schrieb Michael Balzer:
As the other thread got off-topic: I'd still like to get forward regarding release 3.2.016.
We identified three open issues:
1. VW e-Up sometimes stays awake for 4-5 hours. 2. Wifi AP connection is unstable with some devices. 3. More frequent location flatbed theft false alerts.
My current status on these is:
1. …is probably not a bug on the OVMS but rather a real behaviour of the e-Up performing an extended 12V trickle charge. 2. …has only been reported by Steve Davies and seems (?) to have been solved by the default scan timings – Steve? 3. …seems to be a Heisenbug, i.e. hasn't had any reports since we added extended logging.
Is my status correct? If so, I think these should no longer stop us from releasing 3.2.016.
Regards, Michael
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
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). Mark
On 28 Feb 2021, at 3:57 PM, Michael Balzer <dexter@expeedo.de> wrote:
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.
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.
@all: to provide data on this, you need to set the log level for "location" to verbose:
config set log level.location verbose
"CheckTheft" log messages will then be created for any location change for more than 10m while parking.
Regards, Michael
Am 27.02.21 um 22:53 schrieb Michael Balzer:
Heiko,
that log excerpt was sufficient to now be sure we cannot do anything about these false alerts. You can only raise your alert threshold.
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.
… 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 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 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 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 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 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 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 2021-02-21 15:58:52.688 CET I (288952398) ovms-server-v2: Send MP-0 L48.987923,12.216293,0,338.8,0,0,0.0,30,0,0.000,0.951,0.053,0,0,AN,8,0.9,0.0
2021-02-21 15:59:09.668 CET I (288969378) ovms-server-v2: Send MP-0 L48.986771,12.213362,310.5,72,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AN,6,1.4,0.0 → first jump to 200m distance 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 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 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
2021-02-21 16:00:24.378 CET W (289044098) location: CheckTheft: flatbed.moved @48.994774,12.209670 gpsmode=AN satcount=5 hdop=1.9 gpsspeed=0.0 → second jump to 906m distance → alert 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 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 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 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
2021-02-21 16:01:43.658 CET I (289123378) ovms-server-v2: Send MP-0 L48.987961,12.216274,124.1,345.1,1,1,0.0,30,0,0.000,0.951,0.053,0,0,AA,9,1.2,0.0 → back to park position 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 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 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 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 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 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 …
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.
IOW, that looked exactly like an actual flatbed theft would have looked.
The only thing you can do is raise your theft alert threshold to, say, 1000m. Or higher if these GPS jumps go beyond 1000m.
It seems this is a glitch in the SIM5360 GPS receiver.
Regards, Michael
Am 27.02.21 um 19:57 schrieb sharkcow:
Ah, thanks for the tip (I had that on in the beginning but could'nt make much of the logs so I'd turned it off meanwhile :-/)
Here's a bit more log info.
Am 27.02.21 um 17:57 schrieb Michael Balzer:
Heiko,
off-topic, but that's why I provide the email export feature on my server. Simply tick the checkbox and set your desired export time, and the server will send you a full data export zipped once per day.
That way you can always go gack in time to any point.
Your log excerpt was a bit too narrowed down, please show a few more messages with the "location" tag around the alert.
Regards, Michael
Am 27.02.21 um 17:41 schrieb sharkcow:
I got one false theft alert a few days back, but it seems the server logs aren't saved that long... :(
relevant lines of console log attached.
sharkcow
Am 27.02.21 um 16:47 schrieb Michael Balzer:
As the other thread got off-topic: I'd still like to get forward regarding release 3.2.016.
We identified three open issues:
1. VW e-Up sometimes stays awake for 4-5 hours. 2. Wifi AP connection is unstable with some devices. 3. More frequent location flatbed theft false alerts.
My current status on these is:
1. …is probably not a bug on the OVMS but rather a real behaviour of the e-Up performing an extended 12V trickle charge. 2. …has only been reported by Steve Davies and seems (?) to have been solved by the default scan timings – Steve? 3. …seems to be a Heisenbug, i.e. hasn't had any reports since we added extended logging.
Is my status correct? If so, I think these should no longer stop us from releasing 3.2.016.
Regards, Michael
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
I had my first real one of these trigger last night: 1616938067 2021-03-28 13:27:47 53961 #158 C rx msg P AVehicle is being transported while parked - possible theft/flatbed (@0.000000;-?.??????) There are logs for a valid gps position ~6 minutes prior and 30 second after this. But here's the log (1 second after the alert) that shows the nmea sentence: 1616938068 2021-03-28 13:27:48 53968 #158 C rx msg L 0.000000,?.??????,0,9,1,1,0.0,0,0,0,0,0,0,0,12,0,0.0,0.0 That one is very interesting because the latitude is 0.0 but the reported longitude is really the latitude! The log essentially tells this story: A,B A,B 0,B 0,A A,B A,B Sort of looks like a simcom bug? (I don't want to post my location to the mailing list but I can send the raw log to interested parties.) Craig
Craig, I agree, that one looks like a modem bug, and like one we can detect. The other case was different though, coordinates seemed legit. Regards, Michael Am 29.03.21 um 02:02 schrieb Craig Leres:
I had my first real one of these trigger last night:
1616938067 2021-03-28 13:27:47 53961 #158 C rx msg P AVehicle is being transported while parked - possible theft/flatbed (@0.000000;-?.??????)
There are logs for a valid gps position ~6 minutes prior and 30 second after this. But here's the log (1 second after the alert) that shows the nmea sentence:
1616938068 2021-03-28 13:27:48 53968 #158 C rx msg L 0.000000,?.??????,0,9,1,1,0.0,0,0,0,0,0,0,0,12,0,0.0,0.0
That one is very interesting because the latitude is 0.0 but the reported longitude is really the latitude! The log essentially tells this story:
A,B A,B 0,B 0,A A,B A,B
Sort of looks like a simcom bug?
(I don't want to post my location to the mailing list but I can send the raw log to interested parties.)
Craig _______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
I had this happen again last night but this time it was the longitude that was zero; pull request #637 should solve it. Craig
On Sat, 27 Feb 2021 at 17:48, Michael Balzer <dexter@expeedo.de> wrote:
1. Wifi AP connection is unstable with some devices 2. …has only been reported by Steve Davies and seems (?) to have been solved by the default scan timings – Steve? 3.
Hi, I took the car out to check and this problem is resolved. I had no issues with my android tablet losing connection to the SSID. Thanks, Steve -- https://www.telviva.co.za/legal/email-disclaimer <https://www.telviva.co.za/legal/email-disclaimer>
participants (6)
-
Chris van der Meijden -
Craig Leres -
Mark Webb-Johnson -
Michael Balzer -
sharkcow -
Steve Davies