2.3 Upload Firmware and Config Files

Check List · Step 3 of 12 · Optional learning step for reinstalling FluidNC firmware and uploading files
ℹ️
Optional Section: The board is shipped with FluidNC firmware, config.yaml, and the required WebUI file pre-installed from the factory. You do not need to repeat this step for normal first-time use.
▶️ Shared V5.77 / V5.88 Tutorial Video
The PiBot V5.77 Carrier and V5.88 Ultra use the same FluidNC firmware upload procedure shown in this video. The operating steps are shared, but always use the firmware package and config.yaml intended for your board model.
📥
Download the V5.77 test config.yaml from 5 Documentation. For the FluidNC installer and index.html.gz, use the ESP32-S3 package supplied with your board or by PiBot support. Do not use a V5.88 firmware package.
⚠️
Warning: Running erase_s3.bat will erase the existing firmware and files from the ESP32-S3 flash. This operation cannot be undone. Only continue if you really want to reinstall the firmware and upload the files again.
1
Install the CP2102 Driver
  • Connect the board to your Windows PC using a USB-C data cable.
  • Install the corresponding CP2102 USB-to-UART driver.
  • Open Windows Device Manager and check the assigned COM port.
  • Write down the COM port number. You may need it during firmware upload or serial connection.
2
Erase the Existing Firmware
💡 Open the firmware folder first. Make sure the package explicitly supports the PiBot V5.77 Carrier plug-in ESP32-S3 module.
  • Find and run erase_s3.bat.
  • Wait until the erase process is completed.
  • ⚠️ This step removes the existing firmware and files from the board.
3
Upload the Wi-Fi Firmware
  • Run install-wifi_s3.bat.
  • The tool will automatically detect the COM port and start uploading the firmware.
  • Wait until the upload is fully completed.
  • After upload, select the board COM port and open the serial connection.
4
Upload Config and WebUI Files
  • Press CTRL + U to open the file upload function.
  • Upload the first file: the test config.yaml.
  • Wait until the upload is complete.
  • Press CTRL + U again and upload the second file: index.html.gz.
Upload Order File Purpose
1st config.yaml Factory test configuration file for the checklist procedure.
2nd index.html.gz FluidNC WebUI file.
💡 If the uploaded configuration file is not named config.yaml, use FluidTerm or another command-line tool to send $Config/Filename=your-file.yaml with the exact filename. Then press CTRL + R to restart and load it.
5
Restart the Board
  • Press CTRL + R to restart the board.
  • Wait for the startup message to appear.
  • After rebooting, the terminal should show the FluidNC 4.0.x version information.
⚠️
Note: If USB CDC appears in red in the self-check message, this does not affect normal use. It is used for the test in Section 3.1 Test Secondary USB.
Expected Results
  • The CP2102 driver is installed and the board COM port can be found.
  • The Wi-Fi firmware is uploaded successfully.
  • The test config.yaml and index.html.gz are uploaded successfully.
  • After pressing CTRL + R, the startup message shows FluidNC 4.0.x.