Platforms config Yaml file
- Note
- 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 plaforms (with names UAV_1 and UAV_2)
- Note
- StSupervisor works with multicast streaams 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
- Note
- 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 in the list.
# Platforms
platforms:
# First platform
- platform: Legion1
active: true
name: Legion 1
description: First platform
type: UAV
sensors:
- sensor: EO1
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
- sensor: Tail1
name: Tail
description: Tail camera
active: true
type: video
url: udp://227.1.1.2:30122
triggers: !!inc/file triggers.yml
- sensor: Operator1
name: Operator
active: false
type: video
url: udp://227.1.1.3:30123
- sensor: Radar1
name: Radar
active: false
type: video
url: udp://227.1.1.4:30124
# Second platform
- platform: Legion2
active: false
name: Legion 2
description: Second platform
type: UAV
sensors:
- sensor: EO2
active: false
name: EO/IR
type: video
url: udp://228.1.1.1:1234
Triggers can be configured both inline and as a separate yaml file.
# this trigger will send a start message when stream becomes online
- trigger: start
conditions:
state: 'online'
# this trigger will send a start message based on telemetry defined conditions
- trigger: start
armed: true
conditions:
telemetry:
sensorTrueAltitude:
above: 200
# Send arrived message based on telemetry defined conditions - platform location is inside of predefined polygon
- 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]]]
# Send stop message based on telemetry defined conditions - ground speed < 20
- trigger: stop
armed: true
conditions:
telemetry:
platformGroundSpeed:
below: 20