Last updated
Last updated
Multiple instances of Virtual Skynode can be run when the following conditions are met:
Each instance must use a separate storage directory. Use the --storage
launch argument to control this
Each instance must use a separate root filesystem image. Use the --rootfs
launch argument to control this
Each instance should be configured to have a unique MAVLink system_id after launch. Use AMC or MAVLink to set the APX4 parameter MAV_SYS_ID
to unique values
Each instance must use a separate unique IPv4 address in the same subnet. Use the --guest-ip
launch argument to control this.
Each instance's virtual FMU must be configured to use the "self-containd" simulation without Gazebo:
Example launch commands for three separate virtual skynode instances:
Launch the first instance:
Launch the second instance:
Launch the third instance:
Each instance of Virtual Skynode will consume CPU, RAM and disk space. Running multiple Virtual Skynode instances is therefore only viable on more powerful machines.
How to run multiple instances of Virtual Skynode on a single machine to emulate multiple vehicles