Thanks for that information:
It’s very interesting to know there is something like this available. I am thinking I will have a try with this Duet feature and see if i can make it work reliably before fitting any switches.
So last ditch attempt have taken the pin out cleaned it put it back and it did its self test several times hooray oh hang on that was short lived.
I am now looking for an alternative to the bl touch thank you for all your help getting me to this point but I must just have the crap one! lol
I don't want to be ploughing the printhead into the bed so its time to move onto something more reliable IR ?
Thanks for posting the screenshot... I see that you get some statistics with Kisslicer. I don't get anything with Cura. I'm wondering whether or not I have a Java issue, or an issue with the version of the Duet2 WiFi Web Interface that i'm running. Do those statistics start when the "Processing gcode file" progress bar goes away? The progress bar doesn't go away for me. It's there throughout the entire print. Could you post a screenshot of your "Software Information" section under Settings > General? Also, which web browser are you using to access the web interface? Thanks!
@beginning-freak said in 15A Fuse burning out:
Resistance is 0,8/0,9 Ohm
Did you subtract the reading you get when you short the two meter leads together? That is often a significant fraction of 1 ohm.
A 15A fuse will take quite a lot more than 15A for a few minutes before it burns out. Therefore, if the fuse is burning out quickly, the bed heater is likely to be drawing more than the 18A limit of the Duet. So you should use an external SSR or mosfet switch for the bed heater. Best is the Auberin DC-DC SSR that I link to he the wiki page about bed heaters.
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.04RC1 (2019-07-14b1)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6
I went ahead and opened another thread on the issue to get more visibility.
@dc42 Yes, I tried to follow https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware.
As for the temperature of the chip and after a while it gets pretty hot (I have no way to measure the temperature)
At 210 the heater just stops going up. It remains stable at that temperature. And the correct temperatures can be controlled manually through console or web without issue.
I have tracked it to the software. I finally tried a completely new program. The g-code it outputs results in the correct set temperature being reached.
I found that and the broken g-code just before I checked back here. I don't know why the software is suddenly malfunctioning. But apparently it is. The temp is set at 210. So the hardware is responding correctly and it's apparently not a configuration setting like I was afraid it was going to be.
;Generated with Cura_SteamEngine 15.01
; Default start code
G28 ; Home extruder
G1 Z15 F100
M107 ; Turn off fan
G90 ; Absolute positioning
M82 ; Extruder in absolute mode
; Activate all used extruder
M104 T0 S210
G92 E0 ; Reset extruder position
; Wait for all used extruders to reach temperature
M109 T0 S210
;Layer count: 298
If you're happy with controlling it through c-code without feedback then: (however I'd rather put the fan under thermostatic control. Maybe explicitly starting it and switching to thermostatic control once chamber temperature has been reached.)
-> heater ON -> Turn fan ON
M106 P2 S255 ;turn on chamber/fan2
M141 S50 ;turn on chamber heater
M149 ;optional wait for chamber temperature
-> Heater OFF -> Let fan ON for a delay then turn OFF
M141 S0 ;turn off chamber heater
G4 S10 ;wait 10 seconds
M106 P2 S0 ;turn off chamber/fan2
you'd also want to consider what happens when things don't go according to plan, and where to place the g-code
Huh, didn't intend to tag Sim234, but seems it does so if you qoute and delete the refrence in the post.
@thejs said in Duet 2 wifi printing at 4mm/s '"PLEASE HELP'":
I added new printer in Cura-Under Machine Settings-GCodeFlavor- I chose RepRapVolumetric out of these options.
That looks like your Cura version is a bit outdated because newer versions (at least the current 4.2) have a clear distinction between RepRap and Marlin. And if you select RepRap(Volumetric) then you also have to enable volumetric extrusion in RRF via M200.
Still this won't solve your heating issues. But as @Veti said check if you have a tool selected. If that still does not help please post the contents of your config.g.
@nr12 said in Support for I2C during Tool Changing:
Hey, thanks for getting back, There was an M107 in the gcode file, which the slicer added and it disabled all the fan ports. one of these fan ports was powering the Arduino.
M107 should only disable the fan assigned as the print cooling fan, which is Fan 0 unless you specify different fans in your M563 tool definition commands.
Looks like your connection to Duet3D was lost, please wait while we try to reconnect.