Howdy all. I’m trying to install klipper on an skr mini e3. I have klipper running on 2 other printers, both with a stock creality control card. But I decided to ‘upgrade’ on the one I’m building and picked up an skr. I have been fighting with this for literally months, and have walked away from it for the last month because I want to chuck it in a lake. I live on a lake, so that’s not an idle threat.
Anwyay, this is my 2nd card. I bought one, had this same issue (below) and then bought a brand new one thinking the 1st, which was 2nd hand was defective. To date, I have 3 different pi 3b’s all running klipper and all running dedicated printers. I’ve swapped them back and forth on the skr board to verify that the 1 I’m trying to use is not the issue. The skr pi, when moved to my other printers works fine and the other printers pi’s moved to the skr, all fail identically.
I have swapped cables back and forth from working printers to the skr, no change. I’ve changed SD cards, no change, I’ve built the firmware using the skr specs at least a hundred times (because why not) and no change, I’ve download and used pre-compiled firmware from skr, and no change.
Uploading the firmware, the board appears to flash each time, the ‘firmware.bin’ file is renamed ‘firmware.cur’ every time.
However,
Going through the PI direct using putty and trying to just find the board in order to get the config file set and I ALWAYS get,
“pi@core:~ $ ls /dev/serial/by-id~
ls: cannot access ‘/dev/serial/by-id~’: No such file or directory”
I know this is supposed to be a good card and a proven combo, I’ve followed several tutorials on how to do what I’m doing, and I’m just failing over and over and over again. I don’t know what I’m missing or what I’m doing wrong as I’m going step by step.
Its been a while since I have set up a new printer on Klipper, but have done a few with that same board you are using. are you in the klipper directory when you try to get the id? I think you have to be in that directory for it to work.
I could be completely wrong or outdated. Just throwing it out there just incase
Your Pi isn’t seeing the USB interface on the SKR mini. No amount of monkeying around in directories will fix that, the kernel isn’t seeing the USB device.
I’d start being certain your USB cable isn’t a charge-only cable.
If that checks out, then I’d plug the SKR mini into a PC, mac, or different Pi.
You should also check to see if the SKR mini has a jumper that can configure how the USB interface behaves.
I’m copy/ pasting it. Using the same pi, leaving it powered up but connecting to my other printers and it kicks back the address immediately. Switch back to the skr and same error.
I’m using cables off of working printers. It’s definitely not that. I bought a pair of brand new “high speed” to try, they work fine on my other printers but no difference.
I’m getting the exact same issues on 2 cards, its got to be an ID 10 T error…
Well, hell if I know what I just did but they’re actually talking to each other at the moment. I was watching a video on how to install klipper on a creality v2.2 board that came out of my ender 5+, reloaded for the 10 billionth time the firmware and got an address. Jumped onto mainsail and pasted it into the config file and watched it load past the mcu error and then shut down because all the sensors are out of range. Which makes sense as the card is sitting on my desk and all the sensors are 5 feet away.
Maybe the video scared it… I know I’m a little hesitant to look too hard at the card right now. It’s likely setting me up somehow…
I had one with a bad usb plug solder connection. The grounding/shielding traces around the outside of the plug had popped off the board due to some previous rough handling. If you held it at the right angle, it would work. After resoldering the data connection lines, I hot glued the plug down to the board and it is still working. Normally one might try to just resolder, but if the pads pull off, it is typically game over.
I just completed cataract surgery (Tuesday) and am getting accustomed to reading glassss, as opposed to just taking off glassss for very close jnspection.
Bought some new PPE for working with the CNC, safety glasses that do not go over regular.glasses. also noticed that there are magnifying safety glasses. Like reading glasses, or maybe like jeweller’s loupes. Thinking I might need somethjng like that myself for soldering. Well, for.soldering, reading.glassss might be enough.
I.did get extended depth of field lenses for the cataract surgery, so I can see okay most ranges, but anything closer than about 16" (45cm) to my face is no bueno. Still used to holding my phone about half that distance, so learning to keep my reading glassss close to hand.
That should be an asterisk (*) at the end, not a tilde (~).
I like to do a watch. I’m AFK, but I think it is:
sudo dmesg -w
Then plug it in and you should see the logs there. The number in the brackets is the number of second since the computer booted. So it is usually pretty easy to see the difference between new and old messages.
If you start a path in Unix with a leading slash (like /dev or /etc), it is an absolute path. So it always starts at the very top, regardless of where you are. It is similar to cd C:\, which always changes to that directory, no matter where you started.
cd klipper only works from your home directory. AFAIK, there is no /klipper, only /home/pi/klipper. When you start a new terminal, you start at home (usually), which is /home/pi. If you want to quickly return home, you can use cd ~. Tilde is a short name for home.
I’m glad something clicked. I hope it isn’t an intermittent issue in the future. dmesg is very reliable at determining if the pi can see the board. You were smart to check the firmware.cur. I hope it was just a typo and not a cable that works 4/7 days/week or something.
