#Sensorless homing leviathan_v1.2

1 messages · Page 1 of 1 (latest)

ruby steeple
#

I'm trying to setup Sensorless homing on my voron 2
I'm using a leviathan board from LDO..
I can't get the toolhead to move X or Y, it all ways Homes in the current position, independent of the value i use in the driver_SGT: -64 to 63

fringe vault
#

Query_endstops do any of them show as triggered?

summer fox
#

@ruby steeple

ruby steeple
#

@fringe vault Yes, both entrostops are always triggered

summer fox
#

so driver_sgt

ruby steeple
#

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?

ruby steeple
ruby steeple
#

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

lean bay
#

i need help with this too . didnt think it would be smart to just create a new thread

tulip raven
#

This is all in my writeup, macros and and all afaik.

lean bay
#

I looked i didn't see any reference to the leviathan 1.2 board.

tulip raven
#

process is stil lthe same

lean bay
#

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...

lean bay
tulip raven
#

they generally wont. they start with _

#

but you can type em

lean bay
#

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

tulip raven
#

its one of two things for the name of the driver

lean bay
#

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

tulip raven
#

yep.

#

or use kalico and all that pain goes away, no more macros at all

lean bay
tulip raven
#

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

lean bay
tulip raven
#

i have that in my 2.4 config as well

lean bay
tulip raven
#

what is it

#

does beacon show up in lsusb

lean bay
#

yes

lean bay
tulip raven
#

then you should be doing the beacon initial startup to see if its triggering etc

#

i assume you updated to latest firmware

lean bay
#

using moonraker or my computer?

lean bay
#

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

tulip raven
#

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

lean bay
tulip raven
#

what is

position_min:

in your z block

#

[stepper_z]

lean bay
#

and it says No Beacon model loaded

tulip raven
#

you havent done one yet

#

did you do these?

  1. 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

lean bay
#

i did this......

lean bay
tulip raven
#

position_min: -5

#

always be ready on emergency stop

lean bay
tulip raven
#

-5 should help

lean bay
#

when i query beacon it says no model

tulip raven
#

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

lean bay
lean bay
#

also when i query the endstops the z axis says triggered

lean bay
#

its working now. i see i had to bring it low first then set the height then let it run

lean bay
lean bay
#

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?

tulip raven
#

Why would you ever home z first?

#

It makes no sense ever except on like a v0

lean bay
#

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

tulip raven
#

I never tried it. If it's told to home in middle of bed it should never just home where it is.

shell tulip
#

Maybe post a klipper log file. We can check it over.

lean bay