PanelDueFirmware 3.2-RC3 released

wilriker

I am pleased to announce the third release candidate for PanelDueFirmware 3.2. This release contains primarily bug fixes and a few small changes in behavior. See below for details.

Version 3.2-RC3

Upgrade Notes and Limitations

See 3.2-RC2

Changes since RC2

Extrusion and retraction commands are now a single line to prevent being interleaved by other commands
Screensaver is now a popup to better interact with existing or incoming popups
No longer fetch detailed M409 for Fans or Sensors (as they are currently not required)

Bug Fixes since RC2:

Screensaver timeout select pop-up would not disappear when clicking anything but "Set" or a tab button
Extrusion factor was not always targeting the correct extruder
Extrusion factor controls were not hidden if amount of tools was decreased
Bed and chamber controls were not hidden if they were removed from config
If a JSON key path was too long it would result in an endless fetch-loop

Downloads and Instructions

Binaries can be found at https://github.com/Duet3D/PanelDueFirmware/releases/tag/3.2-RC3
Flashing instructions can be found at https://duet3d.dozuki.com/Wiki/PanelDue_Firmware_update

wilriker

I just released 3.2-RC3+1 with one additional bugfix. I expect this to be the last release candidate before releasing 3.2 final.

Version 3.2-RC3+1

Bug fixes:

Message box was not closed on PanelDue if closed e.g. in DWC

Downloads and Instructions

Binaries can be found at https://github.com/Duet3D/PanelDueFirmware/releases/tag/3.2-RC3%2B1
Flashing instructions can be found at https://duet3d.dozuki.com/Wiki/PanelDue_Firmware_update

oozeBot

Thanks. We'll update all our panels this morning and report back with any issues.

@wilriker - one item I'd like to ask, with the introduction of the Object Model, could Baby Steps be modified to mirror what's set in DWC instead of being fixed at .02mm?

wilriker

@oozeBot said in PanelDueFirmware 3.2-RC3 released:

@wilriker - one item I'd like to ask, with the introduction of the Object Model, could Baby Steps be modified to mirror what's set in DWC instead of being fixed at .02mm?

Baby step amount in DWC is a DWC-local setting that RRF does know nothing about. Therefore unfortunately this cannot be mirrored to PanelDue.

BoA

I would like to se a setting for baby steps - step in paneldue

dc42

Current babystepping amount is present in the OM already, it's in move.axes[n].babystep.

wilriker

@dc42 I think the request is rather about the amount to be applied when pressing the babystep buttons.

dc42

Ah, I misunderstood.

wilriker

@BoA said in PanelDueFirmware 3.2-RC3 released:

I would like to se a setting for baby steps - step in paneldue

This can be added quite easily. Though, I would like to fix this to 4-6 preset values because user-input is always quite tricky.

How about:

0.01
0.02
0.05
0.1

Something smaller? Something larger? Something completely different?

oozeBot

@wilriker that would certainly cover it for us! However, long term, I'd still suggest syncing this with DWC through the Object Model.

Thanks!

wilriker

@oozeBot said in PanelDueFirmware 3.2-RC3 released:

However, long term, I'd still suggest syncing this with DWC through the Object Model.

Once user variables have been implemented in RRF this would be very easy.

oozeBot

I wanted to report back that I'm seeing an M291 S3 popup on the PanelDue fail to display randomly..

I'll be doing more testing today and through the weekend, so maybe I can put my finger on the exact scenario which is causing it.

To quickly describe where I've seen it happen, it's at the beginning of a job when homing - I have an M291 S3 command in my homez.g file. It's here that sometimes the popup is never displayed on the PanelDue.

Thanks

docbobo

I just set up my 5i with an BTT SKR 1.4 Turbo using 3.2-RC3 together with all the other betas (DWC, DSF, FW).

At least for me, M300 doesn't result in any sound coming out of the PanelDue, even though it does beep when I am pressing some of the buttons.

Am I missing anything there?

BoA

@docbobo I would say M300 is processed by the board, not the panel. If Your board has no "beeper" then no sound

docbobo

@BoA Well, the documentation seems to say

Play beep sound, use to notify events like the end of printing. If an LCD device is attached to RepRapFirmware, a sound is played via the add-on touch screen control panel. Else the web interface will play a beep sound.

wilriker

@docbobo Yes, M300 are supposed to be played by PanelDue. I have to investigate the problem because it worked when I tested a while back.

docbobo

@wilriker Let me know if there's anything I can do.

BTW, when running mesh compensation, I noticed that coordinates for X Y Z were updating the screen, even though it was in sleep mode. Doesn't seem to happen while printing.

BoA

@docbobo I am not sure, but isn't the board responsible for sending this M300 to panel to make it beeping?

wilriker

@docbobo said in PanelDueFirmware 3.2-RC3 released:

@wilriker Let me know if there's anything I can do.

Will let you know if that's necessary, thanks.

BTW, when running mesh compensation, I noticed that coordinates for X Y Z were updating the screen, even though it was in sleep mode. Doesn't seem to happen while printing.

I am not exactly sure if I understand what you mean. Du you mean it's waking up the panel from screensaver when running mesh compensation?

If so, here's the small list of what will wait up the panel from screensaver:

Incoming message pop-up
Machine state changed e.g. Idle to Busy or Printing to Paused, etc.

docbobo

@wilriker no, it’s not waking up the panel. It was mostly black, just the numbers for x, y, and z were appearing.