PanelDueFirmware 3.2-RC3 released
-
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?
-
@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.
-
I would like to se a setting for baby steps - step in paneldue
-
Current babystepping amount is present in the OM already, it's in move.axes[n].babystep.
-
@dc42 I think the request is rather about the amount to be applied when pressing the babystep buttons.
-
Ah, I misunderstood.
-
@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?
-
@wilriker that would certainly cover it for us! However, long term, I'd still suggest syncing this with DWC through the Object Model.
Thanks!
-
@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.
-
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
-
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?
-
@docbobo I would say M300 is processed by the board, not the panel. If Your board has no "beeper" then no sound
-
@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.
-
@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. -
@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.
-
@docbobo I am not sure, but isn't the board responsible for sending this M300 to panel to make it beeping?
-
@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.
-
@wilriker no, itβs not waking up the panel. It was mostly black, just the numbers for x, y, and z were appearing.
-
@docbobo - I've seen this as well..
@wilriker - I've had the PanelDue not display an M291 S3 command like I described earlier several times today. There is no pattern to it that I've been able to find. However, I can say with certainty that it is still occurring.
Like I mentioned before, it's within my homez.g file as interaction is expected when beginning a print.
Thanks
-
@docbobo Thanks for reporting. I'll investigate that.