Firmware 2.0RC2b/1.21.1 RC2b released
-
@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. -
David, is this a 2.0 behavior change or a 1.21.1 rc4 issue?
-
There is no intended behaviour change from earlier firmwares in this respect.
-
Then I'm surprised it isn't working as I set it, as I've not changed any motor currents etc. so I would still expect to see\feel that the fan is working, but patently it isn't.
-
What motor currents are you using?
-
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 E1200 ; Set maximum speeds (mm/min)
M201 X500 Y500 Z250 E250 ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E1100 I50 ; Set motor currents (mA) and motor idle factor in per cent
M84 S90 ; Set idle timeout -
At 1A the stepper drivers won't get hot enough to trigger the thermal warning. See my earlier reply.
-
I unstand what you are saying, so unless I drive the motors above their normal operating currents, then the fan will never come on.
But according to the datasheet (https://www.trinamic.com/fileadmin/assets/Products/ICs_Documents/TMC2660_datasheet.pdf) section 11.3, a flag is set when the chip reaches 100 degrees (OTPW), is this not trapped, so that external cooling can be applied ??
Granted this is not optimal, but as there is no local temperature probe, its all that's available to monitor the temperature of the Duet board, and effect some forced cooling.