Thanks for your explanations. It turned out to be other issues.

First of all, the fan I used for testing doesn't support PWM, I can get it running by tuning the F parameter, but overall I can't get it running consistently.

Second, it turned out that I accidentally reversed the polarity of my other fans yikes. Luckily no damage.

And at last I can highly recommend adding the H-1 parameter just to ensure it wasn't configured as a fan for a tool.

@Phaedrux said in Issues upgrading to 3.2.2 firmware:

iles, one at a time i

Cool, thanks. I used the tool to create a new config, and then i diffed both configs old and new to see where I forgot something. Machine is moving and not killing itself, and the delta calibration works.

Mesh bed calibration not working yet: Error: G29: No valid grid defined for bed probing

Issue was my M557 command which used a too low S value, I had it set to 5. Now that I set it to 20 it works

@danal said in Delta auto calibration without z probe:

Thank you very much, turned out that I had the wrong delta radius. I thought it's the size of the print bed, so I set it to a safe smaller value. But of course that was completely wrong. I'm now using a proper calculated value.

@alankilian said in Arduino as Z-Probe questions:

The Z_PROBE_MOD pin is an output from the DUet tht can control a servo to deploy a BLTough for example.

Does that mean, I can use that pin, to ouput a servo pwm signal from the duet using the following configuration?

M950 S0 C"zprobe.mod"  ; assign GPIO port 0 to heater3 on expansion connector, servo mode
...
M280 P0 S80  ; set 80deg servo position on GPIO port 0

Can I hook that pin up to the Arduino to read the signal issued by the M280 command?

I couldn't find anything using the search. Is it possible to create a custom gcode command for a g-code which doesn't exist yet?

I'd like to create a M601 command which simply executes M226. Is that somehow possible?

[Edit] Nevermind, I just created a M601.g file in the sys folder with the following code

; M601 is the command Prusa printers issue to pause print
; However in duet/reprap firmware that command doesn`t exist
; And therefore we can bind it to the actual reprap pause command which is M226
M226

Well, seems like my perimeter overlap was so small, that the infill layer didn't properly connect and was "bridging" mid air. I increased the perimeter overlap and now the issue is gone ....

@phaedrux Agreed

@peter247 said in IdeaMaker upload to Duet:

@adras You do it the normal way save it to the hard drive , then download it to your Duet .

Ok, thanks. Way too much effort I'll stick to Pruser Slicer then

I just wanted to give the IdeaMaker slicer a try. But I was unable to figure out how to configure it to upload the gcode via Wifi to my duet board.

Does anyone know if that's even possible?

Ok, thank you very much!

@dc42 I've got another question I hope you can help me.

• When are the deployprobe and retractprobe macros executed? Only when a BLTouch is connected, or for the other probe types as well?

@fcwilt @zapta

Thank you guys, both look awesome.

@alankilian Thanks for the list. However I couldn't find anything which is small, running on 3.3v and has >16 mhz. Nevermind though, The ESP should arrive today and suits all my needs for now.

@alankilian Thanks, they are a bit too slow though. I need at least 16 Mhz

That's great. And I learned, that I skip all the arduino 5V conversion stuff, and just go for an ESP module for my project More Mhz, more memory, and free WIFI I'll never use

@dc42 said in Arduino as Z-Probe questions:

Duet WiFi version 1.04 has 30V tolerance on the Z probe pin. Older Duet WiFis are not.

I've got a 1.02 WIFI, so I guess this means the Z probe pin can only handle 3.3V, right?