Skip to content

Allow configuration of vendor #144

@jclark

Description

@jclark

At the moment we have an nmeaNumbering configuration option is the GPS section of satpulsed, which takes the name of a vendor/manufacturer.

This issue proposes to rename this to vendor and also add a --vendor option to satpulsetool. The value of this option would be passed to the gpsreg module.

Initially, the behaviour would be exactly as now: it would call SetNMEANumbering on the NMEA packet processor.

But in the future we can extend it to allow gpsreg to use the vendor in constructing collections of PacketFormats, PacketProcessors and ConfigProtocols. For example, if the user specifies a vendor of u-blox, there is no point in enabling the various unicore specific implementations of these interfaces, because there is no possibility of a u-blox processor emitting any of these packets.

An unspecified vendor would be OK, and would result in an empty string being passed, which would enable all available implementations of these interfaces.

It could also enable vendor-specific tweaks to the constructed implementations, similar to current NMEA numbering.

Metadata

Metadata

Assignees

No one assigned

    Labels

    in progressCurrently being worked onunicoreRelevant to support for Unicore receivers

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions