Firmware 2.0RC2b/1.21.1 RC2b released
-
FWIW after upgrading I also experienced the heater fault issue; 4 times on an 8 hr print. Probably just bad luck with a loose connector, as after a reset and restore the print started right back up, and I didn't have the heater calibrated either, and I had seen this happen long ago too. Simulation worked fine with the updated PanelDue and it would be amazing to see the simulation done as a parallel thread to calculate upon print start. Originally had an issue with losing the web interface, but copying over a new web directory solved that.
Saw a small improvement in WiFi transfer; now close to 500 KB/s, up from about 400 KB/s.
Good work!
-
So far the new firmware and DWC work great. Love the ability to upload files while homing the printer.
A good test will come tonight, Ditto printing (IDEX) on a 8 hour print run.
-
I've been using this since it was released and have not noticed any issues yet.
-
Last night While printing a long running part, I uploaded a 17mb file at speeds of 700KB/s with no issues.
Well done David!
-
I installed RC3 (or RC2b) and printed a couple of small things (~2 hours prints each) without any problems.
The baby stepping command seems to be responding a bit faster than before -
Hi,
I am using RTOS version and generally no problem. Today i add relay unit for controlling 24V line (M80 and M81).
It is work but when i first start the printer 7" Panel due still connection state, if i send M80 from DWC then paneldue's state change to idle. After that paneldue can send M80 and M81 without any problem.Is this firmware problem or i made any mistake?
Thanks, -
Did a run on WorkBee with 2.0RC2b and the part was identical to the one machined with 1.21.
-
@cgcafer said in Firmware 2.0RC2b/1.21.1 RC2b released:
Hi,
I am using RTOS version and generally no problem. Today i add relay unit for controlling 24V line (M80 and M81).
It is work but when i first start the printer 7" Panel due still connection state, if i send M80 from DWC then paneldue's state change to idle. After that paneldue can send M80 and M81 without any problem.Is this firmware problem or i made any mistake?
Thanks,The PanelDue firmware needs to be updated to support the new Off status returned by the firmware when VIN power is not present.
-
Hi,
Thank you for your answer, tomorrow morning i will check it. Which version it should be? -
The version that hasn't been released yet!
-
@danal said in Firmware 2.0RC2b/1.21.1 RC2b released:
Loaded:
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet Firmware Electronics: Duet WiFi 1.02 or later Firmware Version: 2.0(RTOS)RC2b (2018-05-13b3) WiFi Server Version: 1.21 Web Interface Version: 1.21.1-RC4
Have now printed long-ish (couple of hours) and very short (10 minute) prints with no detectable issues. This is on the large-ish custom delta (600x600x600) at 24V with separate mains heatbed.
-
Thanks to all of you who have provide feedback on RC2B. I'm looking to fix a few old bugs before the 2.0 release, so there will probably be a RC3 next week.
-
I've now had a chance to swap Heater 1 for Heater 2, which has appeared to have fixed my issue with heater crashing & failing print, but it does mean the a board I bought in early January has problems (when I got the board, there were unsoldered joints !!).
One issues I have with this is that the Web interface works as expected, but the PanelDue still shows a "phantom" heater H1, with Current\Active\Standby boxes as well as the re-mapped heater as expected.
-
@dr_ju_ju said in Firmware 2.0RC2b/1.21.1 RC2b released:
I've now had a chance to swap Heater 1 for Heater 2, which has appeared to have fixed my issue with heater crashing & failing print, but it does mean the a board I bought in early January has problems (when I got the board, there were unsoldered joints !!).
If you believe your Duet was delivered and still is faulty, please ask for it to be replaced under warranty.
-
This post is deleted! -
@dc42 I've flipped it back to H1, & started a long'ish print, just to confirm that it still fails. If it does, I'll request a replacement, but at least it looks like the wiring & cartridge etc. are all ok
-
I "may" have found my issue, as although I have an 80mm fan mounted under the duet board, and its enabled with:
M106 P2 S0.5 T55 H100:101:102 ; Set fan 2 (Duet Board) to come on half power if any driver chip reaches 55 degrees
it has not been coming on with this firmware ?? and some of the ic's including the heater power mosfet have been getting very hot to the touch.It used to work fine with the release firmware, but I don't know if anything has changed ??
As I'm in the middle of a long print, for a stop-gap I've carefully sat a 40mm fan on top of the wiring from the drivers, driven from one of the "always on fans", which is keeping everything cool.
I'll investigate further when the print completes (hopefully).
-
I upgraded to the latest firmwareand dwc and all has gone perfectly except for fan sliders. Using chrome, always say all my fans in the web interface. Now only Tool Fan shows. I read somewhere about a similar problem but can’t find it now. This same phenomenon occurs on both my printers and with a mac and a windows pc.
-
Is there a post somewhere explaining the virtues of an RTOS-based firmware? For developer and end-user alike?
-
@dr_ju_ju said in Firmware 2.0RC2b/1.21.1 RC2b released:
I "may" have found my issue, as although I have an 80mm fan mounted under the duet board, and its enabled with:
M106 P2 S0.5 T55 H100:101:102 ; Set fan 2 (Duet Board) to come on half power if any driver chip reaches 55 degrees
it has not been coming on with this firmware ?? and some of the ic's including the heater power mosfet have been getting very hot to the touch.It used to work fine with the release firmware, but I don't know if anything has changed ??
As I'm in the middle of a long print, for a stop-gap I've carefully sat a 40mm fan on top of the wiring from the drivers, driven from one of the "always on fans", which is keeping everything cool.
I'll investigate further when the print completes (hopefully).
The drivers don't actually report their temperatures, they report an over temperature warning if they exceed a threshold that is in the region of
120C100C. In bench testing this happened quite quickly with 3 driver's running at 2.4A if idle current reduction was not allowed to take place and there was no fan cooling, but not at all if the current was reduced to 2.0A.