LogoLogo
  • Welcome
  • Vehicle Operation
    • Getting started
    • Auterion Suite
      • Dashboard
      • Fleet Management
        • Vehicles
          • Cloud Features
          • Groups
        • Flights
        • Compliance
      • Manufacturer
        • Service Bulletins
      • Administration
      • User Management
      • Simulations
    • Auterion Mission Control
      • Installation
      • First steps
      • UI Breakdown
        • Navigating between the views
        • Fly View
          • Fly View UI Overview
          • Vehicle status indicator
          • Flight mode selector
          • Quick actions sidebar
          • Connection manager
          • Vehicle Dashboard
          • Flight Map
          • Camera View
          • Monitoring the Flight
          • Flying Manually (RC/Joystick)
          • Flying a Mission
        • Plan View
          • Plan UI Overview
          • Plan tools
            • Mission Menu
            • Waypoint Missions
            • Survey Patterns
              • Area Survey
              • Corridor Scan
          • Mission Summary
          • Mission Editor Tab
            • Start Section
            • Mission Section
            • End Section
            • Extras
          • Terrain visualization
          • GeoFence
          • Rally Points
        • Quick Vehicle Menu
          • Pre-Flight Checklist
          • Connectivity
        • Photo Gallery
        • Settings
        • Pilot Login
      • Useful resources
        • Mission Planning
          • Mission Cloud Sync
          • Terrain Following
          • Import Geo-Awareness data or KML overlays
        • Maps and Custom Overlays
          • Using Offline Maps
          • Importing GeoPDF overlays
        • Track GCS as Smart Asset in Suite
        • Live PX4 Log Streaming
        • Monitor Local Flights with ADS-B
        • GPS Denied Workflow
        • Windows Crash Logs Analysis
        • Screen Recordings
    • Remote Controllers
      • Skynav Remote Controller
        • Installing Mission Control
        • Joystick and Button Mapping
        • Using LTE for Online Maps in the Field
        • Advanced Radio Settings
        • Drop Guards and Chest Strap
        • Unit Serial Number
    • Settings & Maintenance
      • Vehicle Setup
      • WiFi Setup
      • Compass Calibration
      • Safety Setup
      • Joystick Setup
      • Vehicle Web UI
      • Software Update
      • Remote ID
        • How Remote ID works
        • Remote ID indicators in AMC
        • Frequently Asked Questions
    • Precise Flight
  • App development
    • Getting Started
      • Development environment Setup
      • Connecting to a device
      • Application Development
    • App Framework
      • Building your First App
      • Apps API
      • Sensor Data
      • Video Streams
      • Photos
      • Hardware Peripherals
      • Persistent Storage
      • MAVLink
      • Native Docker Compose
      • App Parameters
      • Log App Data to Auterion Suite
        • How to log Time Series Data
        • How to log basic Text Output
      • How to store an App's Binary Data on Skynode
      • User Web Interfaces
      • Build Arguments
      • Debugging apps with SSH
      • Debugging Apps with gdb
      • PX4 Messages in ROS 2
      • DDS / ROS2 Configuration
      • Structuring Applications with Multiple Services
    • Auterion SDK
      • Installation
      • Write Your First App
      • SDK API
      • Flight Mode API
        • Flight Mode API
        • Dynamics in Body Frame
        • Dynamics in Local Frame
        • Go-To in Local Frame
      • System State API
      • Peripheral Actuator Control API
      • Camera API
      • Navigation Input API
        • Global Navigation
        • Local Navigation
      • Visual Tracking API
    • Simulation
      • Virtual Skynode
        • Simulation-Gazebo Reference
        • Simulation-AirSim Reference
        • Connecting from other Computers
        • Resetting Virtual Skynode
        • Multiple Virtual Skynodes on single machine
      • Physical Skynode
    • Resources
      • Cross Compilation - Faster Builds
      • Auterion CLI Reference
      • Troubleshooting
      • App Tutorial
      • Skynode Vision Kit S
        • Set up the Vision Kit
        • Install and test a simple vision app
    • Legacy app workflow
      • App Development
      • MAVLink
      • Using the App Template
      • Example Applications
        • Autopilot Telemetry (C++)
        • Autopilot Telemetry (Python)
        • Photo Gallery
  • Hardware Integration
    • Getting started
      • Required Sensors
      • Wiring Skynode to the Vehicle
      • Actuators Setup
      • Sensors Setup
        • Set Orientations
        • Compass Calibration
        • Gyroscope calibration
        • Accelerometer calibration
        • Level horizon calibration
        • Airspeed calibration
      • Bench Test
      • Tuning
      • Creating Airframe Configurations for APX4
    • Skynode
      • Skynode X
      • Skynode ENT/GOV
      • Skynode X Integration and Development Kit
        • Get Skynode ready
        • Power Skynode
        • Register Skynode
        • Connect Skynode to AMC
        • Sensors and Peripherals
        • Next steps
      • Payloads
        • Generic USB Webcams (UVC)
        • Workswell Wiris Pro
        • Trillium HD40-LV
        • NextVision Gimbals (with TRIP2)
        • Sony Alpha a7R IV
        • Phase One iXM-100
        • Gremsy Gimbals
      • Connectivity
        • USB-C Network Connection
        • WiFi
        • LTE Setup
        • SIYI MK15
        • Microhard Data Link
        • Data Link Wiring
        • Silvus Data Link
        • Doodle Labs Data Link
        • Custom Data Link
        • Ethernet Interface Configuration
      • Skynode LED Meanings
      • Troubleshooting
      • Legacy DSM/DSMX Support
      • Peripherals
        • Power Module
        • 12S Power Module
        • Pixhawk Adapter Board
        • Pixhawk Payload Bus
        • Data Link Module
        • PX4 F9P GPS
        • Freefly RTK GPS
        • Airspeed Sensor
        • LIDAR
        • USB camera
        • See3CAM_24CUG
    • Skynode S
      • Datasheet
      • Interfaces
      • Basic Vehicle Integration
      • Add LTE to Skynode S
      • Skynode S LED status indicator
      • Skynode S flight logs
    • AI Node
      • Datasheet
      • Evaluation Kit
        • Power AI Node
        • Wiring AI Node to Skynode
        • Internet sharing with Skynode
        • Activate AI Node on Suite
      • Dimensions and CAD model
      • Interfaces
      • Connectivity
        • USB Network Connection
        • Serial Debug Connection
        • AI Node as Network Bridge
        • Standalone Internet Access
      • Updating AuterionOS
    • Advanced Airframe Integration
      • Custom power setup
      • Wiring without Breakout Boards
      • Gripper Integration
        • Setting up Payload Delivery with Gripper
      • ESC Calibration
      • Camera Calibration
        • Camera Calibration on a Computer
        • Camera Calibration on Skynode
      • Serial Port Configuration
    • Flight controller customization
      • AMC's Advanced Mode
      • Flight Controller Shell
      • Micro XRCE-DDS
    • Software customization
    • AuterionOS Customization
      • OEM Tools Installation
      • Adding SSH keys
      • Changing the Root Password
      • Modifying Environment Variables
      • Pre-install Applications
      • Suite Manufacturer Tools
    • AuterionOS System Guide
      • Introduction
      • Flashing PX4 Binary and Vehicle Config
      • Building and Flashing PX4 Firmware
      • SSH Access
      • Filesystem and partitions
      • Environment Variables Reference
      • Types of AuterionOS Images
      • Mavlink Routing and Endpoints
      • Packaging AuterionOS Image
    • Additional Resources
      • Remote ID
        • How Remote ID works
        • Vehicle Serial Number
        • Communication Diagram
        • Remote ID configuration
        • How Auterion tested
      • Auto-Tuning
  • Release Notes
    • APX4
      • APX4 3.2
        • APX4 3.2.1
      • APX4 3.1
        • APX4 3.1.1
        • APX4 3.1.0
      • APX4 3.0
        • APX4 3.0.8
        • APX4 3.0.5
      • APX4 2.7
        • APX4 2.7.37
        • APX4 2.7.25
        • APX4 2.7.20
        • APX4 2.7.12
        • APX4 2.7.7
        • APX4 2.7.6
      • APX4 2.6
        • APX4 2.6.1
      • APX4 2.5
        • APX4 2.5.14
        • APX4 2.5.13
        • APX4 2.5.8
        • APX4 2.5.7
        • APX4 2.5.5
        • APX4 2.5.4
        • APX4 2.5.0
      • APX4 2.4
        • APX4 2.4.2
        • APX4 2.4.1
      • APX4 2.3
        • APX4 2.3.0
      • APX4 2.2
        • APX4 2.2.2
        • APX4 2.2.0
      • APX4 2.1
        • APX4 2.1.1
        • APX4 2.1.0
      • APX4 2.0
        • APX4 2.0.2
        • APX4 2.0.0
    • AuterionOS
      • AOS for AI Node
        • AI Node AOS 1.1.0
        • AI Node AOS 1.0.2
        • AI Node AOS 1.0.0
        • AI Node AOS 0.7.0
        • AI Node AOS 0.6.1
        • AI Node AOS 0.6.0
        • AI Node AOS 0.5.0
        • AI Node AOS 0.4.0
      • AOS for Skynode
        • AOS 3.7
          • AOS 3.7.14
          • AOS 3.7.9
        • AOS 3.6
          • AOS 3.6.14
        • AOS 3.5
          • AOS 3.5.13
        • AOS 3.3
          • AOS 3.3.9
        • AOS 3.2
          • AOS 3.2.9
        • AOS 2.19
          • AOS 2.19.14
        • AOS 2.15
          • AOS 2.15.10
          • AOS 2.15.7
        • AOS 2.12
          • AOS 2.12.8
        • AOS 2.10
          • AOS 2.10.2
        • AOS 2.8
          • AOS 2.8.1
        • AOS 2.7
          • AOS 2.7.15
        • AOS 2.6
          • AOS 2.6.1
        • AOS 2.5
          • AOS 2.5.14
          • AOS 2.5.13
          • AOS 2.5.8
          • AOS 2.5.7
          • AOS 2.5.5
          • AOS 2.5.4
          • AOS 2.5.0
        • AOS 2.4
          • AOS 2.4.1
        • AOS 2.3
          • AOS 2.3.0
        • AOS 2.2
          • AOS 2.2.2
          • AOS 2.2.0
        • AOS 2.1
          • AOS 2.1.1
          • AOS 2.1.0
        • AOS 2.0
          • AOS 2.0.2
          • AOS 2.0.0
    • Auterion Mission Control
      • AMC 1.34
        • AMC 1.34.19
        • AMC 1.34.14
      • AMC 1.33
        • AMC 1.33.13
      • AMC 1.32
        • AMC 1.32.7
      • AMC 1.30
        • AMC 1.30.17
      • AMC 1.29
        • AMC 1.29.7
      • AMC 1.26
        • AMC 1.26.8
      • AMC 1.22
        • AMC 1.22.3
      • AMC 1.19
        • AMC 1.19.5
      • AMC 1.18
        • AMC 1.18.3-1
        • AMC 1.18.3
      • AMC 1.17
        • AMC 1.17.10
        • AMC 1.17.9
      • AMC 1.15
        • AMC 1.15.0
      • AMC 1.14
        • AMC 1.14.6
        • AMC 1.14.0
      • AMC 1.13
      • AMC 1.12
      • AMC 1.11
      • AMC 1.10
        • AMC 1.10.1
        • AMC 1.10.0
      • AMC 1.9
        • AMC 1.9.1
        • AMC 1.9.0
      • AMC 1.8
    • Hardware
      • Skynode Rev 11 (Jan 2022)
Powered by GitBook
On this page
  • AMC does not connect to Skynode
  • Skynode is offline
  • Skynode does not upload flight logs
  • Pairing does not work
  • WebUI and diagnostic report
  • How to generate a diagnostic report?
  • Updating the Skynode or installing custom apps is failing
  • No free disk space available on Skynode
  • Removing all stopped docker applications
  • Removing individual docker applications
  • AMC shows telemetry for only one battery from Skynode
  1. Hardware Integration
  2. Skynode

Troubleshooting

PreviousSkynode LED MeaningsNextLegacy DSM/DSMX Support

Last updated 1 year ago

AMC does not connect to Skynode

  • For the most stable connection, we recommend using a native Ubuntu 20.04 LTS operating system and the provided USB-C cable.

  • Check that you can access the webUI on .

  • Ensure Skynode is powered on by checking the .

  • Disable your firewall or add an exception to allow MAVLink traffic to come through.

  • If Skynode's WiFi is in Access Point Mode (factory default), try connecting as an alternative. Make sure the Wifi antenna is properly attached. This can be very handy for tablets running Android.

Skynode is offline

  • The "Online" status in the suite is refreshed every 5 minutes.

  • Did you card with a data plan?

  • Did you (APN, PIN etc) via AMC correctly?

  • Did you attach the LTE antennas correctly?

  • Did you

  • Does the WebUI on say that Skynode is online?

Skynode does not upload flight logs

Pairing does not work

  • What operating system are you using? Which interface for connection? (Ethernet or USB)? Some OS struggle with Microhard USB interface, therefore we recommend using Ubuntu 20.04 or Android and connecting via ethernet.

  • Disable your firewall on the ground station, as this can prevent MAVLink traffic from getting through to AMC.

  • Does AMC detect the GROUND unit? This can be checked in AMC under Settings -> Microhard. There should be a green label "Ground unit: connected".

  • Are you sure you have connected the GROUND unit and not the AIR?

  • Is the GROUND unit radio powered? It does not receive power over USB or Ethernet, but needs to be powered separately.

  • Does Skynode detect the AIR unit? This can be easily detected with the orange LED. If it is blinking. Skynode cannot even reach it's own radio module. Check the cabling, IP settings and configuration password of the AIR unit.

  • As a test, power up both AIR and GROUND unit without connecting them to anything. For this test, do not connect the GROUND unit to your computer/ground station and don't connect the AIR unit to Skynode. Just power the radios on and wait until they are booted. Do the 3 "RSSI" LEDs blink in a "walking pattern" (indicates "searching for other side"), or are they steady-on (indicates "connection established")?

    • If they are steady-on, power down everything, wire up as described and wait for a connection. If you loaded the pre-paired configs on both AIR and GROUND, you don't have to pair, simply wait for the connection.

  • There is known driver issue when using Windows. This document describes a procedure to install the correct RNDIS driver to resolve it:

  • The Microhard radios support fast ethernet, but no gigabit ethernet. In rare cases, your system might be set up to work exclusively with gigabit devices and fail to fall back to fast ethernet.

WebUI and diagnostic report

The Advanced mode will give you a better understanding of what might be wrong with your Skynode. You will get an insight on each system service and software component status. You will also get access to more information related to the network, peripherals, performance, partitions, etc.

How to generate a diagnostic report?

You can generate a diagnostic report by opening up the Show additional information tab and clicking on the Generate diagnostic report. It will generate a tar file that you can share with Auterion Support to get help.

Updating the Skynode or installing custom apps is failing

Skynode requires some free disk space in order to peform the update. A full disk is the most often reason why updates are unsuccessful.

The web UI shows a similar message: "Device update failed, rollback to the previous system"

The process for updating the Skynode and installing custom applications is based on Mender. To check the installation log, take a look at the file /persistent/mender.log. If you see an error similar to

time="2021-01-01T00:00:00Z" 
level=info msg="Update module output: 
Error processing tar file(exit status 1): 
write /usr/lib/aarch64-linux-gnu/libbfd-2.34-system.so: no space left on device"

No free disk space available on Skynode

The persistent partition /data can be used for custom applications and data. Through the course of time the partition can fill up and require the user to free up unused disk space.

Special care needs to be taken when removing docker images. Under no circumstances should you manually delete files inside /data/docker, since this directory contains Docker's internal database as well as cached layers. Two methods for removing unused docker containers are explained below:

Removing all stopped docker applications

The easiest way of freeing disk space is to remove stopped docker containers. Docker provides a handy command to clean the entire Docker system:

docker system prune --all

Beware that this will require you to reinstall some docker containers should you still require them afterwards.

Removing individual docker applications

It is possible remove specific docker applications with the following method

# List all applications
ls -l /data/app

# Move to the src directory of a specific app
cd /data/app/APPNAME/src

# Shutdown all docker containers associated to this app
docker-compose stop

# Remove the stopped containers
docker-compose rm -f

# Remove the images of the stopped containers
docker rmi APPNAME

# Remove the remaining app folder AFTER using aforementioned docker commands
cd 
rm -rf /data/app/APPNAME

AMC shows telemetry for only one battery from Skynode

When connecting a second battery and power module to the skynode, the readout for the second power module needs to be enabled in AEPX4 by enabling the parameter BAT1_SOURCE. Additionally AEPX4 can be configured such that having both power modules connected is mandatory in order to be able to arm the drone. In order to do so, enforce the number of required power modules by increasing the parameter to COM_POWER_COUNT=2.

Reboot Skynode and telemetry for both batteries should now be displayed in AMC.

Did you

Does the WebUI on say that Skynode is online?

While paired radios typically keep their state across software updates, the pairing process itself is sensitive to the versions of APX4 and AMC. Please ensure you are using the latest version of AMC as well as the latest version of APX4 running on Skynode.

Can you ping the radio module on 192.168.168.1? If not, try . You may have to attempt this reset process several times until it's successful, the reset button is very fiddly and can slip off easily during press-and-hold. In such a case the reset doesn't work as expected. It only worked if you can ping the radio on 192.168.168.1

Reset the modules into a pre-paired state by .

If they are showing the "walking pattern": --> and try again. Again, the fiddly reset button can make this difficult to achieve, and it may take several attempts

The advanced mode in the WebUI is really useful when you need to troubleshoot a problem with your Skynode. You can enable it by going to WebUI.

or with the Auterion SDK fails with the following hint: "Update verification failed. The system has been rollbacked"

it indicates, that there is not enough disk space available to unpack and install the update. See the section below on .

http://10.41.1.1
LED state
over Wi-Fi
insert a valid SIM
configure the cellular network
register Skynode?
http://10.41.1.1
register your Skynode?
http://10.41.1.1
available from the Auterion Suite
http://10.41.1.1
how to free disk space
installing custom apps
resetting the radio to GROUND
loading the configs via the webUI
Reset the AIR and GROUND units
6MB
Microhard Issues Troubleshoot.pdf
pdf
Connection Manager
WebUI
Updating the Skynode