Posts made by Craigrobbo

@Craigrobbo Removing the ! worked thank you

@Phaedrux

Thank you, here is photos of wiring with the 3 different probes I have (the main one in question is the 3d touch / cr touch)

I'll try removing the ! And see how I get on

Thank you

@Phaedrux said in Probe always reads 1000 (deployed):

@Craigrobbo said in Probe always reads 1000 (deployed):

M558 P5 C"^!zprobe.in"

This doesn't look right for a BLTouch.

Try M558 P9 C"^zprobe.in"

Thank you, I gave that a Try, unfortunately didn't help, probe still reads 1000 (deployed ) all the time

@infiniteloop HI.

No that thread is regarding the BIQU micro probe, this is regarding the Cloned BL touch.

The thread about the BiQU was inconclusive and never gotten a working solution

I wasn't the one to drop the probe, but this thread isn't about the fine details of HOW it was damaged.

Im asking about the BL-Touch/3d-Touch

Hi there I'm using a cloned BL touch (3d touch ) I seem to have a problem where it always shows as deployed whether the pin is in or out it does react to the M280 p0 s10 /90 commands and deeply retracts as it should, I thought I had a fault sensor so I tried my genuine CR touch from my Ender and this exactly the same thing.

What's really strange is my old probe which is now damaged which was also a clone of the bltouch, worked perfectly fine unfortunately when I was doing some maintenance my girlfriend stepped on it and broke it

Wiring is as Follows.

Probe side Board Side

Z-Stop (white) -> Z-Probe IN (DUET)
GND (black) -> GND (DUET)
Signal(Yellow) -> PWM5 (DUEX5)
+5v (RED) -> AUX 5v (DUEX5)
GND (BROWN) -> GND (DUEX5)

; Configuration file for Duet WiFi (firmware version 3)
; Made by Craig Robinson
; General preferences

G90 							; send absolute coordinates...
M83 							; ...but relative extruder moves
M550 P"CraigsMachine" 			; set printer name
M669 K1 X1:0:0:0 Y1:-1:0:-1 Z0:0:1:0 U0:0:0:1 ;markforged
;M669 K11 X1:0:0:0 Y1:-1:0:-1 Z0:0:1:0 U0:0:0:1 ;markforged new 



; Network
M552 S1 						; enable network
M586 P0 S1 						; enable HTTP
M586 P1 S0 						; disable FTP
M586 P2 S0                      ; disable Telnet
M575 P1 S1 B57600 				; enable connection for PanelDue


; Drives
M569 P0 S1								; physical drive 0 goes forwards 	X  is drive 0
M569 P1 S1 								; physical drive 1 goes forwards 	U  is drive 1
M569 P2 S0 								; physical drive 2 goes backwards 	Y  is drive 2
M569 P3 S1 								; physical drive 3 goes forwards 	E0 is drive 3
M569 P4 S1 								; physical drive 4 goes forwards 	E1 is drive 4
M569 P7 S1 								; physical drive 7 goes forwards  	Z1 is drive 5
M569 P8 S1 								; physical drive 8 goes forwards 	Z2 is drive 6
M569 P9 S1 								; physical drive 9 goes forwards 	Z3 is drive 7
M569 P10 S1 							; physical drive 10 goes forwards 	Z4 is drive 8
M584 X0 Y2 U1 Z5:6:7:8 E3:4				; four Z motors connected to driver outputs 5,6,7 and 8
M350 X16 Y16 Z16 E16:16 U16 I1 					; configure microstepping with interpolation
M92 X53.33 Y53.33 Z1600 E981:981 U53.33 				; set steps per mm 981 for corect steps 932 for default(E15090:15090 for 256 microsteps)
M566 X1000 Y1000 Z10 E1500:1500 U1000 				; set maximum instantaneous speed changes (mm/min) (tested 500 to 5000)
M203 X20000 Y20000 Z500 E4000:4000 U20000 	; set maximum speeds (mm/min) (tested from 1000 to 20000)
M201 X1000 Y1000 Z100 E800:8000 U1000 		    ; set accelerations (mm/s^2) (tested 100 to 2000)
M906 X950 Y950 Z950 E950:950 U950 I50 			; set motor currents (mA) and motor idle factor in per cent
M84 S30 										; Set idle timeout

;Laser Control
;M452 C"duex.pwm4" R255 F200 ; Enable Laser mode, on exp.heater3, with max intensity being 255, and a PWM frequency of 200


;Pressure advance								;tested 0.01 upto 0.1
M572 D0 S0.05

; Axis Limits
M208 X-230 Y-230 Z0 U-175 S1 			; set axis minima
M208 X175 Y215 Z350 U225 S0 			; set axis maxima

; Endstops
M574 X1 S1 P"zstop" 					; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"xstop" 					; configure switch-type (e.g. microswitch) endstop for high end on Y via pin zstop
M574 Z1 S2 								; configure Z endstop - high end and uses probe
M574 U2 S1 P"ystop"
M671 X-260:260:260:-260 Y-227:-227:302:302 S10 	; leadscrews positions - Front left, Front right, Rear

; Z-Probe


M950 S0 C"duex.pwm5" 

;M558 P5 C"^!zprobe.in" H3 F250:30 T6000 			; set Z probe type to bltouch and the dive height + speeds

;M558 P5 C"^!zprobe.in" H3 F250 T6000 A10 R1.25 S0.008  ; Set Z probe type/mode 5. H=Dive Height. F=Speed probe speed,

M558 P5 C"^!zprobe.in" H5 F150 T6000 ;A10 R1.25 S0.008  ; Set Z probe type/mode 9. H=Dive Height. F=Speed probe speed,



G31 P500 X0 Y-36 Z3.4					; set Z probe trigger value, offset and trigger height (larger number  = Nozzel closer to the bed)
M557 X-220:170 Y-220:170 P8:8 					; define mesh grid

; Thermistors definitions
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 	; configure sensor 0 as thermistor on pin bedtemp
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 	; configure sensor 1 as thermistor on pin e0temp
M308 S2 P"e1temp" Y"thermistor" T100000 B4138 	; configure sensor 2 as thermistor on pin e1temp

; Heaters definitions
M950 H0 C"bedheat" T0 			; create bed heater output on bedheat and map it to sensor 0 aka S0
M307 H0 B0 S1.00 				; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 						; map heated bed to heater 0
M143 H0 S120 					; set temperature limit for heater 0 to 120C

M950 H1 C"e0heat" T1 			; create nozzle heater output on e0heat and map it to sensor 1 aka S1
M307 H1 B0 S1.00 				; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280 					; set temperature limit for heater 1 to 280C
M570 H1 T25						;Heater temp before raising a fault

M950 H2 C"e1heat" T2 			; create nozzle heater output on e1heat and map it to sensor 2 aka S2
M307 H2 B0 S1.00 				; disable bang-bang mode for heater  and set PWM limit
M143 H2 S280 					; set temperature limit for heater 2 to 280C

; Fans
;M950 F0 C"fan0" Q500 			; create fan 0 on pin fan0 and set its frequency
;M106 P0 S0 H-1 					; set fan 0 value. Thermostatic control is turned off

;M950 F1 C"fan1" Q500 			; create fan 1 on pin fan1 and set its frequency
;M106 P1 S1 H0 T45:100 			; set fan 1 value. Thermostatic control is turned on

;M950 F2 C"fan2" Q500 			; create fan 2 on pin fan2 and set its frequency
;M106 P2 S1 H-1 					; set fan 2 value. Thermostatic control is turned off

M950 F0 C"duex.fan3" Q250 		; create fan 3 on pin duex.fan3 and set its frequency
M106 P0 S0 L0 X255 H-1 				; set fan 3 value. Thermostatic control is turned off

M950 F1 C"duex.fan4" Q250 		; create fan 4 on pin duex.fan4 and set its frequency
M106 P1 S0 L0 X255 H-1 				; set fan 3 value. Thermostatic control is turned off

M950 F2 C"duex.fan5" Q250
M106 P2 S255 L255 H-1

M950 F3 C"duex.fan6" Q250
M106 P3 S255 L255 H-1


; TOOLS
; T0
M563 P0 S"Extruder 1" D0 H1 F0 				; define tool 0 - uses extruder 0, heater 1, and fan 0 for partcooling
G10 P0 X0 Y0 Z0 				; set tool 0 axis offsets
;M305 P0 T100000 B3950			; Thermistor type
G10 P0 R0 S0 					; set initial tool 0, active S and standby R temperatures to 0C

; T1
M563 P1 S"Extruder 2" D1 H2 X3 F1 			; define tool 1 - uses extruder 1, heater 2, motor 3 for X axis and fan 2 for partcooling
G10 P1 X0 Y-2.5 Z0 U5.85				; set tool 1 axis offsets(positive numbers = left..... negative numbers = right)
G10 P1 R0 S0 					; set initial tool 1, active S and standby R temperatures to 0C

; T2 - duplication tool
M563 P2 S"Dublication" D0:1 H1:2 F0:2 			; define duplication tool 2 - uses extruder 0 and 1, heater 1 and 2, and fan 0 and 2 for partcooling
G10 P2 X110 Y0 Z0 U-110			; set duplicaiton tool 2 axis offsets - inverse logic - print 110mm to the left with X and 110mm to the right with U
G10 P2 R0 S0 					; set duplication tool initial active-S and standby-R temperatures to 0C
M567 P4 E1:1 					; mixing ratios for extruders. i guess it does not even matter or is even needed

;T3 Laser
M563 P3 S"Laser" X3
G10 P3 L20 X0 Y100 Z0 U100


; Automatic saving after power loss is enabled
M911 S23.00 R23.50 P"M913 X0 Y0 U0 G91 M83 G1 Z2 E-4 F3000" ; Set voltage thresholds and actions to run on power loss

; MISC
M501 							; enable config-override. This is so you have your PID tuning there not here. And other stuff like object model

;Deployprobe
;M42 P0 S1
M280 P0 S10
;G4 P500

`;Retract probe``
;M42 P0 S0
M280 P0 S90
;G4 P500

@oliof said in BIQU microprobe issues:

@Craigrobbo are you saying BLTouch works after separating out the wiring, or Microprobe, or both?

The BLtouch worked when the cables re within the wiring loom and the same when seperated too.

@Craigrobbo said in BIQU microprobe issues:

What should my M950 be?

*edit I replied to the wrong quote sorry!

Sorry, i replied to the wrong quote, I meant to reply to the next one - I did seperate the wiring to mitigate it, also tried an actual BL touch and this works fine

@Craigrobbo said in BIQU microprobe issues:

@jay_s_uk said in BIQU microprobe issues:

@Craigrobbo ok, let's reset. Post the current code you are using.
Also, consider upgrading to 3.5.2

While I have been having a play this evening, I tried your S280 commands again from your guide and this just causes very erratic behaviour, sometimes the probe deploys sometimes it doesn't then sometimes it randomly deploys and retracts on its own...

very strange.

I thought this too, was one of the first things I checked, i isolated the loom but this didnt help, also the results while random are repetable in terms of how it reacts to different commands and the timing of them

@oliof said in BIQU microprobe issues:

@Craigrobbo your probe might pick up electrical noise.

I tried both P5 and P9 as mentioned I am going though different suggestions of code, P5 gives me less erratic results but P9 just sends the machine heywire doing random weird stuff and deploys and retracts on its own.

Its really strange, when in P5 mode the probe detects when its been touched, however in P9 mode it does not p9 makes it randomly deply, but P5 deploys once then never comes back for its second touch and then i get the error (probe already triggered at start of move)

With p9 it just never homes

@Craigrobbo said in BIQU microprobe issues:

@jay_s_uk said in BIQU microprobe issues:

@Craigrobbo ok, let's reset. Post the current code you are using.
Also, consider upgrading to 3.5.2

While I have been having a play this evening, I tried your S280 commands again from your guide and this just causes very erratic behaviour, sometimes the probe deploys sometimes it doesn't then sometimes it randomly deploys and retracts on its own...

very strange.

I thought this but its too consistent when it happens.

@droftarts said in BIQU microprobe issues:

G4 P500

I tried this thank you.

Unfortunately this also does weird things, So it homes, the probe comes out then it retracts on its own before the bed even touches it...

Now for an experiment I tried to touch the probe myself as to mimic a bed home and it just instantly deploys again, and again and will just indefinitely deploy every time i press it in without ever homing...HOWEVER if i let it just randomly retract on its own then it saves the home position... very very very strange.

As for wiring its currently tucked away but I am confident it is right.

I have it wired identical to my BLtouch (which works perfectly if i plug that in, so this confirms my wiring is right)

s for if its a V1 or 2 I m not sure but i bought it about 6 months ago?

What should my M950 be?

*edit I replied to the wrong quote sorry!

@jay_s_uk said in BIQU microprobe issues:

@Craigrobbo ok, let's reset. Post the current code you are using.
Also, consider upgrading to 3.5.2

While I have been having a play this evening, I tried your S280 commands again from your guide and this just causes very erratic behaviour, sometimes the probe deploys sometimes it doesn't then sometimes it randomly deploys and retracts on its own...

very strange.

@jay_s_uk said in BIQU microprobe issues:

@Craigrobbo ok, let's reset. Post the current code you are using.
Also, consider upgrading to 3.5.2

Hi, So As per advice I have upgraded to 3.5.2 - It hasn't fixed the issue but at lest I am now on the latest firmware.

The current code I am using is what I have posted in my very first post, I am open to trying any other suggestions you have.

Thank you for the help

@jens55 said in BIQU microprobe with Duet Maestro:

@yagodajm , I also replaced a BLTouch with a microprobe and ran into a lot of problems before I figured things out. The microprobe uses entirely different commands. Their web site has more info. I will look-see if I can find the details .....

OK, here are the files I changed:

Deployprobe.g:
; the following was for the BLTouch
;M280 P0 S10 ;S10 is the “angle” the PIN is put in to engage.When dealing with BLTouch the engaged position is at angle 10.

; this for the BEQU Micro probe:
M42 P0 S1

........................................................................................

part of my config.g with comments:
; when setting up different probes or end switches the following files (besides config.g) are affected:
; homez.g
; bed.g
; deployprobe.g
; retractprobe.g
; possibly any probing macros

;==============================================
; set up BIQU micro probe
;==============================================

;M950 P0 C"servo0" ; was BLTouch
M950 S0 C"exp.heater3" ; create servo/gpio 0 on heater 3 on expansion connector

;M558 P9 C"^zprobe.in" H3 F60 T6000 A10 R1.25 S0.008 B1 ; was BLTouch
M558 P5 C"^!zprobe.in" H3 F60 T6000 A10 R1.25 S0.008 B1 ; Set Z probe type/mode 9. H=Dive Height. F=Speed probe speed,
; T= speed between probe points, A10 = probe up to 10 times
; R1.25 = allow settlement time, S0.008 = two consecutive probes need
; to be within 0.008 mm,
;M280 P0 S10 ; B1 = turn off heat for the actual probing
; B0 = leave heating on

.....................................................................................................

retractprobe.g:

; the following was for the BLTouch
;M280 P0 S10 ;S10 is the “angle” the PIN is put in to engage.When dealing with BLTouch the engaged position is at angle 10.

;P-number corresponds to our H-number while S defines the “angle” to put the probe into. When dealing with BLTouch the retracted position is at angle 90.

;M280 P0 S90

; this for the BEQU Micro probe:
M42 P0 S0

................................................................................................
I looked at my bed.g and it didn't seem to be changed
I checked my homez.g and didn't notice any specific commands for the microprobe

I can't guarantee that those are the only changes but it will get you going

Hey man,I recently posted issues myself with th same as OP I tried your code and it got me a little further but still having erratic issues.

Did you have any info on your code for the bed.g homez.g etc?

Thnk you!

@jay_s_uk Sorry You're right I was just adhoc typing while I was in bed (been a long day)

But yes the code I posted in my first reply is the code I am currently using,

Unfortunately, its just not working for me and its driving me mad - I am open to suggestions to try

@jay_s_uk said in BIQU microprobe issues:

Thank you - I did follow your guide and of course changed the names accordingly. the probe does "work" and it does register when pressed, however the 2 issues are. Using the M280 codes and setting the probe as a BLtouch in the M950 code then the probe just clicks in and out at random intervals and never really works

If i use M42 commmands and set the M950 to P5 (switch) then it sort of works, it goes to probe, does its first probe then when it tries to do the second slower probe the pin never comes out an I get an error "probe already before move"

So either isnt working for me?

@jay_s_uk

I tried this tutorial at first and the whole thing went heywire, i then followed another post on here and got slightly better results. The M280 command didnt work well at all someone here suggested the M42 command which gave me better results but stilll not right.

As for the M950 command, I think i misunderstand, can you give me the example please?

@jay_s_uk said in BIQU microprobe issues:

@Craigrobbo post your config.g and homing files and board you're using plus the firmware version

HI thank you, I updated the first post.

I did infact find the original post and it got me a little further, Its stopped randomly deploying but now it senses the bed ones then says "probe already triggered at start of move"

HI there, I saw a thread here that i found via google about fixing the erratic behaviour of the biqu microprobe,. I lost the thread and spent the last hour trying to find it.

Any ways when I try to home the probe randomly deploys & retracts , I remember reading somthing about it being an issue withg the PWM pins?

Reprap version 3.3 using Duet2 + Duex5

; Z-Probe
M950 S0 C"duex.pwm5" 

M558 P5 C"^!zprobe.in" H3 F250 T6000 A10 R1.25 S0.008  ; Set Z probe type/mode 9. H=Dive Height. F=Speed probe speed,

;deployprobe.g
M42 P0 S1

;retractprobe.g
M42 P0 S0

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.5 on Sun Nov 07 2021 17:12:53 GMT+0000 (Greenwich Mean Time)
G91               ; relative positioning
G1 H2 Z5 F9000    ; lift Z relative to current position
G90               ; absolute positioning
G1 X0 Y-25 F9000 ; go to first probe point
G30               ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91              ; relative positioning
;G1 Z5 F150       ; lift Z relative to current position
;G90              ; absolute positioning