Print

Voxelab Aquila X1 Firmware | V1.0.1 Board

Board Limitations Note: Due to the design of the Voxelab boards with TMC drivers Linear Advance will probably not work correctly. The feature is available but use at your own risk.

Maybe you’re adding our EZABL kit to the machine. This is the download for you. You will need to update the LCD and Board firmware for this machine. Directions are below.

LCD Notes: Currently only the 12864 LCDs work 100% correctly with this printer and board. We have a kit here to do the conversion. The stock color LCD is glitchy but is functional, this is due to limited support in Marlin for those LCDs.


Download

Supported CPU List
  • STM32F103 RCT6/RET6
  • GD32F103 RCT6/RET6
  • N32F103 RCT6/RET6

This firmware supports the following CPU types and memory capacities. If your board has any CPU other than the STM32F103RCT6 you will need to open the platformio.ini file and read the directions in there on how to build for the CPU your board has. Failure to read the directions and build for the correct CPU may brick your board so make sure you check before flashing.

We also recommend you download the Unified 2 STL pack as well. This contains EZABL mounts, Gantry leveling Blocks, Solid bed mounts, and Bed Level test files. Click here to go to the Unified 2 STL Pack download page.


Installation Directions

You must flash BOTH the LCD and the printer board. If you do not flash both then the firmware will not function correctly.

Printer LCD Firmware Update

  1. In the firmware download there is a folder called “LCD Firmware”. Open that folder and then open the folder labeled “DWIN DACAI Color LCDs”
  2. In there is a ZIP file called “DWIN_DACAI_LCDUpdate_TH3D_X.X”. Extract the ZIP file to a blank, FAT32 formatted w/allocation size of 4096 (4K) MicroSD card.
    1. The files must be extracted to the ROOT of the MicroSD card. If they are not the firmware will not update.
  3. Power the printer off and remove the LCD from its snap-on bracket.
  4. On the rear of the Aquila X1 LCD, there is an SD slot that you access by removing the 4 screws on the rear of the casing.
  5. Insert the MicroSD card with the files on it into the LCD.
  6. With the LCD cable connected to the printer and the MicroSD card inserted into the rear of the LCD turn on the printer. You will see the LCD change from black to blue to orange. Wait 30 seconds after it turns orange and then power off the printer.
    1. If you have the DACAI LCD the LCD will show text progress of the update.
  7. Remove the MicroSD card and re-assemble the LCD
  8. Turn the printer on. You should see our logo and the Marlin logo when you power on if the firmware updated successfully

1. – Printer Board Firmware Update

NOTE: You must have our LCD firmware loaded on the LCD screen before updating the board firmware. Please do this before flashing the firmware on the printer board.

NOTE: Every time you flash the firmware it must start with firmware followed by random numbers/letters. It must be a different file name every time you flash. This is a limitation with the bootloader on these boards. It will NOT rename the file like other boards after it flashes.

1.a – Setup VSCode with our installation guide

1.b –Download the firmware

1.c –Extract the files to a folder on your computer

1.d –Open the folder labeled “Firmware” in VSCode

1.e –Open the Configuration.h file that is located under the “Marlin” folder on the left side of the VSCode screen

1.f – In the Configuration.h file, uncomment (remove the 2 / in front of #define) the AQUILA_X1 line and any other options you are going to use in the firmware.

CPU TYPE – Verify and Set your default_envs: Because these boards shipped with multiple CPU variants you must open up the printer and check what CPU you have. If it is not the STM32F103RCT6 then you will need to open the platformio.ini file and change the default_envs from STM32F103RCT6_voxelab to whatever environment matches the CPU you have. There are directions and details in the platformio.ini file itself, read them and update the default_envs value to whatever CPU is in your printer. If yours is not listed, then it is not supported.

1.g –Click the ✓ at the bottom of VSCode to compile the firmware. The firmware will compile. This may take 1-5 minutes depending on the speed of your computer and internet connection

1.h – On the left side of VSCode expand “.pio” and “build” until you see the CPU Build folder. Right click on tthe CPU Build folder and click “Reveal in File Explorer”. The CPU build folder will match whatever the default_envs value is set to in the platformio.ini folder so make sure to pay attention.

1.i – In the file explorer open the CPU Build (this is the same as the default_envs name you used) folder

1.j – Look for the latest firmware-XXXXXXXX-XXXXX.bin file and copy that to your SD card in a folder called “firmware” on the SD card itself. If your SD card does not have a folder called “firmware” on it then make one. This SD card must be FAT32 formatted. If you compiled more than one time you will see multiple firmware files. Use the latest one based on the date the file has.

1.k – Power OFF your printer and Insert the SD card with the latest firmware-XXXXXXXX-XXXXX.bin file into your printer. Turn the printer on. It will take a little longer than normal to boot up.

1.l – When the printer boots you will see the TH3D logo on your LCD. Make sure to reset your EEPROM on your printer after flashing any firmware. You can do this from your printer LCD or by sending a M502 followed by M500 with your favorite Gcode sender application.


THIS FIRMWARE AND ALL OTHER FILES IN THE DOWNLOAD ARE PROVIDED FREE OF CHARGE WITH NO WARRANTY OR GUARANTEE FROM TH3D STUDIO LLC. SUPPORT IS NOT INCLUDED JUST BECAUSE YOU DOWNLOADED THE FIRMWARE.

TH3D STUDIO LLC IS NOT LIABLE FOR ANY DAMAGE TO YOUR PRINTER, PERSON, OR ANY OTHER PROPERTY DUE TO USE OF THIS FIRMWARE. IF YOU DO NOT AGREE TO THESE TERMS THEN DO NOT USE THE FIRMWARE.


Changelog Information

We do not maintain a full change log for this firmware. However, you can track all changes and modifications to our firmware code on the GitHub repo for Unified 2 Firmware.

Table of Contents