diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 0000000..83b6a1c --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,27 @@ +--- +name: Bug report +about: Bug report for BTT_Octopus_Color_PIN_Diagram +title: "[BUG] (short description)" +labels: '' +assignees: '' + +--- + + +### Bug Description + + + +#### Additional Information + +* Provide pictures or links to videos that clearly demonstrate the issue. diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 0000000..8e6b201 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,31 @@ +--- +name: Feature request +about: Request a Feature. +title: "[FR] (feature request title)" +labels: '' +assignees: '' + +--- + + + +### Description + + + +### Feature Workflow + + + +1. [First Change] +2. [Second Change] +3. [and so on...] + +#### Additional Information + +* Provide pictures or links that demonstrate a similar feature or concept. +* See [How Can I Contribute](#how-can-i-contribute) for additional guidelines. diff --git a/.github/code-of-conduct.md b/.github/code-of-conduct.md new file mode 100644 index 0000000..9adb586 --- /dev/null +++ b/.github/code-of-conduct.md @@ -0,0 +1,119 @@ +# GadgetAngel Community Code of Conduct + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and leaders pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, disability, ethnicity, gender identity and expression, level or type of +experience, education, socio-economic status, nationality, personal appearance, +race, religion, or sexual identity and orientation. + +## Our Standards + +We are committed to providing a friendly, safe and welcoming environment for +all. + +Examples of behavior that contributes to creating a positive environment +include: + +* Be kind and courteous to others +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Collaborating with other community members +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +* The use of sexualized language or imagery and sexual attention or advances +* The use of inappropriate images, including in a community member's avatar +* The use of inappropriate language, including in a community member's nickname +* Any spamming, flaming, baiting or other attention-stealing behavior +* Excessive or unwelcome helping; answering outside the scope of the question + asked +* Trolling, insulting/derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or electronic + address, without explicit permission +* Other conduct which could reasonably be considered inappropriate + +The goal of the standards and moderation guidelines outlined here is to build +and maintain a respectful community. We ask that you don’t just aim to be +"technically unimpeachable", but rather try to be your best self. + +We value many things beyond technical expertise, including collaboration and +supporting others within our community. Providing a positive experience for +other community members can have a much more significant impact than simply +providing the correct answer. + +## Our Responsibilities + +Project leaders are responsible for clarifying the standards of acceptable +behavior and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behavior. + +Project leaders have the right and responsibility to remove, edit, or +reject messages, comments, commits, code, issues, and other contributions +that are not aligned to this Code of Conduct, or to ban temporarily or +permanently any community member for other behaviors that they deem +inappropriate, threatening, offensive, or harmful. + +## Moderation + +Instances of behaviors that violate the GadgetAngel Community Code of Conduct +may be reported by any member of the community. Community members are +encouraged to report these situations, including situations they witness +involving other community members. + +You may report in the following ways: + +In any situation, you may send an email to . + + +Email and direct message reports will be kept confidential. + + +These are the steps for upholding our community’s standards of conduct. + +1. Any member of the community may report any situation that violates the +GadgetAngel Community Code of Conduct. All reports will be reviewed and +investigated. +2. If the behavior is an egregious violation, the community member who +committed the violation may be banned immediately, without warning. +3. Otherwise, moderators will first respond to such behavior with a warning. +4. Moderators follow a soft "three strikes" policy - the community member may +be given another chance, if they are receptive to the warning and change their +behavior. +5. If the community member is unreceptive or unreasonable when warned by a +moderator, or the warning goes unheeded, they may be banned for a first or +second offense. Repeated offenses will result in the community member being +banned. + +## Scope + +This Code of Conduct and the enforcement policies listed above apply to all +GadgetAngel Community venues. This includes but is not limited to any community +spaces (both public and private), the entire GadgetAngel Discord server, and +GadgetAngel GitHub repositories. Examples of GadgetAngel Community spaces include +but are not limited to meet-ups, audio chats on the GadgetAngel Discord, or +interaction at a conference. + +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. As a community +member, you are representing our community, and are expected to behave +accordingly. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 1.4, available at +, +and the [Rust Code of Conduct](https://www.rust-lang.org/en-US/conduct.html). + +For other projects adopting the GadgetAngel Community Code of +Conduct, please contact the maintainers of those projects for enforcement. +If you wish to use this code of conduct for your own project, consider +explicitly mentioning your moderation policy or making a copy with your +own moderation policy so as to avoid confusion. diff --git a/.github/contributing.md b/.github/contributing.md new file mode 100644 index 0000000..97b9fa9 --- /dev/null +++ b/.github/contributing.md @@ -0,0 +1,71 @@ +# Contributing to BTT_Octopus_Color_PIN_Diagram + +Thanks for your interest in contributing to BTT_Octopus_Color_PIN_Diagram! + +The following is a set of guidelines for contributing to BTT_Octopus_Color_PIN_Diagram, hosted by the [GadgetAngel](https://github.com/GadgetAngel) on GitHub. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a Pull Request. + +#### Table Of Contents + +[Code of Conduct](./code-of-conduct.md) + +[I don't want to read this whole thing, I just have a question!!!](#i-dont-want-to-read-this-whole-thing-i-just-have-a-question) + +[How Can I Contribute?](#how-can-i-contribute) + * [Reporting Bugs](#reporting-bugs) + * [Suggesting Features or Changes](#suggesting-features-or-changes) + * [Pull Requests](#pull-requests) + +## Code of Conduct + +This project and everyone participating in it is governed by the [GadgetAngel of Conduct](./code-of-conduct.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [GadgetAngel](mailto:joannmanges@gmail.com). + +## I don't want to read this whole thing I just have a question!!! + +> **Note:** Please don't file an issue to ask a question. You'll get faster results by using the resources below. + +Bigtreetech hasFacebook groups where our knowledgable user community can provide helpful advice if you have questions. + +* [Bigtreetech Octopus on Facebook](https://www.facebook.com/groups/531985571570025/) + + +## How Can I Contribute? + +### Reporting Bugs + +This section guides you through submitting a Bug Report for BTT_Octopus_Color_PIN_Diagram. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports. + +When you are creating a Bug Report, please [include as many details as possible](#how-do-i-submit-a-good-bug-report). Fill out [the required template](./ISSUE_TEMPLATE/bug_report.md), the information it asks for helps us resolve issues faster. + +> **Note:** Regressions can happen. If you find a **Closed** issue that seems like your issue, go ahead and open a new issue and include a link to the original issue in the body of your new one. All you need to create a link is the issue number, preceded by #. For example, #8888. + +#### How Do I Submit A (Good) Bug Report? + +Bugs are tracked as [GitHub issues](https://guides.github.com/features/issues/). Use the New Issue button to create an issue and provide the following information by filling in [the template](./ISSUE_TEMPLATE/bug_report.md). + +Explain the problem and include additional details to help maintainers reproduce the problem: + +* **Use a clear and descriptive title** for the issue to identify the problem. +* **Describe the error in the manual** in as many details as possible. +* **Include screenshots, links to videos, etc.** which clearly demonstrate the problem. + +### Suggesting Features or Changes + +This section guides you through submitting a suggestion for BTT_Octopus_Color_PIN_Diagram, including completely new features. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions. + +When you are creating an enhancement suggestion, please [include as many details as possible](#how-do-i-submit-a-good-feature-request). Fill in [the template](./ISSUE_TEMPLATE/feature_request.md). + +#### How Do I Submit A (Good) Feature Request? + +Feature Requests are tracked as [GitHub issues](https://guides.github.com/features/issues/). Please follow these guidelines in your request: + +* **Use a clear and descriptive title** for the issue to identify the suggestion. +* **Include screenshots and links to videos** which demonstrate the feature or point out the part of the "Color PIN Diagram" to which the request is related. +* **Explain why this feature would be useful** to most readers. + +### Pull Requests + +Pull Requests should always be targeted to working branches (e.g., `master`). If this is your first Pull Request, please read Github's [Pull Request](https://help.github.com/articles/creating-a-pull-request/) documentation. + +* Fill in [the required template](./pull_request_template.md). +* Don't include issue numbers in the PR title. +* Include pictures, diagrams, and links to videos in your Pull Request to demonstrate your changes, if needed. diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md new file mode 100644 index 0000000..0d6216f --- /dev/null +++ b/.github/pull_request_template.md @@ -0,0 +1,27 @@ +--- +name: pull request +about: Open a pull request. +title: "Title (open a pull request Title)" +labels: '' +assignees: '' + +--- +### Requirements + +* Filling out this template is required. Pull Requests without a clear description may be closed at the maintainers' discretion. + +### Description + + + +### Benefits + + + +### Related Issues + + diff --git a/Electronics_Case_Wiring_Diagram/README.md b/Electronics_Case_Wiring_Diagram/README.md new file mode 100644 index 0000000..b9b6bfe --- /dev/null +++ b/Electronics_Case_Wiring_Diagram/README.md @@ -0,0 +1,23 @@ +# Electronics Case Wiring Diagram for QUEEN (my Voron 2.4 build): + +This repository contains JPG and PDF files for the electronics case for QUEEN. + +### The PDF file of the "Electronics Case Wiring Diagram" for QUEEN: + +Coming Soon. + + + +## A Picture of the "Electronics Case Wiring Diagram" for QUEEN: + +Coming Soon. + + \ No newline at end of file diff --git a/README.md b/README.md new file mode 100644 index 0000000..3d4c53a --- /dev/null +++ b/README.md @@ -0,0 +1,173 @@ +# This is my Build Log Repository for my Voron 2.4 250mm DIY 3D Printer called "QUEEN": + +This repository contains wiring diagrams, specification sheets, any documentation I use to complete my Voron 2.4 build. Designs for the back panel or designs that have aesthetic value. + +My Voron 2.4 3D Printer has a name "QUEEN". + +## Mother board I plan on using: + +I will be using the Octopus Pro V1.0 board and the mother board for my Voron 2.4 printer. +I will be powering my TMC5160 PRO stepper motor drivers with 48V DC. + +## Planning Phase: + +This is a work in progress. I am still planning on my Voron 2.4 build. + +I have all my PIF parts and sourced all my parts via "sub-kits". This will be explained later. + +I want to post an Excel spreadsheet for where I bought all my "sub-kits" or individual items for my Voron 2.4 build. + +## MODS I plan for QUEEN: + +For now these are the MODS I plan on trying out: + +GadgetAngel's Voron 2.4 MODS (250 mm^3 Build): + Tool head PCB board options (MODS) I am considering: + A. Hartk1213's "Tool headBoard for Voron Afterburner v4.1" (https://github.com/hartk1213/Voron-Hardware/tree/hartk1213/Voron-Hardware/Afterburner_Toolhead_PCB). Buy one at https://deepfriedhero.in/products/toolhead-board-for-voron-v2-4?_pos=1&_psq=boards&_ss=e&_v=1.0&variant=40751516418217 + AA. Wiring Diagram for "Tool headBoard for Voron Afterburner v4.1" Toolhead board: https://github.com/hartk1213/Voron-Hardware/blob/hartk1213/Voron-Hardware/Afterburner_Toolhead_PCB/Images/Rev3.2/wiringDiagram.png + B. Hartk1213's "Voron Afterburner Toolhead Board v3.rabbit" (https://github.com/hartk1213/Voron-Hardware/tree/hartk1213/Voron-Hardware/Afterburner_Toolhead_PCB). Buy one at https://deepfriedhero.in/products/voron-afterburner-toolhead-board-v3-rabbit?_pos=1&_psq=v3.&_ss=e&_v=1.0 + BB. Wiring Diagram for Voron Afterburner Toolhead Board v3.rabbit" Tool headboard: https://github.com/hartk1213/Voron-Hardware/blob/hartk1213/Voron-Hardware/Afterburner_Toolhead_PCB/Images/Wiring/ERCF-Toolhead%20SKR%201_4%20wiring.png + C. TURBO CAN Tool Head PCB Mod: https://github.com/henrikssn/TurboCAN (STM32F072CBUx) + + Other MODS I am considering for my build: + A. MGN12 Mod (https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/arkeet/mgn12); + B. PINS Mod (https://github.com/hartk1213/MISC/tree/main/Voron%20Mods/Voron%202/2.4/Voron2.4_Pins_Mod); + C. GE5C mod (https://github.com/hartk1213/MISC/tree/main/Voron%20Mods/Voron%202/2.4/Voron2.4_GE5C/STLs); + D. NeverMore Micro Filter Mod (https://github.com/0ndsk4/VoronUsers/tree/0ndsk4/printer_mods/0ndsk4/Nevermore_Air_Filter/Nevermore_Micro); + E. V2.4_z_drive_motor_tensioner_mod (https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/edwardyeeks/V2.4_z_drive_motor_tensioner_mod); + F. Klicky Probe Mod (https://github.com/jlas1/Klicky-Probe); + G. Ti Bracker Mod (https://github.com/tanaes/whopping_Voron_mods/tree/main/extrusion_backers); + H. Other-V2-Idlers (https://github.com/VoronDesign/VoronUsers/tree/a425971f2986578e2e5c10e638f59d02172687c1/printer_mods/Phalanx/Other-V2-Idlers) + I. AB-BN Afterburner mod (https://github.com/VoronDesign/VoronUsers/blob/master/printer_mods/Badnoob/AB-BN/Readme.md); + J. Sexbolt Z-Endstop Mod (https://github.com/hartk1213/MISC/tree/main/Voron%20Mods/Voron%202/2.4/Voron2.4_SexBolt_ZEndstop); + K. PCB Cover Mod (https://github.com/craxoor/VoronMods/tree/master/PCB%20Cover); + L. Z_Drive_Belt_Exit_Covers (https://github.com/VoronDesign/Voron-2/tree/Voron2.2/STLs/VORON2.2/Bottom_Skirts_%2B_Decorative_Parts/Z_Drive_Belt_Exit_Covers); + M. Umbilical Mod (https://github.com/hartk1213/MISC/tree/main/Voron%20Mods/Voron%202/2.4/Voron2.4_umbilical_strain_relief) & (Y Endstop relocation - https://github.com/hartk1213/MISC/tree/main/Voron%20Mods%2FVoron%202%2F2.4%2FVoron2.4_Y_Endstop_Relocation); + N. Decontaminator_Purge_Bucket_&_Nozzle_Scrubber (https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/edwardyeeks/Decontaminator_Purge_Bucket_%26_Nozzle_Scrubber); + O. bottom_panel_mag_clip Mod (https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/hernsl/bottom_panel_mag_clip); + P. Deck_Panel_Support_Clips Mod (https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/wile-e1/Deck_Panel_Support_Clips); + Q. skirt_switch_mod (https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/tayto-chip/skirt_switch_mod) [RH or LH side Skirt] AND/OR + R. PowerSkirt Mod (https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/leandromarceddu/PowerSkirt) [RH or LH side Skirt] AND/OR + S. Side_Fan_Support_No_Tape Mod (https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/StvPtrsn/Side_Fan_Support_No_Tape) [RH or LH side Skirt]; + T. Skirt_Mod_250 Mod (https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/MarcPot/Skirt_Mods/250) [Rear or Front Skirt] AND/OR + U. BTT_PITFT50_v2_Mount Mod (https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/alanho/BTT_PITFT50_v2_Mount) [Rear or Front Skirt] OR + V. LCD_case_mod (https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/Spaghetti-Bolognese/LCD_case_mod) [Rear or Front Skirt]; + W. Mag Panel Mod (https://github.com/Yeriwyn/VoronUsers/tree/V1-and-V2-panels/printer_mods/yeri/V1_V2_Magnetic_Panels) + X. oab1 v2.2 Recirculating Filter (https://github.com/oab1/VoronMods/tree/main/v2.2%20Recirculating%20Filter) + +## How I calculated the power requirements for my QUEEN build: + +I know a lot of you already know the answer but for the rest of us that are still learning about bipolar stepper motors and stepper drivers. I want to share what I have learned today. I never realized that the motors I own are bipolar-series motors. + +To me when things are connected in series the wires are daisy-chained together (positive lead1, negative lead1 is connected to positive lead2, negative lead2). + +When things are wired in parallel then the positive leads are connected together and the negative leads are connected together. + +So I thought the 3D printer motors where connected together in parallel on the 3D printer, which they are. If you look at the system in a "macro" view not a "micro" view. + +My problem was not understanding the term "series" and "parallel" when it applies to the internal wiring of the 4 wire bipolar motor (a "micro" view). + +I had to look at 8 wire bipolar motors before I actually go it through my thick head. + +Maybe this will help others: +[Drawing of 8 wire bipolar-parallel motor](https://www.google.com/search?rlz=1C1KDEC_enUS925US925&sxsrf=AOaemvLwrmaDl8ua4lQseCKg1z3Zyqv7hA:1632969577225&source=univ&tbm=isch&q=stepper+driver+schematic+with+bipolar+parallel&fir=4TCFBxk3bBwQHM%252CPz8Y0vCOJhjweM%252C_%253Bdc6Xcx5op01amM%252CPz8Y0vCOJhjweM%252C_%253BItQbyHd9IexujM%252CdmTk8dQZiaTOKM%252C_%253BJq7NH4XUzw-gaM%252CbmpTPUvcAgJ1iM%252C_%253BNUciJ8biUMyATM%252CdmTk8dQZiaTOKM%252C_%253Bek59VPLAp7FTaM%252CfLr7UhIdS3zfiM%252C_%253Bcr7a5jpp9XtmSM%252CzzUhUZJ6gFb9SM%252C_%253BcHqWrnFkQqbUFM%252CU6NS1Lt6QBz7EM%252C_%253BxAUcqizP6jkfWM%252C8vsQdXCGrpQ9nM%252C_%253BHgNwYdr3N6uCPM%252CNKxfcF59LDIYkM%252C_&usg=AI4_-kR9_lmMfvjdB0rNsNvfnE_PhDKY6w&sa=X&ved=2ahUKEwi28NDc1aXzAhXFmmoFHevzDAUQ7Al6BAgCEEY&biw=1514&bih=650&dpr=1.25#imgrc=HgNwYdr3N6uCPM) + +[Drawing of 8 wire bipolar-series motor](https://www.google.com/imgres?imgurl=https%3A%2F%2Fbuildbotics.com%2Fcontent%2Fimages%2F2019%2F09%2F8wireSeries.png&imgrefurl=https%3A%2F%2Fbuildbotics.com%2Fwiring-stepper-motors%2F&tbnid=c1vZXhJLkcsohM&vet=12ahUKEwinr7uN1aXzAhUGFKwKHYYtChEQMygJegUIARCzAg..i&docid=NKxfcF59LDIYkM&w=716&h=395&q=stepper%20driver%20schematic%20with%20bipolar%20motor%20series&ved=2ahUKEwinr7uN1aXzAhUGFKwKHYYtChEQMygJegUIARCzAg) + +So ALL my motors are 4-wire bipolar-series motors! + + To Determine the amount of Power Required for your Voron 2.4 build: + + Fact: During a Z Hope move 6 motors will be active at a time. + Fact: Extruder (E) Motor LDO-42STH20-1004ASH: + Rated Peak current: 1.0A/ Phase + Fact: Z motors and AB motors are LD0-42STH40-2004MAH + Rated Peak current: 2.0A / Phase + + Rule of Thumb (https://robotics.stackexchange.com/questions/14071/how-to-calculate-my-power-supply-voltage-and-current): + 1. Power_supply_current = number_of_motors * 1/3 * motor_peak_current for "bipolar-series motors" (All LDO motors are bipolar-Series Motors!) + 2. Power_supply_current = number_of_motors * 2/3 * motor_peak_current for "bipolar-parallel motors" + + Since ALL LDO motors I own are bipolar-Series Motors we will use Rule of Thumb #1 ONLY! + Power_ _supply_current = (5 * 1/3 * 2.0 Amps) + (1 * 1/3 * 1.0A) = 3.333 + 0.333 = 3.6667 or 4 Amps in series for 48V @ 4Amp = 192 Watts or 200 Watts PSU (if the PSU supplies the full power without an aluminum plate for heat dissipation). + +Power my Voron 2.4 48VDC 250 mm Build (running all HT motors from LDO at 48VDC) with the following: +See Spec Data sheet : https://www.meanwellusa.com/upload/pdf/UHP-200(R)/UHP-200-spec.pdf + +1. 48V PSU UHP-200-48 (AC to DC PSU)[(4.2A*0.8)= 3.36 Amps; I need 4 Amps! [not on aluminum plate so 80%]] : https://www.digikey.com/en/products/detail/mean-well-usa-inc/UHP-200-48/7707242 +2. 24V PSU UHP-200-24 (AC to DC PSU)[(8.4A*0.8)= 6.72 Amps ; I want at least 9 Amps! [not on aluminum plate so 80%]]: https://www.digikey.com/en/products/detail/mean-well-usa-inc/UHP-200-24/7707239 + +3. 48V PSU UHP-350R-48 (AC to DC PSU)[(7.3A*0.70)= 5.32 Amps; I need 4 Amps [not on aluminum plate so 70%]] : https://www.digikey.com/en/products/detail/mean-well-usa-inc/UHP-200-48/7707242; https://www.newark.com/mean-well/uhp-350r-48/power-supply-ac-dc-48v-7-3a/dp/01AH8032?ost=uhp-350r-48 +4. 24 PSU UHP-350R-24 [(14.6A*0.70)= 10.22 Amps; I want at least 9 Amps [not on aluminum plate so 70%]]: https://www.newark.com/mean-well/uhp-350r-24/power-supply-ac-dc-24v-14-6a/dp/01AH8029?ost=uhp-350r-24 + +5. 48V PSU UHP-500-48 (AC to DC PSU)[(10.45*0.7)= 7.315 Amps; I need 4 Amps [not on aluminum plate so 70%]] : https://www.newark.com/mean-well/uhp-500-48/power-supply-ac-dc-48v-10-45a/dp/01AH8038?ost=uhp-500-48 +6. 24V PSU UHP-500-24 (AC to DC PSU)[(20.9*0.7) = 14.63 Amps; I want at least 9 Amps [not on aluminum plate so 70%]]: https://www.newark.com/mean-well/uhp-500-24/power-supply-ac-dc-24v-20-9a/dp/01AH8036?ost=uhp-500-24 + +So I could use option 3 & 4 OR 5 & 6. Since I plan on LEDS and running a Raspberry Pi 4B with a solid state disk drive via USB 3.1 interface instead of using a Micro-SD card I want to have enough power to add extras to my Voron Build. + +I opted to buy the UHP-500-48 for my 48VDC supply +I opted to buy the UHP-500-24 for my 24VDC supply +I opted to buy the RSP-25-5 for my 5VDC supply +I opted to buy the UHP-200-12 for my 12VDC supply. + +I will use the Octopus Pro to power the stepper motor drivers, heater cartridge, temperature sensors, limit switches, and generate signals on PINs to control stuff, but I do not plan on powering stuff off the Octopus Pro board that is considered optional equipment like LEDs, and endoscope or cameras. Since my Raspberry Pi (running Klipper) is the brains of this setup, I will be using a solid state drive to act as the disk drive for the Raspberry Pi. This adds additional current draw and the Raspberry Pi will have its own 5V PSU. + +All my LEDS are 12VDC or 24VDC. So that is why I am running a separate 12VDC PSU and added additional current capability to my 24VDC supply. + +I plan on running all TMC5160 (HV) PRO stepper motor drivers for all my motors on QUEEN. +I know this is an overkill but if I want the power it will be there. I am lazy, and I do not want to redo wiring at a later date. + +I am hoping I can fit all of this in my electronics case for a 250 mm build. But the UHP power supplies are 1/2 the width of LRS-series PSUs. I can fit the UHP-500-48 and UHP-500-24 in the same footprint as the LRS-200-24 PSU that is specified in the BOM. + +## The PDF file of the "Color PIN Diagram" for the Octopus Pro V1.0: + +You can view the PDF in your browser by clicking on the filename ["BIGTREETECH-Octopus-Pro-V1.0-Color-PIN-V2.2.pdf"](https://github.com/GadgetAngel/BTT_Octopus_Color_PIN_Diagram/blob/main/BTT_Octopus_Pro_V1.0_Color_PIN_Diagram/BIGTREETECH-Octopus-Pro-V1.0-Color-PIN-V2.2.pdf) and then hit the download button. + +You can view an even higher resolution image when you view the PDF in you browser by clicking on the filename ["BIGTREETECH-Octopus-Pro-V1.0-Color-PIN-V2.2-600ppi.pdf"](https://github.com/GadgetAngel/BTT_Octopus_Color_PIN_Diagram/blob/main/BTT_Octopus_Pro_V1.0_Color_PIN_Diagram/BIGTREETECH-Octopus-Pro-V1.0-Color-PIN-V2.2-600ppi.pdf) and then hit the download button. + +## A Picture of the "Color PIN Diagram" for the Octopus Pro V1.0: + +You can download the JPG file for this "Color PIN Diagram" by clicking on the filename ["BIGTREETECH-Octopus-Pro-V1.0-color-PIN-V2.2.jpg"](https://github.com/GadgetAngel/BTT_Octopus_Color_PIN_Diagram/blob/main/BTT_Octopus_Pro_V1.0_Color_PIN_Diagram/BIGTREETECH-Octopus-Pro-V1.0-color-PIN-V2.2.jpg) or the filename ["BIGTREETECH-Octopus-Pro-V1.0-color-PIN-V2.2-600ppi.jpg"](https://github.com/GadgetAngel/BTT_Octopus_Color_PIN_Diagram/blob/main/BTT_Octopus_Pro_V1.0_Color_PIN_Diagram/BIGTREETECH-Octopus-Pro-V1.0-color-PIN-V2.2-600ppi.jpg) and then hit the download button. Again, to download the PDF just click on the filename ["BIGTREETECH-Octopus-Pro-V1.0-Color-PIN-V2.2.pdf"](https://github.com/GadgetAngel/BTT_Octopus_Color_PIN_Diagram/blob/main/BTT_Octopus_Pro_V1.0_Color_PIN_Diagram/BIGTREETECH-Octopus-Pro-V1.0-Color-PIN-V2.2.pdf) or the filename ["BIGTREETECH-Octopus-Pro-V1.0-Color-PIN-V2.2-600ppi.pdf"](https://github.com/GadgetAngel/BTT_Octopus_Color_PIN_Diagram/blob/main/BTT_Octopus_Pro_V1.0_Color_PIN_Diagram/BIGTREETECH-Octopus-Pro-V1.0-Color-PIN-V2.2-600ppi.pdf) and hit the download button. + +![JPG of Color PIN Diagram](BIGTREETECH-Octopus-Pro-V1.0-color-PIN-V2.2.jpg) + +## Located in the "Wiring_Harness_Diagram" directory you will find the wiring harness diagram for QUEEN: + +This is the wiring harness diagram I developed for my Voron 2.4 build: + +![JPG of wiring harness Diagram](images/Voron_2.4_Tool_Head_PCB__Wiring_Harness.jpg) + +You can view the PDF in your browser by clicking on the filename ["Voron_2.4_Tool_Head_PCB__Wiring_Harness.pdf"](https://github.com/GadgetAngel/Voron2.4_My_Build_Log/blob/main/Voron2.4_My_Build_Log/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness.pdf) and then hit the download button. + +## Located in the "Electronics_Case_Wiring_Diagram" directory you will find the wiring diagram for the electronics case for QUEEN: + +This is the electronics wiring diagram I developed for my Voron 2.4 build: + +YET TO BE DONE, coming soon. + +## The Original BIGTREETECH Wiring Diagram for the Octopus Pro V1.0: + +![Original Wiring Diagram](images/BIGTREETECH-Octopus-Pro-V1.0-Original-Wiring-Diagram.jpg) + +## BIGTREETECH has a GitHub repository for the Octopus Pro V1.0: + +The BIGTREETECH Github repository is located at https://github.com/bigtreetech/BIGTREETECH-OCTOPUS-Pro + +## Klipper firmware supports the Octopus Pro V1.0 board: + +Here is the link to the config file on GitHub for the Octopus pro V1.0 board https://github.com/Klipper3d/klipper/blob/master/config/generic-bigtreetech-octopus.cfg. + +If you are using the "PROBE" connector for a proximity sensor you will need to add a [probe] section to the "generic-bigtreetech-octopus.cfg" file and ensure that the sensor_pin: PC5 + +There is only two PINs that are different between the Octopus V1.1 pin-out and the Octopus Pro V1.0 pin-out. The Octopus V1.1 pin-out has PC5 on the EXP2 connector but on the Octopus Pro V1.0 this pin on the EXP2 connector is now "Not Connected (NC)". + +The second PIN difference is that on the Octopus V1.1 pin-out PB7 is the signal PIN used on the PROBE/SENSOR connector and on the BLTouch header but on the Octopus Pro V1.0 the signal pin on the PROBE connector is PC5. Which means that on the Octopus V1.1 board you can only use either a BLTouch or a Proximity Sensor but NOT both. On the Octopus Pro V1.0 since the signal pins for the PROBE connector is different from the BLTouch, if you wanted to, you could use both ports. + +If you plan to use a voltage higher than 24V on MOTOR_POWER_IN then please pay attention to the following footnotes on the "Color PIN Diagram": 1. + +You may need to change the Fuse on the MB_POWER_IN, calculate the maximum amps you will be using (3.(the four heaters {HE0-HE3}, 3.3V rail, 5V rail, and 12V rail all come off the 24V rail). The maximum amps for 3.3 V rail is 1 Amp. The maximum amps for the 5V rail is 8 Amps. The maximum amps for 12 VDC rail is 4 Amps. So the total maximum amps for 3.3 VDC rail + 5 VDC rail + 12 VDC rail is equal to 13 Amps, but the amps needed to run the four heaters needs to be added to this value. Since BIGTREETECH supplies us with a 20 Amp fuse, then BIGTREETECH is saying that you have 7 more Amps available for the four heater ports or 1.75 Amps / heater cartridge. + +Please use the "Color PIN Diagram" in [BTT_Octopus_Pro_V1.0_Color_PIN_Diagram](https://github.com/GadgetAngel/BTT_Octopus_Color_PIN_Diagram/tree/main/BTT_Octopus_Pro_V1.0_Color_PIN_Diagram) to obtain the correct PIN assignments. + +If you decide to flash a new bootloader to the Octopus Pro V1.0 board (you should not need to because you can upload the new Klipper firmware using the micro-SD card reader) and find that the micro-SD card bootloader no longer works you will want to return the board to its shipment state by finding the original bootloader and "bootlaoder+firmware" files at https://github.com/GadgetAngel/BTT_SKR_13_14_14T_SD-DFU-Bootloader/tree/main/bootloader_bin/backed_up_original_bootloaders + diff --git a/Wiring_Harness_Diagram/README.md b/Wiring_Harness_Diagram/README.md new file mode 100644 index 0000000..7633c8b --- /dev/null +++ b/Wiring_Harness_Diagram/README.md @@ -0,0 +1,19 @@ +# Wiring Harness for QUEEN (my Voron 2.4 build): + +This repository contains JPG and PDF files for the wiring harness for QUEEN. + +### The PDF file of the "Wiring Harness" for QUEEN: + +The PDF file looks the same as the JPG file. You can enlarge the image for both file types to get all the details. + +You can view the PDF in your browser by clicking on the filename ["Voron_2.4_Tool_Head_PCB__Wiring_Harness.pdf"](https://github.com/GadgetAngel/Voron2.4_My_Build_Log/blob/main/Voron2.4_My_Build_Log/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness.pdf) and then hit the download button. + +You can view an even higher resolution image when you view the PDF in your browser by clicking on the filename ["Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.pdf"](https://github.com/GadgetAngel/Voron2.4_My_Build_Log/blob/main/Voron2.4_My_Build_Log/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.pdf) and then hit the download button. + +## A Picture of the "Wiring Harness" for QUEEN: + +You can download the JPG file for this "Wiring Harness" by clicking on the filename ["Voron_2.4_Tool_Head_PCB__Wiring_Harness.jpg"](https://github.com/GadgetAngel/Voron2.4_My_Build_Log/blob/main/Voron2.4_My_Build_Log/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness.jpg) or the filename ["Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.jpg"](https://github.com/GadgetAngel/Voron2.4_My_Build_Log/blob/main/Voron2.4_My_Build_Log/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.jpg) and then hit the download button. + +Again, to download the PDF just click on the filename ["Voron_2.4_Tool_Head_PCB__Wiring_Harness.pdf"](https://github.com/GadgetAngel/Voron2.4_My_Build_Log/blob/main/Voron2.4_My_Build_Log/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness.pdf) or the filename ["Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.pdf"](https://github.com/GadgetAngel/Voron2.4_My_Build_Log/blob/main/Voron2.4_My_Build_Log/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.pdf) and hit the download button. + +![JPG of Wiring_Harness Diagram](Voron_2.4_Tool_Head_PCB__Wiring_Harness.jpg) diff --git a/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness.jpg b/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness.jpg new file mode 100644 index 0000000..097852f Binary files /dev/null and b/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness.jpg differ diff --git a/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness.pdf b/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness.pdf new file mode 100644 index 0000000..4f20ba5 Binary files /dev/null and b/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness.pdf differ diff --git a/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.jpg b/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.jpg new file mode 100644 index 0000000..0858b7d Binary files /dev/null and b/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.jpg differ diff --git a/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.pdf b/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.pdf new file mode 100644 index 0000000..b6acb39 Binary files /dev/null and b/Wiring_Harness_Diagram/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.pdf differ diff --git a/images/BIGTREETECH-Octopus-Pro-V1.0-Original-Wiring-Diagram.jpg b/images/BIGTREETECH-Octopus-Pro-V1.0-Original-Wiring-Diagram.jpg new file mode 100644 index 0000000..91d7fd5 Binary files /dev/null and b/images/BIGTREETECH-Octopus-Pro-V1.0-Original-Wiring-Diagram.jpg differ diff --git a/images/BIGTREETECH-Octopus-Pro-V1.0-color-PIN-V2.2.jpg b/images/BIGTREETECH-Octopus-Pro-V1.0-color-PIN-V2.2.jpg new file mode 100644 index 0000000..d89841e Binary files /dev/null and b/images/BIGTREETECH-Octopus-Pro-V1.0-color-PIN-V2.2.jpg differ diff --git a/images/BIGTREETECH_Octopus_Pro-V1.0-original-PIN.jpg b/images/BIGTREETECH_Octopus_Pro-V1.0-original-PIN.jpg new file mode 100644 index 0000000..a18f7f3 Binary files /dev/null and b/images/BIGTREETECH_Octopus_Pro-V1.0-original-PIN.jpg differ diff --git a/images/Voron_2.4_Tool_Head_PCB__Wiring_Harness.jpg b/images/Voron_2.4_Tool_Head_PCB__Wiring_Harness.jpg new file mode 100644 index 0000000..097852f Binary files /dev/null and b/images/Voron_2.4_Tool_Head_PCB__Wiring_Harness.jpg differ diff --git a/images/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.jpg b/images/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.jpg new file mode 100644 index 0000000..0858b7d Binary files /dev/null and b/images/Voron_2.4_Tool_Head_PCB__Wiring_Harness_400ppi.jpg differ