-
but only with 3d printed instruments
I've printed an American Native flute and I also have made a Didgeridoo with my own mouthpiece, so...
Challenge acceptedThe main advantages are more flexible pin allocation, and conditions and loops in GCode.
I remember we've discussed the benefit of conditions back in RepRap-forum, but I don't remember, what I wanted to do with it.
In general, for a single nozzle 3D printer, there's no need to update?
I have another DuetWiFi and a Maestro in spare, so I could give it a try. -
6 factor still being the most appropriate?
the "best" is the one you get the best results with.
what the factors calibration do has not been change from 2 to 3.
see what they do herehttps://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer#Section_Setting_up_the_bed_g_file
-
-
we should start a music channel in here to compare lockdown, non, 3d projects!@o_lampe
That sounds like a pi$$ing contest, nooo I pass
(and I would win hands down, no doubt)
-
@Veti true, I tended to use 6 until I got a stable calibration then reduced for actual printing.
I
With RRF3 is it possible to create something that will do the probing for the bed.g probe trigger heights and automatically populate the file or is it still a manual process? that was the biggest PITA that I had, and with the printer sitting so long I will need to basically start from scratch to calibrate.I couldn't see anything obvious other then this still being referenced in the Delta Calibration steps. I didn't go through the full differences to RRF3, and what the conditional processes can do, just looked the process for migration, so apologies if this is a question answered in the dozuki.
-
@o_lampe mine was just lutherie type stuff, woodwork, painting, electrics, so if you we get to 3d instruments, you've already won.
-
With RRF3 is it possible to create something that will do the probing for the bed.g probe trigger heights and automatically populate the file or is it still a manual process?
the configurator will generate a bed.g for you
https://configtool.reprapfirmware.org/Start -
@Veti yes, it's just that previously to determine the trigger heights ( 3 underbed sensors for hot end probing) it felt like it took an age to probe, get the results, put them through a spreadsheet to get the differential to origin, then input into the bed.g file for the probe points. I had created a file to probe all of the calibration points 5(?) times to then average the trigger height in a spreadsheet which I then put in to bed.g manually.
When I was looking before at the conditional g-code I remember some talk of being able to use <average> but cant find anything in the forum, Probably not using the correct search terms.
I think the configurator is a great tool, but I havent been in to it for a long time. I'll have a look to see what has changed,
-
@Dugee
yup, I gave up dealing with underbed (piezo) sensors.
On my XXL-Delta I have Davids smart effector which gave me the best results so far. -
-
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@o_lampe I looked at that, with the amount of work involved in putting a smart effector into my machine it isnt worth it.
It's only a Mini, and one of the reasons for getting the machine back out is to print the pieces for a D bot, as I think that will be more useful for what I want to print.
I can just print everything I need on the mini, it's tight but it just makes it.
-
@jay_s_uk I saw that one, but it doesn't automate the trigger heights, but the calibration process.
I did see a thread that included automating the trigger heights,
https://forum.duet3d.com/topic/14280/invitation-to-share-your-conditional-gcode-scripts
but havent yet found any follow up.
I also found this one, which I'll have to read through first!
https://forum.duet3d.com/topic/17872/automatic-bed-leveling-with-conditional-gcode-iterations/40
