PanelDueFirmware 3.2-RC1 released
-
@wilriker when the tool is in standby, click it again and it goes to off
-
@jay_s_uk On heater - heater will go to off, but clicking on tool switches between stby and active
-
@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.
-
@BoA oh yea, i forget you can click both. ignore my previous comment
-
@wilriker And one small thing - When setting screensaver timeout I can not "unclick" the button to close selection like with i.e. Info Timeout
-
@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.Manuel
Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
with probably always latest firmware/DWC (incl. betas or self-compiled)
My Tool Collection -
@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.
-
@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?
Manuel
Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
with probably always latest firmware/DWC (incl. betas or self-compiled)
My Tool Collection -
@wilriker Works like a charm
-
@BoA Thanks for confirming.
Manuel
Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
with probably always latest firmware/DWC (incl. betas or self-compiled)
My Tool Collection -
@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. -
@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.
-
@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.
-
@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.
-
@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...
-
@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.
-
@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....
-
I am getting popcorn
This is getting ridiculous.It is so hard to understand, that older hardware is not capable of handling new features?
-
@CaLviNx said in PanelDueFirmware 3.2-RC1 released:
Ah so Duet is using the Apple business model of planned obsolescence
I hope so!
This typed on a MacBook Pro Retina, 15-inch, Late 2013, running Mac OS X 10.14 Mojave perfectly, and expecting quite a few more years out of it, even though OS X 10.15 Catalina is the last version of OS X that will support it. I've also got an iPad 3 from 2012, on iOS 9.3.6, that still works pretty well for web browsing and streaming TV, and the iPhones I've had have generally served me well for 3 to 4 years, far longer than anyone I know has kept an Android phone. Sure, I paid more up front, but long term? To me, Apple's perceived planned obsolescence is BS. I don't know anyone with even a high-end laptop from 2013 that runs Windows 10 nicely (though my MacBook Pro does).
But then let's not start a Mac vs PC flame war.
Ian
-
I agree, it's getting very tedious.
First, I should point out that until late last year, PanelDue was a product of my own company, which pre-dates Duet3D. So any blame for lack of foresight falls on me, not on Duet3D.
I designed PanelDue in 2014, as an accessory for the RepRapPro Ormerod 3D printer. My original design used an 8-bit processor, but after I realised the limitations of that processor I switched to the 32-bit ATSAM3S2BA. This was when very few 3D printer control boards (let alone 3D printer accessories) used 32-bit processors.
By December 2015 I had some OEM requests for customised splash screens, and I realised that a processor with more memory might be needed. So I had some PanelDue made with the ATSAM3S4B processor.
This all happened before the Duet WiFi was launched in 2016. From August 2016 (around the time of the Duet WiFi launch), I switched all production of PanelDue boards to use the larger processor, despite the negative impact on profitability. So all PanelDue boards with the smaller processor are more than 4 years old and their manufacture pre-dates bulk shipping of the Duet WiFi.
I guess my crystal ball failed, because back in 2014 I didn't know that we would develop the Duet WiFi, or how successful it would become, or how in 2020 RepRapFirmware would provide so much additional data available to user interfaces via its object model that we would need more memory to make use of it. But I did have the foresight even before Duet WiFi was launched to switch to a larger processor, which more than 4 years later has turned out to be sufficient to support the new features in PanelDueFirmware 3.2. I upgraded the processor further in PanelDue v3.
Those who bought a PanelDue 4+ years ago with the smaller processor can continue to use it, with exactly the same functionality as now (somewhat more than when they bought it), by continuing to use version 1.24 firmware. Those who have continued to develop their 3D printers and would like the new functionality can choose to replace the PanelDue control board (keeping the LCD), or replace the processor if they feel able, or hack the open source firmware to remove features they do not want in order to make the firmware fit.
I had none of those options with equipment I purchased that cost many times more than a PanelDue:
- The only time I took an iPhone as part of a mobile phone contract, it became unusably slow because of a forced firmware update after just 18 months, 6 months before the contract ended
- The Humax PVR I bought had a bug which forced me change my password to a much less secure one. They announced that they would not fix that bug - in fact, they have never issued any firmware updates for that PVR. Their attitude seems to be ship and forget.
So please tell me, is Duet3D really being unreasonable in producing new firmware that doesn't run on a $40 piece of hardware more than 4 years old, while RepRapFirmware continues to support the older hardware/firmware combination?
