#(SOLVED) Klipper crash with longboi.cfg
1 messages · Page 1 of 1 (latest)
@pale parcel you have any ideas?
That's a pretty generic error for the initial connection. Is the Longboi running the same Klipper/Kalico build as the main MCU? CAN cabling is solid and bus is terminated correctly?
Just to eliminate that possibility, try and connect it via USB.
When I looked through the log, I was looking for the versions. They all appear to be 0.13.0-320-gc8032494.
Can we get the longboi and afc-lite configuration files?
So I don't see anything in the log that I would consider a "klipper crash". when I crash happens, grab and upload you klippy.log before restarting klipper
Pretty sure it's Traceback (most recent call last): File "/home/trident/klipper/klippy/klippy.py", line 135, in _connect cb() File "/home/trident/klipper/klippy/mcu.py", line 959, in _connect config_params = self._send_get_config() ^^^^^^^^^^^^^^^^^^^^^^^ File "/home/trident/klipper/klippy/mcu.py", line 955, in _send_get_config raise error("Can not update MCU '%s' config as it is shutdown" % ( mcu.error: Can not update MCU 'mcu' config as it is shutdown Can not update MCU 'mcu' config as it is shutdown Once the underlying issue is corrected, use the "FIRMWARE_RESTART" command to reset the firmware, reload the config, and restart the host software. Error configuring printer
But usually there's another error somewhere, but I'm not seeing one.
That's for his main MCU, I normally get this when just restarting klipper service. And then hitting restart klipper fixes everything(for me). But I have a feeling that there was another error that's not in this log, but I could be wrong
Yes it’s running the same klipper. I trayed also with the afc-lite how was working before, same error...
I think the same, the error is not in the log. The host start up, then comes the blue field 'The printer is not ready
The klippy host software is attempting to connect ' and maybe after 1 sec. (it’s realy fast) comes the message 'shutdown' in an orange field, disapear and moonraker cannot connect to klipper appears. It’s look like the printer do and emergency stop by itself
How are your CAN terminations configured?
FWIW, I looked through your configs and the pin aliases for your longboi.cfg and that all checks out. So this is more likely some kind of physical/electrical issue
Please run this debugging script when not printing and post the resulting link in chat.
Armored Turtle Project Documentation
@rain dove
I was thinking the same, but with the ac-lite board it works and with longboi too but with mcu cfg from afc-lite, if I change to the longboi.cfg, it "crash"
For me personally my first path of action would be to start with a minimal MCU entry and then work my way up with pin definitions
Your message contradicts that? #1499527009729249370 message
i think the issue is that the longboi.cfg won’t work but using the afc-lite cfg will work for longboi from my understanding
@marsh narwhal could you share your working longboi.cfg? I'm honestly not sure if I sent Dylan the most up to date one
I really need to put that in the repo. My own BTs still run with raw pin definitions and no alias file
Sure, here is the config that I use. I just renamed it AFC_Lite.cfg
correct
So I did a complet reinstal from all with the longboi config from @marsh narwhal and it's work again
(SOLVED) Klipper crash with longboi.cfg
These two configs have a the assignments swapped for HUB and TN_TRL, otherwise they are the same in all but name (more aliases in Akash's config). PD3 = HUB = SW9 in the new config.
Well it's the nuclear option but I'm glad it's working now 😄
I reinstalled klipper totaly new and puted the config from akash that’s it