PanelDue Firmware 3.4.1-pre2 released

mfs12

Release Notes

This release requires RepRapFirmware 3.3 or later.

Version 2 (after August 2016) and Version 3 PanelDue are supported.

3.4.1-pre1:

M291 S3 message not cleared
Fix m291 jogging axes shown
Add support for QOI thumbnails in gcode files (supports one QOI image with max size 160x160)
- https://github.com/phoboslab/qoi/

3.4.1-pre2:

improved file detail popup layout
use faster stack size calculation when not debugging
updated RRFLibrary
added CRC16 to gcode request
- by default CRC16 is enabled
- added option to disable checksum and CRC16 in gcode requests
improved m291 jogging layout
fixed m291 axis selection handling

Downloads and flashing instructions:

Binaries can be found at https://github.com/Duet3D/PanelDueFirmware/releases/tag/3.4.1-pre2

Flashing instructions can be found at https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_PanelDue

oozeBot

@mfs12 Our logo no longer fits into 256k as the binary size of the firmware keeps growing. If you remember, we had to rework it for 3.4.1-pre1 as the binary size of the firmware grew several KB. Now, 3.4.1-pre2 is an additional 2kb larger. Any further compression of the bmp is seriously degrading it as we already whittled it down as much as we could to get it to fit for 3.4.1-pre1..

I'm not sure what our options will be as the firmware continues to grow in future releases.

We are also having issues with the go version of bmp2c. The following error is thrown. Any ideas? The escher3d version is corrupting our 8-bit bmp.

Thanks

bmp2c.exe oozebot.bmp oozebot.bin -b -c

output:
        0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
};
panic: open oozebot.bin: The system cannot find the file specified.

goroutine 1 [running]:
main.main()
        /home/manuel/Sync/3DP/github/PanelDueFirmware/Tools/gobmp2c/bmp2c.go:46 +0x12b6

oliof

@oozeBot the go version seems to require the -outfile flag before the name of the output file.

oozeBot

@oliof @mfs12 Ok- we were able to further reduce the file size of our logo, but still can't get the go version of bmp2c to work. It continues to return "The system cannot find the file specified". Is the following command line correct? I've checked the code and don't see any other parameters.

bmp2c.exe oozebot.bmp -outfile oozebot.bin

oliof

@oozebot in a quick test,

/bmp2c.exe -binary -outfile bla.bin ../../../src/Icons/Keyboard_30h.bmp

generated the bla.bin file for me without issue. So if you want to generate the binary output, it seems like -binary and -outfile both are required.

oozeBot

@oliof thanks. I might try from Linux as even with that example, I couldn't get it to work on Windows..

oozeBot

@mfs12 no luck so far.. Is there any documentation that goes with the bmp2c tool?

In the meantime, is there any chance you could convert the attached image to binary using the go version? It converts with bmp2c-escher3d.exe but is corrupted like reported in a previous thread. the go version correctly converts it, but we have been unsuccessful in getting it to work.

paneldue7i.8bit.bmp.txt

oliof

@oozebot It needs to be a 24bit bmp. So I converted your BMP to that:

convert paneldue7i.8bit.bmp -type truecolor pd7i.bmp

And then this command ran without error:

bmp2c -binary pd7i.bmp -outfile pd7i.bin

I am attaching the output for you here

pd7i.bin

Let me know if this works.

oozeBot

@oliof said in PanelDue Firmware 3.4.1-pre2 released:

convert paneldue7i.8bit.bmp -type truecolor pd7i.bmp

Thank you! That fixed it.. plus we learned something..!

PaulHew

Updating to Pre2 fails.
15/03/2022, 23:31:01 Error: Failed to communicate with PanelDue bootloader (no START signal received). Please try again or press the Erase and Reset switches on PanelDue.

The Paneldue indicates it is receiving firmware, then errors in the console.

P.

Phaedrux

@paulhew said in PanelDue Firmware 3.4.1-pre2 released:

Please try again or press the Erase and Reset switches on PanelDue.

Press the erase and reset switches on the paneldue.