Skip to main content

FAQ and errors

General RigiCloud errors​

For any issue related to unknown errors or blank pages, users should try:

  1. Refresh page
  2. Log out and Log in
  3. Check if the same issue happens in private broswer mode
  4. Refresh cache (Ctrl + Shift + R or Ctrl + F5 in Windows)

If the issue is not solved, users should contact RigiTech Support.

Airbridge Planner​

Error fetching data​

"Error fetching data" messages displayed are typically related to terrain altitudes not properly calculated. In these cases, users should try:

  1. Hide the altitude graph
  2. Check if waypoints, geocages and/or rally points do not have terrain altitudes and, if that is the case, move slightly the point/vertice or remove it.

If this is not enough, users should follow General RigiCloud errors.

Control Tower​

GNSS checks not passed before takeoff​

When UA cannot takeoff because position checks are not passed, users should:

  1. Confirm that the horizontal position of the UA is correct and within the limits
  2. Confirm that the vertical position of the UA is correct and within the limits
  3. Move if needed

Vertical position checks may be more sensitive than horizontal ones. In that case, as a general recommendation, when flying a route for the first time, users should:

  1. Measure the position and altitude of the UA at the desired takeoff and landing positions by keeping it on for at least 15 minutes, without nearby sources of interferences.
  2. Update the position and altitude based on the average observed in the flight plan.
  3. Validate the flight plan through simulations.
  4. Execute an operation (by following the standard operating procedures).

In areas where the vertical positioning on ground is not optimal, this might not be enough. In those cases, users may request RigiTech Support to increase their vertical margins.

Synchronise parameters​

If the parameters of a UA are outdated (a warning is displayed in the Control Tower), users should click on "Synchronize Parameters" (within Tools).

Simulator​

Flight plans below takeoff terrain​

The simulator assumes that the terrain is at the same level as the takeoff point.

This means that when simulating flight plans where the flight altitude becomes lower than the takeoff point, as soon as the altitude drops to this level, the simulator considers it a terrain collision and stops progressing.

We are aware of this limitation and are working on a solution. In the meantime, there are two alternatives:

  • For flight plans where the takeoff point is significantly higher than the landing point, simulate the reverse route and, after executing the back transition (when the simulator is about to land), perform an RTO. In long operations, this may result in emergency landings due to low battery.
  • Divide the flight plan (for simulation purposes only) into equivalent segments.