New VCore, Klippy isn't connecting
I've got a brand new build. It's a 400, octopus 1.1, ebb42. Following the instructions, I have flashed the octopus and the ebb42, I've wired everything except the bed. I've run the macro to copy the vcore printer.cfg over, and I've edited it accordingly, including telling it about the ebb42. When I save and restart I get the message in the image, saying that Klippy is attempting to connect and to try again in a few moments, but nothing ever happens. If I restart or firmware restart, there's no changes. I can't get past this and I'm not sure what's going on.
Solution:
Jump to solution
I think I was being an idiot. I had disconnected the power to the toolboard for something and didn't connect it back. Once I did that I got an error that said that the toolboard was behind so I flashed it again. Now I'm getting a different error.
42 Replies
attack your printer.cfg
config
when you flashed the octopus and the ebb42 - did they flash correctly? Meaning did the configurator say that they were able to connect?
yup, I had no issues at all flashing either. I was surprised cause I struggled to flash my vminion with the octopus board a few months ago when I built it. But this time around I had no issues with the octopus and the ebb42 had no issues either.
Do lights show up on the octopus? (checking that it has power)
Either way, try disconnecting everything from the octopus other than the USB from the pi and see if it connects
Something could be wired wrong and messing with power or data
Essentially, start over with a fresh flashing of the control board to see if you can get back to zero
From a console on the RPi, run:
@TheTik The lights do show up on the octopus. There isn't much connected to it honestly. I flashed it before installing the stepper drivers like the instructions said. Using the ebb42, the only things that are connected to the octopus is the steppers (excluding the extruder), the y endstop, and the 12v 4028 fan. I got the 400 wiring from ratrig so those "should" be good. I can disconnect everything though and try again.
@Jamin Collins [VC 3.1 400mm]
The octopus is showing up.
it may be showing up, but it is not showing up where your config is looking for it:
from your
printer.cfg:
From the control board you've selected:
GitHub
RatOS-configuration/boards/btt-octopus-11/config.cfg at v2.x · Rat-...
The RatOS modular klipper configuration. Contribute to Rat-OS/RatOS-configuration development by creating an account on GitHub.
if you add the following to your
printer.cfg it should correct this issue:
Alternatively, you could check to see if the above referenced path /dev/btt-octopus-11 exists.
it's possible it doesdoing this will break the auto updates from Rat-OS
@Jamin Collins [VC 3.1 400mm]
/dev/btt-octopus-11 does exist and it's a symlink back to the same /dev/ttyACM0 that the symlink /dev/serial/by-id/usb-Klipper_stm32f446xx_btt-octopus-11-if00 points to. I did try to change the config to point to /dev/serial/by-id/usb-Klipper_stm32f446xx_btt-octopus-11-if00 directly, but that didn't do anything (which is expected since it points to the same device).I would try flashing the EBB42 using the configurator again
is it the EBB42 it's failing to connect to? Based on the description is seem to be the main MCU that it's failing to connect to.
Solution
I think I was being an idiot. I had disconnected the power to the toolboard for something and didn't connect it back. Once I did that I got an error that said that the toolboard was behind so I flashed it again. Now I'm getting a different error.
that's expected since you haven't attached your thermistors
attach them, and update your printer.cfg to match your hardware
the hotend thermistor is connected. The commisioning guide says that I need to try to get a bed mesh before I connect my bed heater and thermistor.
sorry for the confusion, my read of the error was an inability to reach the main MCU
you won't be able to do the bed mesh until they are connected due to fail-safes, I believe it's an ordering issue in the commissioning guide
ok the bed thermistor is suppose to be connected but not the heater.
Also, I believe the commissioning guide omits mention of doing a
z-tilt before the bed mesh
if you don't, you'll spend a lot of time fighting to square the frame when the issue is actually a tilted bedok it looks like everything is connected, but my 4028 fan is screaming and never throttling down...
invert the pin for it
switch the red and the black?
just the config, put a
! in front of itI don't see a config for the fan
it's in the include files, but you can override it in your
printer.cfg after the MCU and toolboard includesConnecting a 4028 fan | RatOS
4028 server fans are becoming a popular option for part cooling because of their light weight and great pressure and flow rates. In this guide we'll go over how to connect one and use it for part cooling. 4-pin fans usually aren't used in 3d printers, and many boards only provide 2-pin ports, but fear not! There's always a way.
that didn't make a difference.
do you have just the red and black connected or red, black, and blue?
red black and blue is grounded
and does the fan respond at all to any % change?
ok the snippet from the doc above fixed it
also, where is the blue connected? toolboard or mcu?
fixed it. It's connected to the MCU cause it's a 12v fan and there's no 12 power on the toolboard
right, the power can come from the MCU, but it can still be controlled by the toolboard, hence the question
Thanks so much. I think I'm good for now. I'll do the z-tilt and then the bed mesh. But at least I can finally move forward
but glad you go tit worked out
thanks!
well that sucked. In order to run Z_TILT_ADJUST you have to home first and I guess the inductive probe isn't configured properly and it never stopped and the front two printed peices that hold the bearing for the lead screws broke off from the force before I could shut it down.
I know when I built my minion the probe was somehow not matching the default config and I had to put a
^ in front or something. I'm trying to find the docs around the probe and the commands to see if it is triggered or not and I'm not seeing it anywhere.😬 yes, all of the v-core relies on reliable z-probing
gotta test that the endstops (including Z!) are working before attempting to home 😦
lesson learned the hard way I guess
I learned the same one, the same way when switching from standard nozzle to volcano