Need help to config this probe
-
Changed that line = still works like the other and no G30
-
@tecno only probe types 8 and 9 are supported on toolboard. Use type 8 for IR probe. See https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Mini_differential_IR_sensor_by_dc42
Also, don’t think you need to invert probe with ! (exclamation mark). And connect to 3.3, not 5V. See https://duet3d.dozuki.com/Wiki/Duet_3_Tool_Board
Ian
-
OK done that but still G30 error
I can not find anything in gcode files to be edited. From where comes Z probe 0 ?
Anything missing in my config.g ?Cheers Bengt
-
@tecno have you tried, M280 P0 S10 ; deploy BLTouch and M280 P0 S90 ; retract BLTouch
Have you got a deployprobe.g and a retractprobe.g ? -
This IR Probe fixed nothing moving here
-
@tecno you set the probe number with the K parameter in M558. If undefined it defaults to probe 0.
-
Tried K0 K1 K2 still the same error
-
@tecno please post your current config.g, response to M122, and check your toolboard firmware version matches your mainboard version. And show a picture of your wiring.
Ian
-
probe works running home all but I can not calibrate
-
@tecno Please send
M122 B121
, post your homeall.g, and if possible post pictures of the IR probe wiring on the Toolboard.In your config.g:
M584 X2 Y1 Z3:4 E0 ; set drive mapping
You aren't using the toolboard extruder?
M574 X1 S1 P"!^121.io2.in" ; configure active-high endstop for low end on X via pin ^io3.in M574 Y1 S1 P"!^io0.in" ; configure active-high endstop for low end on Y via pin ^io0.in M574 Z1 S1 P"!!121.io1.in"
You don't need to enable pullup resistors (with ^ character) on X and Y, only Duet 2 using 'probe.in' need it.
On Z, this may be conflicting with the probe, change this toM574 Z0 S2
. This may cause your Z homing not to work, depending on how homeall.g and homez.g are configured. I expect these are not using G30 to home at the moment.; Z-Probe M558 C"121.io1.in" P8 H3 K2 F120 T6000 ; G31 P50
Use
K0
or leave the K parameter out entirely. If you really want to set the probe number, and set it to K2, then useG30 K2
when probing.M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 ... M308 S1 P"121.temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
You're using the RRF configuration tool's default thermistor. Find out what thermistors you actually have and update these lines for more accurate temperature readings.
Ian
-
Good morning Ian,
I am not using the toolboard extruder, bowden to get as light printhead as possible on my Chiron.Made the changes to M574, not working on Z lifts up Z and error Homing failed
M558 no K
M308 both work but how accurate Bed is Anycubic original and Hotend I do belive this is E3DV6 sold by them.
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat May 01 2021 17:31:12 GMT-0700 (Pacific Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-405 Y-405 F3000 ; 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-405 Y-405 F240 ; move slowly to X and Y axis endstops once more (second pass)
G1 H2 X200 Y200 F3000
G1 H1 Z-455 F240 ; move Z down stopping at the endstop
G90 ; absolute positioning
G92 Z 1.35 ; set Z position to axis minimum (you may want to adjust this) ||||||||| tested 1.35 measured with slip gauges G1 Z0 goes down to bed with paper |||||||||
So this is where probe triggers.; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon May 10 2021 11:46:07 GMT+0200 (centraleuropeisk sommartid)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Z-455 F1800 ; move Z down until the endstop is triggered
G92 Z1.35 ; set Z position to axis minimum (you may want to adjust this)M122 B121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.3RC2 (2021-05-11 14:59:50)
Bootloader ID: not available
Never used RAM 4088, free system stack 0 words
Tasks: Move(notifyWait,0.0%,153) HEAT(delaying,0.2%,81) CanAsync(notifyWait,0.0%,66) CanRecv(notifyWait,0.0%,79) CanClock(notifyWait,0.0%,66) TMC(delaying,2.8%,57) MAIN(running,92.0%,339) IDLE(ready,0.0%,40) AIN(delaying,4.9%,62), total 100.0%
Last reset 00:15:19 ago, cause: power up
Last software reset time unknown, reason: AssertionFailed, available RAM 4592, slot 1
Software reset code 0x0120 ICSR 0x00000000 SP 0x20003cac Task Freestk 130 bad marker
Stack: 00000544 00023174 00019cb5 20003044 00016e33 20003044 00016505 20000ed0 00000000 00000001 0000828d 200071c8 200071c8 200071e0 00000000 20000f50 000116b3 00022530 000225e8 00021c40 00019c55 200071c8 200071c8 20000f50 00008405 200071d8 000009c6
Driver 0: position 0, 80.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 973, writes 9, timeouts 0, DMA errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 7, peak Rx sync delay 522, resyncs 2, no step interrupt scheduled
VIN: 24.6V
MCU temperature: min 18.0C, current 31.0C, max 31.1C
Ticks since heat task active 247, ADC conversions started 915818, completed 915817, timed out 0, errs 0
Last sensors broadcast 0x00000002 found 1 2 ticks ago, loop time 0
CAN messages queued 11066, send timeouts 0, received 8292, lost 0, free buffers 36, min 36, error reg 0
dup 0, oos 0, bm 0, wbm 0
Accelerometer detected: no
I2C bus errors 4619, naks 4619, other errors 4619Cheers
Bengt -
I think I´ve got it working sort of.
homeall.g
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-405 Y-405 F3000 ; 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-405 Y-405 F240 ; move slowly to X and Y axis endstops once more (second pass)
G90
G1 H2 X200 Y200 F3000
G30; Z-Probe
M558 C"121.io1.in" P8 H10 F120 T6000 ;
G31 P50 X0 Y-36 Z1.35
M557 X15:400 Y15:400 S20 ; define mesh gridHope this will others having this promblem
Big thanks to the crew