Wondering if anyone can help me see what I am missing. Doesn’t seem like a lot of traffic on the kalico page. So I Installed kalico several times, updated leviathan and NH. Using mainsail and moomraker won’t connect to klipper. Only installed it because it seems to be the easiest way to set up sensorless homing.
#Kalico help??maybe
vast rivet
dry summit
Wondering if anyone can help me see what I am missing. Doesn’t seem like a lot o...
start by checking whether klipper (kalico) is actually running: systemctl status klipper
vast rivet
dry summit
Well, no wonder you can't connect...
Now see if journalctl -u klipper -r tells us why it doesn't start
dry summit
Looks like kiauh didn't install the python dependencies properly
try ~/klippy-env/bin/pip install -r ~/klipper/scripts/klippy-requirements.txt
vast rivet
dry summit
hmm
sudo apt update
sudo apt install libopenblas-dev
then, that works, try that last pip comamand again
vast rivet
dry summit
that's...weird
vast rivet
Ya this sucks. 🤬
dry summit
Ya this sucks. 🤬
gimme a minute
I'm booting up a fresh (ish) pi image. I want to actually try this for myself
kalico shouldn't be that hard to install
vast rivet
I’m probably doing something wrong. But I followed the steps. There’s only a couple.
dry summit
what guide did you follow?
the actual kalico docs are kinda useless on this subject...
"use kiauh". ya...but....
also, just out of curiosity, what device are you on? like an actual raspberry pi? or something else?
vast rivet
Pi4. I used kiauh. Added the GitHub kalico. Posted it further up.
dry summit
so the interesting thing is my install worked...but it also didn't even TRY to compile numpy. it just grabbed a prebuilt wheel from pipi
so it becomes a bit of a "what's different" game
my test was on a pi5, but I doubt that changes anything....
one thing I did do (mostly by accident) is I installed from mainline first, then switched it to kalico... wonder if that changed something...
vast rivet
Any way you could write down steps at all. So I installed pi lite. Then installed kiauh, then klipper. Changed the repository to kalico. Then moonraker, then mainsail, then klipper screen. I know it’s the order it shows on the Voron docs. I even installed all then went back and added and switch to kalico.
dry summit
that really sounds about right
the problem is just whatever detail is making your system not grab a preconfigured wheel for numpy, I think
vast rivet
I’m honestly confused. It was originally connected without kalico.
dry summit
here's my thought:
try installing the pi with bookworm (the previous version of debian/piOS)
I've seen a bunch of talk of install problems of various sorts on trixie (even though I just did it seemingly fine)
but I think it might be worth a shot
and bookworm will still be supported for several years, so there's no major concerns with installing it at this point
vast rivet
I can try that. Did my repository’s seem correct? Is it just kalico causing the issue? Everything connects with normal klipper.
Or something to do with the rp2040 and stm32 flash?
vast rivet
also I followed the Esoterical instruction to set up firmware on the leviathan and Nitehawk. Should I have done it the way LDO page shows?
dry summit
Or something to do with the rp2040 and stm32 flash?
Your error is on the pi. You're nowhere near anything to do with the mcus at that stage
vast rivet
Question, If I tried it without doing Kalico, Should the problem persist since it is a trixie issue?
vast rivet
Dependencies?
dry summit
Dependencies?
The things that it's trying to install to support the software. Stuff like numpy
Are you sure they both install that?
Are you sure they both install the exact same version of that?
vast rivet
No Idea. Like I said I use the pi imager that voron says to use with the selections they say. Then I down load Kiauh, Then through that application I installed Klipper, Then changed to repository '''https://github.com/KalicoCrew/kalico.git, main)''' , then install moonraker(Arksine), then Mainsail, Then mainsail config I believe, then klipperscreen. I have also tried all of that, then switched to Kalico and same thing. Other than switching the github to kalico, I have alsways used the process from LDO/Voron.
dry summit
No Idea. Like I said I use the pi imager that voron says to use with the selecti...
It just feels like you're arguing with me about...nothing
Just try the older version, and see if it works
If it doesn't work, you've lost 20 minutes
If I'm right, all your problems go away
I can assure you the voron docs don't specifically mention installing trixie: they long predate it existing
vast rivet
I'm not arguing with you. I was just asking questions to try and learn how it works and understand it better, and make sure I didn't mess up something. I'm at work and can not try this for a little bit.
dry summit
I'm not arguing with you. I was just asking questions to try and learn how it wo...
Fair enough
dependencies are a software concept. The libraries and tools that a piece of software depends on, which therefore have to get installed for the actual software to function
So for example in this case, when you tell kiauh to install kalico, the first thing it actually does is go and install a bunch of other stuff: numpy, greenlets, heck, python itself
And all of those things need to be in place and working before kalico itself can actually work...and it's one of those other installs that's falling on its face in your system (specifically numpy)
vast rivet
I apologize about that. Soon as I get I will set it up from the older version. I picked up a couple new Micro cards to use as well.
I truly appreciate all the time you have spent helping.
dry summit
I apologize about that. Soon as I get I will set it up from the older version. I...
It's all good. Honestly, i spend too much time "under the hood" of this stuff, and forget how opaque the process is if you don't have the familiarity with what's actually happening
vast rivet
welp, I installed Pi OS 32bit legacy, installed klipper, moonraker, mainsail, then klipperscreen. then added the Github KalicoCrew then swiched. moonraker cant connect to klipper.
However, I also did the commands you had me run yesterday. and it worked.
vast rivet
'''~~~~~~~~~~~~~~~~~~~ [ Main Menu ] ~~~~~~~~~~~~~~~~~~~ ║'''
╟──────────────────┬────────────────────────────────────╢
║ 0) [Log-Upload] │ Klipper: Installed: 1 ║
║ │ Owner: KalicoCrew ║
║ 1) [Install] │ Repo: kalico ║
║ 2) [Update] ├────────────────────────────────────╢
║ 3) [Remove] │ Moonraker: Installed: 1 ║
║ 4) [Advanced] │ Owner: Arksine ║
║ 5) [Backup] │ Repo: moonraker ║
║ ├────────────────────────────────────╢
║ S) [Settings] │ Mainsail: Installed ║
║ │ Fluidd: Not installed ║
║ Community: │ Client-Config: Mainsail-Config ║
║ E) [Extensions] │ ║
║ │ KlipperScreen: Installed ║
║ │ Crowsnest: Not installed ║
╟──────────────────┼────────────────────────────────────╢
║ v6.0.8 │ Changelog: https://git.io/JnmlX ║
╟──────────────────┴────────────────────────────────────╢
║ Q) Quit ║
╚══════════════════════════════════════════════════════'''
dry summit
However, I also did the commands you had me run yesterday. and it worked.
so we got it? you're functional?
jade hareBOT
@vast rivet When posting configs or logs, please surround with code fences (```) so that Discord formats them correctly. Example:
```ini
[mcu]
serial: /dev/serial/by-id/usb-klipper-12345-if00
```
[mcu]
serial: /dev/serial/by-id/usb-klipper-12345-if00
I still have lots of things to add now for the sensorless homing and beacon. But looks like it. Thank you very much for the help and the time. Unfortunately I'm sure I will have more questions.
south flare
feel free to edit this to keep the bot happy 😜
vast rivet
Just to make sure. I do not need to do anything special correct. Just use the Kalico docs to set up sensorless.