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

I had issues with one of these, and it turned out my belt was too heavily tensioned. These motors have very long shafts, so require support at the end if you are going to tension them to more than a loose fit. I got around it by redesigning the mounts to include an enclosed 608 bearing which the end of the motor shaft slides into - since doing that no issues with grinding or over heating. Hope this helps!

HI all,

I have a new custom Delta build which has some skew apparent in the prints. If I print a cube and measure the surfaces in relation to each other, there is some skew apparent - up to around 1mm across a 300mm cube.

I know the correct approach is to rebuild - and I will be. My issue is the skew in the frame is caused by the printed corners which in total will be 5 full days of printing on my i3Mk3s, and cost me four rolls of filament, so I'm not eager to do this immediately. The original printed parts were printed on another machine, and it's inaccuracies have translated into these parts. I do know that the MK3s is very square and accurate though, so I can likely fix the issue using it.

So, I was wondering if I can do a quick and dirty fix in the firmware, and I've been looking at M556. I've never played with it before, and it looks like it's largely designed for Cartesian machines, rather than Deltas - although I see that it does have an effect in the brief testing I've done on the Delta.

Before I jump down the rabbit hole though, I wanted to ask about the expected use cases for M556, what it's limitations are and also if there are additional features not mentioned on the GCODE Wiki.
Also, of course, is there a 'better' way to correct axis skew within the firmware on a Delta that anybody knows about?

Currently, my setup is:
Board: Duet WiFi 1.02 or later (duetwifi102)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.03 (2019-
06-13b2)
Duet WiFi Server Version: 1.23

Thanks in advance if anybody has an advice!

Thanks all for the comments! I already built rods with Traxxis ends for now, but as I'm planning multiple tools for this printer I want to move to a magnetic system.

I'll reach out to Haydn about buying the balls for the effector and hopefully Delrin rod ends suitable for 8mm rods.

Hi all,

I'm looking to get a set of mag balls and rod ends for a smart effector based delta - as it's a large format I've already got the carbon fibre ready (rods will measure 515mm center to center) so just need the magnetic parts. Is there any UK stocks of these anywhere or should I shout out to Haydn?

Thanks in advance

Colin

I had issues with one of these, and it turned out my belt was too heavily tensioned. These motors have very long shafts, so require support at the end if you are going to tension them to more than a loose fit. I got around it by redesigning the mounts to include an enclosed 608 bearing which the end of the motor shaft slides into - since doing that no issues with grinding or over heating. Hope this helps!

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.