inductive Z-probe problem after firmware upgrade
-
It shows triggered when it should (gives a value of 1000 when approached with something metal).
Also i kinda solved it, tho im not sure if this is a solution "as intended"
Apparantly i forgot to tell the system to use the probe as a Z-stop.So heres the updated config:
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X300 Y198 Z160 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 S2; Z-Probe
M558 P5 C"^zprobe.in" H5 F120 T6000
;M558 P5 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X28 Y12 Z0.4 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid; Heaters
I added the M574 Z1 S2 line, then needed to slow the home script because of fast aproach
Tell me if im doing this wrong
Next are the heaters, configuring my slicer again, start working with my materials apart from generated G-code.
Enough to do -
@rubinkingma
You shouldn't need the M574 Z1.... Let me look at my config, one moment. -
@rubinkingma
This should be all you need, this is mine:M558 P5 C"^io3.in" H5 F600 T6000 A10 G31 P500 X0 Y25 Z3.6 M557 X15:205 Y25:205 P4Usually the team that scores the most points wins the game.
-
What do you have in your homing files?
@rubinkingma said in inductive Z-probe problem after firmware upgrade:
; Z probe
M558 P5 X0 Y0 Z1 ; Analog Z probe, also used for homing the Z axis
G31 X 28 Y12 Z0.4 P500 ; Set the probe height and threshold (put your own values here)You should remove the old RRF2 commands.
-
Weird, when i dont it complains about "cant enable endstop".
-
Can you paste in your homeall.g and homez.g?
Sorry, what board are you using? Just to confirm the pins.
Usually the team that scores the most points wins the game.
-
Thank you for your reply, what part is RRF2 ?
I got to 3xx firmware today after running 1.19 since 2017Used the configurator and while i could have dropped some old stuff in there looking for solutions i'm not at the point where i can see the difference between old and new config.
-
homeall ( I have been dicking around with this for mesh compensation)
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Mon Sep 19 2022 15:01:08 GMT+0200 (Midden-Europese zomertijd)
;G91 ; relative positioning
;G1 H2 Z5 F6000 ; lift Z relative to current position
;G1 H1 X-305 Y-203 F1800 ; move quickly to X or Y endstop and stop there (first pass)
;G1 H1 X-305 ; home X axis
;G1 H1 Y-203 ; home Y axis
;G1 X5 Y5 F6000 ; go back a few mm
;G1 H1 X-305 F360 ; move slowly to X axis endstop once more (second pass)
;G1 H1 Y-203 ; then move slowly to Y axis endstop
;G1 H1 Z-165 F360 ; move Z down stopping at the endstop
;G90 ; absolute positioning
;G92 Z0 ; set Z position to axis minimum (you may want to adjust this); Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Mon Sep 19 2022 15:01:08 GMT+0200 (Midden-Europese zomertijd)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-305 Y-203 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-305 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-203 ; then move slowly to Y axis endstop
G1 H1 Z-165 F360 ; move Z down stopping at the endstop
G1 H2 Z5 F6000
G90 ; absolute positioning
G1 X150 Y100 F6000
G30 ;probe bed; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioningHome Z
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Mon Sep 19 2022 15:01:08 GMT+0200 (Midden-Europese zomertijd)
G91 ; relative positioning
G1 H2 Z5 F600 ; lift Z relative to current position
G1 H1 Z-165 F1000 ; move Z down until the endstop is triggered (first pass)
G1 Z5 F1000 ; go back a few mm
G1 H1 Z-100 F360 ; move slowly to Z axis endstop once more (second pass)
G92 Z0 ; set Z position to axis minimum (you may want to adjust this); Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
Ah, nevermind about the old config parts. I see now that it's two separate configs. I've edited your post to make it a bit clearer.
Can you send M122 and M98 P"config.g" in the console and copy and paste the results here?
-
M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.2 (2022-09-13 15:11:16) running on Duet WiFi 1.02 or later
Board ID: 08DAM-9K9K2-NGNSN-6J9D6-3S46T-TPSRK
Used output buffers: 1 of 26 (24 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 74924 of which 40 recycled
Never used RAM 13184, free system stack 106 words
Tasks: NETWORK(ready,15.2%,237) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,292) MAIN(running,84.8%,442) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 01:25:43 ago, cause: power up
Last software reset at 2022-09-19 20:21, reason: User, GCodes spinning, available RAM 13256, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x08
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 40.0, current 40.5, max 43.3
Supply voltage: min 24.3, current 24.5, max 24.7, 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
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 31
Driver 1: standstill, SG min 38
Driver 2: standstill, SG min 13
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2022-09-19 21:49:25
Cache data hit count 4294967295
Slowest loop: 8.64ms; 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 0.7ms, write time 24.2ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 1254428ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 883, completed 883, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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: 243.62ms; fastest: 0.07ms
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.27
WiFi MAC address 5c:cf:7f:f7:de:92
WiFi Vcc 3.37, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25864
WiFi IP address 192.168.1.201
WiFi signal strength -77dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0 -
I see the issue.
In the homez.g file change this:
G91 ; relative positioning G1 H2 Z5 F600 ; lift Z relative to current position G1 H1 Z-165 F1000 ; move Z down until the endstop is triggered (first pass) G1 Z5 F1000 ; go back a few mm G1 H1 Z-100 F360 ; move slowly to Z axis endstop once more (second pass) G92 Z0 ; set Z position to axis minimum (you may want to adjust this)to this
G1 X150 Y150 F6000 G91 ; relative positioning G1 H2 Z5 F600 ; lift Z relative to current position G90 G30 -
Your homez.g file is still looking for an endstop. It needs to be changed to use G30 instead of a G1 H1 Z move in order to use the probe.
Your homeall.g is using both an endstop move AND a G30 to probe.
Here are the corrected files
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.3.13 on Mon Sep 19 2022 15:01:08 GMT+0200 (Midden-Europese zomertijd) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-305 Y-203 F1800 ; move quickly to X or Y endstop and stop there (first pass) G1 H2 X5 Y5 F6000 ; go back a few mm G1 H1 X-305 F360 ; move slowly to X axis endstop once more (second pass) G1 H1 Y-203 ; then move slowly to Y axis endstop G90 ; absolute positioning G1 X150 Y100 F6000 G30 ;probe bed; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.3.13 on Mon Sep 19 2022 15:01:08 GMT+0200 (Midden-Europese zomertijd) G90 ; absolute positioning G1 X150 Y100 F6000 G30 ;probe bed -
@phaedrux
Stop replying so fast
But you're right, I missed the homeall.g error.
-
Thanks to you both!
So it works now, this or next week ill start printing again and see what else i can find to complain about.
This used to be my "quick and dirty" machine, and after a few years almost the only machine i use.
I never took the time to really make it print nicely because i had a E3D volcano on it with a 0.8 Nozzle.
Now with all these cool changes i want to dial it in with a 0.6 nozzle and make it a really nice machine.
Its a core XY "hypercube" remix with hiwin rails for the bed.
It should be able to make very nice prints if i just spend some time with it -
Excellent! Happy Printing!
