Advertisement

Quick Links

Microdrones VSM User Guide
UgCS 2.11.227
Copyright © 2017, SPH Engineering

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the VSM UgCS 2.11.227 and is the answer not in the manual?

Questions and answers

Summary of Contents for Microdrones VSM UgCS 2.11.227

  • Page 1 Microdrones VSM User Guide UgCS 2.11.227 Copyright © 2017, SPH Engineering...
  • Page 2: Table Of Contents

    CONTENTS Contents Connecting Microdrones autopilot to UgCS First time vehicle connection ........
  • Page 3: Connecting Microdrones Autopilot To Ugcs

    1.1 First time vehicle connection See Disclaimer. Please follow these steps to connect an Microdrones vehicle to the UgCS: 1. Microdrones vehicle must be properly configured, calibrated and tested using tools and instruction from the official Microdrones web site prior to using it with UgCS. UgCS does not support initial configuration, setup and calibration of Microdrones vehicles.
  • Page 4: Mission Execution Specifics

    4. Repeat steps above for each your Microdrones vehicle. Note that if both uplink and downlink are connected only uplink will be active because the Microdrones stops telemetry sending after reception of commands via uplink. The downlink can be activated either by issuing "A- RM"...
  • Page 5: Telemetry Information Specifics

    Continue Aircaft continues mission 1.6 Configuration file Default configuration file of the Microdrones VSM suits most needs and it is generally not necessary to modify it. Configuration file location: • On Microsoft Windows: C:\Program Files (x86)\UgCS\bin\vsm-microdrones.conf • On GNU/Linux: /etc/opt/ugcs/vsm-microdrones.conf...
  • Page 6: Serial Port Configuration

    • Example: vehicle.microdrones.serial_port.1.name = com1 vehicle.microdrones.serial_port.1.baud = 38400 1.6.3 Model name override By default the VSM sets ’MD’ model name for the Microdrones vehicles. It can be overriden to more specific name in the VSM configuration. Example: vehicle.microdrones.custom.my_drone.serial_number = 1102 vehicle.microdrones.custom.my_drone.model_name = MD4-200...
  • Page 7: Logging Configuration

    1.7 Common configuration file parameters 1.7.2 Logging configuration 1.7.2.1 Level Optional. • Name: log.level = [error warning info debug] • Description: Logging level. • Default: info • Example: log.level = debug 1.7.2.2 File path Optional. • Name: log.file_path = [path to a file] •...
  • Page 8: Mission Dump Path

    CONTENTS 1.7.3 Mission dump path Optional. • Name: [prefix].mission_dump_path = [path to a file] • Description: File to dump all generated missions to. Timestamp is appended to the name. Delete the entry to disable mission dumping. All directories in the path to a file should be already created. •...
  • Page 9: Tcp Connection Configuration

    1.8 Communication with vehicle 1.8.1.2 Port baud rate Optional. • Name: [prefix].[port index].baud.[baud index] = [baud] • Description: Baud rate for port opening. [baud index] is an optional arbitrary name used when it is necessary to open the same serial port using multiple baud rates. [port index] is an arbitrary port indexing name. •...
  • Page 10: Udp Connection Configuration

    CONTENTS 1.8.2.2 remote TCP port Optional. • Name: [prefix].detector.[con index].tcp_port = [port number] • Description: Remote port to connect to. • Example: vehicle.ardupilot.detector.1.tcp_port = 5762 1.8.3 UDP connection configuration Optional. VSM which communicates with vehicles via network should define at least one network connection, otherwise VSM will not try to connect to vehicles.
  • Page 11: Disclaimer

    2 Disclaimer 1.8.4.1 IP-address for proxy Optional. • Name: [prefix].tcp.[con index].proxy = [IP-address] • Description: IP-address to connect proxy to. Specify local or remote address. • Example: vehicle.ardupilot.tcp.1.proxy = 127.0.0.1 1.8.4.2 TCP port for proxy Optional. • Name: [prefix].tcp.[con index].port = [port number] •...

Table of Contents