You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bug in the Telit HE910 firmware that reports the GPS speed signal as 1/100 of the actual value. We've known about this for a while so I added a x100 to the signal value before publishing it. Works OK sometimes, but I'm seeing some signal values show up like {"name":"gps_speed","value":10721}. The GPS speed signal values around these instances make me think that these instances are 100x too high.
I'm also noticing that other signals like engine_speed are also wonky at times....so I'm not sure if my x100 correction is sometimes not needed (which would be unfortunate if it's unreliable) or if something more systemic is going on.
The text was updated successfully, but these errors were encountered:
I think this latest hardware shipment has updated modem firmware that corrects the gps speed bug. On my development unit 352682050003671 the x100 correction is definitely required. But on one of the brand new units, 352682050124857, the x100 correction is clearly unnecessary.
I'll confirm on Monday with some new hardware. We have access to the modem firmware version, so we could apply the correction factor selectively based on that.
There is a bug in the Telit HE910 firmware that reports the GPS speed signal as 1/100 of the actual value. We've known about this for a while so I added a x100 to the signal value before publishing it. Works OK sometimes, but I'm seeing some signal values show up like {"name":"gps_speed","value":10721}. The GPS speed signal values around these instances make me think that these instances are 100x too high.
I'm also noticing that other signals like engine_speed are also wonky at times....so I'm not sure if my x100 correction is sometimes not needed (which would be unfortunate if it's unreliable) or if something more systemic is going on.
The text was updated successfully, but these errors were encountered: