Platform Configuration

Very important! YAML requires a specific indentation and spacing to work. YAML uses spaces. Do not use tabs! The suggested syntax for YAML files is to use 2 spaces for indentation.

Basic platform configuration

Here is an example of the configuration file that defines two UAV platforms (with names Legion 1 and Legion 2)

StSupervisor works with multicast streams only. As it is a monitoring service, it makes no sense to directly consume unicast streams. If, for any reason you only have a unicast in your system and want to monitor the stream, consider using ImpleoTV's unicast to multicast recaster.

First UAV has 4 video sensors: - EO/IR sensor with the stream coming on udp://227.1.1.1:30120 - Tail camera sensor with the stream coming on udp://227.1.1.2:30122 - Operator screen capture sensor with the stream coming on udp://227.1.1.3:30123 - Radar capture sensor with the stream coming on udp://227.1.1.4:30124

Radar sensor has active setting set to false (active: false), so this sensor is not monitored (set it to true, to enable monitoring).

Second UAV has only one sensor: - EO/IR sensor with the stream coming on udp://228.1.1.1:1234

If you only have one UAV (platform) to monitor, there should be one platform on the list.

# Platforms 
platforms:
# First platform 
  - name: Legion 1     
    active: true
    description: First platform
    type: Plane
    sensors:
      - name: EO/IR
        description: EO/IR sensor
        active: true       
        type: video
        url: udp://227.1.1.1:30120
        # trigger events (OR), based on conditions (AND)
        triggers: !!inc/file triggers.yml

      - name: Tail
        description: Tail camera
        active: true
        type: video
        url: udp://227.1.1.2:30122
        triggers: !!inc/file triggers.yml 

      - name: Operator1 
        description: Operator   
        active: false         
        type: video
        url: udp://227.1.1.3:30123   

      - name: Radar1
        description: Radar
        active: false     
        type: video
        url: udp://227.1.1.4:30124  

# Second platform
  - name: Legion 2
    active: false
    description: Second platform
    type: Plane
    sensors:
      - name: EO2
        active: false
        description: EO/IR
        type: video
        url: udp://228.1.1.1:1234      

Triggers can be configured both inline and as a separate yaml file.

- trigger: start
  armed: true
  conditions:
    state: online
- trigger: start
  armed: true
  conditions:
    state: online
    telemetry:
      platformGroundSpeed:
        above: 100
      sensorTrueAltitude:
        above: 200
- trigger: arrived
  armed: true
  conditions:
    telemetry:
      location:
        coordinates: [[[34.7373, 32.0686], [34.8616, 32.0686], [34.8616, 32.1238], [34.7373, 32.12387], [34.7373, 32.0686]]]
- trigger: stop
  armed: true
  conditions:
    telemetry:
      platformGroundSpeed:
        below: 20