#Sensorless homing leviathan_v1.2
1 messages · Page 1 of 1 (latest)
Query_endstops do any of them show as triggered?
@ruby steeple
@fringe vault Yes, both entrostops are always triggered
how high is your sensitivity?
so driver_sgt
driver_sgt: 2
i found that the nitehawk-sb.cfg for the toolhead board had the endstop_pin defined for x and y
removed the config
now it looks like the _HOME_X macro is not runnig correcly and the motor is going full power. It triggers on 2 and fails on 1 (no movement)
do i need to explicitly setup a [homing_override] to call the _HOME_X and _HOME_Y macros?
yes
Thanks ill do that later this evening and let you know
it's working perfectly, I've lowered the run current will homing to just 0.6A and the bump isn't even audible
Thanks
Pedro
i need help with this too . didnt think it would be smart to just create a new thread
This is all in my writeup, macros and and all afaik.
I looked i didn't see any reference to the leviathan 1.2 board.
process is stil lthe same
I have the tmc auto tuned as well. But I also don't know how to tell what tmc my A and B drivers are...
I'll look again. And see what I missed... also the macros do not show up on the dashboard
Oooh wow I found the write up and reading now you mention the sorority thing. Is this the same if my tmc is 5160? The sg4_thrs?
I'm not even sure if I'm putting in the right tmc. I left them the way the sample printer config came. I looked up how to find that info out and I may not have understood
(I noticed that there's different inputs for 2209 and 5260) so I fear I have the wrong one in
its one of two things for the name of the driver
Nvm I found the info the drivers are 5160
The Zs are 2209
So in the macros o have to change the names to match tmc5160 stepper_x and so on so that the voltage changes
kalico? ill look into it. sounds like ill start from scratch again
look in my github, in my profile here, for a 2.4 and a v0 config using it. its so much easier. i have a writeup to switch to kalico too
thank you ill give it a try
thank you i think kalico helped and using the "use_sensorlesshoming" worked out. mine are set to 0. so far so good now on the getting beacon to work
i have that in my 2.4 config as well
maybe you can help me with that... i have the usb plugged into my pi and when i query endstops it comes up as triggered.....
yes
it has an ID and everything i already put those in
then you should be doing the beacon initial startup to see if its triggering etc
i assume you updated to latest firmware
using moonraker or my computer?
"beacon_calibrate"?
whatn iinitial start up? im just following the site and when i get to the calibrate part it doesnt move down it triggers and says to tune the nozzle tip but its so far away from the bed
Proceed through a standard nozzle paper offset test, repeating
TESTZ Z=-0.01
or similar until the paper drags.
you can certainly make z drop by 1mm but be careful
z=-1 then use -0.1 later
yea but it is so high that it wont move down because it says its out of range
also i just did a home
and it says No Beacon model loaded
you havent done one yet
did you do these?
- Configure Kalico / Klipper for Beacon¶
[stepper_z]
endstop_pin: probe:z_virtual_endstop # use beacon as virtual endstop
homing_retract_dist: 0 # beacon needs this to be set to 0
remove probe, add beacon, etc
i did this......
min position is 0
i followed all tha stuff there
m112 yes.
-5 should help
is the red light on?
there is a light on beacon for when it senses metal
it hsould be off and as it drops it will light up, so you know it sees the bed
i assume you have a build plate on
no light im going to turn it off replug it and see
its off... but it doesnt come on when i move it to the plate either....
also when i query the endstops the z axis says triggered
its working now. i see i had to bring it low first then set the height then let it run
Ah nice. Good to hear.
thank you for your patience
ok so i ran into a huge issue.
i got everthing setup. but if i home Z first instead of all or x and y. it will run to top right corner and crash and then go down to home z (since no metal in that far corner it just keeps going)
so my question is how do i force a x and y home if there is non saved at the time of homing z?
i wouldnt lol but just in case i make a mistake and code it into something by accident. or press the macro.
ok is there a way to set it so that it wont work at all unless i home x and y first? i want to make it mistake proof a little
I never tried it. If it's told to home in middle of bed it should never just home where it is.
That should be the default behavior. If yours allows a Z home without homing X and Y first, then there is an issue with your homing override.
Maybe post a klipper log file. We can check it over.
ok nvm i found the correct overide i think i must have messed the one the @tulip raven had in his write up some where... it wont let me home z now without homing x and y now. i knew that was odd.