The build from Hell continues
This time I replaced the control board with a new Octopus 429 and replaced both SD cards with brand new ones and started the entire install from scratch. Got thru the initial config where I installed VCore Three config and then hit the brick wall again with "mcu unable to connect".
46 Replies
now you need to edit your printer.cfg file to match your setup
I did. Redid every step from new.
The only thing on that list I didn't do was the SSH. Will try that now.
Okay, I connected using Putty and got: login as
This doesn't match any instructions I can find so I don't know where to go from here. Tried admin but it asks for a password but won't let me enter anything.
Putty keeps losing connection. Don't know if that's a clue
Finally found Teaching Tech's tutorial and found those answers
ran dmesg and got no errors that i could see
When you flashed the firmware to the octopus it changed to firmware.cur?
yep
And you have USB C connected on the octopus to USB A on the pi?
I know I fucked up the wiring before, but that was because I was returning to this build after two back-to-back disasters (lightening strike and hurricane) so I was a bit out of it and lost where I was. I've since redid all the wiring from the begining to make sure I was fresh on the subject and that it was completed correctly. So yes. it is plugged in and I've tried all the different USB ports on the pi to make sure that wasn't the issue.
Can you show a picture of your octopus board and pi?
I unplugged everything but the steppers and USB C on the control board to rule out any possible issues caused by wiring.
Have you tried different cord from Octopus to pi?
5 minutes ago.
Tried both cords that came with the 446 and the 429 and another I had on hand. no difference.
Are you sure you grabbed the correct firmware when you flashed the octopus?
Just flashed it again with the Octopus pro 429 after I updated everything to make sure. Same result
And yes, there really is no way to conuse the files. They are clearly labeled and distinct.
and you did
COMPILE FIRMWARE before?Yes. Like I said, I started from scratch and did everything by the numbers.
ok, just checking all the steps. Lot's of people say they do everything and miss little steps.
I know that one from experience. but then I finally got a full nights sleep.
If you ssh into the pi and run
dmesg -w while plugging in the octopus to the pi, what is the output?I didn't see any error messages and it appears that it detected the USB plug in, but then I don't really know what I'm looking at exactly. Do I just copy and paste the results?
yes, please copy paste the results
Ah, didn't realize it would paste as a txt file.
if you do
lsusb what is the output?pi@ratos:~ $ lsusb
Bus 001 Device 005: ID 1d50:614e OpenMoko, Inc.
Bus 001 Device 004: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@ratos:~ $
and what is the output of
ls /dev/serial/by-id/*?/dev/serial/by-id/usb-Klipper_stm32f429xx_btt-skr-2-429-if00
yeah, i don't know why, but it looks like it is identifying as a SKR 2. @miklschmidt have you ever seen something like this before?
Lets assume I fucked up and recompile the firmware. My wife was talking in my ear at the time and it is possible that I picked the wrong 429.
Just reflashed the firmware and ran ls /dev.... Results came back octopus 429 this time. /dev/serial/by-id/usb-Klipper_stm32f429xx_btt-octopus-pro-429-if00
I think I got the wrong firmware when I tried flashing the second time because I moved to the laptop which I'm not as comfortable with.
it should work now - probably will give you a ADC out of range or something like that error
It did at that.
because you don't have the thermistor or other stuff hooked up
yeah, I got that. I'll plug everything back up and restart.
Yeah, kill the power before you plug anything in
Okay, everything is up and running. This is what happens when you try and juggle too many jobs at once. The small stuff gets overlooked and bits you in the ass.
BTW, I run a prop and special FX studio for Disney, etc. Check out our website. I owe you a favor/discount.
www.studiooz.org
Okay, new problem. Got everything set up and ran through all the calibrations. Axis homed, z-tilt was successful, extruder working correctly, and bed meshed was done and saved. Loaded a printer and it homed the axis and redid the z-tilt only to fail after 10 tries. Restarted the print and this time it timed out after 3 tries because distance was getting larger.
Double check your Z mechanicals. Are the leadsscrews aligned, are they lubed, are you sure you plugged them into the correct driver slots?
Did you do stepper buzz to confirm z0 is front left, z1 is back, and z2 is front right?
first I've heard of stepper buzz
https://www.klipper3d.org/Config_checks.html#verify-stepper-motors
STEPPER_BUZZ STEPPER=z or maybe z0?
That should slowly move just the one z stepperTest was good. z is left, z1 is back, and z2 is right.
Also make sure your probe is mounted securely and isn't wobbling around for each probe. You can run a probe accuracy test https://www.klipper3d.org/Probe_Calibrate.html#repeatability-check
Probe is solidly mounted with no wiggle. Accuracy results: probe accuracy results: maximum 0.091250, minimum 0.077187, range 0.014062, average 0.084094, median 0.084062, standard deviation 0.004374
I would go back to looking at your mechanicals. Double check the screws attaching the bed to the balls that sit in the arms. And make sure everything moves very smoothly by hand with all the Z motions
Ohh another thought, how high above is the nozzle from your probe end? You want it close, like .2mm difference
Z screws are well lubed and been checked for smooth motion. I placed a spirit level on the bed and ran it down to 400mm and then back to the top. If there were any drag or a motor out of sync then it should have changed the level, but it stayed perfect up and down.
As for the probe height, the height I was told was the thickness of a credit card, which is were it's set. I have a .2 mm gauge if that is the correct setting.
Credit card is about 0.2mm so that should be fine
How are the Z leadsscrews attached? 3.0 with the black nuts or is it 3.1 with the Oldham like connections?
3.0
I set the new height on the z probe and just completed a successful z-tilt. just loaded a test print
Well, it made it through the home and z-tilt and is doing a new bed mesh.
And we are printing! I'm serious about that thank you, by the way. My studio builds for Disney and other major companies and we're well known across the world for our props and collectibles. www.studiooz.org
Thank you for the offer but as this is a community discord it would not be right of me to take advantage of this offer. Instead please pay it forward and help others here. Glad your printer is working now