Not homing in correct direction.
-
@BattleDroid said in Not homing in correct direction.:
When you say high end low end.
Consider an axis with min position of 0 and max position of 300. Low end is the 0 end, high end is the 300 end.
So That being said my endstops are on the low end on both my x and y. And i should change (m574 X2) to (m574 X1). Correct?
Yes
Then in my home (all)(x)(y) config change the positive values to negative values. Which should change the direction?
Homing is toward the end stop. If they are at the low end the G1 H1 moves will have negative values, the G1 move will have a positive value.
Frederick
-
Thank you for confirming. So I changed the high end low end. And set the values to negative. And I cant believe it was that much of a hassle for me for that easy of a fix. I believe I have changed those values before but most likely not both together. Which now kinda makes sense why I was getting the endstop errors. But now I kind of have a better understanding of that. Thank you guys. It is now homing correctly. I will now move on to see if I can get the bl touch to work correctly, that I am also fishing in the dark with.
But as for my other problem. I sent M303 H0 S60. It is now tuning the bed. After it tunes (its been going for about 5-10 mins now) assuming it is good I am to Send M500 to save. Then what is M501? Just to load those parameters when it goes to heat up? Also where at the end of my config should I add M501? Just right at the end?
Also what is a bed slinger? lol
-
@BattleDroid said in Not homing in correct direction.:
Then what is M501? Just to load those parameters when it goes to heat up? Also where at the end of my config should I add M501? Just right at the end?
M500 creates (or updates) a file config-override.g and in that file are certain commands. Among them are the commands that reflect the results of the heater tuning operation(s).
M501 goes at the very end of your config.g file. In essence it causes the config-override.g file to be treated as a continuation of config.g, thus executing the commands that are in config-override.g.
Now you don't have to use M501 - you can - if you wish - simply copy the contents of config-override.g into your config.g file at the appropriate locations.
Also what is a bed slinger? lol
It's the type of printer that moves the bed back and forth along the Y axis and moves the X gantry up and down along the Z axis.
There are many others types.
Frederick
-
Ah, gotcha. That makes sense now. Thank you. You guys have been super helpful. I just closed about 30 tabs since those questions have been solved for me. haha
I am now trying to see if I can get the probe to work. I am googling how to change the mesh grid(?) when it probes. I noticed when it first tried to probe it wasn't quite on the bed. I am assuming its coordinates on the m557 line. Still searching. The other thing I have to find is why it doesn't deploy the probe when it starts homing. It is lit up, it will kick in and out when I turn the printer on. But I need to find what I change to make it deploy when it goes to home.
-
@BattleDroid said in Not homing in correct direction.:
Ah, gotcha. That makes sense now. Thank you. You guys have been super helpful. I just closed about 30 tabs since those questions have been solved for me. haha
I am now trying to see if I can get the probe to work. I am googling how to change the mesh grid(?) when it probes. I noticed when it first tried to probe it wasn't quite on the bed. I am assuming its coordinates on the m557 line. Still searching. The other thing I have to find is why it doesn't deploy the probe when it starts homing. It is lit up, it will kick in and out when I turn the printer on. But I need to find what I change to make it deploy when it goes to home.
Do you have a deploy probe and retract probe script? M401 should deploy it and M402 retract. I was in a very similar position to you just the other week so this is all very fresh and familiar for me!
-
I cant say if I do or not. I did try the M401 and M402 commands which didn't seem to do anything. So I assume not? I will try to look into this more.
-
@BattleDroid said in Not homing in correct direction.:
M558 P1 C"zprobe.in+zprobe.mod" H5 F120 T6000
If you're using a BLTouch this line is not correct.
Instead you would need
; Z-Probe BLtouch M950 S0 C"PINNAME" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H5 F200 T6000 ; set Z probe type to bltouch and the dive height + speedsThe PINNAME part would be the name of the pin you are using for the servo connection. Usually heater pin 3 or 7 on the expansion header. Which are you using?
exp.heater3for exampleThen you would need 2 macro files in /sys folder called deployprobe.g and retractprobe.g
They would contain the servo commands to deploy and retract the pin.
M280 P0 S10 ; deploy BLTouchM280 P0 S90 ; retract BLTouchThen when you send M401 or M402 the pin should deploy and retract if it's working correctly.
Then to probe Z you'd need to have a G30 at the center of your bed to use the probe to set Z0. Post your homeall if you're unsure.
-
*** deleted ***
-
@Phaedrux
Sorry thats alot to take in at once. I appologize for being slow. I am using heater pin 3.Here is my homeall while I re read that again.
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.2 on Sat Jan 23 2021 15:36:11 GMT-0600 (Central Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-375 Y-255 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X-5 Y-5 F6000 ; go back a few mm
G1 H1 X-375 Y-255 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X15 Y15 F6000 ; 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 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
@BattleDroid said in Not homing in correct direction.:
G1 X15 Y15 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bedThe homeall is correct, but you should change the X15 Y15 to be a position that places the probe at the center of the bed.
-
Ok i will change that.
Does this seem more correct now in my config?
; Z-Probe BLtouch
M950 S0 C"heater3" ;create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F200 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z2 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y45:195 S20 ; define mesh grid -
Also I was messing around with the mesh settings there on the x andy, im changing them more to the center right now.
Edit i think i just realized thats describing the dimensions of where i can probe.
-
@BattleDroid said in Not homing in correct direction.:
M950 S0 C"heater3" ;create servo pin 0 for BLTouch
Almost. the pin name is
exp.heater3Also don't forget to set the XYZ offset of the probe from the nozzle in G31
G31 P500 X0 Y0 Z2 ; set Z probe trigger value, offset and trigger height
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
-
Ok, in relation to that. Do I use how far the probe is from the nozzle? or Nozzle from the probe?
Example: I used
G31 P500 X24.1 Y21.4 Z-4.5 ; set Z probe trigger value, offset and trigger height. The probe being closer to the front of the nozzle(+), and to the right (+).Edit, I just seen the link you added after I replied, reading through that now.
-
Ok reading that, and going back a bit here. Before I can test and calibrate I believe I need to get the probe to retract properly first. I do have both of those macro files in /sys. When I send m401 and m402 nothing seems to happen. Same if I send M280 P0 S10. When I first supply power to the board turning the printer on the probe will deploy and retract twice.
I read through the BLtouch wiki a couple times now, but I believe we covered most of that here already, the labeling for the BLtouch and whatnot. I'm not sure where to look next. Aside from my probe in/out files. Do I need an additional m280 code in the config.g file? -
Hi,
Are you connecting the BLTouch to the 50 pin expansion connector on the Duet 2 or to a Duex 2/5 board?
Frederick
-
@fcwilt
Hello,Yes I do have it connected to the 50 pin expansion. 1) +5v 2)GND 8)Heater3 and then connected to zprobe pins: z probe in and ground. Basically just how the wiki shows. I am using duet 2 board.
-
@BattleDroid said in Not homing in correct direction.:
@fcwilt
Hello,Yes I do have it connected to the 50 pin expansion. 1) +5v 2)GND 8)Heater3 and then connected to zprobe pins: z probe in and ground. Basically just how the wiki shows. I am using duet 2 board.
OK if the probe self tests on power up you've got the +5 and GND connections right.
That leaves the Heater 3 connection - double check just to be sure.
Also try to verify if whatever you are using for an extension cable has continuity from end to end for that connection.
M280 P0 S10 should deploy and M280 P2 S90 should retract.
I believe that M280 P0 S160 initiates self test - you could try that.
Frederick
-
Can you check your firmware version? Send M115
Should be 3.2
Also send M98 p"config.g" and report what it says.
Did you change that pin name to exp.heater3?
Photo of the wiring?
If you send those m280 commands in the console do they make the pin go in and out?
-
I have tried all 3 of those commands for it not to do anything. Just gives me a good green signal at the bottom. I will double check that connection.
Sending m280 commands also leads to nothing moving, just a green bar with it in console.
I did change that pin name to exp.heater3.FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-05-19b2
M98 p"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 203CIll try to figure out a photo of the wiring here. Hopefully it works.
