GPS flatbed alerts from military jamming/spoofing?
I've had no GPS false alerts since Craig added the NMEA checksum validation and I fixed the VW e-Up state detection. That is, until war on Ukraine began. Since then, I've had multiple alerts, mostly late night. I wouldn't have thought military GPS jamming or spoofing would have an effect with that range, the next war region is ~ 1.200 km from here. I've added some more logging to see if we can detect and filter this. Reduced log from the latest event below. HDOP jumps from 1.8 (good) to 5.6 (bad), but only after the alert has been triggered. Should we generally scale the alarm threshold by HDOP (if available)? Regards, Michael 01:31:35 vehicle dist=15 smoothed=13 alarm=500 gpsmode=AA satcount=6 hdop=2.0 gpsspeed=0.0 01:48:30 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 02:04:10 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 02:20:50 vehicle dist=14 smoothed=16 alarm=500 gpsmode=AA satcount=3 hdop=500.0 gpsspeed=0.0 04:15:15 vehicle dist=260 smoothed=60 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:15:15 vehicle dist=297 smoothed=107 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:15:20 vehicle dist=216 smoothed=129 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=8.5 04:15:20 vehicle dist=184 smoothed=140 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=8.5 04:16:00 vehicle dist=1162 smoothed=344 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:00 vehicle dist=1322 smoothed=540 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:00 CEST W flatbed.moved gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:05 vehicle dist=1419 smoothed=716 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:16:05 vehicle dist=1426 smoothed=858 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:17:25 vehicle dist=710 smoothed=828 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=5.2 04:17:25 vehicle dist=303 smoothed=723 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=5.2 04:17:30 vehicle dist=245 smoothed=627 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:30 vehicle dist=233 smoothed=549 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:35 vehicle dist=161 smoothed=471 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=13.7 04:17:35 vehicle dist=143 smoothed=405 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=13.7 04:17:40 vehicle dist=100 smoothed=344 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:40 vehicle dist=87 smoothed=293 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:45 vehicle dist=50 smoothed=244 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:45 vehicle dist=36 smoothed=203 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:50 vehicle dist=127 smoothed=187 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:50 vehicle dist=136 smoothed=177 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:55 vehicle dist=110 smoothed=164 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:55 vehicle dist=104 smoothed=152 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:18:00 vehicle dist=107 smoothed=135 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=0.0 04:18:05 vehicle dist=57 smoothed=119 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=9.4 04:18:05 vehicle dist=44 smoothed=104 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=9.4 04:18:10 vehicle dist=34 smoothed=90 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.2 04:18:15 vehicle dist=17 smoothed=66 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.8 04:18:15 vehicle dist=6 smoothed=54 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.8 04:18:25 vehicle dist=25 smoothed=35 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=1.7 04:18:25 vehicle dist=29 smoothed=34 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=1.7 04:18:35 vehicle dist=25 smoothed=30 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:32:25 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:48:15 vehicle dist=15 smoothed=14 alarm=500 gpsmode=AA satcount=5 hdop=3.1 gpsspeed=0.0 04:48:20 vehicle dist=15 smoothed=14 alarm=500 gpsmode=AA satcount=5 hdop=3.1 gpsspeed=0.0 04:48:25 vehicle dist=18 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=3.1 gpsspeed=1.5 04:48:30 vehicle dist=14 smoothed=16 alarm=500 gpsmode=AA satcount=4 hdop=6.2 gpsspeed=0.0 -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Should we generally scale the alarm threshold by HDOP (if available)?
This sounds like a good idea and approach. Regards, Mark
On 31 Mar 2022, at 2:15 PM, Michael Balzer <dexter@expeedo.de> wrote:
I've had no GPS false alerts since Craig added the NMEA checksum validation and I fixed the VW e-Up state detection.
That is, until war on Ukraine began. Since then, I've had multiple alerts, mostly late night. I wouldn't have thought military GPS jamming or spoofing would have an effect with that range, the next war region is ~ 1.200 km from here.
I've added some more logging to see if we can detect and filter this.
Reduced log from the latest event below. HDOP jumps from 1.8 (good) to 5.6 (bad), but only after the alert has been triggered.
Should we generally scale the alarm threshold by HDOP (if available)?
Regards, Michael
01:31:35 vehicle dist=15 smoothed=13 alarm=500 gpsmode=AA satcount=6 hdop=2.0 gpsspeed=0.0 01:48:30 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 02:04:10 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 02:20:50 vehicle dist=14 smoothed=16 alarm=500 gpsmode=AA satcount=3 hdop=500.0 gpsspeed=0.0 04:15:15 vehicle dist=260 smoothed=60 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:15:15 vehicle dist=297 smoothed=107 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:15:20 vehicle dist=216 smoothed=129 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=8.5 04:15:20 vehicle dist=184 smoothed=140 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=8.5 04:16:00 vehicle dist=1162 smoothed=344 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:00 vehicle dist=1322 smoothed=540 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:00 CEST W flatbed.moved gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:05 vehicle dist=1419 smoothed=716 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:16:05 vehicle dist=1426 smoothed=858 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:17:25 vehicle dist=710 smoothed=828 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=5.2 04:17:25 vehicle dist=303 smoothed=723 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=5.2 04:17:30 vehicle dist=245 smoothed=627 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:30 vehicle dist=233 smoothed=549 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:35 vehicle dist=161 smoothed=471 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=13.7 04:17:35 vehicle dist=143 smoothed=405 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=13.7 04:17:40 vehicle dist=100 smoothed=344 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:40 vehicle dist=87 smoothed=293 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:45 vehicle dist=50 smoothed=244 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:45 vehicle dist=36 smoothed=203 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:50 vehicle dist=127 smoothed=187 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:50 vehicle dist=136 smoothed=177 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:55 vehicle dist=110 smoothed=164 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:55 vehicle dist=104 smoothed=152 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:18:00 vehicle dist=107 smoothed=135 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=0.0 04:18:05 vehicle dist=57 smoothed=119 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=9.4 04:18:05 vehicle dist=44 smoothed=104 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=9.4 04:18:10 vehicle dist=34 smoothed=90 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.2 04:18:15 vehicle dist=17 smoothed=66 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.8 04:18:15 vehicle dist=6 smoothed=54 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.8 04:18:25 vehicle dist=25 smoothed=35 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=1.7 04:18:25 vehicle dist=29 smoothed=34 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=1.7 04:18:35 vehicle dist=25 smoothed=30 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:32:25 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:48:15 vehicle dist=15 smoothed=14 alarm=500 gpsmode=AA satcount=5 hdop=3.1 gpsspeed=0.0 04:48:20 vehicle dist=15 smoothed=14 alarm=500 gpsmode=AA satcount=5 hdop=3.1 gpsspeed=0.0 04:48:25 vehicle dist=18 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=3.1 gpsspeed=1.5 04:48:30 vehicle dist=14 smoothed=16 alarm=500 gpsmode=AA satcount=4 hdop=6.2 gpsspeed=0.0
-- 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, Aha! I've had two false GPS alerts that occurred since I installed the 4G modem around the end of February, but the modem change should have no effect for my Roadster with its separate GPS sensor. You've identified a different possible correlation. The distance from my location to Ukraine is much farther, but who knows what changes may have occurred. -- Steve On Thu, 31 Mar 2022, Michael Balzer wrote:
I've had no GPS false alerts since Craig added the NMEA checksum validation and I fixed the VW e-Up state detection.
That is, until war on Ukraine began. Since then, I've had multiple alerts, mostly late night. I wouldn't have thought military GPS jamming or spoofing would have an effect with that range, the next war region is ~ 1.200 km from here.
I've added some more logging to see if we can detect and filter this.
Reduced log from the latest event below. HDOP jumps from 1.8 (good) to 5.6 (bad), but only after the alert has been triggered.
Should we generally scale the alarm threshold by HDOP (if available)?
Regards, Michael
01:31:35 vehicle dist=15 smoothed=13 alarm=500 gpsmode=AA satcount=6 hdop=2.0 gpsspeed=0.0 01:48:30 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 02:04:10 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 02:20:50 vehicle dist=14 smoothed=16 alarm=500 gpsmode=AA satcount=3 hdop=500.0 gpsspeed=0.0 04:15:15 vehicle dist=260 smoothed=60 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:15:15 vehicle dist=297 smoothed=107 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:15:20 vehicle dist=216 smoothed=129 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=8.5 04:15:20 vehicle dist=184 smoothed=140 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=8.5 04:16:00 vehicle dist=1162 smoothed=344 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:00 vehicle dist=1322 smoothed=540 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:00 CEST W flatbed.moved gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:05 vehicle dist=1419 smoothed=716 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:16:05 vehicle dist=1426 smoothed=858 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:17:25 vehicle dist=710 smoothed=828 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=5.2 04:17:25 vehicle dist=303 smoothed=723 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=5.2 04:17:30 vehicle dist=245 smoothed=627 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:30 vehicle dist=233 smoothed=549 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:35 vehicle dist=161 smoothed=471 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=13.7 04:17:35 vehicle dist=143 smoothed=405 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=13.7 04:17:40 vehicle dist=100 smoothed=344 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:40 vehicle dist=87 smoothed=293 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:45 vehicle dist=50 smoothed=244 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:45 vehicle dist=36 smoothed=203 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:50 vehicle dist=127 smoothed=187 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:50 vehicle dist=136 smoothed=177 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:55 vehicle dist=110 smoothed=164 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:55 vehicle dist=104 smoothed=152 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:18:00 vehicle dist=107 smoothed=135 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=0.0 04:18:05 vehicle dist=57 smoothed=119 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=9.4 04:18:05 vehicle dist=44 smoothed=104 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=9.4 04:18:10 vehicle dist=34 smoothed=90 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.2 04:18:15 vehicle dist=17 smoothed=66 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.8 04:18:15 vehicle dist=6 smoothed=54 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.8 04:18:25 vehicle dist=25 smoothed=35 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=1.7 04:18:25 vehicle dist=29 smoothed=34 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=1.7 04:18:35 vehicle dist=25 smoothed=30 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:32:25 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:48:15 vehicle dist=15 smoothed=14 alarm=500 gpsmode=AA satcount=5 hdop=3.1 gpsspeed=0.0 04:48:20 vehicle dist=15 smoothed=14 alarm=500 gpsmode=AA satcount=5 hdop=3.1 gpsspeed=0.0 04:48:25 vehicle dist=18 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=3.1 gpsspeed=1.5 04:48:30 vehicle dist=14 smoothed=16 alarm=500 gpsmode=AA satcount=4 hdop=6.2 gpsspeed=0.0
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
On 3/30/22 23:15, Michael Balzer wrote:
I've had no GPS false alerts since Craig added the NMEA checksum validation and I fixed the VW e-Up state detection.
That is, until war on Ukraine began. Since then, I've had multiple alerts, mostly late night. I wouldn't have thought military GPS jamming or spoofing would have an effect with that range, the next war region is ~ 1.200 km from here.
I've added some more logging to see if we can detect and filter this.
Reduced log from the latest event below. HDOP jumps from 1.8 (good) to 5.6 (bad), but only after the alert has been triggered.
Should we generally scale the alarm threshold by HDOP (if available)?
If we did scaling based on HDOP I think we could also lower alarm distance from 500m (250m was my first guess). Here's a quick spreadsheet: https://docs.google.com/spreadsheets/d/1C9mvMw3PSl58qmg-lRHdzMXzB2S4glE4vitd... It's unfortunate that HDOP lags the increase in distance, maybe you could adjust the smoothed calculation to damp that? Craig
I've checked in my logging changes so we can collect some more data on this first. The change also enables repeated alarms, the previous implementation would disable the alarm and further checks/logs on the first trigger. By default, the alarm will be repeated every 15 minutes (if the conditions are still met), new config for this is "vehicle flatbed.alarminterval", 0 disables repetitions. Regards, Michael Am 31.03.22 um 18:51 schrieb Craig Leres:
On 3/30/22 23:15, Michael Balzer wrote:
Reduced log from the latest event below. HDOP jumps from 1.8 (good) to 5.6 (bad), but only after the alert has been triggered.
Should we generally scale the alarm threshold by HDOP (if available)?
If we did scaling based on HDOP I think we could also lower alarm distance from 500m (250m was my first guess). Here's a quick spreadsheet:
https://docs.google.com/spreadsheets/d/1C9mvMw3PSl58qmg-lRHdzMXzB2S4glE4vitd...
It's unfortunate that HDOP lags the increase in distance, maybe you could adjust the smoothed calculation to damp that?
Craig
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Craig, nearly there, you additionally need to set component "location" to level verbose. Changing logging levels via the web UI becomes effective immediately, no need to reboot. More on SD logging: https://docs.openvehicles.com/en/latest/userguide/logging.html#logging-to-sd... Regards, Michael Am 01.04.22 um 00:27 schrieb Craig Leres:
On 3/31/22 13:29, Michael Balzer wrote:
I've checked in my logging changes so we can collect some more data on this first.
I booted this version on a couple of modules, is the attached config sufficient to collect some to the sd card?
Craig
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
On 3/31/22 21:58, Michael Balzer wrote:
nearly there, you additionally need to set component "location" to level verbose.
Ah, I saw hdop being logged in a ESP_LOGI() call so I think the default of info was good enough, I didn't notice it wasn't the one you added. I have one module that's been up for almost a day with zero logs. I guess this can happen if rounding never occurs? if (last_dist != round(dist/10)) [....] I've attached some (anonymized) logs from my dev module. Craig
Craig, to extract the essential data from your logs for analysis, simply do this: cat log.* | { echo "time,dist,smoothed,alarm,gpsmode,satcount,hdop,gpsspeed" ; egrep "CheckTheft: vehicle parked.*hdop" | sed -Ee "s/\.[0-9]{3} .* dist/ dist/g" -e "s/ [a-z]+=/,/g"; } > hdop.csv Attached is your CSV data & mine, with a new alarm today. Your parking lot has pretty good GPS reception with never less than 7 satellites in view, my case is near the edge of GPS unusability with some periods of only 2 satellites in view. Regards, Michael Am 02.04.22 um 19:18 schrieb Craig Leres:
On 3/31/22 21:58, Michael Balzer wrote:
nearly there, you additionally need to set component "location" to level verbose.
Ah, I saw hdop being logged in a ESP_LOGI() call so I think the default of info was good enough, I didn't notice it wasn't the one you added.
I have one module that's been up for almost a day with zero logs. I guess this can happen if rounding never occurs?
if (last_dist != round(dist/10)) [....]
I've attached some (anonymized) logs from my dev module.
Craig
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
On 4/2/22 11:06, Michael Balzer wrote:
Your parking lot has pretty good GPS reception with never less than 7 satellites in view, my case is near the edge of GPS unusability with some periods of only 2 satellites in view.
My condo has a detached two car garage and the walls and tar & gravel roof are fairly RF transparent. My dev unit is in the spare bedroom and there is aluminum (or similar) in the walls and roof that does a good job of blocking both gnss and siriusxm satellite radio so the antenna (attached to window blinds) does not have a 360° view of the sky. Essentially it can only see out the window (which I believe has a UV coating that probably degrades the signal some amount. Craig
Everyone, I've just pushed an attempt to fix the false alerts by introducing and applying a normalized GPS "signal quality" level from the satellite count and HDOP. From analysis of my collected GPS data I've come to the conclusion the HDOP isn't a reliable standlone indicator. I've seen coordinates off by 8 kilometers with HDOP at 1.5, which should normally mean "nearly perfect". Only by taking also the satellite count into account, all false position readings could be filtered. https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/8aa6... GPS: add normalized signal quality level, add web UI live status info Location: flatbed movement alarm only with reliable positioning New metrics: v.p.gpssq -- GPS signal quality [%] (<30 unusable, >50 good, >80 excellent) v.p.gpstime -- Time (UTC) of GPS coordinates [Seconds] New configs: [vehicle] gps.sq.good -- SQ level for location state "reliable", default 60 [vehicle] gps.sq.bad -- SQ level for location state "unreliable", default 40 New events: gps.sq.good -- GPS position is now reliable gps.sq.bad -- GPS position is now unreliable For the Teslas I've added a simple 0/100 setting, and a satellite count based calculation for the Jaguar. Btw, the Model S adaption seems to lack handling for losing the GPS lock, and the Jaguar iPace seems to lack setting the GPS lock at all. The quality level replaces the GPS lock status role for the location module: no location changes or flatbed alerts will be emitted while quality is "bad". The quality formula and thresholds work nicely for my region, please test & report if changes are necessary. I've added the quality level to the MP "L" message, so you can easily check your levels from a daily data export. It's also included in the live widget of the web UI's status page. Regards, Michael Am 02.04.22 um 21:30 schrieb Craig Leres:
On 4/2/22 11:06, Michael Balzer wrote:
Your parking lot has pretty good GPS reception with never less than 7 satellites in view, my case is near the edge of GPS unusability with some periods of only 2 satellites in view.
My condo has a detached two car garage and the walls and tar & gravel roof are fairly RF transparent. My dev unit is in the spare bedroom and there is aluminum (or similar) in the walls and roof that does a good job of blocking both gnss and siriusxm satellite radio so the antenna (attached to window blinds) does not have a 360° view of the sky. Essentially it can only see out the window (which I believe has a UV coating that probably degrades the signal some amount.
Craig
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
participants (4)
-
Craig Leres -
Mark Webb-Johnson -
Michael Balzer -
Stephen Casner