IR Probe issue after 3.1.1 update from 3.0
-
Just installed 3.1.1 update from 3.0 Duet2wifi with IR Probe, worked fine with 3.0 but now wont get triggered
previously had BLtouchCoreXY machine
; Z-Probe M950 H3 C"nil" ; Disable heaters h7 to free up pins M558 P1 C"^zprobe.in" H5 F800 T2000 ; set Z probe type M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch G31 X0 Y-40 Z2.65 ; Z probe trigger offset, high Z number closer means to bed (LARGER Z MEANS CLOSER BED) M557 X10:290 Y10:290 S25 ; define mesh grid; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v2.1.5 on Wed Jan 08 2020 19:38:55 GMT-0500 (Eastern Standard Time) M400 ; make sure everything has stopped before we make changes G91 ; use relative positioning G1 H2 Z20 F6000 ; lift Z relative to current position G1 H1 Y-350 F3000 ; move quickly to Y axis endstop and stop there (first pass) G4 P500 ; wait 500msec M400 ; make sure everything has stopped before we make changes G1 Y0 ; move away from home G4 P500 ; wait 500msec G1 H1 X-350 F3000 ; move quickly to X axis endstop and stop there (first pass) G4 P500 ; wait 500msec M400 ; make sure everything has stopped before we make changes G90 ; back to absolute positioning G1 X150 Y150 F3000 ; Centre Print head G30 G1 X0 Y0 F2000 ; Head To Origin -
@Adamfilip Is it a Duet IR probe, or something else? You shouldn't need to invert the Z-probe pin. You also don't need these two lines:
M950 H3 C"nil" ; Disable heaters h7 to free up pins M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouchAlso:
M558 P1 C"^zprobe.in" H5 F800 T2000
F800 (13.33mm/s) is VERY fast for probing, I'm not sure you'll get very repeatable results. Try F200. You can speed up the travel speed 'T' if you want.Finally,
G31 X0 Y-40 Z2.65: you've got quite a Y offset. You may find that any rotation of the X carriage around the X axis magnifies the probe movement, and doesn't represent the height of the nozzle off the bed. It's better to put the probe physically in line with the nozzle in the X axis, if possible, so Y offset is 0, with an X offset.My config for a Duet IR probe, on a Cartesian bed-slinger:
; Z-Probe M558 P1 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X20 Y0 Z1.25 ; set Z probe trigger value, offset and trigger height M557 X-85:85 Y-85:85 P5 ; define mesh gridIan
-
Thanks for the info. removing those lines fixed the issue.
I also slowed it down as you suggested.I am unable to move the probe location. just isnt convenient for my machine
-
finding the Duet IR Probe is being less reliable detecting a surface then it was with 3.0. I just ran grid mesh, and it did a few probings then gave me an error.. Z probe was not triggered. im using a build tak black surface. never caused me an issue before. not sure if it matters but the Sensor Zprobe shows a value of 88 when not near surface and 400-500 when probing
-
@Adamfilip said in IR Probe issue after 3.1.1 update from 3.0:
finding the Duet IR Probe is being less reliable detecting a surface then it was with 3.0. I just ran grid mesh, and it did a few probings then gave me an error.. Z probe was not triggered. im using a build tak black surface. never caused me an issue before. not sure if it matters but the Sensor Zprobe shows a value of 88 when not near surface and 400-500 when probing
Check that you are using "zprobe.in" as the port name in the M558 command, not "^zprobe.in".
-
Hmm I made that adjustment. ("zprobe.in")
unfortunately its still giving me probing issues, not detecting reliably now; Z-Probe M558 P1 C"zprobe.in" H5 F200 T2000 ; set Z probe type G31 X0 Y-40 Z2.65 ; Z probe trigger offset, high Z number closer means to bed (LARGER Z MEANS CLOSER BED) M557 X10:290 Y10:290 S25 ; define mesh gridWhen I watch it do the probing the light comes on. but it still plunges down farther
-
You have no P value in your G31 command, which could be part of the problem. The correct value for the IR sensor is P500. Alse check that you don't have a G31 command in config-override.g, or another one in config.g.
What readings do you get from the Z probe now? It should be very close to 0 when the probe is not triggered, about 465 when it is close to being triggered, and about 535 when it is triggered and the LED is on.
-
Revised
; Z-Probe M558 P1 C"zprobe.in" H5 F200 T2000 ; set Z probe type G31 X0 Y-40 Z2.65 P500 ; Z probe trigger offset, high Z number closer means to bed (LARGER Z MEANS CLOSER BED) M557 X10:290 Y10:290 S25The Z probe reading fluctuates alot.. when machine is idle.. 80-100 typical, not close to zero..
last time i tried. it homed fine once. but when i tried to do Grid compensation. it failed on third probingnothing is congfig overide related
-
It does give off 4 flashed during start up
-
Clean the sensor with a cotton bud and some IPA?
-
I Cleaned the sensor and its still glitching.
after updating firmware, its not working reliably.. -
Not sure what else to try.. its not working
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v2.1.5 on Wed Jan 08 2020 19:38:55 GMT-0500 (Eastern Standard Time) M400 ; make sure everything has stopped before we make changes G91 ; use relative positioning G1 H2 Z20 F6000 ; lift Z relative to current position G1 H1 Y-350 F3000 ; move quickly to Y axis endstop and stop there (first pass) G4 P500 ; wait 500msec M400 ; make sure everything has stopped before we make changes G1 Y0 ; move away from home G4 P500 ; wait 500msec G1 H1 X-350 F3000 ; move quickly to X axis endstop and stop there (first pass) G4 P500 ; wait 500msec M400 ; make sure everything has stopped before we make changes G90 ; back to absolute positioning G1 X150 Y150 F3000 ; Centre Print head G30 G1 X0 Y0 F2000 ; Head To OriginConfig
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.5 on Wed Jan 08 2020 19:38:55 GMT-0500 (Eastern Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"TitanXY" ; set printer name M667 S1 ; select CoreXY mode ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S0 ; physical drive 0 goes backwards M569 P1 S0 ; physical drive 1 goes backwarsa M569 P2 S0 ; Z physical drive 2 goes backwards M569 P3 S1 ; Extruder physical drive 3 goes Forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X32 Y32 Z32 I0 ; configure microstepping without interpolation M350 E16 I1 ; configure microstepping with interpolation M92 X400 Y400 Z1593 E409 ; set steps per mm M566 X600 Y600 Z20 E800 ; Set maximum instantaneous speed changes (mm/min) M203 X9000 Y9000 Z1500 E10000 ; Set maximum speeds (mm/min) M201 X1000 Y1000 Z250 E5000 ; Set accelerations (mm/s^2) M906 X1200 Y1200 Z1500 E1300 I30 ; Set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout M572 D0 S0.15 ; Pressure Advance ; Set idle timeout ; Axis Limits M208 X-7 Y-22 Z0 S1 ; set axis minima M208 X312 Y331 Z300 S0 ; set axis maxima ; Endstops M574 X1 S1 P"xstop" ; X min active high endstop switch M574 Y1 S1 P"ystop" ; Y min active high endstop switch ; Z-Probe M558 P1 C"zprobe.in" H5 F200 T2000 ; set Z probe type G31 P500 X0 Y-40 Z2.65 ; Z probe trigger offset, high Z number closer means to bed (LARGER Z MEANS CLOSER BED) M557 X10:290 Y10:290 S25 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M140 H0 ; Map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 A61.9 C160.5 D1.3 B0 S0.5 v24.4 ; disable bang-bang mode for the nozzle heater and set PWM limit M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M143 H1 S285; set temperature limit for heater 1 to 280C M307 H1 A310.2 C150.5 D3.5 B0 S1 v24.3 ;NEW ;M307 H1 A493 C243 D3.9 B0 S0.9 v24.3 ; disable bang-bang mode for the nozzle heater and set PWM limit ; 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 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan1" Q500 ; create fan 2 on pin fan1 and set its frequency M106 P2 S1 H1 T45 ; set fan 2 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined -
probe reading fluctuates alot.. when machine is idle.. 80-100 typical, not close to zero..
-
Is this a Duet IR sensor or a clone? Was it purchased recently?
-
its a Duet sensor.. not clone. purchased 4 months ago
-
I reduced the trigger value from 500 down to 400 and it seems to be working again. before updating firmware it worked fine at 500
-
@Adamfilip said in IR Probe issue after 3.1.1 update from 3.0:
I reduced the trigger value from 500 down to 400 and it seems to be working again. before updating firmware it worked fine at 500
Is it working better now?
-
no, I spoke too soon!
It does trigger more consistently but its all over the place now
l) -
Should i use M558 P2 instead of P1?
-
I ran a Mesh compensation sequence and I noticed that when it was probing. While watching the Z probe values.. sometimes the Probe value was around 100 between probings and other times it was zero.. makes me wonder if there is a wire issue
