BIQU microprobe issues

Craigrobbo

@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"

jay_s_uk

@Craigrobbo you should be setting up with "P" in M950 and not "S".
We have some info about the microprobe here.
https://teamgloomy.github.io/fly_e3_pro_v3_bltouch_3_5.html#micro

I would also suggest upgrading your firmware to 3.5.2

Craigrobbo

@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

@Craigrobbo M950 P0 C"duex.pwm5"
Not
M950 S0 C"duex.pwm5"

And of course following that link above you have to use the right pin names for your board (and just to be clear, I wrote that guide when I was part of the beta testing of the microprobe for BTT

Craigrobbo

@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

@Craigrobbo who said anything about M950 P5?
I think you need to look at the gcodes dictionary as you're confusing M950 and M558

Craigrobbo

@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

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

Craigrobbo

@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

Craigrobbo

This post is deleted!

Craigrobbo

@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.

oliof

@Craigrobbo your probe might pick up electrical noise.

jay_s_uk

@Craigrobbo as I've already said, your M950 command is wrong. You also don't use M280 but M42. Make sure you're reading the info for the microprobe and not the bltouch!

droftarts

@Craigrobbo Make sure you're clicking on the 'BTT MicroProbe' tab on this page: https://teamgloomy.github.io/fly_e3_pro_v3_bltouch_3_5.html#micro
And make sure you know whether you have a V1 or V2 MicroProbe; I'm assuming it's a V2.

As @jay_s_uk pointed out, your configuration is wrong. You have:

; 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,

It should be

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

Also, add the G4 P500 pause to deployprobe.g and retractprobe.g:

;deployprobe.g
M42 P0 S1
G4 P500

;retractprobe.g
M42 P0 S0
G4 P500

Don't use M280 to deploy or retract the probe. If it still doesn't work, post pictures of your wiring at each end.

Ian

Craigrobbo

What should my M950 be?

*edit I replied to the wrong quote sorry!

oliof

@Craigrobbo that's got nothing to do with the configuration, but how your wires are run; i.e. if they run close to motor wires for a longer section. Best to try and get rid of that by either rerouting the wiring or by adding a ferrite bead.

Craigrobbo

@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?

Craigrobbo

@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

@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

Craigrobbo

@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