Heading and speed values for standing still devices

[McFlyssss]

New Issue Checklist

• [x] Updated to Bad Elf firmware to latest version.
• [x] Updated platform to latest compatible version.
• [x] Browsed open/resolved tickets to find similar issue.

Issue Description

We are adding support for bad elf devices to an iOS app. We successfully connect using EAAccessoryManager and parse the nmea messages.

During QA, the team has realised that the onscreen device information differs from the data we receive when the device is standing still. Under those circumstances, the device screen shows 0kts for speed and - for heading. When parsing the data, the RMA nmea messages provide <1 kt values and 'random' figures for heading. The messages are valid. We are wondering if there is any filtering/threshold we should apply on specific cases.

Complete output from your IDE, including the stack trace, if available.

NA

ENVIRONMENT

Please fill out the complete configuration of your setup below. This will help Bad Elf Engineers reproduce and resolve your issue faster.

Bad Elf Model:

GPS Pro +

Firmware Version:

3

Platform:

iOS >15

Protocol String:

com.bad-elf.gps

[brhackle]

Thanks for the questions! Yes, the GNSS engine will continue to provide track/speed updates even when stationary, but most apps/UIs will suppress these below a certain speed threshold. For Bad Elf products, this speed threshold is ~0.9 knots.

Hope that helps!

[McFlyssss]

Dear @brhackle ,

Thanks for such a quick answer. That helps enormously. We will take that threshold into consideration from now on.

Kind regards!

[McFlyssss]

Dear @brhackle ,

There is another question I'd love to ask you.

There is one more value that we do not know how to match with the ones appearing on screen: accuracy. We have been looking for documentation but we are struggling. The closest parameter we can think of is hdop but that does not seem to be the right one.

Any idea or resource we could use to show the right gps accuracy to the users?

Thanks in advance