Troubleshooting

This page covers common issues you may encounter when using INTERGRID Configurator and how to resolve them.

Browser Compatibility

Symptom: The Configurator loads but the Connect button is missing or disabled, or you see a message about an unsupported browser.

Cause: INTERGRID Configurator requires the Web Serial API, which is only available in Chromium-based browsers.

Solution:

Use Google Chrome, Microsoft Edge, Brave, Arc, or another Chromium-based browser.
Firefox, Safari, and mobile browsers (including Chrome on Android/iOS) do not support the Web Serial API.
Make sure your browser is up to date.

Symptom: No serial ports appear in the connection dialog, or your device doesn't show up in the list.

Solution:

Verify the USB cable is firmly connected to both the device and your computer.
Try a different USB port on your computer.
Check your USB cable — some cables are charge-only and do not support data transfer. Use a cable you know works for data.
Make sure the device is powered on.
On Windows, check Device Manager to see if the device appears as a COM port. If it shows with a warning icon, you may need to install drivers.
On Linux, ensure your user has permission to access serial ports (typically the dialout group).
Close any other applications that might be using the serial port (other configurators, terminal programs, flight controller tools).

Symptom: The device connects but then disconnects unexpectedly, or the connection is unstable.

Solution:

Replace the USB cable — this is the most common cause. Use a high-quality, short cable.
Avoid USB hubs — connect directly to your computer's USB port.
On laptops, try a different USB port (some ports share bandwidth with other peripherals).
If using FC Passthrough, make sure the flight controller is not being accessed by another tool simultaneously.

Symptom: You change settings but they revert after reconnecting, or the save operation fails.

Solution:

Make sure you click Save before disconnecting. Changes are held in memory until explicitly saved to the device's EEPROM.
If the save operation reports an error, check your connection stability and try again.
If settings persistently fail to save, the device's EEPROM may have an issue — try a factory reset and reconfigure.

Symptom: The firmware flash process stops partway through, shows an error, or the device becomes unresponsive after a flash attempt.

Solution:

Don't panic — the bootloader is separate from the main firmware and is rarely affected by a failed flash.
Disconnect and reconnect the USB cable.
Try connecting to the device again in the Configurator.
If the device is detected, attempt the firmware flash again.
If the Configurator backed up your settings before the flash, they will be restored automatically after a successful flash.
Ensure you have a stable USB connection (no hubs, good cable) and that your computer won't go to sleep during the process.

tip

If a flash fails repeatedly, try using a different USB port or cable, and close all other applications that might be using system resources.

Symptom: The interface shows stale data, controls don't respond as expected, or the app seems stuck.

Solution:

Clear local storage — Go to Settings → Configurator → Clear Local Storage. This removes cached data and resets the app state. See Clear Local Storage.
Try an incognito/private window — This rules out browser extensions or cached data as the cause.
Disable browser extensions — Ad blockers or privacy extensions can interfere with the Web Serial API or the app's network requests.
Hard refresh the page (Ctrl+Shift+R / Cmd+Shift+R) to clear the browser cache.

If you've tried the above solutions and are still experiencing issues:

Enable the Debug Console — Go to Settings → Configurator and toggle on the debug console. Reproduce the issue and note any error messages. See Debug Console.
Contact SIGSA Support — Visit the Help page in the Configurator for contact information and feedback options.
Include details — When reporting an issue, provide your browser name and version, operating system, device model, firmware version, and a description of the steps that led to the problem.