Hi, I'm finding the OVMS GPS really unreliable. For instance, here are the current "v.p." values from my OVMS. I'm apparently going 88 km/h on the highway notwithstanding that my car is parked at my house: v.p.acceleration v.p.altitude 9.7m v.p.direction 347.5° v.p.gpshdop 1 v.p.gpslock yes v.p.gpsmode AN v.p.gpsspeed 88.3404km/h v.p.latitude -34.0584 v.p.location v.p.longitude 18.4477 v.p.odometer 15053km v.p.satcount 9 v.p.speed 0km/h v.p.trip 22km xi3.v.p.tripconsumption 125Wh/km xi3.v.p.wheel1_speed 0km/h xi3.v.p.wheel2_speed 0km/h xi3.v.p.wheel3_speed 0km/h xi3.v.p.wheel4_speed 0km/h xi3.v.p.wheel_speed 0km/h Earlier when I went out the GPS position got similarly stuck and only recovered when I power cycled the OVMS. simcom status: OVMS# simcom status Network Registration: RegisteredHome Provider: VodaCom-SA Signal: -99 dBm State: NetMode PPP: Connected on channel: #2 GPS: Connected on channel: #1 I turned the modem off with the gui and then turned it on. Result of doing that was it did not get a PPP connection after some minutes, and the GPS did not connect. I tried this twice with the same result. Position is still the old one as above, no 3G PPP connection and no GPS connection. My GPS antenna is currently on the dashboard - could it be overheating in the sun there? - it is probably pretty warm. (But my car is currently under shade since I got home) I now went and power cycled the OVMS and the SIMCOM connected successfully, GPS connected, and has the correct position: OVMS# metrics list v.p. v.p.acceleration v.p.altitude 5.2m v.p.direction 0° v.p.gpshdop 1 v.p.gpslock yes v.p.gpsmode AA v.p.gpsspeed 0km/h v.p.latitude -34.0XXX v.p.location Home v.p.longitude 18.4XXX v.p.odometer 15053km v.p.satcount 9 v.p.speed 0km/h v.p.trip 22km xi3.v.p.tripconsumption 125Wh/km xi3.v.p.wheel1_speed 0km/h xi3.v.p.wheel2_speed 0km/h xi3.v.p.wheel3_speed 0km/h xi3.v.p.wheel4_speed 0km/h xi3.v.p.wheel_speed 0km/h I'm running with the ABRP script - is it possible that this is impacting the reliability? Otherwise I'm looking for ideas... Thanks, Steve
Steve, a) did you pick an active GPS antenna? I.e. one with a voltage on the label. The module can barely get a signal with passive antennas. b) If you restart the modem, wait for "State: PoweredOff" before starting it again. c) You can monitor the NMEA sentences by setting log level verbose gsm-nmea. d) Not getting PPP as well may point to a general modem issue, maybe also log gsm-mux & simcom to check for that. Regards, Michael Am 12.01.21 um 11:05 schrieb Steve Davies:
Hi,
I'm finding the OVMS GPS really unreliable.
For instance, here are the current "v.p." values from my OVMS.
I'm apparently going 88 km/h on the highway notwithstanding that my car is parked at my house:
v.p.acceleration v.p.altitude 9.7m v.p.direction 347.5° v.p.gpshdop 1 v.p.gpslock yes v.p.gpsmode AN v.p.gpsspeed 88.3404km/h v.p.latitude -34.0584 v.p.location v.p.longitude 18.4477 v.p.odometer 15053km v.p.satcount 9 v.p.speed 0km/h v.p.trip 22km xi3.v.p.tripconsumption 125Wh/km xi3.v.p.wheel1_speed 0km/h xi3.v.p.wheel2_speed 0km/h xi3.v.p.wheel3_speed 0km/h xi3.v.p.wheel4_speed 0km/h xi3.v.p.wheel_speed 0km/h
Earlier when I went out the GPS position got similarly stuck and only recovered when I power cycled the OVMS.
simcom status:
OVMS# simcom status Network Registration: RegisteredHome Provider: VodaCom-SA Signal: -99 dBm
State: NetMode
PPP: Connected on channel: #2
GPS: Connected on channel: #1
I turned the modem off with the gui and then turned it on. Result of doing that was it did not get a PPP connection after some minutes, and the GPS did not connect.
I tried this twice with the same result. Position is still the old one as above, no 3G PPP connection and no GPS connection.
My GPS antenna is currently on the dashboard - could it be overheating in the sun there? - it is probably pretty warm. (But my car is currently under shade since I got home)
I now went and power cycled the OVMS and the SIMCOM connected successfully, GPS connected, and has the correct position:
OVMS# metrics list v.p. v.p.acceleration v.p.altitude 5.2m v.p.direction 0° v.p.gpshdop 1 v.p.gpslock yes v.p.gpsmode AA v.p.gpsspeed 0km/h v.p.latitude -34.0XXX v.p.location Home v.p.longitude 18.4XXX v.p.odometer 15053km v.p.satcount 9 v.p.speed 0km/h v.p.trip 22km xi3.v.p.tripconsumption 125Wh/km xi3.v.p.wheel1_speed 0km/h xi3.v.p.wheel2_speed 0km/h xi3.v.p.wheel3_speed 0km/h xi3.v.p.wheel4_speed 0km/h xi3.v.p.wheel_speed 0km/h
I'm running with the ABRP script - is it possible that this is impacting the reliability?
Otherwise I'm looking for ideas...
Thanks, Steve
_______________________________________________ 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
Hi, My GPS antenna is the one Openenergymonitor sells - Has "Frequency 1575.42MHz" and "Voltage 2.7-5V" on it from which I assume that it is active. I turned on gsm-nmea logging - and put that in my config. I examined logging closely. Seems like I was at latitude = -34.0584, longitude = 18.4477 at 11:01:24 local. Going 89.2km/h on the local M3 freeway. Sounds sensible. We send update to ABRP: 2021-01-12 11:01:24 SAST I (420418) script: [sendlivedata2abrp.js:287:GetUrlABRP] http://api.iternio.com/1/tlm/send?api_key=xxx&token=yyyy&tlm={ "utc":1610442084,"soc":97,"soh":97,"speed":89.2,"car_model":"bmw:i3:19:38:other","lat":"-34.0584","lon":"18.4477","elevation":"9","ext_temp":24.5,"is_charging":0,"batt_temp":21.37,"voltage":394,"current":25.23,"power":"9.9"} (But no sendRequestDone/Failed for quite a while) Just after that the OVMS lost its connection to my v2 server: 2021-01-12 11:01:25 SAST I (421118) ovms-server-v2: Connection is ovms.xxxx:6870 CAA5060 2021-01-12 11:01:25 SAST I (421118) ovms-server-v2: Status: Connecting... Looks like everything was blocked till 11:01:56 (nothing logged - and I poll speed at every second). 11:01:57 we sent some v2 records: 2021-01-12 11:01:57 SAST I (453118) ovms-server-v2: Send MP-0 S96.7,K,0,0.00,idle,standard,230,225,0,0,0,0,0,0,0,0,0,0,122.01,0,0,0,0,0,0,0,0,0,0,232,0,0.00,393.25,97,0.00,0.00 2021-01-12 11:01:57 SAST I (453128) ovms-server-v2: Send MP-0 D128,8,4,32.6352,42.6192,21.37,140,150440,88.8,0,24.5,3,1,1,14.45,0,12.6,144,31.122,-2.08,23 2021-01-12 11:01:57 SAST I (453138) ovms-server-v2: Send MP-0 L-34.058353,18.447664,347.5,9.7,1,1,88.8,140,0,12.981,1.848,0,0,0 2021-01-12 11:01:57 SAST I (453138) ovms-server-v2: Send MP-0 F3.2.015-435-g86461a92-dirty/ota_0/main (build idf v3.3.4-845-gd59ed8bba-dirty Jan 11 2021 08:51:35),WBY8P620607D23024,6,1,BMWI3,VodaCom-SA,-1,-1 But I don't find these in the database so it seems they didn't get there. At 11:01:59 seems like we got our connection back - well for MQTT at least. 2021-01-12 11:01:59 SAST I (455558) ovms-server-v3: Status: OVMS V3 MQTT login successful 2021-01-12 11:01:59 SAST I (455558) ovms-server-v3: Tx event server.v3.connected 2021-01-12 11:02:03 SAST I (456118) ovms-server-v3: Subscribe to MQTT topics 2021-01-12 11:02:03 SAST I (456118) ovms-server-v3: Transmit all metrics Eventually we get the "done" call back in ABRP from the call at 11:01:57: 2021-01-12 11:02:21 SAST I (477558) script: [sendlivedata2abrp.js:267:OnRequestDone] response={"statusCode":200,"statusText":"OK","body":"{\"status\": \"ok\"}",.....} inprogress:0 failed:6 succeeded:32 But the gps position is now stuck - so it seems like when the modem lost its internet connection and recovered the GPS connection never recovered. 11:03:50 I see this: 2021-01-12 11:03:50 SAST I (566298) simcom: CREG Network Registration: Searching 2021-01-12 11:03:50 SAST I (566378) simcom: CREG Network Registration: RegisteredHome Did our connection drop again? Apparently yes since MQTT re-establishes again: 2021-01-12 11:03:51 SAST I (567678) ovms-server-v3: Status: OVMS V3 MQTT login successful 2021-01-12 11:03:51 SAST I (567688) ovms-server-v3: Tx event server.v3.connected 2021-01-12 11:03:54 SAST I (568118) ovms-server-v3: Subscribe to MQTT topics 2021-01-12 11:03:54 SAST I (568118) ovms-server-v3: Transmit all metrics These are sent at 11:03:59: 2021-01-12 11:03:59 SAST I (575118) ovms-server-v2: Send MP-0 S95.4,K,0,0.00,idle,standard,228,222,0,0,0,0,0,0,0,0,0,0,122.01,0,0,0,0,0,0,0,0,0,0,232,0,0.00,392.03,97,0.00,0.00 2021-01-12 11:03:59 SAST I (575128) ovms-server-v2: Send MP-0 D128,8,4,31.59,45.7704,21.88,170,150470,89.1,0,24,3,1,1,14.49,0,12.6,144,31.122,-1.75999,23 2021-01-12 11:03:59 SAST I (575128) ovms-server-v2: Send MP-0 L-34.058353,18.447664,347.5,9.7,1,0,89.1,170,0,7.468,2.431,0,0,0 2021-01-12 11:03:59 SAST I (575138) ovms-server-v2: Send MP-0 F3.2.015-435-g86461a92-dirty/ota_0/main (build idf v3.3.4-845-gd59ed8bba-dirty Jan 11 2021 08:51:35),WBY8P620607D23024,17,1,BMWI3,VodaCom-SA,-1,-1 I see these in the database. But the GPS position can't be right since its the same as before at we're still buzzing along at about 90km/h. But we never see further updates to the GPS position (times here are UTC - 2 hours behind local time): (Or to be exact - the position reported doesn't change). mysql> select * from ovms_historicalmessages where h_timestamp > '2021-01-12 08:50' and h_recordtype = 'L' order by h_timestamp; +-------+-----------+---------------------+--------------+----------------+-------------------------------------------------------------------+---------------------+ | owner | vehicleid | h_timestamp | h_recordtype | h_recordnumber | h_data | h_expires | +-------+-----------+---------------------+--------------+----------------+-------------------------------------------------------------------+---------------------+ | 1 | CAA5060 | 2021-01-12 08:57:53 | L | 0 | -34.081341,18.455862,9,-2.9,1,1,51.4,100,0,1.732,1.220,0,0,0 | 2021-01-13 08:57:53 | | 1 | CAA5060 | 2021-01-12 08:58:54 | L | 0 | -34.079269,18.448431,270.9,15.9,1,1,60,100,0,-12.787,1.300,0,0,0 | 2021-01-13 08:58:54 | | 1 | CAA5060 | 2021-01-12 09:00:05 | L | 0 | -34.077259,18.445993,7.9,9.4,1,1,78.3,110,0,5.127,1.430,0,0,0 | 2021-01-13 09:00:05 | | 1 | CAA5060 | 2021-01-12 09:03:18 | L | 0 | -34.058353,18.447664,347.5,9.7,1,1,88.5,160,0,27.786,2.176,0,0,0 | 2021-01-13 09:03:18 | | 1 | CAA5060 | 2021-01-12 09:03:59 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,89.1,170,0,7.468,2.431,0,0,0 | 2021-01-13 09:03:59 | | 1 | CAA5060 | 2021-01-12 09:05:01 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,22.5,180,0,-10.997,2.340,0,0,0 | 2021-01-13 09:05:01 | | 1 | CAA5060 | 2021-01-12 09:06:04 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,39.4,190,0,15.430,2.489,0,0,0 | 2021-01-13 09:06:04 | | 1 | CAA5060 | 2021-01-12 09:07:03 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,2,190,0,0.745,2.470,0,0,0 | 2021-01-13 09:07:03 | | 1 | CAA5060 | 2021-01-12 09:08:04 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,31.3,200,0,7.751,2.620,0,0,0 | 2021-01-13 09:08:04 | | 1 | CAA5060 | 2021-01-12 09:09:04 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,16.6,200,0,10.479,2.580,0,0,0 | 2021-01-13 09:09:04 | | 1 | CAA5060 | 2021-01-12 09:10:07 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,36.8,200,0,-8.339,2.580,0,0,0 | 2021-01-13 09:10:07 | | 1 | CAA5060 | 2021-01-12 09:11:10 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,22.1,210,0,0.828,2.688,0,0,0 | 2021-01-13 09:11:10 | | 1 | CAA5060 | 2021-01-12 09:12:07 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,29.6,220,0,30.590,2.772,0,0,0 | 2021-01-13 09:12:07 | | 1 | CAA5060 | 2021-01-12 09:13:08 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,36.4,220,0,1.179,2.772,0,0,0 | 2021-01-13 09:13:08 | | 1 | CAA5060 | 2021-01-12 09:14:09 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,30.5,220,0,6.646,2.750,0,0,0 | 2021-01-13 09:14:09 | | 1 | CAA5060 | 2021-01-12 09:15:45 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,0,220,0,0.000,2.750,0,0,0 | 2021-01-13 09:15:45 | | 1 | CAA5060 | 2021-01-12 09:15:55 | L | 0 | -34.058353,18.447664,347.5,9.7,1,0,0,220,0,0.000,2.750,0,0,0 | 2021-01-13 09:15:55 | | 1 | CAA5060 | 2021-01-12 09:39:42 | L | 0 | -34.058353,18.447664,347.5,9.7,0,0,0,220,0,0.000,2.750,0,0,0 | 2021-01-13 09:39:42 | Now this area of Cape Town where I was on the freeway has quite poor cell coverage - it's urban but they won't have dreaded cell towers there. So the drop outs are perhaps expected but it does seem like there is some issue with recovering the GPS connection when the data connection comes back? (Why does the GPS drop when the cell connection drops?) Steve On Tue, 12 Jan 2021 at 12:05, Steve Davies <steve@telviva.co.za> wrote:
Hi,
I'm finding the OVMS GPS really unreliable. (...)
participants (2)
-
Michael Balzer -
Steve Davies