PanelDueFirmware 3.2-RC1 released

BoA

@wilriker After. I can cycle through all 3 state from DWC. From panel only active<->stby, but from DWC all 3.
Just testem with new FW and it works for heatbed. Buttons go gray when heatbed put to off state.

wilriker

@BoA Starting to feel a bit stupid here but how do you get the tool to go back into the off state via DWC?

Also for bed and chamber heaters that's something different because these are heaters. Tools have a state separate from their heater's state.

BoA

@wilriker OK. Nevermind. All You wrote is true. Tool does no goes back to off. only heater does.

jay_s_uk

@wilriker when the tool is in standby, click it again and it goes to off

BoA

@jay_s_uk On heater - heater will go to off, but clicking on tool switches between stby and active

BoA

@wilriker This is perhaps small issue with RRF not paneldue, but putting M116 P0 in tpost0.g seems to block refreshing tool status (and temperature refreshing) until temperature is reached.

jay_s_uk

@BoA oh yea, i forget you can click both. ignore my previous comment

BoA

@wilriker And one small thing - When setting screensaver timeout I can not "unclick" the button to close selection like with i.e. Info Timeout

wilriker

@BoA said in PanelDueFirmware 3.2-RC1 released:

@wilriker This is perhaps small issue with RRF not paneldue, but putting M116 P0 in tpost0.g seems to block refreshing tool status (and temperature refreshing) until temperature is reached.

I tried but I cannot reproduce this. Will have to look some more into that.

@BoA said in PanelDueFirmware 3.2-RC1 released:

@wilriker And one small thing - When setting screensaver timeout I can not "unclick" the button to close selection like with i.e. Info Timeout

That's basically for all of the selection. Click on "Setup" on the bottom right to close it.
EDIT: I put it on the list for the next release to auto-close it.

BoA

@wilriker My scenario details:

tool is off/stby
set active temperature like 200*C
put tool to active to start heating

Then refreshing stops until temp is reached.

wilriker

@BoA Thanks for being so precise that always helps!
I will most likely only get back to it next week, though.

Did the new build fix the other reported issues?

BoA

@wilriker Works like a charm

wilriker

@BoA Thanks for confirming.

BoA

@wilriker Well... I do not how to say this... Moving head from panel does nothing tool active or not - does not matter. All axes homed.

dc42

@BoA said in PanelDueFirmware 3.2-RC1 released:

@wilriker This is perhaps small issue with RRF not paneldue, but putting M116 P0 in tpost0.g seems to block refreshing tool status (and temperature refreshing) until temperature is reached.

That's an issue we already know about. It will require a change to RRF.

A Former User

@dc42 said in PanelDueFirmware 3.2-RC1 released:

Those of you with older version 1 and version 2 PanelDues, please note that we do not expect this release to work on old PanelDue boards that use the ATSAM3S2B chip, due to lack of RAM. However, we do expect it to work on later version 2 PanelDues using the ATSAM3S4B chip. If you have a PanelDue using the ATSAM3S2B chip, we suggest you replace the board by a version 3 PanelDue board, which can drive your existing LCD.

I really hope this is a joke and not real?

In which reality did any sane person think that such a firmware "upgrade" which is going to require certain users of already purchased equipment to make a further purchase a good idea.

I can understand that control board hardware evolves by a large degree but the display hardware...

Users of older display equipment are left with two choices: buy an upgrade to said hardware or continue to use older firmware.

I'm almost speechless with disbelief.

Phaedrux

@CaLviNx said in PanelDueFirmware 3.2-RC1 released:

Users of older display equipment are left with two choices: buy an upgrade to said hardware or continue to use older firmware.

What is the alternative? Halt development of paneldue features entirely? Do you still use your old 486 from 92 or did you upgrade that as well?

@CaLviNx said in PanelDueFirmware 3.2-RC1 released:

I'm almost speechless with disbelief.

Almost, but not quite.

elmoret

@CaLviNx said in PanelDueFirmware 3.2-RC1 released:

I'm almost speechless with disbelief.

How is this unlike literally any other software/hardware situation?

You cannot run iOS 14 on a iPhone 3.

You cannot run Windows 10 on a 286.

You cannot flash the firmware of a 4k HDTV onto a 720p HDTV.

Etc...

wilriker

@BoA said in PanelDueFirmware 3.2-RC1 released:

@wilriker Well... I do not how to say this... Moving head from panel does nothing tool active or not - does not matter. All axes homed.

I have a slight idea what the reason could be although the code looks good. Will need to test and verify later.

Again thanks for reporting.

A Former User

@elmoret said in PanelDueFirmware 3.2-RC1 released:

@CaLviNx said in PanelDueFirmware 3.2-RC1 released:

I'm almost speechless with disbelief.

How is this unlike literally any other software/hardware situation?

You cannot run iOS on a iPhone 3.

You cannot run Windows 10 on a 286.

You cannot flash the firmware of a 4k HDTV onto a 720p HDTV.

Etc...

Ah so Duet is using the Apple business model of planned obsolescence to generate sales, thanks for the clarification....