Troubleshooting & FAQ

Use the checklist below to help troubleshoot your issues, or search for a specific issue below. If you have a problem not listed on here or need extra support, please feel free to reach out to us via or ask us a question on our community Discord channel.

Troubleshooting Checklist

Quinly Troubleshooting Checklist (Downloadable pdf)

Troubleshooting- Firmware & Hardware

Error message on the Ender 3: Err: EEPROM Version after flashing firmware.

  1. On your printer LCD, go to your printer menu.
  2. Head to your Configuration menu. 
  3. Enter into the advanced settings menu.
  4. Scroll to the bottom until you see "Initialize EEPROM", and select "Init".
  5. Reboot your printer, then reboot your Raspberry Pi.

In the case it gives you "'EEPROM Version Error' Initialize EEPROM? " Go ahead and hit "Reset".

My Arduino IDE is not compiling.

  • Ensure that under ‘Tools’, you have Sanguino 1284p selected as your board and processor is ATmega1284P (16MHz).

  • If you are on the MAC Operating System and it is not compiling, try following this guide to update to Arduino 1.8.12.  

My BLTouch is not responding to Quinly and my Ender 3. 

  • Ensure everything is wired correctly. You can look up online resources to wiring your BLTouch, or send us an email at if you require further assistance
  • There are 3 ways you can plug in the BLTouch if you have the V4 board (32 bit), and only one way on the 8 bit board.
  • Ensure that you are on the right firmware version for your printer. You can take a look at the installation manual to ensure you're on the correct firmware version.

My BL Touch only probes one corner of the plate and will not proceed with the rest of the print. My LCD displays “Stopped” and Quinly proceeds to reset without printing. 

1. Check and re-seated all the BL Touch connections.

2. Re apply hot glue to the connections in the electronics box, if needed.

3. Re-level the corners of the bed.

4. Double check the Z-offset in the configuration on LCD.

5. Reboot your printer and your Raspberry Pi.

Troubleshooting- Connection to Quinly on the Raspberry Pi

If you are having trouble connecting to Quinly, follow these steps to help diagnose your issue.

1. Make sure the Rasperry Pi is booted properly, take a look at the LED lights near the power cable. You will be able to see a red LED as well as a green LED that may be flashing.

2. Is your Raspberry Pi underpowered? If your RPi is underpowered, you may notice it will not connect to Quinly.

If you're noticing an issue with your Raspberry Pi that is not listed here, you may reference this guide here. If your Raspberry Pi is correctly booted, and there are no problems here, browse the issues below to continue troubleshooting.

My RPi booted properly, but the IP does not show up/ RPi does not read my wpa_supplicant.conf file. 

  • Ensure that your wpa_supplicant file is a ‘.conf’ file and not a ‘.txt’. 
  • Ensure that the country code is correct.
  • Ensure that the quotation marks surrounding country codes and wifi information are still there.
  • Ensure that it is placed into E:Boot (not Root if on Linux), you do not need to put it in any particular folder. Make sure to safely remove the SD card afterwards. 
  • If it is still not working, try downloading a fresh file from the Resources page, and using Notepad++ or Sublime Text to edit the file. 
  • As a very last resort, you may have to reflash your Raspberry Pi Image.

I am able to connect to Quinly via the IP, but the connection drops after a few minutes.

With this issue, you are able to connect to the UI from the displayed IP on the LCD, but after a few minutes, you are no longer able to access the UI on the same IP.

This may be due to your IP constantly changing due to your router. To check if this is the issue, you may log into your Router IP or use a IP scanner for your local network (Angry IP Scanner is great for this) to see if your RPi's Ip has changed since boot.

  • If you see the IP has changed. You will have to set a static IP for your Raspberry Pi. The steps on how to do so will differ based on your router, so you may have to look up how to do so.
  • If has not changed, please connect with us via Discord or at to continue troubleshooting.

Quinly is not updating stats on my browser when accessed remotely even though I am connected and actively printing.

When accessing your Raspberry Pi remotely when on the same network, if you are on a school or work network, there may be a firewall issue where updates are not sent over the browser. We suggest contacting your IT department to assist with the issue.

If you are having this issue despite being on a private, home network, there may be something wrong with your Raspberry Pi image or SD card. Try re-flashing the Raspberry Pi Image to see if it solves the problem, if not, you may need to replace your SD card. We recommend the brand, Sandisk, with a minimum storage of 8gb.

My Raspberry Pi displays an IP, but the UI does not load when trying to access <pi_ip>:8080

If your printer LCD displays an IP, but the UI does not display when you are trying to access, it may be that the timezone of your RPi is off. 

  1. Open the command prompt/ terminal of your computer. 
  2. Type ssh pi@<your_pi_ip>  (eg. ssh pi@ 
  3. Type in Yes to connect. 
  4. Enter 3dque for your password.
  5. Type in date and check to see if your date matches your local time. 
  6. If it does not, type in sudo raspi-config
  7. Navigate down to Localisation Options

     8. Go to ‘Change Time Zone’ and select your region followed by your city. 

  1. Once that has been completed, use your left and right arrows to head back and finish. 
  2. You should see on your command prompt/terminal that it has updated to the correct time zone.

    11. Once completed, try accessing the UI once again at <pi_ip>:8080 on your local browser. 

If the issue persists after trying these steps, please send us an email at

Printer connection to Quinly is unstable -prints are always failing or UI is not responsive.

In this case, your printer is shown as connected, but you may not be receiving correct printer updates, or your prints are always shown as failing and not completing. In this case, try rebooting your Raspberry Pi to see if it helps with the issue-- ensure that the printer is on before you restart the Raspberry Pi. If the same issues continue after rebooting, try reflashing the Quinly Image. If it continues to be unstable even after reflashing, you may need to replace your SD Card. We recommend the brand, Sandisk, with a minimum storage of 8gb.

Nothing is being displayed on my monitor when I plug in my Raspberry Pi. 

**This is only if you choose to use the Raspberry Pi on it's own, without accessing it remotely via <pi_ip>:8080.

When you first set up your pi and connecting it to your printer and monitor:

  1. Ensure your HDMI cables are plugged in correctly and they are snug.
  2. Ensure that your Raspberry Pi image was flashed correctly, following the instructions from  
  3. Ensure that all your cables are plugged in before booting the Raspberry Pi (ie. connecting it to a power source. You may have to unplug the power cable and plug it in again.

Troubleshooting- Software

I get the error message “Error occurred fetching files!”

This typically means that Quinly is still starting up. Please wait a few minutes and hit refresh. Your files should be loaded back up within 5 minutes. 

I cannot delete a file that I uploaded.

Ensure that your file does not have any symbols, such as %, #, and keep your file name to a minimum number of characters. We are working to be able to support characters in the future.

Quinly shows that my print job is “Printing”, yet my printer is not actually printing.

  1. Check that the printer is not in the “Heating” or “Resetting” stage as shown on the printer card. If it is not in those two stages, proceed to Step 2. 
  2. In the case that it is shown as printing, but the printer is ‘frozen’, it may mean that the connection has been lost or broken briefly. 
  3. To remedy, turn off the Raspberry Pi followed by the printer. 
  4. Wait for the part to cool and safely remove the part, if applicable. 
  5. Restart the printer then turn on the Raspberry Pi.

I hit the abort button, but the job is still printing. 

The printer will continue to finish the commands it received before the abort button was hit. For example, if the printer is heating up, it will only abort after it finishes heating. Wait a few more minutes and the printer should stop printing. 

Note: Abort clears and removes the entire job from the queue, and will put the printer in suspended mode. The user must manually clear any prints off the bed

I submitted a job, but nothing is being printed, the job is shown as unassigned. 

  1. Ensure that the printer is connected properly to the printer. 
  2. To check, take a look at the hotend and bed temperatures displayed on Quinly. It should reflect what is shown on the printer LCD. 
  3. If not, power off the pi and reboot the printer and power on the Raspberry Pi and check cables are connected snugly.

An unfinished job has disappeared from the queue. 

This means the job has failed or has been aborted. When a job cannot be completed, due to cooldown failure, or printer connection problems, it will be marked as failed and removed from the queue.

Printer does not suspend until after it finishes the entire job.

This is the intended functionality of "Suspend". Suspend is used for maintenance between jobs. If you require the job to be removed in the middle of the print, please use the "Abort" function.


Is Quinly compatible with SKR board firmware?

Unfortunately Quinly is not currently compatible with SKR board firmware. Please take a look at the Installation Manual for which firmware version you require.

Is Arc support enabled in the firmware?

Yes, it is enabled in both the 8 bit and 32 bit for Ender 3's.

Can I add a bed cooling fan to the Printer?

Yes, take a look at our video, which will walk you through how to add a cooling fan. Quinly for Ender 3 Diy Bed Cooling Fan - YouTube.