Topics created by simplesimson

@simplesimson said in Duet Maestro BL-Touch Not working:

If i change it back i can not deploy. I think this is because it thinks it is already deployed? As the signal reads 0 isnt this the feedback for beeing deployed?

No.

@simplesimson said in Duet Maestro BL-Touch Not working:

atm I am able to print - so do everything including leveling by using the I0 in my deployprobe.g. Meaning as soon as it gets deployed i turn the inversion off.
As soon as i retractprobe.g I again turn it back on with I1.
Leaving any of the inversion (I0 or I1) out results in total malfunction.

I don't understand what this means.

@simplesimson said in Duet Maestro BL-Touch Not working:

The probe returns 0 when retracted? If so it only returns 1000 for the split second its triggerd somewhere in the middle of its stroke?

No. As I said, you're focusing too much on the trigger state read out of 0 or 1000. Normally it should read 0. The only time it would change to 1000 is the split second when the deployed pin contacts the bed. It resets immediately to 0. You may not see it change in the DWC display at all.

Your config,g should have

; Z-Probe M558 P9 H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds ; deployprobe.g ; called to deploy a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Dec 16 2021 14:48:53 GMT-0600 (Central Standard Time) M280 P64 S10 ; deploy BLTouch ; retractprobe.g ; called to retract a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Dec 16 2021 14:49:09 GMT-0600 (Central Standard Time) M280 P64 S90 ; retract BLTouch

And your homing file should have something like

; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Dec 16 2021 14:49:38 GMT-0600 (Central Standard Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-235 Y-215 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X5 Y5 F6000 ; go back a few mm G1 H1 X-235 Y-215 F360 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X15 Y15 F6000 ; go to first bed probe point and home Z G30 ; home Z by probing the bed

Use the procedures shown here to test that it's all working correctly.
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

M401 and M402 should deploy and retract the pin.
G30 should deploy the pin and start the z axis moving.
Touching the pin at that point should stop movement.

69f22445-b45b-43cc-a08d-0e7b2489d9d8-image.png
source: https://github.com/dc42/OrmerodSensorBoard/blob/master/SchematicAndPCB/Mini-differential-IR/V1.2/board.png
@dc42 the parts arrived. but i think i have to point the green square on the back as shown on the scematic or? so that its towards the corner of the pcb, away from the black capacitor, or?

Regards, Simon

EDIT: I tryed it as you described. I had to face green square to the outside for it to read

M563 P0 D0 H1 F2

https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_fans

Where do you have the fans actually connected?

@simplesimson said in Home Z several times and get average:

@dc42 hey 🙂 thanks for your answer

my M558 (config.g) looks like this:
M558 P1 H2.5 F120 T9000 I0 R1 A5 S0.1

But when doing G28 at the start of the print it doesnt check 5 times.
It just uses my homeall.g
can i define a special M558 in homeall.g?

Does it probe twice? You've set the tolerance to 0.1mm (S parameter), so it will only probe twice if the two readings differ by no more than 0.1mm. I suggested you use S0.

Ty!
maybe this section indeed helps:

```For a CoreXY or H-Bot machine, RepRapFirmware assumes that the motor connected to the X motor output moves the head in the +X and +Y directions when it runs forwards, and that the Y motor moves the head in +X and -Y directions when it runs forwards. [Note: firmware 1.18 and earlier assumes that the motor connected to the Y motor output moves the head in the -X and +Y directions when it runs forwards]. So you can start with these M569 commands in config.g:

Problem solved. I had to reduce the microstepping to 16. Works just fine now.