Page 8
• SkyHub can supply NMEA coordinate stream to the external sensor. Some sensors have internal data recorders but require an external GPS receiver. SkyHub can act as such an additional GPS receiver by providing the UAV coordinates to sensors.
Page 13
SkyHub. Power-on checks The cable connecting SkyHub and DJI M350 RTK drones has built-in LED indicators. You may check the connection condition by their examination: Figure 3.1 — Numbered LEDs on cable • LED1 lights up when the power is coming from the drone.
Page 14
Important: It is strongly recommended to switch on a remote controller before any operations with the SkyHub Wi-Fi. After powering on the SkyHub operates as Wi-Fi access point with following credentials: • SSID: UgCS-SkyHub-****** (where ****** is the SkyHub serial number) •...
Page 16
M300 / M350 SkyHub User Manual Access to Onboard File System One may use any SCP client to access the SkyHub file system. For example, one may use WinSCP. Figure 4.3 — WinSCP settings While pressing the Login button one may choose between login via SCP (to have access to the file system).
Page 18
UgCS Companion application establishes connection with SkyHub automatically if DJI driver is enabled. SkyHub indicator on upper left corner of the application turns green if connection is established. If there is more than one computer with UgCS used in the network, tap on UgCS indicator in upper left corner of UgCS Companion application to access the list of UgCS instances available and select necessary one.
Page 19
Setup Interface to ArduPilot SkyHub User Manual Setup Interface to ArduPilot SkyHub can be connected to the flight controller flashed with the ArduPilot 4.x.x firmware. 1. Make sure UgCS version 4.3 or higher is used (download links can be found in Prerequisites section) and VSM for ArduPilot vehicles is installed.
Page 20
6. Open application Mission Planner, connect it to the vehicle autopilot and check serial port settings used for SkyHub communication. Check port configured baud rate. Speed should be the same as configured at SkyHub side in the [MAV] section of the SkyHub config (recommended 230400). If adjustment is needed don’t forget write them and restart autopilot.
Page 21
SkyHub and autopilot. Figure 4.9 — Mission Planner MAVlink inspector data Vehicle 2 and Comp 5 correspond to configured at SkyHub System (2) and Component (5) 9. In case of correct Autopilot, UgCS and SkyHub configuration, Payload data b64 is displayed at drone telemetry in UgCS.
Page 23
Setup Interface to PX4 SkyHub User Manual Setup Interface to PX4 SkyHub can be connected to the flight controller flashed with the PX4 1.10.x or higher firmware. 1. Make sure UgCS version 4.3 or higher is used (download links can be found in Prerequisites section) and VSM for PX4 vehicles is installed.
Page 24
COMPONENT_ID value in the [MAV] section of the SkyHub config. Make sure that V2_EXTENSION parameter is set to TRUE in the [MAV] section of the SkyHub config. ArduPilot/PX4 Configuration to find all available settings with default values and descriptions.
Page 27
The second important step is to configure used autopilot and payloads. Pay attention that related section will be available for configuration only after it enabling and SkyHub restart. For example, DJI autopilot related parameters are collected within the [DJI] section:...
Page 43
1. Before use FTT FT742 sensor should be configured to use NMEA messages and compass disabled. If compass enabled, SkyHub will log reported values anyway, but to get accurate readings it is recommended to rely on Heading of the drone and wind direction relative to the sensor body, and calculate wind direction accordingly.
Page 45
Figure 5.1 — Emlid Reach M2 Port Pinouts 3. If USB connection is used, USB cable +5 wire should be isolated from SkyHub. Make sure that there is a stable power source for Emlid Reach M2, only the red LED lights up when the receiver lacks power.
Page 46
Important: GPS Receiver loads settings from separate config file. The file location: /etc/skyhub/gnss.conf. File format: INI (https://en.wikipedia.org/wiki/INI_file) 8. Check parameters in gnss.config file. Set SERIAL_DEVICE to /dev/ttyUSBX (X is the USB port number) when the USB connection is used with SkyHub of both generations: [GNSS] BAUD_RATE=115200 ;...
Page 47
Magnetometer module relies on the ROS subsystem. So, the first steps are ROS Bridge setup ROS Bridge Configuration. Then set QSPINQTFM to true in [ROS_PAYLOADS] section: [ROS_PAYLOADS] QSPINQTFM=true Restart the Skyhub and add such section for every QuSpin device instance: [ROS_MAGNETOMETER_QSPINQTFM_0] ACCEL_DATA_LOGGING=OFF ALTITUDE_SOURCE=v1:altimeter:default:0 BAUD_RATE=230400 FILTER=OFF MAGNETIC_ENVIRONMENT=AVERAGE OFFSET_FORWARD_M=0.0...
Page 49
Set ENABLE_PPS item to true in [ROS_MONITOR_GNSSOUT_0] section: [ROS_MONITOR_GNSSOUT_0] ENABLE_PPS=true By default, SkyHub supports the connector 2 as the PPS signal source and the connector 5 as output for the PPS signal consumer. Note: Please, contact our support team if PPS Sync configuration changes are required.
Page 50
ROS Bridge Setup ROS Bridge plugin is a key component for interaction with ROS framework. All ROS-based payload drivers use this module to interact with core SkyHub services (ground software connections, log files, flight controller data acquisition). This process always starts automatically at the Skyhub startup.
Page 52
4. Ensure that the drone with a correct profile appears in the UgCS on the PC and all drone indicators (battery, uplink, downlink, satellites) are green. Select the drone and the mission. 5. Ensure the only used payloads are true in the [PAYLOADS] section in the SkyHub configuration file. Each payload should be properly configured (see Payloads Setup).
Page 53
Log Files Management below for details). 7. Start the UgCS-CPM and UgCS application on PC. Check the UgCS, Drone, and SkyHub indicators are green. Add the Terrain Following widget and other widgets related to connected payloads by clicking the plus button.
Page 54
Attention: It is strongly recommended not to set Target Altitude more than 10 meters for the laser altimeter above water Attention: AGL and AMSL waypoints are navigated using GPS. SkyHub altitude safety check will trigger failsafe if drone flying to AGL or AMSL waypoint will go below MIN_ALTITUDE_M + 10.
Page 55
14. 16. After the mission has been completed the drone stops at the last waypoint then climbs to increase its altitude to value configured in skyhub.conf file section [TF] value FAIL_SAFE_ALTITUDE_M. 17. Switch the flight mode to N-Mode to take control, then return the drone to the desired landing position, and land the drone manually.
Page 59
Conditions of auto switching to ARMED state are defined with parameters ACTIVATION_ALTITUDE_M and ACTIVATION_SPEED_MPS in the [OA] section in skyhub.conf file. If the drone (UAV) ascends above ACTIVATION_ALTITUDE_M and the speed above ACTIVATION_SPEED_MPS, Obstacle Avoidance becomes ARMED, otherwise it stays DISARMED. The UgCS-CPM displays the Obstacle Avoidance ARMED or Obstacle Avoidance DISARMED message in UgCS-CPM log.
Page 61
There are two ways to download log files: • Using UgCS-CPM (see Log Files Management) • With any web browser via HTTP protocol (supported for SkyHub 2 only) When the second way is chosen, open http://10.1.0.1 (Wi-Fi) or http://192.168.0.33 (Ethernet) in your browser and choose the required log file from a list of all recorded ones.
Page 67
(see Connect to SkyHub Using Ethernet). 2. Go to Settings > SkyHub and make sure the IP-address corresponds to the connection way. 3. Open UgCS-CPM and go to Tools > Manage Logs. 4. Press the Browse button to choose the destination folder for log files.
Page 70
3. Upload manually the firmware to MicroSD root (path: /run/media/mmcblk1p1) by FTP/SCP client. 4. Connect to SkyHub via ssh and move to the MicroSD root. 5. Unpack the firmware package and manually run the script to uninstall the SkyHub firmware from the device: $ tar -xvf skyhub-*.tar.gz $ skyhub-*/uninstall.sh...
Page 71
7 • Configuration Parameters • Configuration file location: /etc/skyhub/skyhub.conf • File format: INI (https://en.wikipedia.org/wiki/INI_file) Important: The SkyHub device should be restarted after any change in the configuration file by reboot command or by power cycling. SkyHub Configuration Table 7.1 — SkyHub settings...
Page 73
Select specified altimeter to fill ALT: v1:altimeter: columns. ALTIMETER_SOURCE default:0 First configured altimeter will be choosen with default mask /data/ Where to write managed logs in Skyhub DATALOG_DIR skyhub_logs filesystem Start new log file at every reached LOG_PER_LINE false waypoint.
Page 74
Description Begin to write logs without taking off or START_ENABLED false CPM activation. Set to true start log writing at startup. Table 7.2 — SkyHub advanced settings Parameter Default Value Description [APP] Log the system info such as CPU SYSINFO_LOG...
Page 75
DJI response timeout, s SENDING_PERIOD_MS Period of data sending to ground, ms UART serial device. Default value SERIAL_DEVICE /dev/ttyAMA2 depends on the SkyHub generation Alternative connection with USB USB_DEVICE enabled cable Set to true for M350. Set to false for FORCE_TRUNCATE false other DJI drones.
Page 76
Autopilot Configuration SkyHub User Manual Parameter Default Value Description UART serial device. Default value SERIAL_DEVICE /dev/ttyAMA2 depends on the SkyHub generation SYSTEM_ID MAVLink system Id of SkyHub TELEMETRY_RATE Telemetry frequency, Hz Using MAVLink V2_EXTENSION V2_EXTENSION true messages. Set to false to disable it.
Page 85
Altimeter Configuration SkyHub User Manual Lightware SF30/D Altimeter Configuration This driver supports multiple instances of SD30D altimeters connected to the same SkyHub device. You should provide additional section for every configured instance (zero-base): [ROS_ALTIMETER_LIGHTWARESF30D_0] IS_FILTERED=false RATE_HZ=39 RETURN_MODE=LAST UART_BAUD_RATE=115200 UART_SERIAL_DEVICE=/dev/ttyAMA1 Table 7.12 — Lightware SF30/D altimeter settings...
Page 86
UART serial device Configure Altimeter Monitor Altimenter Monitor will be started automatically at the Skyhub startup. There is no option to enable or disable it. This node works as a single instance. You should provide the only section of monitor...
Page 91
(used for debugging only) SkyHub 2: /dev/ttymxc1 Serial device name. Default value SERIAL_DEVICE SkyHub 3: depends on the SkyHub generation /dev/ttyAMA3 Transmitted pulse length, micro second. TXLENGTH_US The value is automatically increased if it is less than the required value.
Page 96
Pergam Laser Falcon board and can be sent upon request. The stored information is updated every 500 ms. The FREQUENCY_HZ parameter only sets the frequency of requests from SkyHub to the Pergam Laser Falcon, while the Pergam Laser Falcon continues to work according to its scheme.
Page 104
Table 7.29 — GPS Output settings Parameter Default Value Description [ROS_MONITOR_GNSSOUT_0] UART serial device. Default value SERIAL_DEVICE /dev/ttyAMA4: depends on the SkyHub generation BAUD_RATE 115200 UART baud rate, bps List of message to be generated. This module implements only RMC,GGA and MESSAGES RMC GGA ZDA ZDA message types.
Page 105
Guidelines for navigation values choosing Skyhub provides a number of parameters that allow you to adjust the flight algorithms. This section provides a description of the expected impact of the provided parameters, but the specific values a re entirely dependent on the user’s task and the actual conditions: wind speed, altitude, acceptable accuracy and required speed.
Need help?
Do you have a question about the SkyHub and is the answer not in the manual?
Questions and answers