Troubleshooting

Windows doesn’t recognize MOD as you plug it

Certain Windows systems don't recognize the MOD as a network device or fail to find the correct driver.
Use this driver for such cases: http://web1.moddevices.com/shared/mod-duo-rndis.zip

For more information see Troubleshooting_Windows_Connection.

MOD boots into restore mode by default

If the main MOD OS becomes unbootable for some reason, the MOD will automatically boot into restore mode. (used for performing OS updates)
You know the MOD is in restore mode if the inputs and output leds are blue and the display says "plugin USB cable to PC" or "copy file, eject and unplug".

When this happens we need to force a new installation of the MOD OS.
We do this by starting the restore mode with a special "force install" flag.

The method for starting this special mode is:

1. Turn off your MOD
2. Hold the left knob and footswitch down
3. Turn on the MOD (while still holding the knob and footswitch down)
4. Wait 5 seconds and let go of the knob and footswitch
   The MOD is now booting into restore mode, but will allow the installation of any valid MOD release (including the same as already installed or downgrades).
5. Connect the MOD to your PC (if not done yet) and wait for a new mass storage drive to appear
6. Download the latest release from [Releases]
7. Copy the modduo*.tar file onto the new drive and use your OS option to safely remove the drive
8. Disconnect the USB cable

On some rare cases the MOD might boot again in restore mode after this.
If that happens please start over from step 1.

Using Firefox and 'noscript' add-on prevents loading of cloud pedalboards

Open noscript preferences, then go to the advanced tab, then 'ABE'. The system ruleset should look like this:

# Prevent Internet sites from requesting LAN resources.
Site LOCAL
Accept from LOCAL
Accept from http://integrate.moddevices.com/
Deny

Note the new 'Accept from ...' rule. This makes noscript accept requests from cloud pedalboards into the local network.