Problem codes

When something goes wrong, FORGE Studio shows a code with what happened and what to do. Here is every code. If the problem stays, write to us with the code.

FORGE Studio

APP-101 FORGE Studio met an unexpected error.: Studio keeps running. If something stopped working, close Studio and open it again.; Write to us about APP-101
APP-102 A Studio window stopped unexpectedly.: Studio opens the window again. If it keeps happening, restart the computer.; Write to us about APP-102
APP-103 A Studio page stopped working.: Press Try again, or open another page from the left. The flight controller and the link are not affected.; Write to us about APP-103
APP-104 There is not enough free space on this computer's disk.: Free some space on the disk (delete or move files you do not need), then try again.
APP-105 Windows did not let Studio write a file it needs.: Restart the computer and try again. If it keeps happening, install Studio again from uvira.in.; Write to us about APP-105
APP-106 Studio could not move its files from its old name.: Your older recordings and settings stay in the folders named UVIRA Ground Control. Close Studio, move what you need into the UVIRA FORGE Studio folders, then open Studio again.; Write to us about APP-106
APP-107 You sent UVIRA a problem report from Help.: UVIRA reads it and answers by e-mail within 1 working day.; Write to us about APP-107

Connecting to the flight controller

CON-101 This computer could not send to the drone.: Check the computer is still on the drone's Wi-Fi. Studio tries again every 2 seconds.
CON-102 The flight controller did not answer.: Check the drone is powered and its Wi-Fi is on. Studio tries again every 2 seconds.
CON-103 The connection to the flight controller was lost.: Studio keeps trying. Check the drone is powered and within Wi-Fi range.
CON-104 The connection to the flight controller could not open.: Studio tries again every 2 seconds. If it keeps failing, restart Studio.; Write to us about CON-104
CON-105 There is no live link to the flight controller.: Connect to the flight controller on the Connect page, then try again.
CON-106 The flight controller did not answer the request.: Check the link in the status bar, then try again.
CON-107 The flight controller could not join the Wi-Fi network.: Check the network name and password, that the network is 2.4 GHz and that the drone is in its range. Then join it again from the flight controller's phone setup page (System › Simulation network).
CON-108 The flight controller is paired with another computer.: Join the drone's own Wi-Fi (its name and password are on the drone's card) and press Pair this computer (Setup › Connection) within 2 minutes of turning the drone on.
CON-109 Pairing is closed now.: Pairing works in the 2 minutes after the drone is powered on: turn it off and on, then press Pair this computer (Setup › Connection).
CON-110 The flight controller refused the pairing.: Turn the drone off and on and press Pair this computer (Setup › Connection) again. If it keeps refusing, update its firmware in Account › Updates.; Write to us about CON-110
CON-111 This flight controller's firmware does not do that yet.: Update the flight controller's firmware in Account › Updates, then try again.

The flight controller

FC-101 The setup steps on the phone page are not finished.: Open the phone setup page and finish its steps, then arm.
FC-102 The drone does not take off in this mode.: Select STABILISE, ALTHOLD or LOITER first, then arm.
FC-103 The flight controller is still finding level.: Keep the drone still for a few seconds after powering it, then arm.
FC-104 The height sensor is not ready yet.: Wait a few seconds, then try again.
FC-105 This mode needs a GPS position and there is none.: Check the GPS is plugged in and has a clear view of the sky. Without GPS, fly STABILISE or ALTHOLD.
FC-106 There is no home position yet.: Wait for the GPS to find its position, then try again.
FC-107 The drone leans too much.: Put it level on the ground. In the simulation, press Restart the simulation if it lies tipped over.
FC-108 The throttle is not down.: Move the throttle stick to the bottom, then arm.
FC-109 The radio signal is lost.: Switch the radio on. In the simulation you can also fly with a radio plugged into this computer by USB, or with Studio's sticks on the virtual flight controller (Fly › Sticks).
FC-110 This mode needs to know which way is north.: Connect a compass, or fly a little in STABILISE or ALTHOLD with GPS first.
FC-111 A motor test or a calibration is running.: Wait for it to finish, then try again. If nothing is running, switch the drone off and on: the motion sensor may not be answering.
FC-112 The battery reads low.: Charge the battery, or check the battery cells in Setup › Airframe on the phone page.
FC-113 The flight controller does not know your drone yet.: Answer Setup › Airframe on the phone page first.
FC-114 The simulation does not know where on the Earth it flies.: Enter its latitude and longitude in Simulate › Where it flies.
FC-115 FORGE could not start.: FORGE needs a program on the drone (send one from the FORGE page), the override switch off, the battery not critical and a FORGE licence on the board. Armed in FORGE on the ground, the drone takes off to 2 m by itself, then the program starts. If this board has no FORGE licence yet, programs are kept but do not run: tell UVIRA in Help › Something wrong? with the board's serial; we fix it within 1 working day.
FC-116 The drone is not ready for that mode yet.: Wait a few seconds and try again, or fly STABILISE.
FC-117 That cannot be done while the drone is armed.: Land and disarm, then try again.
FC-118 The flight controller did not accept the request.: Update the flight controller's firmware in Account › Updates so it matches Studio.; Write to us about FC-118
FC-119 The flight controller could not do it.: Look in Fly › Events for why, then try again.
FC-120 On the real drone, Studio's flight buttons work only from the computer paired with it.: Pair this computer (Setup › Connection › Pairing: switch the drone off and on, then pair within 2 minutes). Fly to point and Take off work only in the simulation: on the real drone, fly with your radio.
FC-121 The radio signal was lost in flight.: The drone follows its radio-loss setting. When the signal is back, move the mode switch to take control again.
FC-122 The battery is low.: Bring the drone back and land soon.
FC-123 The flight controller lost track of its attitude or position.: Land as soon as it is safe and check the sensors in Setup › Flight controller before flying again.
FC-124 The drone lost its position.: Fly STABILISE or ALTHOLD and bring it back by sight.
FC-125 The FORGE program stopped giving valid commands.: The flight controller took over. Fly it by hand, then check the program in FORGE.
FC-126 The drone left the geofence.: It comes back by itself. Move the mode switch to take control again.
FC-127 The battery is critically low.: The drone lands now. Charge the battery before flying again.
FC-128 Crash detection stopped the motors.: Disarm, set the drone upright and check the propellers, arms and motors before flying again.
FC-129 The drone spun out of control and is landing.: Check the motor directions, motor order and propellers in the motor test on the phone setup page (Motors) before flying again.
FC-130 The motion sensor stopped answering in the air.: Check its connector before flying again. If it happens again, contact UVIRA support.; Write to us about FC-130

The virtual flight controller and the simulation

SIM-101 The virtual flight controller stopped.: Start it again from Connect.; Write to us about SIM-101
SIM-102 The virtual flight controller could not start.: Start it again, or restart Studio.; Write to us about SIM-102
SIM-103 Your plan does not include the simulation on this computer right now.: Sign in, or renew your FORGE Studio plan from Account.

The 3D view

3D-101 The 3D view started but its picture did not come through.: Press Start the 3D view again. If it happens again, update the graphics driver from the graphics card maker's website.; Write to us about 3D-101
3D-102 The 3D view closed unexpectedly.: Open the 3D view again.; Write to us about 3D-102
3D-103 The 3D view could not start.: Open it again. If it does not start, restart Studio.; Write to us about 3D-103
3D-104 The 3D view could not prepare the world and the drone.: Open it again. If it keeps failing, choose the world again in Simulate › Where it flies.; Write to us about 3D-104
3D-105 The drone camera's picture did not come through.: Close and open the 3D view again.; Write to us about 3D-105
3D-106 The 3D view could not open its connection on this computer.: Restart Studio. If it keeps happening, restart the computer.; Write to us about 3D-106
3D-107 Studio could not reach UVIRA to download the 3D view.: Connect to the internet, then open the 3D view again.
3D-108 The 3D view download stopped because the connection dropped.: Open the 3D view again: the download continues from where it stopped.
3D-109 The 3D view download did not match what UVIRA published, so it was deleted.: Open the 3D view again to download it again.; Write to us about 3D-109
3D-110 The 3D view download could not be unpacked.: Open the 3D view again. If it keeps failing, check the disk has free space.; Write to us about 3D-110
3D-111 The new 3D view could not be put in place.: Restart Studio and open the 3D view again. The one you had stays until then.; Write to us about 3D-111
3D-112 The 3D view needs a part of Windows (DirectX) that this computer does not have yet, and it was not installed.: Open the 3D view again and press Yes when Windows asks to allow the change.
3D-113 The 3D view could not run with this computer's graphics, in any of the ways Studio tried.: Everything else in Studio works without it. Studio sent UVIRA a report; we contact you. A newer graphics driver from Windows Update often fixes it: then open the 3D view again.; Write to us about 3D-113

FORGE programs

FRG-101 The FORGE program stopped running: a part of it took too long or it crashed.: Check the Computation bar at the top of FORGE: keep heavy maths out of every tick, or spread it over more states.
FRG-102 The FORGE program gave no command in its first seconds.: Make its first state command the drone from the start, with a fly block.
FRG-103 The FORGE program stopped sending commands.: Make every state keep commanding the drone each tick, also while it waits.
FRG-104 The FORGE program handed control back.: If that was not meant, check the condition before its hand-back block.
FRG-105 The FORGE program asked for a mode a program may not fly.: Change the mode in its fly blocks.
FRG-106 The mode the FORGE program asked for needs something the drone lacks now.: Check the GPS and the position estimate, or use a mode that does not need them.
FRG-107 The FORGE program's command had values that are not numbers or are out of range.: Check for divisions by zero and the limits in the blocks that feed its fly block.
FRG-108 The program upload stopped because the drone did not answer.: The program on the drone is unchanged. Check the link and upload again.
FRG-109 The drone refused the program.: Read the reason shown, correct the program in FORGE and upload again. The program it had stays.
FRG-110 The flight controller could not store the program.: Upload again. If it keeps failing, restart the drone and contact UVIRA support.; Write to us about FRG-110
FRG-111 Reading the program from the drone stopped.: Check the link and read it again.

Updates

UPD-101 Studio could not reach UVIRA to look for updates.: Studio tries again later. Check the internet connection.
UPD-102 The update information from UVIRA did not pass Studio's check, so it was ignored.: Studio checks again later. If it keeps happening, contact UVIRA support.; Write to us about UPD-102
UPD-103 The update download stopped because the connection dropped.: Choose Update now to continue it from where it stopped.
UPD-104 The update download did not match what UVIRA published, so it was deleted.: Choose Update now to download it again.; Write to us about UPD-104
UPD-105 The update's installer did not start, so nothing changed.: Choose Update now again. If it keeps failing, download Studio from uvira.in and install it.; Write to us about UPD-105
UPD-106 The update did not finish installing, so the version you had is still installed.: Try again from Account › Updates.; Write to us about UPD-106
UPD-107 The firmware for this flight controller could not be downloaded.: Check the internet connection and try again.
UPD-108 The older copy of Studio could not be removed.: Remove it in Windows Settings › Apps › Installed apps: the UVIRA FORGE Studio entry for everyone on this computer.
UPD-109 The flight controller was not updated because it is armed.: Land and disarm, then press Update the flight controller again.
UPD-110 The flight controller did not take the update from this computer.: Over Wi-Fi it takes an update only from the computer paired with it: pair this computer (Setup › Connection › Pairing: switch the drone off and on, then pair within 2 minutes). A flight controller with firmware older than 0.2.1 is updated with Install over USB.
UPD-111 The new firmware stopped on its way to the flight controller.: The firmware on it did not change. Keep the drone close and powered, then press Update the flight controller again.
UPD-112 The new firmware was damaged on its way to the flight controller, so it was not used.: The firmware it had is still there. Press Update the flight controller again.; Write to us about UPD-112
UPD-113 The flight controller could not store the new firmware.: The firmware it had is still there. Switch the flight controller off and on, then try again. If it keeps happening, contact UVIRA support.; Write to us about UPD-113
UPD-114 The flight controller refused the new firmware: it is not made for this flight controller.: The firmware it had is still there. Look for updates again, then try again. If it keeps happening, contact UVIRA support.; Write to us about UPD-114
UPD-115 The new firmware is too large for the flight controller.: Nothing changed on the flight controller. Contact UVIRA support.; Write to us about UPD-115
UPD-116 The firmware update went wrong on the way.: The firmware on the flight controller did not change. Press Update the flight controller again.; Write to us about UPD-116
UPD-117 The new firmware did not start, so the flight controller went back to the firmware it had.: The flight controller works as before. UVIRA hears about it; try the update again after the next release.; Write to us about UPD-117
UPD-118 The flight controller did not come back with the new firmware after its restart.: Check that it is powered, switch it off and on again, then connect: Studio shows which firmware it runs.

Account and plan

ACC-101 UVIRA's server gave an unexpected answer when Studio checked your plan.: Studio keeps working and checks again later. If it lasts more than a day, contact UVIRA support.; Write to us about ACC-101
ACC-102 Studio cannot reach UVIRA.: Check the internet connection and try again. After the first sign-in, Studio works offline for 14 days.
ACC-103 Sign-in did not work.: Check your e-mail and password and try again.
ACC-104 This computer was signed out of your UVIRA account.: Sign in again on the Account page.
ACC-105 The flight controller could not be linked to your account.: Check the internet connection and try again from the Account page.

Recordings and Analyse

REC-101 This recording could not be opened.: It may be damaged or made by a newer Studio. Update Studio, or open another recording.; Write to us about REC-101
REC-102 A recorded 3D view video could not be finished.: The flight log is kept. In Analyse the video may not jump to every point; record the next flight as usual.; Write to us about REC-102
REC-103 The file could not be saved.: Check the disk has free space, then try again.; Write to us about REC-103
REC-104 The flight video could not be made.: Close the 3D view and try again. If it keeps failing, restart Studio.; Write to us about REC-104
REC-105 The flight report could not be made.: Try again. If it keeps failing, restart Studio.; Write to us about REC-105
REC-106 The 3D view could not be recorded with the flight log.: The flight log is kept. Close and open the 3D view, then record the next flight.; Write to us about REC-106

Radio and sticks

RAD-101 The throttle is up or a stick is pushed over.: Move the throttle to the bottom and let the other sticks go back to the middle, then arm.
RAD-102 A switch on the radio is flickering by itself.: Check the switch on the radio. Studio ignores it until it is steady; the sticks still work.

Settings and drones

SET-101 The saved actors could not be read, so Studio started with the usual actors.: Studio kept a copy of the damaged file beside it. Place your actors again in Simulate › Actors.; Write to us about SET-101
SET-102 A saved world could not be read, so it was left out.: Get the world again from the Marketplace or from its file in Simulate › Where it flies.; Write to us about SET-102
SET-103 Studio could not save a setting.: Check the disk has free space. The setting is used until Studio closes.; Write to us about SET-103
SET-104 Sending the drone stopped because the flight controller did not answer.: The drone on the flight controller is unchanged. Check the link and send it again.
SET-105 The flight controller refused the drone.: Read the reason shown, correct the drone in Setup › Drone and send it again.
SET-106 The flight controller could not store the drone.: Send it again. If it keeps failing, restart the drone and contact UVIRA support.; Write to us about SET-106
SET-107 This file is not a settings file Studio can read.: Choose a settings file saved from Setup › All settings (Save them to a file…) or by the phone setup page.
SET-108 Some settings were not set on the flight controller.: Check the link and that the drone is disarmed, then import the file again and apply.
SET-109 The settings file could not be saved.: Check the disk has free space and choose another folder, then save it again.; Write to us about SET-109

Marketplace and School

MKT-101 The Marketplace could not be reached.: Check the internet connection and try again.
MKT-102 The Marketplace list did not pass Studio's check, so nothing from it is offered.: Try again later. If it keeps happening, contact UVIRA support.; Write to us about MKT-102
MKT-103 The Marketplace download stopped because the connection dropped.: Press Get again to continue it from where it stopped.
MKT-104 The Marketplace download did not match what the Marketplace lists, so it was deleted.: Press Get again to download it again.; Write to us about MKT-104
MKT-105 The Marketplace did not send the file.: Try again later.
MKT-106 The item from the Marketplace could not be added to Studio.: Press Get again. If it keeps failing, contact UVIRA support with this code.; Write to us about MKT-106
MKT-107 The School lessons from UVIRA did not pass Studio's check, so the lessons Studio has stay.: Nothing to do now: Studio tries again later. If it keeps happening, contact UVIRA support.; Write to us about MKT-107

Still Stuck?

Send us the code and what you were doing. A person replies within 1 working day.

Write to us with the code