Firmware 2.0RC2b/1.21.1 RC2b released
-
@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).
Julian,
Old goat, learning new things….
-
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.
Julian,
Old goat, learning new things….
-
@dr_ju_ju : the board does a such a good job dissipating the heat of the drivers that 1A is not enough to overheat the drivers, hence it won't trip the flag...
-
Just lower the temperature threshold or have the fan be connected to an "always on" connection. Case closed. Next subject.
-
-
@dr_ju_ju said in Firmware 2.0RC2b/1.21.1 RC2b released:
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.
Yes that's the over temperature warning flag that we monitor as I described in my earlier reply. You need more than 2A motor current to set it off.
-
So far Idex is working well. Here is a short video and picture using ditto printing of 2 sets of parts.
-
When i level my bed before a print i’m Getting the following message, “Number of calibration factors (0) not equal to number of lead screws (4)”
These are the probes that I’m doing. this worked on 1.19 so I’m not sure what’s up with this.
G30 P0 X30 Y280 Z-999 ; probe near back left lead screw
G30 P1 X390 Y280 Z-999
G30 P2 X390 Y25 Z-999
G30 P3 X30 Y25 Z-999 S4 ; probe near a leadscrew and calibrate 4 motors -
Anyone have any ideas on the leveling issue?
-
The Z value in your G30 commands should be -9999 or -99999, not -999.
