EDIT:
I have Firmware Version 1.17 on my PanelDue and will Upgrade to the latest. The macros are only supported from 1.20 in.

Sorry for the late response.

I tested the code and it works absolutley flawless!

Thank you for your help!

up!

I really want this feature - or a workaround - as well

I do not think your ideas help. I tested them but they did not improve anything...

but I found the mistake!

You know....in programming you are often start counting with 0....not with 1. So my x Stepper is not P0.1 but P0.0....

Oh my gosh...works now.

MacNite 12 Mar 2021, 11:59
Maybe some of you have seen my post of trying to built a calibration routine for the CR3D Idex machines.

https://forum.duet3d.com/topic/21803/calibration-routine-for-dual-extruder-printers

This thread did not get much tracktion...probably due to the kind of complex nature of such a routine. So I'll try to break down the problem into smaller chunks.

The "newest" problem is the user-interaction.
After completing the z-calibration the user should be asked, if he is satisfied with the results. Otherwise it should be repeated.

	; start z-calibration routine
while z_satisfied = false
    M291 P"Put a piece of Paper on the built plate" R"Calibration of z-Position" S2
    T1
    M291 P"Move the Bed up using the buttons until the paper slightly graps on the nozzle" R"Calibration of z-Position- Tool 1" S3 X0 Y0 Z1
    G10 P1 Z{-axes[3].position}		; set z-offset of Tool1 to value from last calibration
    M500 P10                        ; safe Tool1 offset
    G1 Z5
    T2
    M291 P"Move the Bed up using the buttons until the paper slightly graps on the nozzle" R"Calibration of z-Position- Tool 2" S3 X0 Y0 Z1
    G10 P2 Z{-axes[3].position}		; set z-offset of Tool2 to value from last calibration
    M500 P10                        ; safe Tool2 offset
    G1 Z5
    M291 P"Remove Piece of Paper" R"Calibration of z-Position" S2

	; start test print for z-calibration
    ;M98 P"z_test_print.g"				; Print z-calibration lines

	; ask user if he is satisfied
	M291 P"Are you satisfied with the z-calibration results or should this step be repeated" R"Calibration of z-Position" S2
	; If M291_input = yes
    ;    z_satisfied = true
    ;else
    ;    z_satisfied = false

Is it possible to get a "feedback" and or yes/no-buttons with M291 or is there any other way of "user-interaction"?

Greets
Max

Hey guys,

at the moment I am working on a dual extruder tool together with @CR3D . The first prototype of the tool is working right now - the tool is comparable to a Startasys or Ultimaker 3 Nozzle-Lifting assembly but the actuation is done by a servo. At the moment I am stresstesting and performing little improvements.

I want to use / built a firmware-integrated nozzle-offset-routine for both hotends - in this I want to calibrate the x, y and z offset of both nozzles.
To calibrate the offset of both nozzles I want to use a routine similar to the one by BCN3D and Craftbot.
At first I want to move the nozzle - close to the bed using a PanelDue and/or webInterface.
After that is done for both tools a simple z-offset test print (i.e. 20x20mm 1-layer square) shall be printed.
Afterwards the user shall be promted if the z offset is ok. If yes: the routine continous. If no: the routine goes back to z-offset adjustment.

The same is done for x-y-offest - just with using "line" extursions like the ones on the picutre:

I tried to built a flow chart of the things I want to do:

Writing the gcode and doing basic configuration is not a problem for me.
My main questions are:

1. How can I safe the new Offsets to the config.override?
2. How can I create "buttons/popups" in DWC and PanelDue as an "interface" for the calibration routine"
3. Is this even possible within RRF3.x or is something similare integrated?

Have a nice day,
Max

Thanks for your response!

For the time beeing I'll try some drivers I have laying around (without SPI) to just test it....maybe later on I'll return to the SPI-question. Mostly because I don't know how to compile duet firmware on my own and have to read that up

Have a nice day,
Max

@t3p3tony

Refering to the documentation that will not work with the Duet 6HC.

Greets
Max

Hey Guys,

Is there any way to add an external USB Slot or SD Card Slot for GCODE Transfer to the DUET 6 HC.

Thanks for your Help,

Greets
Max

@phaedrux yes. That is a possibility as well. But I think that would be to much effort / hardware just to get an Interface and USB-Connectivity.

Greets
Max

@t3p3tony

Refering to the documentation that will not work with the Duet 6HC.

Greets
Max

Hey guys,

at the moment I am using a PanelDue 7i on my Voron Trident in combination with a Duet 6 HC. Is there any way to make the SD-Card Slot working or add an USB-Stick for file transfer?

Thank you for your help!
Max

@o_lampe yes - thank you for the hint! That's actually what I plant to do: using prusa-slicer / super-slicer for this instead of "firmware-presets".

I reach out to @pfn and ask for his/her progress.

Hey guys,

at the moment I am building a Voron Trident (I think my 4th or 5th Voron printer). When everything is set up I want to install the Enraged Rabbit Mod.

It's a Filament-Changer / Swapper similar to the Prusa MMU or SMuFF.

Is there anyone who already integrated a system like that into the firmware? The mechanics / base setup (2 steppers, 1 servo, filament sensor) are quite simple to get working in RRF3 (I plan to use a Duet 6 HC with a Duet 3HC expanison board for this).
The standard change precdure for filaments is quite easy too using macros and the t#post, t#pre etc. parts of the Firmware.

In the last days I thought about possiblilitys I don't quite yet have solution for:
(1) The Enraged Rabbit Mod uses 2 Filament Sensors - 1 at the "filament changer" 1 at the tool head. I think these could be set up as external triggers with some macros and should work - I also could use the extrnal triggers for the filament change.
(2) Automatic continous printing: If one spool of the filament changer is empty (recognised by filament sensor) swap to the next spool. I think this could be implemented in some way with global variables...but I really do not know how to use them - is there any "good" example? I find the Documentation of GCODE-Meta-Commands is quite lacking in this regard (at least for people with limited programming skils).

Maybe you could provide some input on this!
Thanks
Max

@phaedrux

Yes , of course. But after further Investigation I think I miss-read that....the M140 H1:H2 only seems to bei a suggested solution, Not an implemented one in the Firmware yet.

https://forum.duet3d.com/topic/3516/using-multiple-bed-heaters/3

Hey Guys,

I am building a large Format using a 410850mm Bed. For Heating I use 2 400400mm Silicone Heaters with 600W each.
Using the two Beds independently works fine:

M140 H1
M140 H2

But I want to use both heaters simultaniously with one single command. I found an old thread where it was mentioned that you could use

M140 H1:H2

To define a Single Bed with 2 heaters.

This does Not Work. If I Set the Temperature in DWC it does only Heat Bed1/Heater1, Not both

Any Suggestion in how to fix this.

Greets
Max

Hey guys,

a few month back I have posted about creating a macro to toggle LEDs on or off
old post

This works fine. Now I want to reuse this code for an RGB LED (neopixel strip with 21 leds) wired to my Duet Mini 5+. I can configure the state of the LED without any problem and set colours I want. But I want a "simple" button on the PanelDue to switch them off and back on.

I just couldn't find the appropriate part of the object model - or is this just a part that is missing?

if state.GIVE_ME_LED_BRIGHNESS_LEVEL == 1
   M150 S21 P0
else
   M150 S21 P255

A workaround for this would be to create a global variable but I think I missunderstood the concept for this. I tried to use:

global LED_state = true ; LED is on

or

global LED_state = 1 ; LED is on

Then I modified the "code" above to:

if LED_state == 1 ; or true if bool
   M150 S21 P0
else
   M150 S21 P255

But the DWC alway responds that the variable does not exist. Any idea on how to bugfix this? Maybe I am just missing a small puzzle piece again.

Thanks for your help.
Max

I do not think your ideas help. I tested them but they did not improve anything...

but I found the mistake!

You know....in programming you are often start counting with 0....not with 1. So my x Stepper is not P0.1 but P0.0....

Oh my gosh...works now.