Topics created by AdrAs

Well, turned out it was something completely different. I just hooked up the board again and the panel due was blank. Suddenly everything stopped working.

It was also weird, that the Serial port changed. The working one was no. 4, the not working one was no.3. Then I thought ... wait a minute ... I've got two usb ports on my laptop, let's use the other one.

Turned out that connecting the duet to one port works, but connecting the duet to the other one doesn't.

I just used a usb tester. On the working port the duet board consumes about 300mA, on the non working port it consumes only 100mA.

And I thought the usb-port survied that 12V incident a couple of years ago. But even if the fuses seem to have recovered, that port is no longer able to deliver enough power.

So the entire problem all the time was having the duet connected to a broken usb-port which doesn't provide enough power.

This feature would be nice, but the problem is not on the Duet side, but on the ideamaker side. With the latest update (4.2.3) repetier support has been added.
5510e3c2-3d04-4db3-a25a-acb9293fc861-image.png
We are waiting for the support of the growing popularity of Duet.
You can slice in Kura, but without plugins it's not fun at all.

Ok, thank you very much!

Well, not as long the motor stall detection doesn't trigger at all. But for now I'll just play with an accelerometer, how hard can it be? xD

@AdrAs said in Mesh probing with probe offset:

Yeah, I could do that in my calibration macro. But the weird thing is that it works fine for the auto calibration. There it's probing on the edges of the print bed even when the nozzle is outside of the printable area

As I recall (and it was a long time ago that I had deltas) the auto-cal procedure allows for that due to specific needs of the auto-cal procedure.

Frederick

@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

Yes, Veti's right, the probe is about 20mm below the nozzle. Besides that the situation seems to be improved, but I've still got an area in front where the nozzle is too low and area opposite to it, where the nozzle is too high.

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 I was referring to a custom one that you'd have to write first. I believe ExecOnMCode lets you replace any code with a custom command and DuetPi Management Plugin handles several standard codes before they are sent to RRF.

Looking at other places in the print it seems like a Z seam. I'll let google search figure out the solution

First M561 to clear any bed transform.
I'm using G32 second Output:
Calibrated 6 factors using 13 points, deviation before 0.725 after 0.063

After that G29. Output: 21 points probed, min error -0.192, max error 0.163, mean -0.008, deviation 0.087
Height map saved to file heightmap.csv

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.

@Stephen6309 Which one?