Satellite Demo

Requirements

The event flow for this demo is as follows

client ⇆ Maps Server ⇆ [ Satellite Modem (serial) | Web Server (REST) ] ⇆ Maps Server ⇆ client

Maps Messaging Components

• Maps Server configured to communicate with the satellite modem
• Maps Server configured to communicate with the REST API

Communications Hardware (choose one)

• Satellite Modem
• Satellite Simulator
• Run the Satellite Comms Server included with the package

Configuration

Modem Side

Install the Maps Server and configure it to communicate with the modem.

In NetworkConnectionManager.yaml, add this to the data section:

      - name: "ST2100 Modem"
        url: serial://localhost:0/
        protocol: stogi
        initialSetup: ""                         # optional init string sent at startup
        incomingMessagePollInterval: 1           # seconds, minimum = 1
        outgoingMessagePollInterval: 20          # seconds, minimum = 15 recommended
        sharedSecret: "This is a shared secret to use"
        sendHighPriorityMessages: false
        modemResponseTimeout: 20000              # ms
        locationPollInterval: 60                 # seconds, GNSS/visibility state updates
        maxBufferSize: 4000
        compressionCutoffSize: 128
        modemStatsTopic: "/modem/stats"
        modemRawMessages: "/incoming/{sin}/{min}"  # Any raw events will be published to incoming and split on sin/min
        bridgeMode: false                        # if true, send raw byte[] with no modifications

        remote:
          sessionId: <optional>                  # not required for this link
          username: <optional>
          password: <optional>

        links:
          - direction: push
            local_namespace: "/report/weather"
            remote_namespace: "/remote/report/weather"
            include_schema: true

        serial:
          port: "com6"
          baudRate: 9600
          dataBits: 8
          stopBits: 1
          parity: n
          flowControl: 0

Please note the port should match the communications port you intend to use. Maps will attempt to autodetect the modem version.

To configure the weather statistics events to be processed and sent, add:

      - name: "Weather stats upload"
        url: loop://localhost:0/
        protocol: loop
        remote:
          sessionId: "internal sessionid"                  # not required for this link
          username: ""
          password: ""
        links:
          -
            direction: push
            local_namespace: "/weather"
            remote_namespace: "/report/weather"
            analystics:
              eventCount: 60
              ignoreList: "timestamp"
              defaultAnalyser: "Advanced"

This instructs the server to subscribe to the /weather topic, process the events using the Advanced analyser, and forward an event after every 60 events.

A complete NetworkConnectionManager.yaml can be found in main/resources/modem_side.

We also need to adjust the MQTT port in NetworkManager.yaml:

      - name: "MQTT Interface"
        url: tcp://:::1884/
        protocol: mqtt
        auth: default
        selectorThreadCount: "{processors}/2"

Changing from port 1883 to 1884 matches the Weather Station simulation setup.

A complete NetworkManager.yaml can be found in main/resources/modem_side.

Once configured, start the server.

---

Weather Station Simulator

This package includes a simple Weather Station simulator that:

• Sets the topic schemas
• Publishes updates once per second to /weather

If the server stops, the simulator will exit.

Starting the Weather Station Simulator

Ensure Maven is installed, then run:

mvn exec:java -Dexec.mainClass=io.mapsmessaging.weather.WeatherGeneratorDemo

It will connect to tcp://localhost:1884/.
If you need a different host or port, modify the code and run again.

---

Server Side

Modem Simulator

If running the modem simulator, the server must be configured to use the ogws API.

Add this to NetworkManager.yaml:

      - name: "ogws interface"
        protocol: satellite
        auth: anon
        bridgeMode: false
        url: satellite://localhost:8500/
        httpRequestTimeoutSec: 30
        pollInterval: 15
        sharedSecret: "This is a shared secret to use"
        maxInflightEventsPerDevice: 2
        namespaceRoot: "/{deviceId}"
        inboundNamespaceRoot: "/incoming/{deviceId}/{sin}/{min}"
        outboundNamespaceRoot: "/outgoing/{deviceId}/#"
        outboundBroadcast: "/inmarsat/broadcast"
        baseUrl: "http://localhost:8085/api/v1.0"
        remoteAuthConfig:
          username: "ogws client id"
          password: "ogws client secret"

Satellite Comms Emulation

If running the agent from this repo, use the Inmarsat IoT interface:

      - name: "inmarsat IoT interface"
        auth: anon
        protocol: satellite
        url: satellite://localhost:8500/

        # Rest Server Config
        baseUrl: "http://localhost:8085/iotMessaging/v1"
        mailboxId: "mailbox-001"
        mailboxPassword: "mailbox-secret"

        remoteAuthConfig:
          username: "ogws client id"
          password: "ogws client secret"

        # Timeouts
        incomingMessagePollInterval: 10
        outgoingMessagePollInterval: 30
        httpRequestTimeoutSec: 30

        # Maps message package config
        bridgeMode: false
        sharedSecret: "This is a shared secret to use"
        maxInflightEventsPerDevice: 2

        # Namespace mapping
        namespaceRoot: "/{deviceId}"
        inboundNamespaceRoot: "/incoming/{deviceId}/{sin}/{min}"
        outboundNamespaceRoot: "/outgoing/{deviceId}/#"
        outboundBroadcast: "/inmarsat/broadcast"

Starting the Emulator

To start the built‑in modem and web server emulation, run:

mvn -pl maps_viasat_harness   exec:java@run-satellite-comms   -Dexec.args="/dev/ttyUSB0 8085"   -DMODEM_LOG_MESSAGES=true

Adjust the COM port and TCP port accordingly.

---

Other

If running against a live server, refer to the documentation appropriate to your modem type and authentication method.