Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gps_speed sometimes reports too high (looks like x100) #1

Open
mgiannikouris opened this issue Nov 8, 2014 · 1 comment
Open

gps_speed sometimes reports too high (looks like x100) #1

mgiannikouris opened this issue Nov 8, 2014 · 1 comment

Comments

@mgiannikouris
Copy link
Owner

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.

@mgiannikouris
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant