@modl I'm glad you got it working. I'll mark this as solved, but you can revert it if you need to.

@o_lampe this is hardly surprising! Why not use a loop to test it?

@apak
Thank you for the solution. ❤

@jp RRF already uses the followings safety timers:

The hardware watchdog timer in the MCU will reset it if the tick interrupt fails to be executed. This is meant to handle catastrophic firmware crashes, or spin loops that wait for hardware to be ready never finding the hardware ready. A software timer that resets the system if the Main task (the lowest priority task in the system, other than the Idle task) doesn't get executed for 20 seconds A software timer that resets the system if the task that manages heater temperatures doesn't get executed for a period of time. This is set to 20 seconds in RRF 3.4.x but is being reduced to 5 seconds in 3.5.

Are you looking for something else?

@FBG said Need to indent the code

My code is:

while state.status != "idle" M42 P5 S1 G4 S2 M42 P5 S0 G4 S10

Danke @jay_s_uk

genau das hatte ich gesucht.

@Exerqtor
You could put an M291 confirmation in start.g
It would prompt on every print though, not just print again.
If you only wanted to have the prompt on print again then I suppose you could compare the current job to the last job
I'm not 100% sure when lastFileName gets updated though.
EDIT
You'd also have to check that both are not NULL

if (job.lastFileName == job.file.fileName) && (job.lastFileName!=null) M291 S4 P"Begin print?" K{"Yes","No",} F1 if input = 1 abort

@OwenD that would probably be easier.
job.filePosition

Current position in the file being processed (in bytes or null)

@OwenD - VECTOR!!!! Excellent. I didn;t know that was added. It's precisely what I need. It allows me to create an array of a given length that I can then fill (as you demonstrate).

Thanks!

For who it might concern/help, I feel like I've got filament-change.g working decently well at this point:

; /sys/filament-change.g v2.2 ; Called when M600 is sent ; Used to do a filament change while printing ;---/ ; -/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/-- ; THIS MACRO ONLY WORKS WITH RRF 3.5.0b1 AND LATER!! ;--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/-- ;-/ ; ====================--------------------------------------------------------- ; Settings section ; ==================== ; Will not be used if you're using a "goto" macro var x = 40 ; The X axis location where you want the hotend to "park" while changing filament var y = 0 ; The Y axis location where you want the hotend to "park" while changing filament var spd = 15000 ; The speed of which you want the hotend to move to the "park" location var lift = 20 ; The Z clearance you want your nozzle to have from the print while changing filament var lights = true ; true / false depending if you have chamber lights or not that you want to turn on ; If you don't have lights you want to turn on don't mess with these var io = 0 ; The GPIO port number (set by M950) for the lights you want to turn on var pwm = 1 ; The PWM to be set on the GPIO port above, 0=off 1=full power var purge = 60 ; The amount of filament your hotend need to purge for a clean filament/color change ; Will be swaped out with global.unload_length if you have that defined! var unload = 12 ; The length of which filament have to be retracted to clear the meltzone ; Don't touch anyting beyond this point(unless you know what you're doing)!! ; ====================--------------------------------------------------------- if exists(global.unload_length) set var.unload = global.unload_length var pwm_res = state.gpOut[{var.io}].pwm ; Store the PWM from the PPIO port so that it can be returned after changing filament if var.lights M42 P{var.io} S{var.pwm} ; Turn on the lights if fileexists("/sys/lib/beep/l.g") M98 P"/sys/lib/beep/l.g" ; Long beep M400 ; Wait for moves to finish G91 ; Relative positioning M83 ; Extruder relative positioning G10 ; Retraction G1 Z1.00 X20.0 Y20.0 F20000 ; Short quick move to disengage from print G1 Z{var.lift - 1} F800 ; Go to spesified Z clearance if !fileexists("/sys/lib/goto/front_right.g") G90 ; Absolute positioning G1 X{var.x} Y{var.y} F{var.spd} ; Move the nozzle to the location defined in the settings section if fileexists("/sys/lib/goto/front_right.g") M98 P"/sys/lib/goto/front_right.g" {var.spd} ; Move to front right for filament change G1 E2 F800 ; Extrude slightly to help form a nice tip on the filament G1 E{-(var.unload)} F800 ; Retract filament from the meltzone M400 ; Wait for moves to finish if fileexists("/sys/lib/beep/xl.g") M98 P"/sys/lib/beep/xl.g" ; Extra long beep M291 S4 R"Manual Filament Change" P"Change & prime filament, then press OK." K{"OK","SKIP",} ; "OK" if input = 0 G1 E{var.purge} F200 ; Purge filament ; "SKIP" if input = 1 G1 E{var.unload} F800 ; Extrude filament back to the meltzone M400 ; Wait for moves to finish if var.lights M42 P{var.io} S{var.pwm_res} ; Return lights to previous state if !exists(global.FilamentCHG) global FilamentCHG = true else set global.FilamentCHG = true

@chrishamm said in object model aktiv extruder on an Idex:

I don't know what the value of your second gpIn port is but that script works OK on my setup if a tool is selected and if I remove the gpIn check.

it's just a magnetic switch. 0 and 1

Thanks for all the assistance on this one. I'be installed 3.5beta3 and confirmed that M28 is including leading spaces on lines, and that my macro is working. I also have my python script to convert an existing script into one created by echo. So I'm wearing the belt and have the suspenders ready in case the belt breaks.

Thanks for all the wise counsel from the team here.

@CNCModeller Just a FYI, I needed to accurately read humidity at different points for a project so I bought five DHT22 and compared them. With them all plugged into the same breadboard next to each other, I checked the readings and got a range of between 31 and 38 RH. According to the data sheet, the accuracy should be +/- 2% (max +/-5%). So spread of +/- 3.5%RH out of around 35%RH is about +/- 10% which is way outside the claimed accuracy according to the data sheet.

@chiranjeevi said in chamber heating fan - auto on when you set chamber temperature:

i tried the PT100 using the official daughterboard, but its not working well, maybe due to interferences. is there a way to add more thermistors to duet 2 wifi?

If you already have the Pt100 daughterboard that would probably be the easiest solution. Interference may be overcome with improved shielded cabling and 4 wire mode.

@T3P3Tony,

Thanks! this is exactly the answer I was searching for. I will try that out but assume it is working just fine.
Therefore I will close the ticket.👍 😊

@chrishamm SOLVED - Thanks
M400 did the trick.

@Exerqtor that looks about right - although you need to test to make sure.

you can just use the spacing setting, rather than the number of points, in you M557 command, since those values come from the spacings reported in the OM.

Am going to use the laser setup here as a template...

https://github.com/TeamGloomy/LPC-STM32-RRFUserConfigs/tree/master/K40 CO2 Laser - SKR 2 - ESP - paulg4h

Will report back on how I get on.