Wiring BIQU microprobe to Duet RotoToolBoard

[Phaedrux]

Can you share the results of sending M122, M122 B1 and M98 P'config.g" in the gcode console?

Also please share your full config.g

[Timothee Leblond]

@Phaedrux

Here is the answer after M98 and M122 B1:

Here is the answer for M122:
console.txt

Here is my full config.g:
config-2.g

[Phaedrux]

Can you try changing
M950 P0 C"121.io0.out" ; Set servo output on Rototoolboard
to
M950 S0 C"121.io0.out" ; Set servo output on Rototoolboard

[Timothee Leblond]

@Phaedrux

Still not working. Commands are sent but no answer.
What triggers me is that the stepper is not moving either although I know it was working.

[Timothee Leblond]

@Phaedrux

Do you think it could have something to do with the Raspberry?

[Phaedrux]

What kind of stepper are you trying to drive?

Your current appears to be set above what the roto board can actually support.

M906 E1600 ; set extruder driver currents

Though I believe the firmware will limit it to 1 amp anyway.

How are you trying to test the stepper? As it is part of a tool, you would need to either heat up the hotend or enable cold extrusion, though I don't see any heaters defined in your config.g.

[Timothee Leblond]

@Phaedrux

I don't need any heater nor fan on my tool this why I don't have such things.
The cold extrusion command is part of my Gcode file though. However I'm testing the motor in DWC sending extrusion commands like G1 E10 F300. But this isn't working anymore...

The motor is this one:

[fcwilt]

@Timothee-Leblond

Hi,

The probe is not working at all except for the random deploy/retract - which is not a good thing.

Frederick

[dc42]

@fcwilt said in Wiring BIQU microprobe to Duet RotoToolBoard:

The probe is not working at all except for the random deploy/retract - which is not a good thing.

My guess is that either you have a bad connection in the control wire between the microprobe and the TOOL1RR, or the microprobe isn't compatible with the 3.3V signal level provided by the TOOL1RR. Have you a specification for the control signal required by the microprobe?

[droftarts]

@dc42 @Timothee-Leblond It does seem to need a 5V signal, see https://github.com/bigtreetech/MicroProbe/blob/master/MicroProbe V2 User Manual_20240330.pdf.

I would try connecting it to the Mini 5+ servo pin, and changing the probe setup. For wiring, see https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_BLTouch#wiring but wire the servo control wire (and 5V and GND, if you want) to 5V_PWM header on the Mini 5+. Then change your config to:

; Probes
M950 P0 C"out6"                              ; Set servo output on Mini 5+ 
M558 P9 H6 F250:30 T8000 C"^!io6.in"            ; Set probe input to IO_6 on Mini 5+
G31 P500 X0 Y0 Z0                                  ; set Z probe trigger value, offset and trigger height

If possible, test your stepper motor on the Mini 5+ as well. If you can get that working, we can then look at why the Roto board isn't working.

Ian

[Timothee Leblond]

@droftarts

But what I can see, the pin on the Roto board is a 5V as well?

Sorry for my confusion but could you please point out the recommended pins on the wiring map?
As the wiring manual does indicate any duet board, I do not want to do any mistakes...

Thank you for your precious help!

[fcwilt]

@dc42

Thanks. I will check the specs.

Frederick

[dc42]

@Timothee-Leblond said in Wiring BIQU microprobe to Duet RotoToolBoard:

But what I can see, the pin on the Roto board is a 5V as well?

The power provided on that pin is 5V but the signal level on the IO0_OUT pin is 3.3V. Most electronics devices these days (including BLTouch) are happy with 3.3V signal levels.

EDIT: according to https://biqu3d.com/blogs/news/biqu-microprobe-new-leveling-technology-that-defines-new-standards the microprobe is compatible with 3.3V control signals.

[Timothee Leblond]

@dc42

Does this mean it is supposed to be working the way I initially wired it?

[droftarts]

@Timothee-Leblond You need a 5V supply, and a separate 5V PWM signal to activate the probe. Currently you're using io0.out, which has a 3.3V signal level. Using the 5V PWM header (red arrows) for 5V, servo control (out6-buff) and GND, use IO6.in for the signal wire.

Ian

[Timothee Leblond]

@droftarts

Hallelujah! The probe is now working with this wiring! THank you!

About the stepper, any idea why it is not working? I know it has been working in the past wired this way to the Roto board.

[droftarts]

@Timothee-Leblond said in Wiring BIQU microprobe to Duet RotoToolBoard:

About the stepper, any idea why it is not working? I know it has been working in the past wired this way to the Roto board.

Your config:

; Extruders
M584 E121.0 ; set extruder mapping
M350 E16 I1 ; configure microstepping with interpolation
M906 E1600 ; set extruder driver currents
M92 E28.09 ; configure steps per mm
M566 E120 ; set maximum instantaneous speed changes (mm/min)
M203 E3600 ; set maximum speeds (mm/min)
M201 E250 ; set accelerations (mm/s^2)

At 28 steps per mm, M92 looks wrong. If you extrude 1mm, the motor would barely move. As @Phaedrux said, the stepper driver is limited to 1A, so perhaps set M906 to E800. Does the motor get 'energised', ie can you turn it easily by hand after sending a command?

Ian

[Timothee Leblond]

@droftarts

Changing the E1600 to E800 and putting a higher value for M92 works.
Is there a way to set this up correctly? I mean finding the right value for the steps per mm?

Thank you,

Tim

[droftarts]

@Timothee-Leblond It depends on what extruder you are using. You said you don't have a heater, I think, so is it something custom? Ultimately you want it to pull in 1mm of filament when 1mm of extrusion is commanded. You can get a baseline figure by changing M92. For a guide, see https://docs.duet3d.com/en/How_to_guides/Calibration#h-3-calibrating-extruder-e-steps-per-mm

Ian

[Timothee Leblond]

@droftarts said in Wiring BIQU microprobe to Duet RotoToolBoard:

My tool is a bioprinter (cold extrusion) so I cannot really follow the guide infortunately. The system is as follows:

I actually don't know how am I suppose to configure the firmware for this.

Thank you,

Tim