Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config: Lulzbot TAZ5 config, and TAZ6 and RAMBo config improvements #6705

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

eraserhd
Copy link

@eraserhd eraserhd commented Oct 5, 2024

This adds a new config for TAZ5 with a DualExtruder v3.

The TAZ6 has mostly the same guts (same mainboard for sure), so I started from that. In the process I made some fixes to the TAZ6 configs:

  • Added missing chassis fans for the TAZ6 configs.
  • Added a commented out chassis fan for the generic RAMBo config.
  • Added T0 and T1 macros for the TAZ6 dual extruder.

The chassis fan was verified from the RAMBo schematic and the wiring instructions for the TAZ6.

The TAZ5 config is tested and works on a real machine. The machine is stock in all the ways that matter for this config.

Differences TAZ5 -> TAZ6 differences were largely about homing. These I things changed:

  • Two endstop pins were different.
  • [bed_screws] section
  • Homing location and some axis extents.
  • Reworked START_PRINT and END_PRINT from Lulzbot's Cura profiles.

The stepper digipot is reconfigured, and I think it's more accurate, but since I don't have enough knowledge to fully confirm it, I didn't change TAZ6 or RAMBo. If I'm right, the TAZ6 and RAMBo configs are underpowering their steppers.

@JamesH1978
Copy link
Collaborator

Thank you for submitting a PR, as you have added a whole new config file, you will need to also submit for the regression tests as per point 4 in the guidelines in https://github.com/Klipper3d/klipper/blob/master/docs/Example_Configs.md

Thanks
James

Signed-Off-By: Jason M. Felice <[email protected]>
@eraserhd
Copy link
Author

Updated, thanks!

@JamesH1978
Copy link
Collaborator

Thanks, generally it looks fine to me, although i am not sure why you have set a min_extrude_temp to 120 in both extruder configs, unless there is a good reason to set 120. We generally do not override default safety behaviour.

Also can you confirm the taz5 was released with the dual extruder option out of the box, ie you could purchase at taz5 with this already fitted and not just an after market option? Our configs are generally only for printers that someone would buy off the shelf in default configuration.

Thanks
James

@eraserhd
Copy link
Author

Re: min_extrude_temp, that was just copied from the TAZ6 config and not otherwise touched. I'll remove it (from the TAZ6, too?)

Re: Dual extruder, it wasn't sold that way... but I'm just thinking about it and I didn't realize it was sold on the TAZ6. I figured it was a common upgrade.

I'll make up a stock TAZ5. My original tool head works enough to verify.

Example configs shouldn't override default safety settings

Signed-Off-By: Jason M. Felice <[email protected]>
Default tool head uses RAMBo E1 pins, and direction is reversed.

Tested with original hardware.

Signed-Off-By: Jason Felice <[email protected]>
@eraserhd
Copy link
Author

Done and tested with the original tool head.

@JamesH1978 JamesH1978 self-assigned this Oct 25, 2024
@JamesH1978
Copy link
Collaborator

Apologies It has taken a while for me to get back to this, looks fine except for the macros in your new file for start print and end print. Usually we don't include macros that aren't explicitly needed. @KevinOConnor what are your thoughts on the T0 and T1 macros, added though?

Thanks
James

@KevinOConnor
Copy link
Collaborator

I don't have a strong preference. If it's a "printer" config file and the macros are relevant to successfully printing on that particular printer than I can see value in adding them to the example configs.

Cheers,
-Kevin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants