PanelDue Firmware 3.4.1-pre1 released

mfs12

Release Notes 3.4.1-pre1

This release requires RepRapFirmware 3.3 or later.

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

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/

Downloads and flashing instructions:

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

Flashing instructions can be found at https://duet3d.dozuki.com/Wiki/PanelDue_Firmware_update

oozeBot

@mfs12 @dc42 What are we doing wrong here? It's obviously not supposed to wrap around that way.

This hasn't been an issue in the past, but since 3.4 is ~40k larger than 3.3, we had to further compress the BMP to get it to fit. It is 8-bit instead of 24-bit. Could that be the issue? We can't compress it down enough as 24-bit to make it fit..

mfs12

@oozebot said in PanelDue Firmware 3.4.1-pre1 released:

This hasn't been an issue in the past, but since 3.4 is ~40k larger than 3.3, we had to further compress the BMP to get it to fit. It is 8-bit instead of 24-bit. Could that be the issue? We can't compress it down enough as 24-bit to make it fit..

DId you patch the splash screen drawing code to support your image encoding?

I think it is likely due to your change of BMP encoding.

It could be interesting to use QOI as well for splash screens.

oozeBot

@mfs12 No, we did not modify any of the drawing code. The real issue is the new size of the 3.4 binary is so much larger than 3.3 that there isn’t enough room left for an 800x480 24-bit BMP to fit as BMP compression isn’t that great.

mfs12

@oozeBot, ok, thanks for reporting this issue then. Can you share the image or the size of it so it can be reproduced.

oozeBot

@mfs12 - here you go. This is a zip file, so you'll need to rename it from .txt to .zip. It contains a full color copy in PNG format and the most compressed BMP copy (and the further compressed BIN file) we could make that would actually build into the firmware and be under 256kb.

oozebot.txt

oozeBot

@mfs12 Any update on this? We are demoing a machine next week and would really like to have our logo working.

dc42

@oozebot we are looking at using QOI compression for splash screen images, so that flash memory space will be less of an issue.

GeneRisi

@mfs12 I don't have thumbnail images working on my 5i paneldue the way I expected. DWC shows the 160x160 thumbnail correctly. I thought I would see the thumbnail on the right side of the screen that comes after selecting the file from the list ( where print, simulate and delete are options)

dc42

@generisi said in PanelDue Firmware 3.4.1-pre1 released:

@mfs12 I don't have thumbnail images working on my 5i paneldue the way I expected. DWC shows the 160x160 thumbnail correctly. I thought I would see the thumbnail on the right side of the screen that comes after selecting the file from the list ( where print, simulate and delete are options)

Did you set the thumbnail format to QOI in the slicer?

mfs12

@oozebot which tool are you using to create you splash screen?

mfs12

Hey @oozeBot,

ok, i found a solution for your problem. The image you were using wasn't too large. It just fits the flash. But for future version you will likely run into trouble as there's not much space left.

I assume you are using the windows tool which seems to corrupt the image.

But luckily there's also a go tool which creates proper images. I checked it with your splashscreen image.

Please check the attachment. Rename from txt to zip. And you have a working version of you image and paneldue-3.4.1-pre1 with you custom splashscreen.

oozebot-fix.txt

oozeBot

@mfs12 thanks! Yeah, I was able to whittle that image down to 13-colors @ 8-bit to make it fit, but then it was corrupted. Can you point me to the go version?

GeneRisi

@dc42 I believe that I did... is there a way to check whether it is a valid?TubSeal3.gcode

Thanks!

mfs12

@oozebot said in PanelDue Firmware 3.4.1-pre1 released:

@mfs12 thanks! Yeah, I was able to whittle that image down to 13-colors @ 8-bit to make it fit, but then it was corrupted. Can you point me to the go version?

It's part of the Paneldue Project...

https://github.com/Duet3D/PanelDueFirmware/tree/master/Tools/gobmp2c

There are precompiled binaries for major platforms which should do the job.

mfs12

Hey @GeneRisi,

I checked your gcode file and the header does not look right...

; G-Code generated by Simplify3D(R) Version 4.1.2
;
;
; thumbnail begin 160x160 4280
; /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0aHB
; wgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIyMjIy
; MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCACgAKADASIAAhEBAx

And it should be something like...

; QOI thumbnail begin 64x64 10448
; cW9pZgAAAEAAAABABABVhIj+HBwchIjAGf7h4eEmwCQZNcAZJCbAJBk1wBkkJsAkGTXAGSQmwCQZ
; NcAZJCbAJBk1wBkkJsAkGTXAGSQmwCQZNcAZAiYCh4j+MzMzh4jAvIgCu4jAAh87wB8CF8ACHzvA
; HwIXVYWI/jc3N4aIwLuIAhfAAj0oGS4zCBcCHzvAHwIXwAIfO8AfAhfAAh87wDILAhky/omJiZ2I

Also there were recent changes to Prusaslicer to support QOI so eventually you need to update that software as well.

GeneRisi

@mfs12 DWC decodes the image correctly so maybe it is only the header that is wrong. I am using a post-processing program (after Simplify3d) to add the image.
Thanks!

dc42

@generisi I think the image is probably not in QOI format. The first few bytes of the header are certainly wrong. DWC accepts images in QOI, PNG or JEG format; but PanelDue accepts only QOI.

Edit: the header suggests that your image is in JPEG format.

GeneRisi

@dc42 Thanks for the help. What I have found, so far, is that Prusaslicer does not export QOI thumbnails yet, even if the microcode style is set as RepRapFirmware (I think they are PNG).

I have a small program that adds thumbnails into my Simplify3d gcode; unfortunately they are not QOI files (JPEG makes sense), so at the moment I can't generate QOI thumbnails...