Sign inSign up

svelde/iot-edge-nmea

By svelde

•Updated over 6 years ago

This Azure IoT Edge module parses NMEA messages from multiple ports and outputs them as events.

Image
0

363

svelde/iot-edge-nmea repository overview

⁠iot-edge-nmea

This Azure IoT Edge module parses NMEA messages from multiple ports and outputs them as events. This module is an IoT Edge implementation of this nmea library⁠.

⁠Introduction

This module parses incoming NMEA messages like GSV, GGA, GSA, GLL, GMC, VTG and TXT. Incoming NMEA messages which are splitted up in multiple messages like GSA and GSV are combined.

Messages from multiple ports are not combined but splitted in multiple outputs.

⁠Docker Hub

This module is available in Docker Hub⁠.

Use it in your IoT device with tag:

svelde/iot-edge-nmea:1.0.0-amd64

⁠Input

Messages are received on input 'input1'.

This is the Input format:

{
    [JsonProperty("data")]
    public string Data { get; set; }

    [JsonProperty("port")]
    public string Port { get; set; }

    [JsonProperty("timestampUtc")]
    public DateTime TimestampUtc { get; set; }
}

⁠Outputs

⁠Regular output

Parsed messages are send over an output with the same name as the port which submitted the NMEA messages.

So the parsed version of a NMEA message coming from 'ttyS0' will be available on output 'ttyS0'.

The Output format is depending on the specific parsed message. See the supported NMEA parser classes⁠ for the specific messages.

An example is:

public abstract class GsaMessage : NmeaMessage
{
    [JsonProperty(PropertyName = "autoSelection")]
    public string AutoSelection{ get; private set; }

    [JsonProperty(PropertyName = "fix3D")]
    public string Fix3D { get; private set; }

    [JsonProperty(PropertyName = "percentDop")]
    public decimal PercentDop { get; private set; }

    [JsonProperty(PropertyName = "horizontalDop")]
    public decimal HorizontalDop { get; private set; }

    [JsonProperty(PropertyName = "verticalDop")]
    public decimal VerticalDop { get; private set; }

    [JsonProperty(PropertyName = "prnsOfSatellitesUsedForFix")]
    public List<int> PrnsOfSatellitesUsedForFix { get; private set; }
}

The NmeaMessage looks like this:

public abstract class NmeaMessage
{
    [JsonProperty(PropertyName = "type")]
    public string Type {get; set;}

    [JsonProperty(PropertyName = "port")]
    public string Port { get; set; }

    [JsonProperty(PropertyName = "timestampUtc")]
    public DateTime TimestampUtc { get; set; }

    [JsonProperty(PropertyName = "mandatoryChecksum")]
    public string MandatoryChecksum { get; set; }
}
⁠Exceptional output

In case a message can not be parsed or another excpetion occurs, a message will be put on output 'Exception'.

This is the Exception format:

public class ExceptionMessage
{
    [JsonProperty("message")]
    public string Message { get; set; }
}

⁠Routes

Here is an example of how to use routes:

{
  "routes": {
    "serialToNmea": "FROM /messages/modules/serial/outputs/ttyACM0 INTO BrokeredEndpoint(\"/modules/nmea/inputs/input1\")",
    "nmeaToEcho": "FROM /messages/modules/nmea/outputs/Exception INTO BrokeredEndpoint(\"/modules/echo/inputs/input1\")",
    "route": "FROM /messages/modules/nmea/outputs/ttyACM0 INTO $upstream"
  }
}

⁠Desired properties

The parser can be limited in the types of messages to be parsed.

Provide this 'filter' desired property to limit all parsers:

"desired": {
  "filter": "GPGSV,GLGSV,GNGSV,GPGSA,GNGSA,GNGLL,GNRMC,GNVTG,"
}

⁠Contribute

The code of this logic is open source⁠ and licenced under the MIT license.

Want to contribute? Throw me a pull request....

Want to know more about me? Check out my blog⁠

Tag summary

Content type

Image

Digest

Size

126.7 MB

Last updated

over 6 years ago

docker pull svelde/iot-edge-nmea:1.0.1-windows-amd64