@cosmowave
That'll do it 😂

@owend thank you, it works flawless! 😊 👍

To whomever it might concern/interest:

I have a CNC-setup where the spindle speed is controlled by manually adjusting a potentiometer.
In order to control the spindle speed via the duet, I have built a contraption that uses a small RC servo to turn the potentiometer for me.

I have created some global variables for better debugging. But the macro will also work with normal variables. But these have to be defined!

my "create lookup macro":

echo >>"lookup.g""" ;create lookup.g M280 P0 S0 ;reset servo position G4 S1 ;wait for servo M80 ;turn on Power G4 S1 ;wait for power set global.servo=0 ;reset servo position M3 P0 S650 ;switch on spindle G4 S2 ;wait for spindle to get up to speed echo "LookupTable START" while global.servo<=180 ;repear until servo arm is at 180° if spindles[0].active-fans[1].rpm>1 || spindles[0].active-fans[1].rpm <-1 ; the loop is repeated as long as the difference between spindles[0].active (set RPM) and fans[1].rpm (measured RPM) >+-1 RPM set global.servo={global.servo+((spindles[0].active-fans[1].rpm)/100)} ; set global.servo depending on the difference between spindles[0].active (set RPM) and fans[1].rpm (measured RPM) M280 P0 S{global.servo} ; use global.servo to set servo position G4 S0.5 ;wait for servo and spindle to get to new RPM else ;if the difference between spindles[0].active (set RPM) and fans[1].rpm (measured RPM) <+-1 RPM echo >>"lookup.g" "if spindles[0].active >= "^spindles[0].active^"" ;append to lookup.g as a new line echo >>"lookup.g" " M280 P0 S{"^ global.servo ^"}" ;append to lookup.g as a new line G4 S1 ;wait M3 P0 S{spindles[0].active+25} ; increase spindle speed by 25RPM echo "LookupTable END" M5 ;turn off spindle M280 P0 S0; reset servo position

@garth_42
Hi all, I posted justa bit too quickly. I figured out the syntax. For anyone in the future, this is the syntax I used:
M117 {"Z-Axis Position: " ^ move.axes[2].userPosition ^ " "}

bda88bb5-4feb-4265-8800-74aeb91a185f-image.png

some where I found this some time ago

Macro "leds on/off"

if state.gpOut[1].pwm == 1 M42 P1 S0 else M42 P1 S1

in config files

; LEDS M950 P1 C"e1heat" Q500 ;use heater 1 outupt for LED M42 P1 S1 ; turn off LEDS

@hebigt I think it is because you are using G91, ie relative coordinates, for moves. X is increasing each loop, so it moves the distance described by var.x not to that actual position. The first time it moves a distance of 0.05mm, next it moves 0.1mm (ie to X0.15), then 0.15mm (ie to X0.3) etc. My mental maths isn't good enough to know what will happen to var.y if you switch to absolute coordinates (G90), but I'm sure there's a simple way around that, too.

Ian

@dc42 nvm you are right. I believe the home flag never went false at the beginning so I added an M18 and that fixed the issue (let me know if there is a better way than just disabling the motors).

However when simultaneously homing C and another axis (Y or X) the homing sequence only stops on Y or X but never when C homes, is there a way to stop the process if C homes first like for X and Y?

@dc42 Ah didn't know extruder's aren't included, thanks!

@dc42 thank-you! Never knew that was there, very useful!

@phaedrux said in 1 Bed 2 bed heaters. How to control both with a single M190?:

I guess the simplest solution would be to wire the heater output to both SSRs signal inputs in parallel.

This would run the risk of overdriving one of the heating elements if both elements don't perform exactly the same. If you have just one signal to drive the SSR then there is just one temperature probe that is being monitored.

@yao that looks like a more conventional driver with optically isolated inputs, of the sort that the 1XD was designed to drive.

@dc42 Here is the updated Retract macro from line 14 of my original post:

M400; clear the command buffer M280 P1 S{global.retract_angle} G4 P400; wait for purge bucket to fully retract

Before adding in the M400, the M280 P1 command was being executed between lines 7 and 8. I don't know if the dwell was being executed early.

@owend I see . Most probably it is my mistake, so I did some workaround
In the main program I create a loop calling 50 times a macro that contains 3125 loops of my code with echo in the end

@bluedust said in Super Slicer and Duet2:

@threepwood
Thanks for that info. Even though I am not using a Voron, it still looks like something I should review to help me get SS working/produce good prints.

The Voron and Rat Rigs are pretty similar so the settings should work pretty well!

@schild0r
I wouldn't use M957 as it's for debugging as you say.
I see no problem with calling the macros for filament-error or load.g from your trigger.
I seem to remember DWC 3.4 allows a filament change to the same filament now, but you can always identify the load.g you want to run with
move.extruders[state.currentTool].filament

@mikeabuilder said in Weird macro behaviour:

Glad it's working, but I'll toss in couple of comments.

The comment - Per @deckingman comment, I think it's good coding practice to check probe values with a ">X" vs "=Y".

Noted, then i guess this will taste better:

if sensors.probes[0].value[0] < 1 set global.klicky_status = "attached" elif sensors.probes[0].value[0] > 999 set global.klicky_status = "docked" echo ""

Another comment - I don't see an initialization for global.klicky_status. If it was not initialized, you should have seen an error in the console or log file.

global.klicky_status get's initialized along with all my other globas thru a macro named "globals.g", "globals.g" on it's side gets called by "init.g" as one of the last steps in my "config.g".
end of "config.g"

; Miscellaneous M950 P0 C"out2" ; create output Port0 attached to out2 connector for LED lights M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss M572 D0 S0.0 ; Disable Pressure Advance M98 P"/sys/lib/init.g" ; iniate external configs M501 ; load config-override.g T0 ; select tool 0

"init.g":

; /sys/lib/init.g ; Called in the end of config.g ; Used to setup more stuff M98 P"/sys/lib/globals.g" ; setup global variables M98 P"/sys/lib/speed/speed_printing.g" ; set normal speed & accel M98 P"/sys/lib/current/xy_current_high.g" ; set normal xy currents M98 P"/sys/lib/current/z_current_high.g" ; set normal z currents M98 P"/sys/lib/fw_retraction.g" ; set firmware retraction settings

"globals.g"

; /sys/lib/globals.g ; Called by init.g ; Used to initialize global variables ; global declarations and defaults ; ====================--------------------------------------------------------- ; temperature ; ==================== if !exists(global.bed_temp) global bed_temp = 0 if !exists(global.hotend_temp) global hotend_temp = 0 if !exists(global.chamber_temp) global chamber_temp = 0 ; ====================--------------------------------------------------------- ; stepper currents ; ==================== if !exists(global.xy_current) global xy_current = move.axes[0].current if !exists(global.z_current) global z_current = move.axes[2].current if !exists(global.e_current) global e_current = move.extruders[0].current ; ====================--------------------------------------------------------- ; mechanical Z pin ; ==================== if !exists(global.zpinx) global zpinx = 194.5 if !exists(global.zpiny) global zpiny = 355 ; ====================--------------------------------------------------------- ; klicky probe ; ==================== ; the distance from the body of the klicky probe to it's own trigger point if !exists(global.klickyoffset) global klickyoffset = 0.23 ; a larger values makes the nozzle closer to the bed after running autoz ; the absolute X location of the klicky while docked if !exists(global.klickydockx) global klickydockx = 18.6 ; the absolute Y location of the klickywhile docked if !exists(global.klickydocky) global klickydocky = 357.3 ; the relative disance and direction of the klicky docking move if !exists(global.klickywipe) global klickywipe = 30 ; -30 for a left wipe 30 for a right wipe if !exists(global.klicky_status) global klicky_status = "none" ; ====================--------------------------------------------------------- ; bed ; ==================== ; define the bed size (print area from 0 to X and Y max) if !exists(global.bedx) global bedx = 350 if !exists(global.bedy) global bedy = 350 ; ====================--------------------------------------------------------- ; misc ; ==================== if !exists(global.initial_extruder) global initial_extruder = 0 if !exists(global.bed_leveled) global bed_leveled = false if !exists(global.job_completion) global job_completion = 0 if !exists(global.debug_mode) global debug_mode = true ; ====================--------------------------------------------------------- ; output current values ; ==================== ;echo "global.bed_temp defined. Value : " , global.bed_temp ;echo "global.hotend_temp defined. Value : " , global.hotend_temp ;echo "global.chamber_temp defined. Value : " , global.chamber_temp echo "global.klicky_status defined. Value : " , global.klicky_status echo "global.bed_leveled. Value : " , global.bed_leveled echo "global.job_completion defined. Value : " , global.job_completion echo "global.debug_mode defined. Value : " , global.debug_mode

Adding an "else with a message stating klicky status is not defined and an abort would be nice, that way you've covered all options for global.klicky_status. Even better would be a third return value for gloabl.klicky_status in klicky_status.g. on Line 12 add an else set global.klicky_status = "invalid". Then you'd see if the value passed back to the main macro is neither 0 nor 1000.

Agreed on that, an else condition that resulted in "invalid" the result was anything between 1 too 999 would fix that with an abort. But i can't figgure out how to construct that, for instance

if sensors.probes[0].value[0] < 1 set global.klicky_status = "attached" elif sensors.probes[0].value[0] > 999 set global.klicky_status = "docked" else sensors.probes[0].value[0] = {what to but here to check if the value is between 1 and 999?} set global.klicky_status = "invalid" echo "Klicky status invalid - aborting" abort echo ""

Or just go the easy route with

if sensors.probes[0].value[0] < 1 set global.klicky_status = "attached" elif sensors.probes[0].value[0] > 999 set global.klicky_status = "docked" else set global.klicky_status = "invalid" echo "Klicky status invalid - aborting" abort echo ""

My speculation is that if the variable was not initialized it might abort the "code block" that contains it, which might be the block starting on line 1and ending on line 90.

Turns out the premature ending was a bug in DWC, so it wasn't my fault this time lol.

@chrishamm said in Weird macro behaviour:

@exerqtor I've got a fix ready that will be part of the next 3.4.2-b1 version. dc42 has already merged it.

Sweet, hope that beta see the light of day pretty soon!

@deckingman thanks for your time and dedication on the repply. I am planning to add some cork sheets on the underside and probably a heater for the chamber in the future for more complex materials. my mirror bed was 4mm as it was only supposed to "flatten" the bed (I was unable to find a good aluminium tooling plate on my country, ended up using a regular aluminim plate) and was actually reused from my home. this printer is only for large projects so I dont mind giving a full hour of cooling down after a 3 or 5 days print. for smaller projects I use a 200X200 printer.

@martin7404 your current version only counts the first endstop. You'll need to duplicate line 13/14 and adjust for endstop1-endstop8 in there to count the others too.

I would also guess maybe putting a G4 P0 after the M98 lines in the test.b file might be instructive. I can imagine the console messages not buffering (are they supposed to buffer?). I might also make testa.g have a parameter that you then echo along with the answer, and have test .g supply a unique value on each m98 call. This would let you see which of teh M98 calls are getting lost (the presumption is it's lat last getting lost, but nice to know for sure).

@deckingman Good question there is another comment in the code...

// 6. Set the speed to the smaller of the requested and maximum speed. // Also enforce a minimum speed of 0.5mm/sec. We need a minimum speed to avoid overflow in the movement calculations.

Which sort of answers your question, but raises the issue of what happens if the speed ends up being reduced below the minimum? Could be an out of date comment, but who knows....

@lem said in Save Z position when shutting down:

which macro / file / command is executed while shutting down?

Usually none. My printer has a separate PSU for the Duet, so that I can shut-off power for steppers and heaters with M81, but I can as well turn the mains switch or pull the plug.

Either you save the positions in all situations you can think of - end.g, pause, resume, abort, M911 … but you won't catch all possible events. Or you always invoke a macro before you plan to shut the printer off.

A better way is to use some "auxiliary end switch" for Z so you have a known height before doing the "real" homing - this can be anywhere along the Z axis.