PanelDue Firmware 3.3.0-rc2 released
@DaveA which firmware and hardware versions are you running?
Since version RRF 3.3 you need to put the files into the "firmware" folder. Renaming is also essential as you already did although you can pass the filename to use as a parameter as well. Please check gcode documentation for further details. Double check you didn't misspell the name.
David and me tested different hardware setups and could reliably do updates.
But be careful don't connect the usb connector of your PanelDue this prevents updates!!!
DaveA last edited by
Well I found my issue but I'm not sure how I did it. There was, indeed, a typo in the PanelDueFirmware.bin. Somehow I managed to get a leading space or some unprintable character before the P. I can't reproduce adding a leading space as both RRF and Windows will remove a leading space. I didn't notice it in the DWC but when I looked at the card in Windows the filename was shifted one position right.
Sorry for the false alarm.
@davea , thanks for the feedback.
fotomas last edited by
Since this is a RC2 it is probably not the time asking for new features. But this is more of an adjustment ...
Move the extrusion window a bit lower so the extruder temp can be seen while manually extruding.
Hey @fotomas, can you create a seperate thread for this feature request, please?
oliof last edited by
@davea ctrl-shift-space will insert a "nonbreaking space" character which will be hard to see and mess with your head. Maybe that happened.
OwenD last edited by
I'm note sure if this is related to this release, or if it's only that I have only just noticed.
It seems that if the PanelDue screensaver activates during a long loop, touching the screen doesn't wake it up afterwards, despite popups like M291 working during the macro loop (whilst the screen saver is active).
KipK last edited by
@owend I was about to post the same issue. Happened yesterday, after a filament runout pause, the panel due was locked on screen saver. Couldn't wake it.
So what i understand the process is:
- wait until screen saver is activated
- then trigger a message M291 to display
And you expect that it should wake up in such a case? Did you realize different behavior with previous versions?
BTW i agree it would be definitely handy if the screen gets activated and shows the message to the user.
OwenD last edited by
No, the M291 worked despite the screen saver being active.
The screen saver could not be woken.
I suspect it's more to do with long loops.
@owend sorry. to ask again. but now i am getting a little confused. could you please try to describe a step by step process to reproduce the issue. It would be very helpful.
@OwenD @KipK the issue displaying M291 message while screen saver is active is tracked now at https://github.com/Duet3D/PanelDueFirmware/issues/147
The M291 screensaver bug got fixed. Will be part of 3.3.0-rc3.
@mloidl the times left issue describes is going to be fixed with https://github.com/Duet3D/PanelDueFirmware/issues/152