Posts made by RajaaKahel

@phaedrux Thanks for the link. Never seen this documentation website before.

@phaedrux
Thank you again! now it's doing better after changing the direction of the coordinate to as you mentioned.
Strange that I have never seen a topic explaining the importance of this issue.

@phaedrux
Thanks for the input, I'll modify the firmware so that it uses my endstops as max instead of min. And will change the X&Y offsets to negative. Then I'll test the probing reach.
However I never got a reversed printed part with my current setup (I printed my owen designs and STLs from the internet).
All texts and images are printed correctly.
I'll get back with my configurations and homing files.

@fcwilt Thanks for the input, but again my problem is why it's not reaching the end towards Y max.

@fcwilt The picture I attached shows the movements of my printer. I don't really understand the point of right and left. The firmware should determine the directions based on X min and Y min. The probe is towards X max and Y max. It shouldn't matter right or left as long as the offset is in correct value ( + or -).
In my case X max is on the left in the picture.
Y max is on the front in the picture.

Here's where the it stops (near Y max) but there are like 5-6cm extra on Y.

@fcwilt

In my case, when I'm in front of the printer, X mini endstop is on my right, and the probe is on the other side of the nozzle (my left).
And Y mini endstop is in the back right corner, +Y moves forward towards me.

@fcwilt I understand that it should skip towards mini, but why it's skipping towards max?
My probe is located towards max in both X and Y.

@phaedrux said in Probe reach area:

Are you sure your probe offsets are correct?

Remember, -X should move left, +X should move right
-Y should move to the nozzle to the front of the bed, +Y to the back.

Yes they're correct, but I'm not sure if the X and Y offsets should be positive or negative.

In my case, when I'm in front of the printer, X mini endstop is on my right, and the probe is on the other side of the nozzle (my left).
And Y mini endstop is in the back right corner, +Y moves forward towards me.

I don't really understand where my problem is.
Here are some pictures, notice the I checked the box to flip plate on X on Simplify3D to match the printer setup.

@rjenkinsgb There's still a good distance after the probe in Y, I tried to increase Y distance to even 370, but still it stops reaching way earlier.
What you mean by reducing the grid? Maybe I should increase both max Y limit and max Y for the probe to 370 or more? (The physical Y limit is at 365).

My probe is not able to reach more in Y although I have like 50mm extra free distance in Y. Why is that?

; Axis Limits
M208 X0 Y0 Z-5 S1 ; set axis minima
M208 X420 Y365 Z430 S0 ; set axis maxima

; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H2 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X26.8 Y23.3 Z3.4 ; set Z probe trigger value, offset and trigger height
M557 X0:420 Y12:365 S30 ; define mesh grid

@stephen6309 Ok thanks, then my offsets are correct as they are.

Hi,
My probe offsets are:
X 26.8 (The nozzle is the closer to 0 position/endstop)
Y 23.3 (The nozzle is the closer to 0 position/endstop)
Z 1.5 (the nozzle is in the negative side of the Bl-touch triggering hight)
The issue is that I had to put Z offset in positive value in order to get the nozzle to touch the bed at 0 hight. Does that mean that the logic is inverted and I have to change X and Y offsets to negative value?

G31 P500 X26.8 Y23.3 Z1.5

Thanks for the input, the probe is now working without farther changes.

@phaedrux
I'm making progress, I changed to the following:

; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z0 ; set Z probe trigger value, offset and trigger height
M557 X15:385 Y40:300 S40 ; define mesh grid

And now I'm able to use M401 and M402. When I home Z the sensor trigger and stops the bed. I guess now I should use M401 and M402 manually to deploy and retract before and after each homing and probbing? Or is there an easy way to do that automatically?

@phaedrux

Thanks for the reply!
M401 and M402 does nothing. The Bltouch is lighting red. If I send "M280 P0 S10" the prob deploys, if i touch it Bltouch starts blinking and doesn't respond then.
I disabled the lines you mentioned.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJMSJ-6J9F6-3SD6J-9VPHG
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 75600 of which 0 recycled
Never used RAM 14940, free system stack 184 words
Tasks: NETWORK(ready,13.8%,236) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,364) MAIN(running,85.4%,443) IDLE(ready,0.7%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:02:15 ago, cause: software
Last software reset at 2022-02-13 09:14, reason: User, GCodes spinning, available RAM 14940, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 0
MCU temperature: min 20.9, current 22.1, max 23.0
Supply voltage: min 24.5, current 24.6, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2022-02-13 09:16:25
Cache data hit count 4294967295
Slowest loop: 4.51ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.1ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 157.98ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

• WiFi -
  Network state is active
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.23
  WiFi MAC address 5c:cf:7f:76:63:fc
  WiFi Vcc 3.40, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 19136
  WiFi IP address 192.168.3.20
  WiFi signal strength -76dBm, mode none, reconnections 0, sleep mode modem
  Clock register ffffffff
  Socket states: 0 0 0 0 0 0 0 0

---

M98 P"config.g"
HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is enabled on port 23
Error: Missing Z probe pin name(s)
Error: Invalid Z probe index
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 577C
Warning: Heater 2 appears to be over-powered. If left on at full power, its temperature is predicted to reach 734C

---

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Dec 18 2021 14:22:20 GMT+0100 (Central European Standard Time)
G91 ; relative positioning
G1 H2 Z5 F18000 ; lift Z relative to current position
G1 H1 X-999 F1800
G1 H1 Y-999 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-999 ; home X axis
G1 H1 Y-999 ; home Y axis
G1 X5 Y5 F18000 ; go back a few mm
G1 H1 X-999 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-999 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X15 Y40 F18000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed

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

---

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Dec 18 2021 14:22:20 GMT+0100 (Central European Standard Time)
;G91 ; relative positioning
;G1 H2 Z5 F18000 ; lift Z relative to current position
;G90 ; absolute positioning
;G1 X15 Y40 F18000 ; 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 F300 ; lift Z relative to current position
;G90 ; absolute positioning

; generated by RepRapFirmware Configuration Tool on Tue Jun 05 2018 01:10:26 GMT+0200 (CEST)
G91 ; relative positioning
G1 Z5 F1000 H2 ; lift Z relative to current position
G1 H1 X-450 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 Y-355 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-450 ; home X axis
G1 H1 Y-355 ; home Y axis
G1 X5 Y5 F18000 ; go back a few mm
G1 H1 X-450 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-355 ; then move slowly to Y axis endstop
G1 X50 Y45 F18000 ;
G1 H1 Z-450 F100 S1 ; move Z down stopping at the endstop
G90 ; absolute positioning
G92 Z0 ; set new Z position
G1 Y45 F18000
G1 Z5 F300 H2 ; uncomment this line to lift the nozzle after homing

---

Hi all, I'm getting a headache making my Bltouch 3.1 running on my Duetwifi 2. I followed this guide and connected the Bltouch and made the changes according to it, but when I'm testing it's not working properly.
Note: both my Duetwifi2 and Bltouch3.1 are original.
I want to use Bltouch for homming Z and bed probing.
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Dec 18 2021 14:22:20 GMT+0100 (Central European Standard Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"RK3D Tool Changer" ; set printer name
M669 K1 ; select CoreXY mode

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S1 ; enable FTP
M586 P2 S1 ; enable Telnet

; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes backwards
M569 P4 S0 ; physical drive 4 goes backwards
M584 X0 Y1 Z2 E3:4 ; set drive mapping
M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 E2208.00:2208.00 ; set steps per mm
M566 X900.00 Y900.00 Z30.00 E40.00:40.00 ; set maximum instantaneous speed changes (mm/min)
M203 X30000.00 Y30000.00 Z960.00 E4800.00:4800.00 ; set maximum speeds (mm/min)
M201 X10000.00 Y10000.00 Z50.00 E1200.00:1200.00 ; set accelerations (mm/s^2)
M906 X1100 Y1100 Z1500 E400:400 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X430 Y365 Z430 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S1 P"zstop" ; configure Z-probe endstop for low end on Z

; Z-Probe
M574 Z0 P"nil" ; no Z endstop switch, free up Z endstop input
;M558 P5 C"zstop" H2 F120 T15000 ; Z probe connected to Z endstop input
; set Z probe type to switch and the dive height + speeds
M558 P9 C"^zprobe.in" H5 F120 T6000 ; Duet 2 WiFi/Ethernet, DueX2/5

M950 S0 C"exp.heater3" ; Duet 2 WiFi/Ethernet
M307 H3 A-1 C-1 D-1
M558 P9 H5 F100 T2000
G31 X0 Y0 Z0 P25

G31 P500 X0 Y0 Z0 ; set Z probe trigger value, offset and trigger height
M557 X15:385 Y40:300 S40 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; 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
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
M308 S1 P"e0temp" Y"thermistor" T100000 B3950 ; 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
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
M308 S2 P"e1temp" Y"thermistor" T100000 B3950 ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2
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 H1:2 T45 ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 S"Left0.6mm" D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z-1.7 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
M563 P1 S"Right0.4mm" D1 H2 F0 ; define tool 1
G10 P1 X0 Y0 Z-1.8 ; set tool 1 axis offsets
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C

; Custom settings are not defined
M501

---

; config-override.g file generated in response to M500 at 2021-12-18 18:15
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 R0.236 C321.589:321.589 D3.52 S1.00 V24.5 B0 I0
M307 H1 R3.055 C180.783:180.783 D6.59 S1.00 V24.5 B0 I0
M307 H2 R2.831 C250.719:250.719 D8.02 S1.00 V24.5 B0 I0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

deployprobe.g
1
M280 P0 S10

retractprobe.g
1
M280 P0 S90

@engikeneer Thank you, it makes sense!
I got it to probe successfully now. And trying to figure out why it not compensation well. I see the Z motor moving tho. But still a bed corner got squished wide line and another corner is too thin.

@Phaedrux

What do you have for a probe now?
Do you actually use a z endstop, or just the probe?

The probe is a DIY switch, it's a Z endstop and a probe at the same time.

You currently have a z endstop defined with M574 using zstop pin and the probe with M558 also using the zstop pin. If you don't want to use a z endstop at all, just don't define one in the first place.

I want to use my DIY switch as a probe and it's probing fine, but my problem is with dive and trigger heights.

What firmware version are you using?
V3.3.

It shows your trigger height as -5, how did you come to that? I would think that it would make more sense to set G31 X0 Y0 Z0 and then use the tool offsets to define where the nozzle tip is in relation to that 0,0,0 point.
That trigger height is just from the configuration tool, wasn't sure what to choose/do first.

Since you need the tools docked before you can do a mesh, you might be nest served by creating a mesh.g file in the system folder. In it you could define exactly what you wanted to happen before doing the mesh. Set the bed temps, wait, deselect all tools, and then send G29 S0 to mesh the bed.

That's good to know!
I'll try to read the documentation again from the beginning, hopefully i get the things in the right order.
Thanks for the input

@dc42
Can you guide me please to get started?