Professeur Schmoll
New member
Hello,
I found a lot of help on other threads on this forum to troubleshoot my build but there's still an issue that i'm not able to solve.
When starting my printer (it's a trident variant) the raspberry freezes most of the time before starting Klipper.
On the screen it stays frozen at:
My IP adress: [xxxx]
[Hostname] login:_
I'm using a Fystec spider 3.0 for the motion system and a second mcu (LDO nitehawk) on the toolhead. The raspberry is a 3B with 8Gb of ram. I installed a 32bit image of Mainsail.
The raspberry receives 5V from the Fystec via a dedicated wire and uses USB for communication with both Fystec & Nitehawk.
The issue happens, I think, when the Fystec spider boots at the same time as the Raspberry.
I tried several things:
-Taping the 5V line on the usb between the Raspi & Fystec: no luck.
-Powering the raspi with its own power supply: no luck.
-I'm using klipperscreen & Obico, bu i tried with a fresh install without any add-ons: no luck.
-Specifying in the config file: "dtcoverlay=dwc2" or something like that. It seemed to work (had a pair of reboots without freezing) but I was not able to connect to the Nitehawk fos some reason.
The only things that works each time is if I power the Raspi before the Fystec:
-I remove a jumper on the board between its power regulation and the ret of the board (it's here for switching between on-board & USB power).
-The still receives 5V and boots.
-On it has booted I power the whole Fystec and klipper launches.
It works independently of the second MCU (nitehawk) being powered or not.
I could find some way to power the fystec AFTER the raspy withour using this jumper (adding a switch or relay to automate) but it seems to me that there should be some easier way to prevent this problem.
Being unable to solve it myself, maybe someone here may help me?
I found a lot of help on other threads on this forum to troubleshoot my build but there's still an issue that i'm not able to solve.
When starting my printer (it's a trident variant) the raspberry freezes most of the time before starting Klipper.
On the screen it stays frozen at:
My IP adress: [xxxx]
[Hostname] login:_
I'm using a Fystec spider 3.0 for the motion system and a second mcu (LDO nitehawk) on the toolhead. The raspberry is a 3B with 8Gb of ram. I installed a 32bit image of Mainsail.
The raspberry receives 5V from the Fystec via a dedicated wire and uses USB for communication with both Fystec & Nitehawk.
The issue happens, I think, when the Fystec spider boots at the same time as the Raspberry.
I tried several things:
-Taping the 5V line on the usb between the Raspi & Fystec: no luck.
-Powering the raspi with its own power supply: no luck.
-I'm using klipperscreen & Obico, bu i tried with a fresh install without any add-ons: no luck.
-Specifying in the config file: "dtcoverlay=dwc2" or something like that. It seemed to work (had a pair of reboots without freezing) but I was not able to connect to the Nitehawk fos some reason.
The only things that works each time is if I power the Raspi before the Fystec:
-I remove a jumper on the board between its power regulation and the ret of the board (it's here for switching between on-board & USB power).
-The still receives 5V and boots.
-On it has booted I power the whole Fystec and klipper launches.
It works independently of the second MCU (nitehawk) being powered or not.
I could find some way to power the fystec AFTER the raspy withour using this jumper (adding a switch or relay to automate) but it seems to me that there should be some easier way to prevent this problem.
Being unable to solve it myself, maybe someone here may help me?