-
TeamFDM.com is an UNOFFICIAL companion site for the DIY Voron 3D printer community. For official docs and final source of truth, visit the Official Voron Discord or the Voron Github
- 0
TeamFDM.com is an UNOFFICIAL companion site for the DIY Voron 3D printer community. For official docs and final source of truth, visit the Official Voron Discord or the Voron Github
Question
scyyie
Hello again! I hope I chose the correct category, if not please let me know. I'm asking for insight and assistance to learn how to get this build up and running. To easier understand the situation, I'll give some details. Please forgive me as I'm doing my best to understand everything as I go as this is my first interaction with anything voron related. I am a glutton for punishment, but also eager to learn/stubborn.
I drove from NJ to MD to buy this build off Facebook marketplace. I was told it wasn't used in over a year.
Specs that I can identify are as follows:
300mm bed, clicky probe, stealthburner, sb2040 for the toolhead with a knomi v1 interface, linear rails, 4 z-axis motors, Raspberry pi 4, BTT octopus v1, umbilical cord, klipper screen. I could be forgetting things.
The Raspberry Pi 4 had python 3.7. Everything was in canbus mode (I think). I was told the pi SD wasn't wiped since there were many customized files. I have pulled off the SD card content for my records.
Here's my sequence of events thus far.
Turned on, klipper screen was only working as a screen for the rp4. Showing the code running to get everything running though no interface. An error was stated something along the lines of asking for a mainsail password. After digging around for 2 days I went ahead with flashing the rp4 with mainsailOS, understanding that the wiring for this could be all set up specifically for whatever the previous owner had configured. I have been checking connections as best I can as I go. Once the rp4 was flashed, I was not able to see the BTT octopus via putty console. Through more digging, I learned that the octopus was in canbus mode. My inexperienced perception led me to flash klipper onto the octopus to clear canbus mode since no other information seemed apparent. I have then successfully shown the octopus as a device on the rp4.
You might ask why wouldn't I leave everything in canbus? Well I didn't (and still dont) know the full scope of using/not using canbus. I simply wanted to identify a base line of operation (homing, printing, calibration, etc) before I attempted to integrate something I know nothing about. C'est la vie, here we are.
I have since been able to home the printer, x and y. Z homing was using the button behind the bed, though i had to enter the coordinates. The quad gantry leveling, I now realize is interesting. Considering there are abrasive marks on the sides, indicates to me that there were some mistakes made prior to me obtaining the printer, but I also have made those marks somewhat worse in my attempts to get homing down. Again, another lesson learned, and I can home the toolhead!
My next plan was to flash klipper onto the sb2040. My reasoning is i can see the pins on the sb2040 have the clicky probe wired specifically to GPIO28. I was thinking if I can flash the sb2040, then the rp4 will recognize it, then I'll be able to utilize the gpio28 pin to have the clicky probe function for Quad Gantry Leveling. Allowing me to almost reach that baseline function.
That's my thinking. I know this is a lot and any consideration or input I am extremely grateful for. Thank you for reading and take care.
Link to comment
Share on other sites
13 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.