'mcu': unable to connect is driving me crazy

General Discussion
1

For a year now I have two Ender6 and an ender3 running with clipper via one sonic pad, this works almost without problems. Now I want to use one Ender6 in a different place and let it work via a PI.
For a few weeks I have been struggling with the installation, although the installation is simple the mcu does not want to connect, except once when I had a connection, then I wanted to set the BL touch in the cfg file via mainsail after a save and restart I could not get a connection anymore. I have reinstalled everything several times but it does not work anymore and I gave up.
After a week and after having gone through some issues here I tried again today. Reinstalled everything again and it worked and there was a connection. Set up the printer, did Z-offset and bed leveling and started the first print. It soon became clear that I had not set the rotation distance correctly because I no longer have the standard extruder. After having adjusted this in the cfg file and saved and restarted nothing wants to work anymore like last week. Again I tried a few times to reinstall everything but it won’t work.

Both last week after I gave up and today I flashed the firmware I use for the Sonic pad back on and everything works perfectly via the sonic pad.

I saved the klipper.log file and looked at it, what immediately stands out is that STM32F407 is mentioned at the top, and further down the STM32F407 is checked and not the STM32F103. This while during the Build the STM32F103 was definitely checked as it should be.
Could it be that this is my problem and what can I do about it?
Log is attached.

[mcu]
serial = /dev/serial/by-id/usb-Klipper_stm32f407xx_1D0039000F47393438343535-if00

CONFIG_STM32_SELECT=y

CONFIG_MACH_STM32F103 is not set

CONFIG_MACH_STM32F207 is not set

CONFIG_MACH_STM32F401 is not set

CONFIG_MACH_STM32F405 is not set

CONFIG_MACH_STM32F407=y

CONFIG_MACH_STM32F429 is not set

klippy (8).log (2.1 MB)

Dirk

2

Hello @Von_W004 !

[quote=“Von_W004, post:1, topic:19871”]
Sonic pad
[/quote]

For we do not know what Creality has done to Klipper on the Sonic Pad, we are not able to help here.

Creality Sonic Pad and Alternatives

3

I think I’ve been misunderstood, I want to use the Ender 6 via a Raspberry PI, the problem I want to explain here is what happens with the PI

I bought the sonic pad last year used together with an ender 3 which has nothing to do with my problem, I mention it because the ender 6 works fine again after reflashing and I therefore assume that the problem is not with the printer.

4

Sorry, I’ve over seen the short note at the end of the first paragraph.

I already was wondering why the klippy.log looked so “normal”.

So you got the chip type directly from the printer board?

5

Could you close out this thread and start it again WITH THE INFORMATION THAT YOU WERE ASKED FOR?

The information requested is there for a reason and if you ignore it, we can’t understand what is the issue.

6

Yes the chip type is STM32F103 , I checked it when preparing the CFG file but in the log is always the STM32F407. unfortunately I don’t have a log file of that time it did work

7

I don’t know if it has anything to do with it but I did reinstalling it over again but I first restarted my PC. And now it works again, my first print was successful after which I switched everything off and restarted it which went without any problems.
With this I will consider it solved, why or how?

Thanks
Dirk

8

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