Discrepancy with flashing PanelDue from Duet

[PDBeal]

There is a discrepancy in the instructions for flashing the PanelDue via the Duet controller.

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_PanelDue

This page says you have to rename the .bin file to PanelDueFirmware.bin, which is fine. However, later on the M997 command example has the full original filename in the command. Obviously these file names are meant to match, but it has me wondering if it's still required to rename the .bin file or not. It works with the rename, but does it work without the rename like the example?

[jay_s_uk]

@pdbeal i believe it works without the rename and its handled internally by RRF

[droftarts]

@pdbeal if you send M997 S4 without the P parameter, it looks for a file named PanelDueFirmware.bin in the /firmware folder. If you use the P parameter, it can be named whatever you want, and you can store it on the SD card wherever you want, as the P parameter can include the path to the file too. See M997 in the Gcode dictionary.

Ian

[dc42]

@pdbeal it's not necessary to rename the file if you use the P parameter. The quickest way is to open the Firmware folder in DWC, upload the new file, then right click on the file and click Install. As long as the filename starts with PanelDueFirmware and ends in .bin that should work.

[PDBeal]

@dc42 It may be pertinent to update the docs.duet3d.com site then reflecting the correct information.

[droftarts]

@pdbeal thanks, I’ll update the documentation when I next get the chance.

Ian

[droftarts]

@pdbeal I've updated this section of the instructions: https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_PanelDue#firmware-update-via-duet

Ian