Jump to content

Search the Community

Showing results for tags 'klipper'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • TeamFDM
    • Site Updates and Announcements
    • Frequently Asked Questions
    • General Discussion
    • Voron User Mods
    • Filaments
    • Build Diaries
    • Introductions
    • Tutorials
  • Voron Build Support
    • Voron 0
    • Voron Trident
    • Voron 2
    • Voron Legacy
    • Voron Extruders
    • Voron Electronics
    • Slicers and Print Troubleshooting
  • Other FDM Printers
    • Ender 3 / Ender 3 Pro
    • Anet A8 / AM8
    • Prusa
    • Generic / Other
  • Marketplace
    • The Bazaar
  • Vendors
    • KB-3D
    • Voron Printed Parts Co.
    • Fabreeko
  • Off-Topic
    • Random
    • TeamFDM Member's Creative Collection

Categories

  • Non Printable Files
  • Printable Voron User Mods
  • Manuals and PDF Guides
  • Creative Collection
  • Tools and Calibration
  • Official Voron Releases

Categories

  • User Mod Installs
  • Build Techniques
  • Programming
  • Team FDM Site Tutorials
  • CAD / Fusion 360 Tutorials

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Voron Serial #1


Voron Serial #2


Voron Serial #3

Found 13 results

  1. My Voron 2.4 running Klipper had been running great for a while but the afterburner assembly was starting to show weakness. I thought it was a good time for an upgrade so I installed a new Orbiter 2.0 with filament detector on my Voron 2.4 and the problems began...... witht he Orbiter 2.0 installed i have not been able to get my rotation distance anything like close to accurate. last print had massive over extrusion with lots of noise from the extruder. To statrt isolating the problem /as an experiment I ran 50mm (requested) filament through the extruder body only (no lower nozzle assempbly) and got about 250mm of filament instead. Fortunately the awful noise stopped. Ergo i think my initial problem is that the over extrusion i jsut discovered was overwhelming the nozzle and jamming. easy so far. On to the print config..... And incredible frustration as any and all changes to the print config file make no measurable difference in the amount of over feed. here is the code after a lot of trial and error and no change (i suspect there are a number of settings that i have turned off or on to see what if anything would happen- no change.). here is the code- ##################################################################### # Extruder ##################################################################### ## Connected to MOTOR_6 ## Heater - HE0 ## Thermistor - T0 [extruder] step_pin: PE2 dir_pin: PE3 enable_pin: !PD4 ## Update value below when you perform extruder calibration ## If you ask for 100mm of filament, but in reality it is 98mm: ## rotation_distance = <previous_rotation_distance> * <actual_extrude_distance> / 100 ## 22.6789511 is a good starting point #Bondtech 5mm Drive Gears AfterBurner ## 34.37086 for Bondtech 8mm gears (Galileo ## rotation_distance: 4.637 for Orbiter 2.0 rotation_distance: 4.637 ## Update Gear Ratio depending on your Extruder Type ## Use 50:17 for Afterburner/Clockwork (BMG Gear Ratio) ## Use 80:20 for M4, M3.1 # orbiter motor LDO-36STH20-1004AHG(XH) # gear_ratio: 7:1 microsteps: 16 full_steps_per_rotation: 200 #200 for 1.8 degree, 400 for 0.9 degree # max_extrude_only_distance: 500 # max_extrude_only_velocity: 120 # <- for orbiter motor LDO-36STH20-1004AHG(XH) # max_extrude_only_accel: 800 # <- for orbiter motor LDO-36STH20-1004AHG(XH) nozzle_diameter: 0.400 filament_diameter: 1.75 heater_pin: PA2 ## Validate the following thermistor type to make sure it is correct ## See https://www.klipper3d.org/Config_Reference.html#common-thermistors for additional options sensor_type: SliceEngineering 450 sensor_pin: PF4 min_temp: 10 max_temp: 270 max_power: 1.0 min_extrude_temp: 170 # control = pid # pid_kp = 26.213 # pid_ki = 1.304 # pid_kd = 131.721 ## Try to keep pressure_advance below 1.0 pressure_advance: 0.025 ## Default is 0.040, leave stock pressure_advance_smooth_time: 0.030 ## E0 on MOTOR6 ## Make sure to update below for your relevant driver (2208 or 2209) [tmc2209 extruder] uart_pin: PE1 interpolate: False run_current: 0.85 hold_current: 0.100 sense_resistor: 0.11 stealthchop_threshold: 0 # driver_TBL: 0 # driver_HEND: 6 # driver_HSTRT: 7 # driver_TOFF: 4 ###################################################################################################### ## I haven't made any changes above or below these lines so i the problem MAY be in here################################## ###################################################################################################### All of which leads me to my theory - incorrect wiring of the ldo-36st17-1004ahg to the tcm2209. Now i am very new to electronics and the instructions for wiring the Orbiter 2.0 to the V2.4 are yet to be found by me (if anybody has them, please share) so it would be an easy mistake. i feel like this is some sort of reversed polarity issue and leaves me with no idea where to begin with figuring this out. anybody got any ideas?
  2. Version 2022.03.31

    83 downloads

    Printable STL files to enable better print calibration for your Klipper based 3D printer.
  3. Don't know if it's allowed to link to the official Voron-Forum, but I think this is a very useful hint in regarding of Printer security: pls. delete the Link if not allowed: https://forum.vorondesign.com/threads/psa-gpio-pins-to-set-at-micro-controller-startup.169/ On my Octopus1.1 the hotend fan pin is PE5. I went for this and it works great
  4. I have the Stealthburner beta(0) running, but I've run into a problem. When I include the klipper macro cfg file into printer.cfg in Klipper, Klipper throws an error "Section 'sb_led.cfg' is not a valid config section". I don't follow everything that's going on in the cfg file, but I don't see anything that looks structurally different from other included cfg files that are not causing problems. The contents of the file were copy/pasted from the file in the "klipper macros" folder inside the Stealthburner beta(0) file I downloaded (did change the pin to pin: PB0, using the neopixel connector on the BTT Octopus board). Also tried copy/pasting the macros from voron_2.4_klipper_config/stealthburner_leds.cfg at master · wuzefacke/voron_2.4_klipper_config · GitHub . Same result. Any ideas what I might be missing/doing wrong?
  5. Whenever I test something like Z_endstop_calibrate or anything which after the end it mentioned to save_config. And we can expect the auto config in our printer.cfg at the bottom. However, this stop happen to me. I got the PID auto config but that's it. After I did 1st PID and it never write anything for me again. Anything to do with my klipper_firmware_dirty? Please help thanks.
  6. Hi. Do you know where should i look at my led problem It was on only logo when I first config the led in printer cfg. I was happy i didnt know what actual light should be on and when all LED will be on. Then sometime later along the building and fixing issue suddenly when power on the 2 part led on green while logo on and white. And sometime later i fixed things later the part led green off again. But logo LED still on normally. Then once i got everything and start initial tuning pid and stuff. Part led on again this time white same as logo. Logo has always been on. After i got klicky install and with led cfg. My logo start to have status color as macro in the config. But part led off again. Please tell me how yo debug. Thanks.
  7. Klipper reports: ERROR Source contains parsing errors: '/home/pi/klipper_config/printer.cfg' [line 12]: 'tu\n' Once the underlying issue is corrected, use the "RESTART" command to reload the config and restart the host software. Printer is halted Specs: V2.4 running klipper and mainsail. Running a Pi4 and Octopus board. I'm new to this stuff, and not looking for a answer to just be dolled out, but kinda lost at this point. I had this error congruently, but have since fixed it I believe by removing that line from the mainsail config file. Source contains parsing errors: '/home/pi/klipper_config/mainsail.cfg' [line 18]: 'CANCEL_PRINT\n' Once the underlying issue is corrected, use the "RESTART" command to reload the config and restart the host software. Printer is halted
  8. I’m looking for a way to set the case light single color LED strip to go off after the printer starts or after the lights are turned on. I have searched and searched and can’t seem to find a way to do it. I have them set to turn on at start up then a macro to toggle on and off. Any help would be appreciated. Yes I am pretty new to Klipper but am catching on to the macros quickly after setting up my Euclid probe.
  9. I'm using Octoprint, Klipper, Canboot, EBB36 and Octoprint with my work in progress Voron 2.4. I have so many issue that make the klipper got disconnected or I fired firmware restart often. Most of the time klipper just doesn't reconnect. What happen? or are there any log file I can trace or look at the real problem?
  10. Hi all, thanks in advance for any and all help and comments. This is my problem... I want to implement a LOAD_FILAMENT macro in my printer.cfg like the example below. [gcode_macro LOAD_FILAMENT] gcode: {% set speed = params.SPEED|default(300) %} {% set max_velocity = printer.configfile.settings['extruder'].max_extrude_only_velocity %} SAVE_GCODE_STATE NAME=load_state M300 # beep G91 G92 E0 G1 E350 F{max_velocity} # fast-load G1 E25 F{speed} # purge M300 M300 RESTORE_GCODE_STATE NAME=load_state My problem is... I keep getting this error. Extrude only move too long (350.000mm vs 50.000mm) Now, I understand what this error means, i.e. 50mm is the max allowable extrude distance and I also learned, based on my research, that the way to avoid this is to have a G92 E0 code before extruding but I still get the error. Any help will be greatly appreciated.
  11. Presently building a 2.4 but I've also converted my Artillery X1s to Klipper/Mainsail. I use to monitor all of my printers and webcams thru one platform OctoFarm is there an equivalent platform available for Klipper?
  12. Bonjour, ou le gcode_macro PRINT_START doit il ce trouver? je l'ai mis dans printer.cfg mais cela n'est pas pris en compte. Merci
  13. More of a Klipper/Mainsail question than slicer, but hope its ok here.... I am really missing the Region Exclude plugin from Octoprint in Mainsail, they have a nice Gcode preview, but no way to exclude something there. This is of course very usefull with a full plate where one item fails (comes from plate, etc) so you can exclude it, and print can continue without printing filament in the air...and making a mess... maybe even failing everything. There is this dude here saying he is using in in beta and should be released, still cannot find it, not in release notes, anything. Is this guy full of bullshit, or am I just a freaking idiot and looking in the wrong places hahaha! Hope someone can help!
×
×
  • Create New...