'MCU': Unable to connect after power cycle

[PinGuiNPL]

Hi, until this morning I was more than satisfied with the board. Before that I had a SKR 1.4 Turbo board with a Pi4B. In the last few days I have converted everything to the SKIPR and have already started calibrating the printer, as I have also made a couple of other upgrades. Everything was going great until yesterday, then I switched off the printer and wanted to continue working on the calibration today.... but unfortunately the printer no longer works. After switching on, Klipper no longer sees the MCU.:

mcu 'mcu': Unable to connect
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

Nothing changed in the config during the night. Nevertheless, I checked these and the path is still:

[mcu]
serial: /dev/ttyS0
restart_method: command

My first try was a different SD card for the MCU, the second with the mks_skipr.bin from MKS Github and the third with my own bin with make menuconfig... None of that worked. To me it looks like some defect. If so, that was my first and last MKS board, I have 3 other printers with SKRs and have never had a broken board. But maybe someone here has an idea I didn't think of.

The clipper log says:

cu 'mcu': Starting serial connect
mcu 'mcu': Unable to open serial port: Could not configure port: (5, 'Input/output error')
webhooks client 281473274428144: New connection
webhooks client 281473274428144: Client info {'program': 'Moonraker', 'version': 'v0.8.0-23-g18f5ff4'}
mcu 'mcu': Unable to open serial port: Could not configure port: (5, 'Input/output error')
mcu 'mcu': Unable to open serial port: Could not configure port: (5, 'Input/output error')
mcu 'mcu': Unable to open serial port: Could not configure port: (5, 'Input/output error')
mcu 'mcu': Unable to open serial port: Could not configure port: (5, 'Input/output error') 

Klippy log klippy (2).log

[ddemeterco]

Same issue here. Messaged mks and now waiting for response

[kino13]

Hello,

I got exactly the same error since yesterday, did anyone find anything else or has mks answered?

[Townie-au]

Hi I also have the same issue

[Townie-au]

I doubt MKS will respond. It's usually the community that works the solution.

[zadnezz32]

I'm in the same situation. No LEDs light up on the MCU side of the car. and the serial doesn't work.

[misssiek]

my klipper have the same error, after shut down and power up, nothing can't help even reinstal.

[kino13]

Hello all,

I know that many of you are having issues of different types, but seriously, redo the cables of the canbus data from scratch with some good cables (I used silicone wire 24AWG). I have installed several can boards since I made this post, and I can assure you 90% of the issues is always the cable or the physical connection of the cable. Another important thing, when the connectivity fails, klipper and even the hosted linux will act in strange ways: losing the can0 interface, not detecting the CAN board when the one failing is the secondary, hanging up, I have seen it all and it was always the cables.

[DK4YA]

Hello all, I know that many of you are having issues of different types, but seriously, redo the cables of the canbus data from scratch with some good cables (I used silicone wire 24AWG). I have installed several can boards since I made this post, and I can assure you 90% of the issues is always the cable or the physical connection of the cable. Another important thing, when the connectivity fails, klipper and even the hosted linux will act in strange ways: losing the can0 interface, not detecting the CAN board when the one failing is the secondary, hanging up, I have seen it all and it was always the cables.

how helpful. All the people before you reported that the connection between host and MCU is not working. This is a direct connection on the board itself. What does that have to do with cable quality? Activating the CAN0 is still a long way off. I have to say that it was much better and easier on the BTT Manta board.

[kino13]

Take it as you want, I have experienced all kinds of issues that got fixed after replacing the cables on the canbus, and yes, I am referring to the MCU. For sure if the issues are happening even before reaching that point, you will need to look elsewhere, but I saw all kinds: hang ups, unresponsiveness, lost of MCU, lost of canbus (obviously), lost of usb detection... And all of them were due to a bad canbus cabling.

On Fri, 20 Oct 2023 at 19:58, DK4YA @.***> wrote:

Hello all, I know that many of you are having issues of different types, but seriously, redo the cables of the canbus data from scratch with some good cables (I used silicone wire 24AWG). I have installed several can boards since I made this post, and I can assure you 90% of the issues is always the cable or the physical connection of the cable. Another important thing, when the connectivity fails, klipper and even the hosted linux will act in strange ways: losing the can0 interface, not detecting the CAN board when the one failing is the secondary, hanging up, I have seen it all and it was always the cables.

how helpful. All the people before you reported that the connection between host and MCU is not working. This is a direct connection on the board itself. What does that have to do with cable quality? Activating the CAN0 is still a long way off. I have to say that it was much better and easier on the BTT Manta board.

— Reply to this email directly, view it on GitHub https://github.com/makerbase-mks/MKS-SKIPR/issues/36#issuecomment-1773166490, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADRZHU3RA57DMLF2R7EYYHTYAK3VRAVCNFSM6AAAAAAVLC6GN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTGE3DMNBZGA . You are receiving this because you commented.Message ID: @.***>

[JJSYSPRO]

My problem started the same as you, but it got worse, now only the LEDs turn on and the board stays frozen, and in serial mode when I connect to the assigned COM, it also stays frozen, does anyone have a solution, I think it is poor quality of the plate,

The monster 8 is already in its third revision, same problems...

[kino13]

I moved to BTT boards on all my printers, I know that does not solve the issue at hand, but I have not had any problem with them and their documentation is excellent.

On Thu, 7 Dec 2023 at 07:00, JJSYSPRO @.***> wrote:

My problem started the same as you, but it got worse, now only the LEDs turn on and the board stays frozen, and in serial mode when I connect to the assigned COM, it also stays frozen, does anyone have a solution, I think it is poor quality of the plate,

The monster 8 is already in its third revision, same problems...

— Reply to this email directly, view it on GitHub https://github.com/makerbase-mks/MKS-SKIPR/issues/36#issuecomment-1844639968, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADRZHUZ4O7XXL3NEKTD6AADYIFLPDAVCNFSM6AAAAAAVLC6GN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBUGYZTSOJWHA . You are receiving this because you commented.Message ID: @.***>

[Lones01]

my klipper have the same error, after shut down and power up, nothing can't help even reinstal.

Hi I also have the same issue

[alexvnesta]

Does anyone have a solution to this issue?