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 (U-Blox NEO) Hardware Support #6

Open
CodeChief opened this issue Aug 27, 2015 · 1 comment
Open

GPS (U-Blox NEO) Hardware Support #6

CodeChief opened this issue Aug 27, 2015 · 1 comment
Assignees
Milestone

Comments

@CodeChief
Copy link
Collaborator

Device, sample and test app.
Minimum support is current Navio+ NEO-MN8 model but attempt to support Navio (original) NEO7M and NEO-6T dongle if the UBLOX hardware is standardized (likely as their configuration tool supports multiple models).

@CodeChief CodeChief self-assigned this Aug 27, 2015
@CodeChief CodeChief added this to the Core SDK milestone Aug 27, 2015
@CodeChief
Copy link
Collaborator Author

Depending on GPS support in the IoT preview it might even be possible to make an ACPI table so the BIOS hooks-up the Navio uBlox GPS to the built-in driver (assuming it exists and supports uBlox). So the user mode C# code can either call the specialized GPS device or do all the serial work itself.

In the "shared mode" the framework would only get generic location data. This is probably not going to work in the current version, but the BIOS trick is worth a try.

In the "raw mode" (easiest to implent for PoC abd sure to work) the framework just wraps access to the GPS serial port, then the user applications (including our sample and test apps) will have to find some third party GPS protocol decoder in order to display any useful information.

Long term, a custom driver should be produced and support both modes. Then sensors can be used throughout Windows or directly accessed by autipilots or RTK wrappers (maybe something happens with REACH support here too). But that is really something which should be provided by the uBlox company so it may be a waste of time to jump-in here with drivers too soon.

Best get the PoC done with raw access then re-evaluate the driver situation. As GPS updates are relatively slow it is not necessary to have a driver in order to complete the drone PoC.

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

No branches or pull requests

1 participant