Firmware Version Determination / Loading Issues

Troubleshooting
1

I just finished assembly of my v4 (after sadly sitting in the box since inception) and I’m trying to determine where I am at for firmware and updates.

Other instructions note that the version should be under a test feature with setup.
Which I do not see…( Awesome Screenshot )
Though there is some different fluid version under the interface… but I can’t seem to line the checksum with any of the releases.

If I use webUI to try and load 1.17, moves through the loading process, but ends with error 0.
The bootloader script appears to fail to detect the USB, though it’s visible for connection using a straight usb-c cable. (JTAG serial debug unit via Espressif)

Is there a way to confirm the version elsewhere?
Do I need to update to an intermediate version first?
Is the script expecting a lower baud rate for detecting the USB channel?

Thank you in advance for your guidance.

2

I think you will need to follow the instructions to load new firmware using the usb cable this first time. The machines shipped with firmware versions before 1 and after 1 updating the firmware needs to be done once with a cord to get it over that bump.

This may help
Note that to update from a firmware version before 1.0 to a version after 1.0 you will need to use a USB cable. There is a video walkthrough for that process https://www.youtube.com/watch?v=od7DpdLel6A

Here are general instructions for updating firmware:
Updating Firmware

Keeping your firmware up to date ensures you have the latest features and bug fixes.

Firmware Update Process

  1. Download the latest firmware from GitHub Releases:

    • firmware.bin

    • index.html.gz

    • maslow.yaml

  2. Access the web interface and go to the “FluidNC” tab

  3. Click “Update the Firmware” and select firmware.bin

  4. Upload the other files using the file upload function

  5. Restart the machine

1 Like
3

I would suggest you reverse the order here, i.e. Green tag: index.html.gz and maslow.yaml (maslow.yaml not generally required) first then the
Orange Tag: to load firmware.bin.
Browser session will restart after firmware loaded

2 Likes
4

I’m not sure why the firmware would not update with a straight USB-C.


./full-install.sh
esptool.py --chip esp32s3 --baud 115200 dump_mem 0x3ff5a018 4 SecurityFuses.bin
esptool.py v4.6
Found 3 serial ports
Serial port /dev/cu.usbmodem3101
Connecting…
/dev/cu.usbmodem3101 failed to connect: Failed to connect to ESP32-S3: No serial data received.
```

# test USB access to ensure data... 
source ~/.fluidnc_venv/bin/activate
python3 -c "
import serial
s = serial.Serial('/dev/cu.usbmodem3101', 921600)
print('Opened OK')
s.close()
print('Closed OK')
"
Opened OK
Closed OK

However, it did update with a USB to USB-C.
Just a heads-up in case anyone else runs into this.

2 Likes
5

Some USB cables are power only, don’t extend the data lines.

1 Like