Hello for the power to the controller I can check but the printer it is new and processing
many project every ok. I don’t know.
I try to connected via usb at the next stuck.
Thankyou
1/ I trust that you capture in incomplet. The last changes on your logs was the 4th march… If you still have them, share the ones of the 10th (or just earlier).
2/ I do not got the point with usb cables… BTW, if the printer is connected by wifi you can try with RJ45 to see (but i do not trust that is related, the printer screen should react, even without local network).
Hi, unfortunately I no longer have the log of the 4th.
I attach again the logs just downloaded (14 files), it crashed about two hours ago. I had to restart.
sorry but by 10 or before do you mean the line? I’m attaching from the beginning to the 12th
===== Config file =====
Loaded MCU ‘extra_mcu’ 112 commands (v0.12.0-40-g77619e91-dirty-20240229_121540-chris-virtual-machine / gcc: (15:10.3-2021.07-4) 10.3.1 20210621 (release) binutils: (2.38-3ubuntu1+15build1) 2.38)
MCU ‘extra_mcu’ config: ADC_MAX=4095 BUS_PINS_i2c1=PB6,PB7 BUS_PINS_i2c1a=PB8,PB9 BUS_PINS_i2c2=PB10,PB11 BUS_PINS_spi1=PA6,PA7,PA5 BUS_PINS_spi1a=PB4,PB5,PB3 BUS_PINS_spi2=PB14,PB15,PB13 BUS_PINS_spi3=PB4,PB5,PB3 CLOCK_FREQ=72000000 MCU=stm32f103xe PWM_MAX=255 RESERVE_PINS_USB=PA11,PA12 STATS_SUMSQ_BASE=256 STEPPER_BOTH_EDGE=1
Configured MCU ‘extra_mcu’ (1024 moves)
Loaded MCU ‘mcu’ 112 commands (v0.12.0-40-g77619e91-dirty-20240301_104656-chris-virtual-machine / gcc: (15:10.3-2021.07-4) 10.3.1 20210621 (release) binutils: (2.38-3ubuntu1+15build1) 2.38)
MCU ‘mcu’ config: ADC_MAX=4095 BUS_PINS_i2c1=PB6,PB7 BUS_PINS_i2c1a=PB8,PB9 BUS_PINS_i2c2=PB10,PB11 BUS_PINS_spi1=PA6,PA7,PA5 BUS_PINS_spi1a=PB4,PB5,PB3 BUS_PINS_spi2=PB14,PB15,PB13 BUS_PINS_spi3=PB4,PB5,PB3 CLOCK_FREQ=72000000 MCU=stm32f103xe PWM_MAX=255
What i looking for that is the log just before the crash. We do not know exactly “when” that happened but you can guest. So you said that happened at 14th around 20h (CET). You printer is probably configured in UTC (so -1h from CET).
1/ first execute
sudo journalctl --boot=-1 > /tmp/log
Then run : tail /tmp/log => the last date should be before the last crash (so in the 14th evening). If not, retry with sudo journalctl --boot=-2 > /tmp/log (then -3, -4 depending on the number of restart from the last crash).
2/ check the logs :
less /tmp/log ensure that there is nothing too sensible for privacy or security (that should not but check)
3/ Send publicly
cat /tmp/log | curl -s --data-binary @- 'https://paste.c-net.org/'
That will answer with a link that you can share here
4/ If you can, please share also :
- klippy.log (the current one)
- klippy.log.2025-03-XX (where XX is 14 or upper)
- moonracker.log (the current one)
- moonracker.log.2025-03-XX (where XX is 14 or upper)
Hi, unfortunately the commands don’t work, I get errors “Data from the specified boot (-1) is not available: No such boot ID in journal” even with -2, -3, -4, -5 …
Am I doing something wrong?