Klipper no longer using X1 and Y1?
#Klipper no longer using X1 and Y1?
fresh oxide
formal rose
Klippy log?
fresh oxide
yes sorry!
fresh oxide
Klippy log?
formal rose
Huh. Looks like it's still loading them...weird. I'll have a look in a bit
fresh oxide
Huh. Looks like it's still loading them...weird. I'll have a look in a bit
thank you so much!
fresh oxide
Huh. Looks like it's still loading them...weird. I'll have a look in a bit
if you need anything else please let me know ill try to help as much as i can
formal rose
if you need anything else please let me know ill try to help as much as i can
I must admit, I'm not seeing anything at all. Are you sure that's what's happening?
Can you buzz the x1/y1 motors still?
If the entire concept of secondary motors had broken then your z motors would be a problem too...
(And I checked the klipper change logs. I don't see anything that sounds likely there either...)
fresh oxide
Can you buzz the x1/y1 motors still?
i cant buzz them, when i do stepper buzz, only the one stepper works, and if i swap ports on my board then then other stepper works.. is it possible my board randomly died? or thoses ports atleast?
formal rose
Sorry, so what buzz commands did you do exactly
fresh oxide
STEPPER_BUZZ STEPPER=stepper_x
fresh oxide
do i need to also do x1
formal rose
Yes
fresh oxide
lovely.... wekp lol... next question then (im assuming now this is a new motor sync thing)
[motors_sync]
axes: x,y
should motor sync also have x,y,x1,y1?
formal rose
I...bear with me. I've never seen that section before. I have no idea why you have that
One moment, while I look it up
fresh oxide
sorry normally looks like this
[motors_sync]
axes: x,y
Axes on which calibration will be performed.
accel_chip: adxl345
Accelerometers for vibration collection: adxl345 / mpu9250 / lis2dw,
etc. Are indicated general or for axis on which calibration is
performed, for example - accel_chip_x or accel_chip_y.
#chip_filter: median
Filter type for data from the accelerometer: 'median' works well in
most cases, but some particularly
formal rose
I don't know what that is. It's not part of klipper
fresh oxide
okay sorry sorry nvm i wont bug you about that then!!!!
thank you for all your help! sorry for bothering!
formal rose
I mean, it sounds possible that it's relevent
But stock klipper behavior is for x1 to sync with x automatically
No special config required, other than the naming of the motors
fresh oxide
motor sync did work because and now i notice with the update its not.. and im wondering if now its wanting it to call up x1 and y1 as well
formal rose
Where is it even coming from though? Like is that some addon?
fresh oxide
yes it is
formal rose
Okay...work with me here... what Addon. What does it do? Why do you need it?
fresh oxide
apparently it helps sync the steppers when running quad X Y steppers (AWD) https://github.com/MRX8024/motors-sync/blob/main/wiki/EN.md
ive been running it for a 2 months now and just yesterday when i did updates is when i noticed it wouldnt activate x1 or y1 anymore
formal rose
Fascinating. Hadn't seen that before at all
It sounds like an interesting addon. But...for testing purposes, I'd suggest disabling it, and see if the problem goes away
fresh oxide
Fascinating. Hadn't seen that before at all
it seemed to work well tbh, i would still do manual motor sync and then every print have that in my print start G-code
fresh oxide
It sounds like an interesting addon. But...for testing purposes, I'd suggest d...
will do
formal rose
At least then we have a better idea if it's the source of trouble or not
fresh oxide
machine is fine im stupid
its just motor sync not working
STEPPER_BUZZ STEPPER=stepper_x1
that make x1 move
the reason i noticed it is when i started a print i noticed the machine just sitting there and stepper driver X and Y where showing no temp (its normal when doing sync motor becuase it kinda shuts the driver off) but then i noticed the machine sitting there and it wasnt doing anything
then i did the stepper buzz command wrong and i thought it was x1 and y1
sorry for wasting your time, i do thank you for the help
formal rose
Is it related to this https://github.com/MRX8024/motors-sync/issues/18 ?
No wasted time. I learned about a new thing, if nothing else
(And you learned how the buzz command works) everybody wins
fresh oxide
ill run the command and show you, i dont seem to get any erros
fresh oxide
(And you learned how the buzz command works) everybody wins
yes i really appreciate that
so honnestly, i think the person changed how the motor sync function works. it use to shut each driver off one at a time and sync the motors. jumping back and forth, now it looks like x1 and y1 are always on and it just shuts off x and y, im wondering if they changed it up
formal rose
Nothing jumps out in the recent commits...but there is an absolute wall of stuff from Dec 8, so...who knows... 😛
fresh oxide
Nothing jumps out in the recent commits...but there is an absolute wall of stuff...
i may shoot them a message and ask LOL
formal rose
There's also the possibility it's been somehow effected by the updates to input shaper that went live a couple of days ago