#my pi keeps crashing in the middle of the night due to moonraker error

115 messages · Page 1 of 1 (latest)

twilit grotto
#

i don't know if it is the pi or the wifi pls help

#

my pi keeps crashing in the middle of the night due to moonraker error

fair bramble
#

Please point me to the error, I don't see any error

#

Or maybe describe in more detail what you mean

twilit grotto
#

At random mostly at night my mainsail pi lost connection and due to that my print has stop is there anyway to in the settings in mainsail so I don’t need the pi to continue the
Print

#

I mostly think it is my WiFi because it’s done things like this before in the middle of the night like drop outs and things like that

fair bramble
#

so I don’t need the pi to continue the Print
Without the pi, the print cannot continue. The pi is controlling the printer

#

I mostly think it is my WiFi because it’s done things like this before in the middle of the night like drop outs and things like that
Then your print would not stop

#

Send a klippy.log. There you should see any errors regarding your print

twilit grotto
fair bramble
#
b'Got EOF when reading from device'
Timeout with MCU 'mcu' (eventtime=15078.839498)
Transition to shutdown state: Lost communication with MCU 'mcu'```The last error was a timeout. This can have different reasons

Before that, there is a file corruption, indicating that the pi suddenly turned off (this has nothing to do with wifi)
#

Checkout sudo dmesg for undervolt messages. journalctl could also give information on what happened

twilit grotto
fair bramble
#

yes

twilit grotto
#

where can i find the journalctl

fair bramble
#

It's also a command

#

And you will need to scroll down way to the bottom

twilit grotto
#

[23121.065398] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[23121.065406] usb 1-1: Product: stm32g0b1xx
[23121.065412] usb 1-1: Manufacturer: Klipper
[23121.065418] usb 1-1: SerialNumber: 5100360007504E5238363120
[23121.066560] cdc_acm 1-1:1.0: ttyACM0: USB ACM device

#

Oct 04 19:17:01 ender3 kernel: rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Oct 04 19:17:01 ender3 kernel: RCU Tasks: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
Oct 04 19:17:01 ender3 kernel: RCU Tasks Rude: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
Oct 04 19:17:01 ender3 kernel: RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
Oct 04 19:17:01 ender3 kernel: NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
Oct 04 19:17:01 ender3 kernel: Root IRQ handler: bcm2836_arm_irqchip_handle_irq
Oct 04 19:17:01 ender3 kernel: rcu: srcu_init: Setting srcu_struct sizes based on contention.
Oct 04 19:17:01 ender3 kernel: arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Oct 04 19:17:01 ender3 kernel: clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Oct 04 19:17:01 ender3 kernel: sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Oct 04 19:17:01 ender3 kernel: Console: colour dummy device 80x25
Oct 04 19:17:01 ender3 kernel: printk: legacy console [tty1] enabled
Oct 04 19:17:01 ender3 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=76800)
Oct 04 19:17:01 ender3 kernel: pid_max: default: 32768 minimum: 301
Oct 04 19:17:01 ender3 kernel: LSM: initializing lsm=capability
Oct 04 19:17:01 ender3 kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes, linear)
Oct 04 19:17:01 ender3 kernel: Mountpoint-cache hash table entries: 512 (order: 0, 4096 bytes, linear)
Oct 04 19:17:01 ender3 kernel: rcu: Hierarchical SRCU implementation.
Oct 04 19:17:01 ender3 kernel: rcu: Max phase no-delay instances is 1000.
Oct 04 19:17:01 ender3 kernel: Timer migration: 1 hierarchy levels; 8 children per group; 1 crossnode level
Oct 04 19:17:01 ender3 kernel: EFI services will not be available.

#

it happened again

fair bramble
#

You should give me more output of both

twilit grotto
#

This is what I’m using to power the pi

fair bramble
#

This doesn't really help. Like I wrote. I need more output. Best would be to send the whole dmesg and journalctl logs

twilit grotto
#

sudo dmesg

fair bramble
fair bramble
# twilit grotto

What's that? Just journalctl kernel messages from when it crashed?

twilit grotto
# twilit grotto

it crash and rebooted. i got a better power solution and i think that what the problem was

#

but on another thing when i sent my z offset then home and set it too 0.1 it feel like the z offset changed

fair bramble
#

Sry, I might misunderstand. You set z offset, then home, then change it and then you feel like it changed?
Ofc it chaged, you just changed it. Please explain again what you mean

twilit grotto
#

after i set the new offset value and save it ill go to rehome the printer to check the offset again with the paper test after i saved the value but it will feel off like it will be to high

#

from when i save the new value to rehoming the print to check the new value it feel like the offset has not update or it set to a different value

twilit grotto
#

it was that my cr touch was loose

#

i'm still getting the random stops when I'm printing

#

print will just stop at random points it's not consistent at what layer it will stop but the fans will still be on and the pi will still be on but the hotend will stop and turn off when I check mainsail I get a Moonraker error

fair bramble
#

log

twilit grotto
#

thats the best way i can explain it

#

got you

#

these are logs right after it happened

fair bramble
#

Btw ty for the tip, I forgot to answer here further as I was busy the last few days. Sry for that 🙈

twilit grotto
#

your doing a lot you should be get something for your work

fair bramble
#

Are you sure that it's a Moonraker error?

fair bramble
fair bramble
# twilit grotto

I think that USB hub is the problem. What Pi is that even? It looks like a pi3 but there are no usb and ethernet ports?

fair bramble
twilit grotto
#

i miss read that i though you had a shop

#

im happy you get something for helping out

fair bramble
#

Oh no. It's just that we have some sponsors and mete got a lot of stuff for testing that he can't use all by himself xD

#

That was meant as a reply to the shop thing ^^

twilit grotto
#

it a pi 3a+

#

do you think its too old

#

its also very Temperamental like if I try to turn on the printer before the pi is completely set up with mainsail it will not boot all the way

fair bramble
#

No, the problem is most likely how your printer is connected

#

The device cannot be found sometimes

#

At least those are the most prominent errors I can find right now

twilit grotto
#

the only reason i use the hub is for input shaper

fair bramble
#

All other errors I can find are all a file corruption

#

So the printer is connected through the "real" usb port?

twilit grotto
#

the pi only has one usb port

#

so it connect to the hub

fair bramble
#

Ah, now I get it

#

Best would be to disconnect the input shaper once tuned and just use the usb port of the pi directly with your printer. Test if that helps with your problem first

twilit grotto
#

ya that's it probably

#

ill run some longer prints and it seems to be only things longer then an hour as well

#

but thank you ill run some test and get back to you

twilit grotto
#

I'm also get this in my console Unknown command:"M106" i dont know where it is my printer.cfg

stuck token
twilit grotto
#

would you know how to do that in orca slicer

fair bramble
stuck token
#

Sry... Autocorrection. Yes the gcode file fits

twilit grotto
fair bramble
twilit grotto
#

What do you mean by flavor

fair bramble
fair bramble
#

The first thing in advanced

twilit grotto
#

yes

#

it is

fair bramble
#

M106 is a marlin gcode to set the fan speed. So it only appear if you have some flavor different than Klipper.
So it might be an old sliced gcode? Looking at the printer config, it looks correct.
But I saw that you don't pass your temperature to your START_PRINT macro. You might want to add it, to handle it like you want

twilit grotto
#

how would i add that

#

and do you use kamp

#

im getting this with some lager prints

stuck token
stuck token
# twilit grotto

your bed mesh range cannot be probed/reached with your probe. so you have to modify your bed_mesh coordinates, which can be reached from your probe.

twilit grotto
#

thank you big dog

fair bramble
fair bramble
twilit grotto
#

so i changed it to a heater_fan heatbreak_cooling_fan

#

[heater_fan nozzle_cooling_fan]
pin: PC7

[heater_fan controller_fan]
pin: PB15
heater: heater_bed
heater_temp: 45.0

[heater_fan heatbreak_cooling_fan]
pin:PC6
heater: extruder
heater_temp: 50.0

#

these are my fans in my printer cfg

stuck token
twilit grotto
#

should i just put a [fan]

stuck token
#

you need a [fan]

twilit grotto
#

even if i dont have a pin on it

twilit grotto
#

like what on the printer is would a part cooling fan before

stuck token
#

Which printer do you have?