GithubHelp home page GithubHelp logo

voronusers's People

Contributors

aaronherrick avatar arkeet avatar bartlammers avatar cbc02009 avatar clee avatar eddietheengineer avatar edwardyeeks avatar fheilmann avatar gadgetangel avatar geoffrey-young avatar hartk1213 avatar jlas1 avatar john-- avatar kevinakasam avatar kiloqubit avatar lakoblue avatar lococnc avatar loganfraser avatar mandryd avatar mapleleafmakers avatar masgar avatar maverick-3d avatar newphreak avatar nhchiu avatar richardjm avatar samwiseg0 avatar stvptrsn avatar voron-github-bot avatar xbst avatar zen3dlab avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

voronusers's Issues

Consider linking with CadHub

Just a quick suggestion since you've got both openscad files and STL files in this repo and I'm sure it's a pain updating the STLs each time there's a change to the SCAD code.

CadHub has a feature that allows you to link to an external url to fetch code.

To take @evandepol 's the DIN-Rail-Cable-Mount as an example, the following url: https://github.com/VoronDesign/VoronUsers/blob/master/printer_mods/evandepol/Voron2.4-Cable-clamps/CAD/DIN-Rail-Cable-Mount-350mm.scad

Is encoded into this CadHub url:
https://cadhub.xyz/dev-ide/openScad#fetch_text_v1=https%3A%2F%2Fgithub.com%2FVoronDesign%2FVoronUsers%2Fblob%2Fmaster%2Fprinter_mods%2Fevandepol%2FVoron2.4-Cable-clamps%2FCAD%2FDIN-Rail-Cable-Mount-350mm.scad

image

So that it can be fetched on the fly, meaning that the link will automatically stay up-to-date with the repo, so the link could be added to a readme or even just in a comment at the top of the code.

I'm the main dev behind CadHub, so I'm trying to improve it as I go, but one big limitation to this approach atm is that it's single file only, i.e. the Combination Clamp won't work because it uses use <> statements. Multi-file projects is on the TODO list though.

Also unfortunately I haven't added proper UI for making these urls but the structure is just https://cadhub.xyz/dev-ide/openScad#fetch_text_v1=<you-url>, the included url doesn't have to be encoded but it makes it safer, an easy way to get the url is to go to the file you're interested in on github, open the dev tools and paste the following into the console:
'https://cadhub.xyz/dev-ide/openScad#fetch_text_v1=' + encodeURIComponent(location.href)
And that should give you the url.

Anyway ignore me if this isn't useful. Feel free to let me know if you have any feedback about Cadhub too.

Hidden Cable Z Cover Not 2.4 compatible.

After tearing down and not really thinking about it I found that the cover can't fit under the 2.4's Z linear rails as I think is intended. The 2.4 part and the dimension on the rail height in the manual are 3mm. I plan to edit the file for 2.4 builds in that area or maybe move the Z rails up 3mm to give them a small amount of clearance. Not really keen on moving the rails though. Please include a note of incompatibility with BOM/Stock build in the README. MD ... that being said, thank you for your hard work.

M3x16 hole length for "GE5C No Endstops" mod is wrong

@hartk1213 . The M3x16 hole length for "GE5C No Endstops" mod is wrong.

image
If you use M3x16 screw, you should have 16-2 = 14 mm of hole length. In your design, the hole length is only 13mm long then you have the screw touching the end of the threading of the MGN9 carriage.

You have good hole length value for "GE5C Standard Endstops" and "GE5C Halleffect". 20mm screw length - 2 = 18mm.

I also done a quick redesign of "GE5C No Endstops" for M3x20 screws as I hadn't so many M3x16 in my screws box. I join it here:
GE5C No Endstops - M3x20.zip

No duplicates and no additions policies discourages participation

(Response to #258 (review)):

Please don't make changes in other people's directories.

@KiloQubit I understand why that's a policy, but it combines with the no duplicates policy in discouraging ways.

If the only way to get a mod into the repository is to submit something unique or integrate it with an existing mod, then there are potentially many refinements to those mods that will never make it to the repo, because the refinements can only be placed in the original directory (to avoid making a copy) and the original author is no longer paying attention, or maybe was never that familiar with GitHub in the first place and couldn't execute a multi-step PR sequence without a lot of help. The burden of this kind of contribution is high, and will get higher over time as more "unique" ideas are taken by the first mover.

I understand maintaining this repo is a significant time commitment and something the maintainers do for free for the community, which I and many others greatly appreciate. Thank you for your time!

color_order_GRB config option has been removed

The neopixel color_order_GRB config option has been removed. If necessary, update the config to set the new color_order option to RGB, GRB, RGBW, or GRBW.

So it has to be color_order: GRB in the printer.cfg

Just wanne let people know who try to copy paste the config. Thanks

Small change to README for Voron 0.1

Love the slim handles mod. You might want to add a comment that these work with the v0.1 as well. The only difference that I can see is that there is no clip to remove, so the user will need to insert 4 nuts on each side instead of 3.

Unable to clone repo due to filename length (GadgetAngel)

Unable to clone repo. Filename is too long.

printer_mods/GadgetAngel/Cricut_Voron_Logos/Voron_SW_Logo/1_Color_Layer_WithOut_Logo_Outline_WithOut_Silhouette/Cricut_VoronSW_Logo_RearPanel_1Layer_WithOut_Logo_Outline_WithOUT_Silhouette_and_BackPanel.jpg: Filename too long
error: unable to create file

error: unable to create file printer_mods/GadgetAngel/Cricut_Voron_Logos/Voron_SW_Logo/1_Color_Layer_WithOut_Logo_Outline_WithOut_Silhouette/Cricut_VoronSW_Logo_RearPanel_IndividualObjects_1Layer_WithOut_Logo_Outline_WithOUT_Silhouette.ai: Filename too long

Different wiring required for SKR Mini E3 V2.0

First of all thank you for this great little mod.
I have encountered a little difficulties wiring it to the latest SKR Mini E3 V2.0. On this card, Klipper does not support I2C protocol on the LCD connector.
Then you need to :
-Wire the screen to the Raspberry Pi directly : SDA (PIN 3), SCL (PIN 5), 5V (PIN 2 or 4) and GND (PIN 6 or 9 or other GND available). See GPIO pinouts on google.
-Enable I2C interface on the RPi with raspi-config in SSH.
-Install a specific script and compile / flash a klipper firmware for a Linux process according to this procedure :
https://www.klipper3d.org/RPi_microcontroller.html
-Then declare new entries in printer.cfg. Here's mine :

[mcu host]
serial: /tmp/klipper_host_mcu

[display]
lcd_type: ssd1306
i2c_mcu: host
i2c_bus: i2c.1

[display_status]

Then it works perfectly.

There is a thread for this Klipper "regression" on this specific board version here :
Klipper3d/klipper#3581

Better scrubbing

Scrubbing currently doesn't always remove excess filament from the nozzle. The scrubbing routing only scrubs horizontally left to right. It can be improved by a back and forth scrubbing. Here's working code BUT it hasn't been tested on other purge bucket locations. Just the default rear/left on a Trident.

ALSO: I changed the G1 codes to G0 codes because G1 is intended for moves involving the extruder (printing) whereas G0 is for other movement. It's recommended to find other places in the macro that use G1 and change them to G0 EXCEPT for ones that involve extrusion like the purge.

      ## Perform horizontal wipe. Wipe direction based off bucket_pos for cool random scrubby routine.
      {% for wipes in range(1, (wipe_qty + 1)) %}
         G0 X{brush_start + (brush_width * (1 - bucket_pos))} F{wipe_spd_xy}
         G0 X{brush_start + (brush_width * bucket_pos)} F{wipe_spd_xy}
      {% endfor %}

      ## Perform back/forth wipe.
      G0 X{(brush_start + (brush_width /2) * bucket_pos)} F{wipe_spd_xy}

      {% for wipes in range(1, (wipe_qty + 1)) %}
         G0 Y{Ry}
         G0 Y{Ry-10}
      {% endfor %}

Voron 2.4, Klipper, Octopus inductive prode help

Can anyone please help me with a voron 2.4 inductive probe setup on a octopus?
I,m unsure on what to wire it as,
be it the probe port directly, with diode on pg15 or 11,
with a 4.7k across + and trigger on the probe port also what to do in the config file.
im getting devation from 0.01-0.06 its the only thing stopping me finishing the build,
also would the fact i plan to get a octopus pro board as the octopusi have it on loan help?

Incorrect/incomplete stl files in repo

In ultrawaffles e3 to switchwire conversion, there are a couple of issues with the stls.

The left xz left bearing block in the repo does not match the cad file, and also does not align with the right bearing block due to being 5mm longer. the cad file is correct.

The back grill doesnt look to be provided in the stls, and it isnt clear from the cad of which one to use

A very minor issue, but there is no inclusion for "generic" drag chain mounting, only igus. I am planning on creating the bearing block to have support for it, but I think it should be mentioned.

I'm creating this because I'm not sure if i could submit a pr to correct these changes or not.

@UltraWaffles for awareness

List of Abandoned Mods

This is a list of mods that are no longer being maintained by the original author. Pull requests can be generated against these mods by anyone, ignoring the normal requirement to get the approval of the original author. PRs against abandoned mods not made by the original author should only be merged with multiple reviewer approvals, and should generally be limited to bug fixes and maintenance patches.

For an mod to be included in this list the following conditions need to be met:

  1. An issue or PR has been open against the mod
  2. An attempt was made to contact the original author either on github or on discord
  3. The author has not responded for a period of at least one month
  4. The Voron Dev Team has decided the mod is worth keeping in the repo instead of being removed. (decision made at their discretion)

List of Abandoned Mods:

Original Author Mod Mod Link
edwardyeeks Decontaminator_Purge_Bucket_&_Nozzle_Scrubber link

Slicer start g-code

Like how you've set this whole thing up and most of it speeks for itself. I'm just a little curious tonhow your slicers start g-code is setup since i can't see anything that will trigger the prime macro.

Voron0_MGN9C_X_Axis - lost y travel + Endstop not triggered.

After doing the conversion i realized you lose a few mm of y travel and the y endstop doesn't get triggered anymore, since the linear block hits the a drive before the extrusion hits the endstop. It isn't specified in the readme and i need to design an custom endstop trigger.

LoudOwl aka Stabby airflow issue

@Baltojikale - first of all, thank you for the amazing mod! Everything was printing nice and fit.

Just one issue: Have you/anyone else made a water test for the fans? Both of my fans are spinning fine, but I have the impression that just one side is effective since the air is mostly blowing from the right hole near the nozzle.

Is this supposed to be like that or expected?

Thank you

volcano AB

Would it be possible for you to design a volcano AB? and post it on here? Thanks

ABBN-30 Rapido Print-Head appears to have wrong dimensions

Hi,
the mount that is published for Rapido appears to be incorrect. The nozzle is too close to the fan shroud.
I sent a message in the discord channel but it has been apparently disregarded.
If so there is a good chance to crash the fan shroud into the bed surface while homing Z...
Rapido ABBN-30 mount issue

SlenderFan 2.4 Upgrade and E3v6 compatibility question

I currently have a E3v6 hotend. When I fit the printhead_rear_e3dv6.stl (standard voron 2.4 part) to the duct.stl (part of this build), the cutout for the e3v6 hotend is not correct. Looks like the duct.stl part might be ready for a mosquito hotend and not the E3v6. If I could get access to the duct.step file then I could modify to accomodate the E3v6 part on my own.

The Sexbolt mod and automatic Z offset

The Sexbolt might need a spring under the plunger to provide enough force to push the filament off of the nozzle when doing an automatic Z offset. The microswitch in the Sexbolt has a very light activation force, so the leftover filament (even at filament printing temps) may activate the microswitch before the nozzle is in contact with the plunger.

Use /dev/serial/by-id instead of /dev/serial/by-path/ for SKR1.3 setup guide (and any other)

@jdlongenecker, I would suggest updating ls -l /dev/serial/by-path/ instructions to be ls -l /dev/serial/by-id in order to avoid issues with controllers being swapped on USB ports later in the build or during troubleshooting

E.g, instead of

pi@octovoron:~ $ ls -l /dev/serial/by-path/platform-fd500000.pcie-pci-0000\:01\:00.0-usb-0\:1.3\:1.0
lrwxrwxrwx 1 root root 13 Oct 13 08:50 /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0 -> ../../ttyACM0
pi@octovoron:~ $ ls -l /dev/serial/by-path/platform-fd500000.pcie-pci-0000\:01\:00.0-usb-0\:1.4\:1.0
lrwxrwxrwx 1 root root 13 Oct 13 08:50 /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4:1.0 -> ../../ttyACM1
pi@octovoron:~ $ ls -l /dev/serial/by-id/usb-Klipper_lpc1768_02900009881C4AAFA085685DC02000F5-if00
lrwxrwxrwx 1 root root 13 Oct 13 08:50 /dev/serial/by-id/usb-Klipper_lpc1768_02900009881C4AAFA085685DC02000F5-if00 -> ../../ttyACM0
pi@octovoron:~ $ ls -l /dev/serial/by-id/usb-Klipper_lpc1768_0800011348104AAFD9B8675DC22000F5-if00
lrwxrwxrwx 1 root root 13 Oct 13 08:50 /dev/serial/by-id/usb-Klipper_lpc1768_0800011348104AAFD9B8675DC22000F5-if00 -> ../../ttyACM1

Happy to make the edits for you if given access to source doc.

Fluidd - Can't upload gcode files to print - "root is not available"

I'm really new to all of this, so I apologize ahead of time if I'm posting things in the wrong spot or not including key info. I just put my Voron 2.4 together and managed to hack my way through the Klipper and Fluidd installs. My latest issue is that I can't seem to upload and print anything. I assume you upload by going to the Jobs tab and clicking the "+" to upload a new file, just like I did with my printer.cfg file. However, there's no "+" sign on the jobs tab, just a red error triangle in its place that carries the message "No root available. Check your logs." I looked in the Moonraker log and it state's the following:

2021-12-24 00:03:43,148 [web.py:log_exception()] - 400 POST /api/files/local (192.168.XXX.XX): Root gcodes not available
2021-12-24 00:03:43,151 [app.py:log_request()] - 400 POST /api/files/local (192.168XXX.XX) [TRUSTED_USER] 312.51ms

I put Xs in for the IP address, but I think that's just a local IP and of no concern. I just don't know this stuff well enough to be sure whether I should have left that there or not. I don't know what any of this log info means, so I thought I would reach out for help. I've read a few posts about issues with permissions and incorrect directory pathways, but I just don't know for sure if it applies to my situation and don't have the slightest clue about how to change of it, ha!

Any help would be greatly appreciated because, as of now, I just have a giant Voron 2.4 paperweight. Thanks!

moonraker.1.log

m3x10 FHCS Voron 2.4r2 Sourcing Guide missing.

Voron 2.4r2 Missing screw references form sourcing guide and not included in kit.

Page 184 x2 required power supply
Page 232 x1 required

M3x10 FHCS not listed in build of materials sourcing guide.
msedge_ct3scCuJJZ
msedge_SEzX7E4vIb
msedge_Ptq1V1cFyA

Procedure to Add Mods

Well I have searched, but I just cannot seem to find the step by step instructions to add an item to this repo.

Could someone provide me with a step by step guide on how to add ?

Thanks

Galileo Extruder supported in your BadNoob AB design?

Hi,
I would like to use the latest Galileo extruder design together with the BadNoob improved AB design, using a Dragon HF hot-end.

I'm not sure both designs are compatible right now, Can you comment on that?

Thanks.

STEP File ??

Hi, don't suppose you can add a step or fusion 360 native file so that I can modify the skirt to use a SH1106 1.3" OLED ?

Many Thanks

Quick question according to the Probe

I'm currently building my own and i got a quick question:
Should there be used a BAT85 Diode for the Probe?
Can't find any wiring diagram according to correctly connect the probe to my SKR E3 mini V2.
Can somebody provide some help?

Lumentec deliver wrong profiles

The linked seller of the profiles "Lumentec" delivers wrong profiles. The described profiles are 18,35mm and not 17mm.

This just for information.

Random purge only goes to one side

I have installed this mod on 2 vorons 2.4 but the purge, as I understand, is supposed to happen one time on the left side and one time on the right, right>

In my case, it happens always on the same side, the right side.

Is there a fix for that? Or how can I change so it uses the left side, which is larger?

Thank you.

VEFACH modification needed for r2 exhaust housing

Not sure if kevinakasam#2097 is around or will see this but the VEFACH parts don't fit the 2.4r2 exhaust housing due to the new screw fixings for the exhaust cover getting in the way. A mod to the coal container would be great if possible.

Thanks.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.