Basic Information:
Printer Model: Voron 2.4
MCU / Printerboard: Manta M8P
Host / SBC: CB4
klippy.log
Hi everyone
I am currently installing a Stealthchanger on my Voron. However, I am having problems with the CAN right at the start. My SB had an EBB from Bigtreetech. The new Tollhead (DB) has a board from Fly, the SHT 36 V3. And I can’t get it to work.
Yesterday, I had a connection and was able to flash it.
Klipper then showed me the error “Pin gpio0 reserved for CAN - can’t reserve for spi0a”.
Now it seems that CAN is not active or only partially active. After every third restart of the system, devices are found again.
“ip link show can0” returns “Device ‘can0’ does not exist”.
iplink also does not show Can.
I have tried various tutorials and watched videos, but I am now stuck.
What also irritates me is that when I made a query while it was working, only one device was ever displayed. The host was never displayed. Is that normal?
Thanks in advance.
EDIT: lsusb:
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 1d50:614e OpenMoko, Inc. rp2040
Bus 005 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
klippy.log (1.4 MB)
What is the process that you’re using to setup your system?
I find that the Esoterical guide is best and it is constantly updated:
Could you provide a clearer picture of your hardware? I’m not sure what you are running/try to run from your description.
Hi
Thank you for your reply. Realy, i don’t know why, but it worked.
But: I tried it with two toolboards, and it worked with the third one. I must have made a mistake when compiling. After compiling, the toolboards were no longer recognized.
Now I have another question. Klipper informs me that the host and the toolboard do not have the same version. But: Shouldn’t the toolboard automatically get the same version as the host with “make menuconfig”?
Mellow toolboards are delivered with Katapult pre-installed.
So what is the solution? Install the new version via USB?
Sorry, this is not enough information to give you an answer. Could you please explain the process you’re going through, how you’re getting the CANBus UUID and putting it into printer.cfg?
It should. Now, if the toolhead version is downlevel to the host version, then you haven’t successfully programmed the toolhead.
If the toolhead version is uplevel to the host version, then I suspect you’ve invented time travel.
1 Like
You’re right, the description wasn’t very detailed. 
Here’s what happened:
I flashed a new SHT36 with pre-installed Catapult via the CAN bus from my Manta M8P V2. I found the UUID as normal via ‘python3 ~/klipper/scripts/canbus_query.py can0’. However, after flashing, the SHT36 no longer appeared and the connection could no longer be established despite the UUID being entered correctly in printer.cfg.
After a few restarts of the host, it worked again, but now it doesn’t work at all. The SHT36 can no longer be found on the CAN and the traffic LED on the SHT36 is not lit.
I then had the same problem with a second SHT36.
I assume that I selected the wrong GPIO for the CAN in the menuconfig. This means that the devices are no longer accessible via CAN and I have to reflash them via USB. I don’t know if that’s correct.
Everything worked with the third SHT39 I tried.
However, I get a message saying that the MCU has an older version (12.xx) than the host (13.xx). Even though I flashed the SHT36 from the host with ‘make menuconfig’/‘make’. After flashing, I did not make any more updates on the host. I will look into Esotericals this evening.
I hope that is understandable. Thank you very much!
That’s very helpful.
What version of Klipper is the Manta M8P running? Is it running V12 or V13?
I highly recommend having everything run V13 - we just had somebody else who had issues with different firmware versions in their system.
With everything working, can you go the the Console page of Mainsail (or it’s equivalent in Fluidd) and take a screenshot of the system components. It should look something like this:
Now, if the FY SHT boards are not updating to V13, could you a) provide me with the PCB version you’re working with and b) provide me the process you are using to Flash the MCUs? This will include the process and screen shots of the response you get from the operations (basically make menuconfig, make and the programming operation).
Hi
thank you very much. I’ll reply in the evening with the answers.
See the screenshot i took last night. There are the actual versions.
Hmmm. I’m guessing that is an indication that you’re not updating the firmware on the FLY SHT boards.
When you post the information I requested, please post an updated klippy.log.
Hi mykepredko
Hey, I found the “problem.” My toolboard has the correct version. It’s the Manta board that has the wrong version! The MCU isn’t the toolhead at all. Thanks for your screenshot, now I’ve solved the first problem, or rather, I can solve it.
Now I still have the problem that I have two toolhead PCBs that are no longer accessible via CAN. I now have to try to flash them via USB.
1 Like
Good to hear that you’re moving forward.
I’m guessing that you have two additional toolheads other than the two shown in your screenshot.
Could you give a full description of your printer as I feel like I’m missing something here.
Also, I asked what is the process you used for setting up your system - could you please explain and/or try the Esoterical process that I provided the link to?
Hi
Sorry for my late answer.
Yea no, i don’t have more than one toolhead. At the end yes, but for the moment, there is only one on the CAN. So it’s right what i see.
I ment, that i don’t see them on den CAN when I query them with “python3 ~/klipper/scripts/canbus_query.py can0”. I re-flashed it over USB, flashed klipper again and now everything is fine and funkctional.
And fpr the SHT36, i didn’t use an Esoterical process. I did it with the docu of SHT36.
Thank you very mnuch.
1 Like
So are you running without any problems now?
Sorry, it’s not clear from what you’ve written here.
If you are running, please click on the “Solved” button.
1 Like
