Evening all! I had a quick search but unless I'm using the wrong key words I don't see anything relating to this - feel free to shoot me down and prove me wrong!

My use case is my various Delta's use a variety of build surfaces and tools depending on the job at hand - for example, I may need to print PLA on a PEI surface, then swap to glass for a PETG job because I need a perfectly flat bottom etc, or Tufnol for nylon etc.

Obviously I need to calibrate when changing tools/surfaces (I only use a G32 auto-cal before each print, and don't use G29 mesh levelling), and generally I need to adjust the IR probe G31 trigger height - especially if I move tools from say a standard 0.4mm to a 1.2mm nozzle.

The only thing I came across which might allow me to define on-the-fly changes of tools/trigger height etc is the Filaments section in DWC - am I on the right lines here in that I could for example place a G31 statement in there which would override the config.g? Also being able to place a custom M665 there might be useful too, but I'm not sure this would override the config.g statements. I am aware that I could write it directly into the gcode, but this isn't always ideal.

I do recall somebody asked something similar recently, but I couldn't find it - perhaps my question was already answered in which case I apologise for my lack of search-fu.

Just for reference, my machines are running 0.85 gen 1 Duets with the 1.26.1 firmware, and the Duet Wifi's are running 2.04.

Just musing here...let me know what I've missed (as I'm sure I have)!

Hi all,

In building up my farm to produce PPE face shields at a more rapid rate, I decided to take my old Kossel XL out of mothballs. The platform is solid and it's printing pretty well straight off the bat, but I wanted to get the thing fully up to date before putting it into production.

The Kossel uses a generation 1 Duet 0.85 and is running a very old firmware, namely 1.09r-dc42, and web interface HTML 1.09, JS 1.09 from 2016!

I've looked around in here and on the Duet site but all I can find if gen 2 instructions, and I've got to admit I got lost trying to follow the different pages.

Does anybody have a link to some clear instructions for updating this old beast? I know there are specific instructions and things to watch out for between versions, and I really don't want to brick a working system...so any advice would be appreciated!

Many thanks

Colin

It's just weird that the output was identical to what I saw. I had been playing with settings, notably M665/M666, G31 and the bed.g coordinates - yours just started happening randomly?

I had the same issue earlier today whilst commissioning a new delta. Turned out for me that after multiple changes in config.g, the existing gcode test model I had on the SD card just plain didn't work. I re-sliced and uploaded a new version of the same model and the problem was fixed.

I hope it's as simple for you, but I'm still interested to know what causes it!

Great! Thanks for the answers, that helps a lot!

Evening all! I had a quick search but unless I'm using the wrong key words I don't see anything relating to this - feel free to shoot me down and prove me wrong!

My use case is my various Delta's use a variety of build surfaces and tools depending on the job at hand - for example, I may need to print PLA on a PEI surface, then swap to glass for a PETG job because I need a perfectly flat bottom etc, or Tufnol for nylon etc.

Obviously I need to calibrate when changing tools/surfaces (I only use a G32 auto-cal before each print, and don't use G29 mesh levelling), and generally I need to adjust the IR probe G31 trigger height - especially if I move tools from say a standard 0.4mm to a 1.2mm nozzle.

The only thing I came across which might allow me to define on-the-fly changes of tools/trigger height etc is the Filaments section in DWC - am I on the right lines here in that I could for example place a G31 statement in there which would override the config.g? Also being able to place a custom M665 there might be useful too, but I'm not sure this would override the config.g statements. I am aware that I could write it directly into the gcode, but this isn't always ideal.

I do recall somebody asked something similar recently, but I couldn't find it - perhaps my question was already answered in which case I apologise for my lack of search-fu.

Just for reference, my machines are running 0.85 gen 1 Duets with the 1.26.1 firmware, and the Duet Wifi's are running 2.04.

Just musing here...let me know what I've missed (as I'm sure I have)!

OK, it was a bit more challenging than I suspected but I have the 0.85 board updated to 1.26.1 & connecting properly to the latest web interface.

I have to say, the documentation could be somewhat clearer in terms of which BIN to use on which board etc - I resorted to guessing in the end and fortunately got it right - even just renaming the file to have something like a '06-85' reference would have helped!

Many thanks for the advice above - much appreciated!

Thanks guys, I'll give it a bash tonight.

Hi all,

In building up my farm to produce PPE face shields at a more rapid rate, I decided to take my old Kossel XL out of mothballs. The platform is solid and it's printing pretty well straight off the bat, but I wanted to get the thing fully up to date before putting it into production.

The Kossel uses a generation 1 Duet 0.85 and is running a very old firmware, namely 1.09r-dc42, and web interface HTML 1.09, JS 1.09 from 2016!

I've looked around in here and on the Duet site but all I can find if gen 2 instructions, and I've got to admit I got lost trying to follow the different pages.

Does anybody have a link to some clear instructions for updating this old beast? I know there are specific instructions and things to watch out for between versions, and I really don't want to brick a working system...so any advice would be appreciated!

Many thanks

Colin

@Phaedrux said in Dead board?:

https://duet3d.dozuki.com/Wiki/Connector_and_spare_part_numbers#Section_Heater_MOSFETs

Excellent resource, many thanks!

@dc42 said in Dead board?:

@SlimShader said in Dead board?:

OK, I just replaced the 7.5A fuse and the board is alive again. However...the hot end heater (E0) is now constantly on as soon as I power the board.

My guess is that the hot end heater wiring was shorted, taking out the fuse and the mosfet. That's the only explanation I can think of for both the mosfet and the fuse blowing.

for sure David, I completely agree - my suspicion is that a wire on the hot end heater connector at the Duet end had a stray strand of wire from the ferrule which caused a short. Those connectors aren't really beefy enough for larger gauge wires - as I'm using an 80w SuperVolcano, I extended using a (16 AWG) wire. I've since done an extension using some spare cable from an old hot end heater into an inline connector which allowed me to place the cables and tape them down to the board once I was sure it was all good. Should have done that in the first place!

After replacing the 7.5A fuse and moving to the other heater channel it seems to be working again, however I need two heater channels - can you let me know the part number for the MOSFET I need to replace, and it's placement on the board? I can see two near the heater channels - I guess it's one of those, but I don't want to pull them off to test which one it is until I have replacements to hand!

OK, I just replaced the 7.5A fuse and the board is alive again. However...the hot end heater (E0) is now constantly on as soon as I power the board.