New Monster 8 MCU error during connect

General Discussion
1

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: MKS Monster 8
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…
klippy.log (13.2 KB)
I recently updated from a spyder 2.2 to a Monster 8 and having a number of issues connecting and such. I use a Mint Linux control mini PC and can’t quite seem to get connected to the printer. It flashed perfectly and I tried it several times and now have a steady stream of log files that indicate mcu shutdown and I can ls -l /dev/serial/by-id/* and it returns a value as well as by-path. Just not sure what I am missing here.

2

Your log does not contain much except Can not update MCU '<name>' config as it is shutdown

3

I really don’t have much to go on beyond that. I am sure you can imagine how many restarts I have gone through.

4

It sees the damn thing.
[ 2.174383] usb 1-4: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
[ 2.174399] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.174405] usb 1-4: Product: stm32f407xx
[ 2.174409] usb 1-4: Manufacturer: Klipper
[ 2.174413] usb 1-4: SerialNumber: 470042000D50315141323320

/dev/serial/by-id/usb-Klipper_stm32f407xx_470042000D50315141323320-if00

5

OK progressing after a reflash. I named the file mks_monster8.bin as I saw in another post and restarted.
New log attached. I am thinking I have to get more info on the thermistor defs.
klippy.log (44.9 KB)

6

The various NTC variants as listed here do not play a big role. Such an error typically points to a wiring issue or dead thermistor.

grafik

It’s your bed’s sensor that is acting up.

7

Awesome! I’ll give it a look see. Thanks and will update.

8

Not sure where I see an error for it this time…target and reading for bed temp are now zeroed out anyway.

klippy.log (49.3 KB)

9

I have kept at editing and am not seeing any errors but still nothing connects and I am just not sure what is happening. It looks like it hangs but continues to receive data from the MCU just fine but nothing in Mainsail.

klippy.log (8.7 KB)

10

Now that I got a clean log indicating startup I figured something else was up so I removed everything with kiauh and reinstalled and viola it’s working. now some tuning and hopefully all will return to normal.
Thanks for the input!

1 Like
11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.