Thank you for helping me. My 3D-Printer finally is able to home properly and performe a mesh bed leveling procedure. 👍

@resam This is exactly the reason you need to perform a flush. See here for an example how custom codes may be implemented: https://github.com/Duet3D/DuetSoftwareFramework/blob/v3.3-dev/src/DuetPiManagementPlugin/Program.cs#L122

@alankilian ¯\_(ツ)_/¯

@cosmowave I have went back and checked, the polarity is flipped by the manufacturer, after quickly flipping the position of red and black wire it now works as intended

@dc42 said in some questions about configuration:

I can look at adding a debounce option to M950 with J parameter.

Is it possible to add a debounce option?

Thank you for the quick responses! I will try multiple small move segment to see how it goes. If that does not work well enough, I'll consider simply buying a second Duet to control my experiment's fluid handling and perfusion.

@dc42

Thanks! As usual 🙂

So I got it the wrong way round: RRF uses Peak-A and marlin uses RMS-A

Thanks!

@droftarts Yes I am using the duet 3 mini 5+ and using the latest beta firmware (Firmware: RepRapFirmware for Duet 3 Mini 5+ 3.3beta3 (2021-04-22))

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.3beta3 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2021-04-22 13:48:47

@dc42 I will set the timing from 1us to 4us and respond after driving. Thank you for letting us know!

Oh, i have seen now, that the second line has to be intended!
It's all clear now.

@poofjunior said in HTTP API for Standalone Duet 3 Mini and Duet 2:

(1) for commands where I'm extracting data (M409), I need to follow up with rr_reply to actually collect it. Versus with DSF, it's part of the response when posting to /machine/code.

Use rr_model in preference to M409, than you will get the reply as part of the response

And (2) after sending a small sequence followed by "M400," I couldn't find a way to tell my code to wait until the machine was actually done. Versus, with DSF, sending M400 causes the http response to hang until the moves have actually finished.

You can use rr_model to query state.status and watch for it to change from Busy to Idle.

@phaedrux said in Endstops Not Respected During Probing:

Caution: the XY coordinates are permitted to be outside the normal printable bed area! This is intentional, because some printers (e.g. delta printers) benefit from probing areas not used for printing.

https://duet3d.dozuki.com/Wiki/Gcode#Section_G30_Single_Z_Probe

Well, that explains it!

@dc42 Any chance we can add a flag to the G30 call to either respect or ignore axis limits?

@daimein2007 join us on discord https://discord.gg/uS97Qs7 and we'll go through things with you

Your config seems to be a mix of RRF2 and RRF3 command syntax. For instance your endstop and probe config is for RRF2, but your heaters etc are RRF3.

What firmware are you actually running?

Please send M122 and M98 P"config.g" in the gcode console and report the results.

@jay_s_uk said in BLTouch M401 and M402 do nothing:

M280 P0 S90

That was it, that was the problem.
Thank you so much!

@dc42 Is it possible to connect a SBC like RPI and use the RPI onboard computer instead of the 120mhz Arm CPU on the duet board?

to overcome CPU the CPU bottleneck.

Br
JHB

@phaedrux I actually updated to 3.2.2 today and so far it's fixed the issue I was seeing.

Boards are wired as described in the documentation. Nothing is near the ribbon cable.
But I'll check all connections...

For the motor config block, try:

; Motor Configuration !!! For stock motors ; !!! Also note that you should edit the current-sense-homing.g file and increase current to 50 on X and Y, 100 on Z. ; !!! M913 X20 Y20 Z60 ---> M913 X50 Y50 Z100 ; M350 X16 Y16 Z16 I1 ; Set X, Y, and Z microstepping with interpolation M350 E32 I0 ; Set Extruder Microstepping without interpolation M92 X100.00 Y100.00 Z400.00 E280.00 ; Set steps per mm M566 X600.00 Y600.00 Z24.00 E300.00 P1 ; Set maximum instantaneous speed changes (mm/min) M203 X15000.00 Y15000.00 Z900.00 E2000.00 ; Set maximum speeds (mm/min) M201 X4000.00 Y4000.00 Z1000.00 E5000.00 ; Set accelerations (mm/s^2) M906 X620.00 Y620.00 Z550.00 E550.00 I50 ; Set initial motor currents (mA) and motor idle factor in percent M84 S1000 ; Set idle timeout before shifitng to idle-current ; Motor remapping for dual Z and axis Limits M584 X0 Y1 Z2:4 E3 ; Set two Z motors connected to driver outputs Z and E1 M671 X-37:287 Y0:0 S10 ; Leadscrew at left connected to Z, leadscrew at right connected to E1

and also current-sense-homing.g:

; 0:/sys/current-sense-homing.g ; Set the current and sensitivity for homing, non-printing, routines M915 X S2 F0 H400 R0 ; Set the X axis sensitivity. M915 Y S2 F0 H400 R0 ; Set the Y axis sensitivity. M913 X50 Y50 Z100 ; Set the X, Y, and Z drivers current percentage for non-print moves, per config.g.

Let me know if that helps.

@phaedrux

I did do the macro thing, I don't recall if I did all the steps as described by DC42 ( missing step would have been the M588 S"*".

Using DWC I did everything except the M588 S"*", I should have tried it but was thinking I would get disconnected.

In panel due, yes, I had to break it up because of line length.

Hopefully if this ever comes up for me again, I remember what I learned here.