Strange homing behavior
-
But I still think that there is a difference between homeall.g and homez.g.
I have changed the homez.g a bit. I have now a "run 1" with a "G1 H1" and a little lift of that afterwards. Than the "run 2" with the "G30":
G90 M300 S800 P100 G1 Y155 X155 F6000 ; go to first probe point M300 S300 P300 M400 M600 S800 P500 G91 ; relative positioning ; Run 1 G1 H1 Z-500 F200 ; move Z down until the endstop is triggered G1 H2 Z5 F6000 ; lift Z relative to current position M400 ; Run 2 M558 F60 ; Chriss - set the down speed M600 S800 P2000 ; beep G30 M558 F350 ; Change the speed backStep one get executed whether I call homez.g or homeall.g, but "step 2" produces a:
Error: Z probe already triggered at start of probing moveWHEN I execute it via homeall.g. It works fine when I execute homez.g.
:?
-
@Chriss so homeall sets some precondition which is different from when you call only homez. So need "only" shorten homeall until you find the reason...
-
How have you wired the probe?
Please post your full config.g
G1 H1 Z-500 F200 ; move Z down until the endstop is triggered
Do not use G1 H1. It is for endstop and negates all of the probe settings. -
@JoergS5
Yes, that was my idea too, bit look at it, there is not much to remove without making it completely useless. I need a homed X and Y to move Z.@Phaedrux said in Strange homing behavior:
How have you wired the probe?
I connected it to "zprobe.in", VCC and GND from the same connector. The ir-probe is much more user-friendly than the bl-touch.
I do not expect a problem with the ir-touch itself, it worked more than 99,998% if I use "homez.g"
Please post your full config.g
You will find it at the end.
G1 H1 Z-500 F200 ; move Z down until the endstop is triggered
Do not use G1 H1. It is for endstop and negates all of the probe settings.I changed the config a bit this morning. I have now:
Homez.g
G90 G1 Y155 X155 F6000 ; go to first probe point M400 G91 ; relative positioning ; Run 1 M558 F250 ; Chriss - set the down speed G30 ; Run 2 M558 F60 ; Chriss - set the down speed M600 S800 P2000 ; beep G30 M558 F350 ; Change the speed backAnd homeall.g
G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-315 Y-315 F1800 ; 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-315 Y-315 F360 ; move slowly to X and Y axis endstops once more (second pass) M98 P"0:/sys/homez.g"config.g
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun May 10 2020 08:05:32 GMT+0200 (Central European Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Homer" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S1 ; enable FTP M586 P2 S1 ; enable Telnet ; Drives M569 P0 S0 ; physical drive 0 goes backward M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2:9 E3 ; Chriss - set drive mapping two Z motors connected to driver outputs E6(9) and Z(2) M671 X-28:330 Y155:155 S5.5 ; Chriss - leadscrews at left (connected to E6(9)) and right (connected to E2) of X axis (S=MaxCorrection) M350 E16 I0 ; Chriss - without interpolation M350 X16 Y16 Z16 I1 ; Chriss - configure microstepping with interpolation M92 X80.00 Y80.16 Z400.00 E431.06 ; Chriss - set steps per mm 2560 From Bondtech: E409.51 Original: E137.81 Calulator: ; https://3d-druck-archiv.de/blog/grundlagen-3d-druck/steps-fuer-x-y-z-achse-einstellen-ueberpruefen-247 ; https://selbstgedruckt.de/berechnungstools/ M566 X900.00 Y900.00 Z12.00 E120.00 ; Chriss - set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z800.00 E1200.00 ; Chriss - set maximum speeds (mm/min) Z180 M201 X500.00 Y500.00 Z20.00 E250.00 ; Chriss - set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0:310 Y0:300 ; Chriss - X carriage moves from 0 to 310, Y bed goes from 0 to 310 ; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe IR Probe M558 P1 C"^zprobe.in" H5 F120 T6000 G31 P500 X-26.0 Y-9.0 Z1.85 ; Z-probe location and offset ; M564 S0 to disable axis limits. ;https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe ;M557 X10:270 Y40:270 P10:10 ; Chriss - define mesh grid M557 X10:270 Y40:270 P5:5 ;M557 X10:270 Y40:270 P2:2 ; https://duet3d.dozuki.com/Wiki/Gcode#Section_M557_Set_Z_probe_point_or_define_probing_grid ;; Heaters ;BED 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 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 A245.4 C400.5 D1.3 S1.00 V24.1 B0 ; Chriss - Disable bang-bang, tuned with "M303 H0 S80" ; https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40#s161 M140 H0 ; map heated bed to heater 0 ; Hotend M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; 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 S280 ; set temperature limit for heater 1 to 280C M307 H1 A461.2 C156.1 D3.1 S1.00 V24.0 B0 ; Chriss - tuned with "M303 H1 S250" ;; Fans ; Fan for the printed part: M950 F0 C"duex.fan4" 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 ; Fan for the Hotend; M950 F1 C"duex.fan3" Q500 ; F="create fan 1" C="on pin duex.fan3" Q="and set its frequency" M106 P1 S1 H1 T45 C"Hotend" ; P="set fan 1" S="value" H="Thermostatic control Heater No." T=" is turned on at 45°C" ;; Tools ; Tool 0 M563 P0 S"Extruder" D0 H1 F1 ; define tool 0 (Fan F1 is bonded automatically) G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ;; Filament Sensors - https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_filament-out_sensors ; Sensor 0 M591 D0 P1 C"e0_stop" S1 ; filament monitor connected to E0_stop ;; Misc ; Configure Port for the PaneDuo M575 P1 B57600 S1 ;; EOF -
Do you have a Duex?
M584 X0 Y1 Z2:9 E3Drive 9?
If so, you may want to define it here:; Drives M569 P0 S0 ; physical drive 0 goes backward M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwardsM350 E16 I0No interpolation for the poor extruder?The M140 must come before the M143 for your bed heater.
;BED 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 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 A245.4 C400.5 D1.3 S1.00 V24.1 B0 M140 H0 ; map heated bed to heater 0M600 isn't a beep. It's a filament change pause.
https://duet3d.dozuki.com/Wiki/Gcode#Section_M600_Filament_change_pause; Run 2 M558 F60 ; Chriss - set the down speed M600 S800 P2000 ; beep G30 M558 F350 ; Change the speed backYou'd want M300
https://duet3d.dozuki.com/Wiki/Gcode#Section_M300_Play_beep_soundI'm actually wondering if some of your comments are being parsed strangely. The forum code block gets pretty confused by them as you can see, but when I copied and pasted it into a text editor with gcode highlighting it detected the comments ; correctly. Not sure how the Duet gcode parser could be handling it. Might be worth cleaning up your comments to be rather minimal particularly in the area where the URLs are.
Can you send M558 P1 and G31 and see if it echoes back the same values as in config.g?
-
@Phaedrux said in Strange homing behavior:
Do you have a Duex?
M584 X0 Y1 Z2:9 E3Drive 9?Indeed, I have one and it is connected.
If so, you may want to define it here:
[...]Added
M350 E16 I0No interpolation for the poor extruder?
I had some strange behaviors in the past with the original extruder. That may be different now with the bondtech. Well, I added it. Lets see later how that works now.The M140 must come before the M143 for your bed heater.
[...]Done!
M600 isn't a beep. It's a filament change pause.
[...]You are right, my bad. I wanted to change the frequency, which ended in the "double comand" and not "double frequency". Typo, I removed all of the beeps in the meantime anyway. They where for debug only anyway.
I'm actually wondering if some of your comments are being parsed strangely.
[...]Indeed, that is a very good idea. I removed all the URLs and removed other things like "°". Just in case, that would not be the first time that I have bombed a parser with unexpected characters.
Can you send M558 P1 and G31 and see if it echoes back the same values as in config.g?
Update:
I tested/played a bit with the setup to understand the behavior better.
Let me describe it like that: The "homeall.g" seems to work from time to time when "z" is not far away from the bed surface. But sometimes it drives into the bed.
It seems that it gets triggered in the air only when "z" is more than 10cm away from the bed when I power on the printer. It works or drives into the bed when the head is below 5cm away from the bed.
Did it make myself clear?
Does that makes any sense to you?Cheers, Chriss
-
I thought we would at elast get something back from M558 P1.
Please try sending the full M558 command from your config.g in the console.
I can't remember if I asked before, but can you send M98 P"config.g" and see what you get for errors and messages?
-
@Phaedrux said in Strange homing behavior:
I thought we would at elast get something back from M558 P1.
Please try sending the full M558 command from your config.g in the console.
I did not fully understand what you mean.
I added "M558 P1" at the end of config.g, without any result. I do not see any output of that, nowhere.I tried telnet:
[chriss@leela ~]$ telnet 192.168.1.170 Trying 192.168.1.170... Connected to 192.168.1.170. Escape character is '^]'. M558 P1 okI can't remember if I asked before, but can you send M98 P"config.g" and see what you get for errors and messages?
I guess that you mean "M98 P"0:/sys/config.g""
[chriss@leela ~]$ telnet 192.168.1.170 Trying 192.168.1.170... Connected to 192.168.1.170. Escape character is '^]'. M98 P"0:/sys/config.g" HTTP is enabled on port 80 FTP is enabled on port 21 TELNET is enabled on port 23 Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 270C Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 486C okSo no parsing error if you where aiming for that.
Cheers, Chriss
-
I mean send this in the console
M558 P1 C"^zprobe.in" H5 F120 T6000
G31 P500 X-26.0 Y-9.0 Z1.85And then try your homing.
Though I'm starting to wonder if it's something wrong with the IR probe itself.
-
@Phaedrux said in Strange homing behavior:
I mean send this in the console
M558 P1 C"^zprobe.in" H5 F120 T6000
G31 P500 X-26.0 Y-9.0 Z1.85And then try your homing.
Done, with the same result, the probe get triggered in the air.
Though I'm starting to wonder if it's something wrong with the IR probe itself.
I have to admit that you may be right. I have in total 3 of the ir-probes here. Two for my corexy build and the one in my CR10.
I replaced the one at my CR10 now with a other one. That seems not brand new any more, but it seems to work now. :?
But it is a bit to early for me to blame the bl-touch. I will play a bit more with the new one before I will confirm that the new one is working.And I will put the suspicious probe into the corexy for some tests.
-
Can you explain the homeall.g to me, please?
I'm fully confused now. I removed the "M98" so source the homez.g from the homeall.g. So it looks like that now:; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun May 10 2020 08:05:32 GMT+0200 (Central European Summer Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-315 Y-315 F1800 ; 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-315 Y-315 F360 ; move slowly to X and Y axis endstops once more (second pass) ;M98 P"0:/sys/homez.g"And you know what? The printer homes Z after it homed X and Y. WTF? I added a "beep" into the homez.g to test whether it get executed and not. And the printer beeped when I executed "G28" right after it homed X and Y.
So I think that the homez.g is executed whether I execute it or not.
Is that the expected behavior? -
@Chriss said in Strange homing behavior:
But it is a bit to early for me to blame the bl-touch. I will play a bit more with
Do you mean your "IR probe" is a BLTouch? This would not be an IR probe and is configurated differently.
-
@JoergS5 said in Strange homing behavior:
@Chriss said in Strange homing behavior:
But it is a bit to early for me to blame the bl-touch. I will play a bit more with
Do you mean your "IR probe" is a BLTouch? This would not be an IR probe and is configurated differently.
Ahhhh.. no.. it is a IR-Probe! Not a BL-Touch, I replaces the BL-Touch with the IR-Probe.. sorry for the confusion. Forget the BL-Touch please..... My bad.
-
@Chriss ok - this would be the easist solution
-
@Chriss if you run homeall and the Z is homed unexpectedly: do you have any special files lying around in the sys or macros folder, which could produce this behavior (tool changing, override,...)? To find the reason, you should delete every files and lines which are not needed. (backup all first)
-
Hmmm... maybe but I do not see it, to be honest. I downloaded the content from the sdcard and grepped a bit in the files. The only files I found, which contain "G30" are:
macros/00_Z-Level:G30 P0 X20 Y155 Z-99999; probe near a leadscrew, half way along Y axis macros/00_Z-Level:G30 P1 X250 Y155 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors sys/bed.g:G30 P0 X20 Y155 Z-99999; probe near a leadscrew, half way along Y axis sys/bed.g:G30 P1 X250 Y155 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors Binary file sys/Duet2CombinedFirmware.bin matches sys/homez.g:G30 sys/homez.g:;G30 ; home Z by probing the bed sys/homez.g:;G30I fully understand your approach but I do not see any unexpected file. Or a file which may have it's bits in the cake.
I'm still very confused that the IR probe, which caused all the problems in the CR10, works very, very well in the corexy. :?
Directory listing of the CR10:
ftp> cd macros 250 Directory successfully changed. ftp> dir 227 Entering Passive Mode (192,168,1,170,136,148) 150 Here comes the directory listing. -rw-rw-rw- 1 ftp ftp 641 Mar 12 2019 01-Test_IR_PD_Homing -rw-rw-rw- 1 ftp ftp 640 May 30 2018 02-Test_Fans -rw-rw-rw- 1 ftp ftp 1099 May 24 2018 03-Test_Heaters -rw-rw-rw- 1 ftp ftp 2223 Mar 12 2019 04-Test_motors -rw-rw-rw- 1 ftp ftp 156 Jul 15 2019 SETNETWORK -rw-rw-rw- 1 ftp ftp 434 Jun 07 2020 99_Chriss_Beep -rw-rw-rw- 1 ftp ftp 199 Jul 02 2020 00_Z-Level -rw-rw-rw- 1 ftp ftp 7 Jun 07 2020 Allow Cold Extrude 226 Transfer complete. ftp> cd .. 250 Directory successfully changed. ftp> cd sys 250 Directory successfully changed. ftp> dir 227 Entering Passive Mode (192,168,1,170,162,76) 150 Here comes the directory listing. -rw-rw-rw- 1 ftp ftp 462 Jul 02 2020 bed.g -rw-rw-rw- 1 ftp ftp 4782 Jul 03 2020 config.g -rw-rw-rw- 1 ftp ftp 483 Jun 22 2020 cancel.g -rw-rw-rw- 1 ftp ftp 1329 Jun 30 2020 stop.g -rw-rw-rw- 1 ftp ftp 4772 Jul 03 2020 config.g.bak -rw-rw-rw- 1 ftp ftp 277520 Feb 19 2019 DuetWiFiServer.bin -rw-rw-rw- 1 ftp ftp 3518 May 10 2020 config.json -rw-rw-rw- 1 ftp ftp 60164 May 03 2019 iap4e.bin -rw-rw-rw- 1 ftp ftp 843 Jun 28 2020 pause.g -rw-rw-rw- 1 ftp ftp 481 Jul 02 2020 start.g -rw-rw-rw- 1 ftp ftp 406 May 10 2020 resume.g -rw-rw-rw- 1 ftp ftp 181 May 10 2020 sleep.g -rw-rw-rw- 1 ftp ftp 716 Jul 02 2020 resurrect.g -rw-rw-rw- 1 ftp ftp 168 May 10 2020 tfree0.g -rw-rw-rw- 1 ftp ftp 228 May 10 2020 tpost0.g -rw-rw-rw- 1 ftp ftp 172 May 10 2020 tpre0.g -rw-rw-rw- 1 ftp ftp 126 May 17 2020 test1log.txt -rw-rw-rw- 1 ftp ftp 432 Jun 27 2020 test2log.txt -rw-rw-rw- 1 ftp ftp 354 May 10 2020 test3log.txt -rw-rw-rw- 1 ftp ftp 42 Aug 27 2019 test4log.txt -rw-rw-rw- 1 ftp ftp 506772 May 19 2020 Duet2CombinedFirmware.bin -rw-rw-rw- 1 ftp ftp 277520 Apr 29 2020 DuetWiFiServer-1.23.bin -rw-rw-rw- 1 ftp ftp 944 Jul 03 2020 homeall.g -rw-rw-rw- 1 ftp ftp 567 May 20 2020 homey.g -rw-rw-rw- 1 ftp ftp 210 May 10 2020 deployprobe.g -rw-rw-rw- 1 ftp ftp 566 May 20 2020 homex.g -rw-rw-rw- 1 ftp ftp 983 Jul 03 2020 homez.g -rw-rw-rw- 1 ftp ftp 432 Jun 28 2020 heightmap.csv -rw-rw-rw- 1 ftp ftp 213 May 10 2020 retractprobe.g -rw-rw-rw- 1 ftp ftp 509 Jun 23 2020 config-override.g -rw-rw-rw- 1 ftp ftp 40804 May 10 2020 Duet2CombinedIAP.bin -rw-rw-rw- 1 ftp ftp 3279 Jul 03 2020 dwc2settings.json 226 Transfer complete. ftp> -
@Chriss I can explain my approach: you say when you run homeall, your Z is homed. But homeall doesn't contain any Z movement (only Z5), so there must be anything which makes the Z movement to trigger the signal. So I thought, something automatic like a tool change (tfree, tpost), heating up or something other could trigger the Z movement.
Looking at your files, bed.g could be triggered somehow.
Other possibility: if you run homeall and the X and Y are already in their endstop positions, is there something specific so the IR probe triggers immediately? (is the position of the IR probe outside your bed, e.g.? => could be the case, as X is 26 and Y 9 mm off the nozzle. To try you could position X and Y somewhere in the middle of the bed before calling homeall) And if IR triggers if it is outside the bed, it may be that the probe must be inverted with a ! in the M558 C command and maybe reduce sensitivity value G31 P value.
-
@Chriss said in Strange homing behavior:
And you know what? The printer homes Z after it homed X and Y. WTF? I added a "beep" into the homez.g to test whether it get executed and not. And the printer beeped when I executed "G28" right after it homed X and Y.
So I think that the homez.g is executed whether I execute it or not.
Is that the expected behavior?That's pretty peculiar.
Can you add an M400 before the M98 to call the homez? That should ensure it's finished all the previous X Y homing moves before moving on.
-
Indeed, it is very peculiar. Well, I needed a break, to I used the weekend do work on my fun car, that was bit more promising.
I tested this morning 8-10 times with "G28" and all axes got homed. And this is the homeall.g:
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun May 10 2020 08:05:32 GMT+0200 (Central European Summer Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-315 Y-315 F1800 ; 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-315 Y-315 F360 ; move slowly to X and Y axis endstops once more (second pass) M400 ;M98 P"0:/sys/homez.g"Yes, Z got homed and yes, the beep from the homez.g changed every time I changed it. So there can be no other file involved.
I do not know why but the trigger up in the air went completely away. :? All of my test this morning where successful. Do not ask my why, the only change from last week was a very, very long power cycle.
But it is very odd to see the homing of Z but you know that you do not execute it from homeall.g. :?
Anyway, my main problem, the trigger in the air, is magically gone now. I'm not sure if I want to touch that again or not, it is working for now.
-
Actually I think this is totally normal. Homeall is homing all axis. It completed the homeall.g and the z axis was still unhomed, so it executes home z.
