Jump to content


Popular Content

Showing content with the highest reputation on 08/06/2015 in all areas

  1. 2 points
    Hello. Long time, no me. I've been fighting on other frontiers... Every now and then I've been printing bits an pieces, but nothing ambitious at all - partly because the performance of my UM2 was compromised. For Xmas gifts, I printed some Xmas trees and I used Formfutura's "glow in the dark" ABS - which turned out to be very abrasive: The block I had on my printer didn't produce very good print quality anymore. I knew I should have simply changed the nozzle, but I pushed the thought back as I guessed I would have to re-make my self-made temperature sensor. When I inserted it to the nozzle block several months ago, I realized the fit was a bit too tight. Now, when removing it from the nozzle block, it didn't come out in one piece. I should have thought about it before. To the new nozzle block I drilled a hole for pushing the temperature sensor out. Okay, so I took the time to change the nozzle and re-make the temperature sensor - and I managed to get a few nice prints out from my UM2. Then, I started having under-extrusion problems... nostalgic feeling, or something. After "some" troubleshooting, I realized the problem was in the stepper motor - or its driver. The torque just wasn't there anymore. Maybe it's me to blame - I have used the extruder stepper motor with 1.5A current. Maybe now this practice took its toll: Great - so my UM2 motherboard needed changing. But wait - there was a reason why I felt I had to use the 1.5A stepper motor current - and even that didn't feel to be always enough. Before my UM-break, I had already ordered this kind of stepper motor: http://www.robotdigg.com/product/29/Nema17-60mm-1.5A-high-torque-stepper-motor But, if the standard stepper motor can be too much for the Pololu driver, probably the new stepper motor would kill it even faster? So, my UM2 motherboard needed changing but even that wouldn't have satisfied me. I decided to bypass the dead Pololu altogether and use an external stepper motor controller. I decided to try to make it in a way I wouldn't need to make a custom firmware - so, I had to remove the dead Pololu: ...and bypass it: The contrast on the picture is a bit misleading - the board looks more clean to naked eye. Most importantly, the hack works. Now the critical digital outputs (pulse, direction, enable) are taken out from the UM2 motherboard to an external stepper motor controller. I happened to have an M542H stepper motor driver waiting to be used - so now I have a lot of headroom in case I need an even more powerful stepper motor for my extruder I decided to use the existing extruder connector for the digital outputs - so I have to remember not to plug a stepper motor directly to the connector anymore. I really need to catch up with Anders Olsson's work, the original UM2 heater/nozzle block has caused me too much headache...
  2. 2 points
    Motorized carbon-pipe-slider for timelapse photography: (more info and picture on http://puremoco.com/pages/sliderCarbon.php) [media=4060] [/media]
  3. 1 point
    Thank you! Actually, I started to think about cooling for the motherboard as well. The circuit board around the stepper motor drivers for X and Y axes had yellow/light brown tint - so the temperatures must get pretty high.
  4. 1 point
    @nallath: Is there an option to add a new printer type (UM2 + 0.8mm nozzle) in the ~/.cura location instead of under the application? Even if I would symlink them I would keep on losing the json's (or the symlink) every time/update.
  5. 1 point
    I just put a slight bend in mine in the area where it touches so it would fit. now it works good.
  6. 1 point
    I guess I miss the old format This "pretty" version rubs me much as Windows 8 did....why screw up what was a functional interface and turn it into a portal experience at every click? I visit a lot of forums that use platforms like vBulletin board and other variations. I can use TapTalk to go into those while mobile. I'm sure you guys are trying to make it better. I'm waiting patiently =)
  7. 1 point
  8. 1 point
    or add an M302 gcode command somewhere to allow cold extrusions
  9. 1 point
    //this prevents dangerous Extruder moves, i.e. if the temperature is under the limit//can be software-disabled for whatever purposes by#define PREVENT_DANGEROUS_EXTRUDE//if PREVENT_DANGEROUS_EXTRUDE is on, you can still disable (uncomment) very long bits of extrusion separately.#define PREVENT_LENGTHY_EXTRUDE#define EXTRUDE_MINTEMP 170#define EXTRUDE_MAXLENGTH (X_MAX_LENGTH+Y_MAX_LENGTH) //prevent extrusion of very large distances. On Configuration.h
  10. 1 point
    TEST CRASH ORTHO [media=4090][/media] De gauche à droite : Nylon...mal stocké...humidité...tentative de récup, dans le four à 45° toute la nuit ! PLA , trop fragile. XT , grand vainqueur ! La suite dans les prochains jours
  11. 1 point
    Thanks Joerg! The print head is full custom. One of a kind currently. I'm actually modeling up a complete new print head / hot end now. It is a much more minimalistic design, and should save a ton of weight. I think that I have some very solid ideas on improving the hot end to allow high temp use, eliminate jamming and excess friction. I have some 4/5 axis mill turn machines at my work that I can use to make prototypes, and am trying to refine the design for best manufacturability. Hoping it could be feasible to do some production runs. I'm also considering making the print head out of billet aluminum as well (versus printed), to ensure perpendicularity between linear bearings, rigidity, and to help dissipate heat.
  12. 1 point
    All right, there seems to be a bit of uncertainty what the .json files actually do. Let me explain that a bit more. The settings are hierarchical in nature. Lets have a look at a setting like "line_width". As you can see it has a "children" option, which contain the settings "wall_line_width", "skirt_line_width", "skin_line_width","infill_line_width","support_line_width" and "support_roof_line_width". Each of the children setting will inherit their value from their parent ("wall_line_width") if they are not enabled / visible. This is to ensure that users who don't want to tweak stuff only have to change one setting. If you make "skin_line_width" visible and change it, it overrides the value of "wall_line_width" for that specific setting (all other children still inherit!). If all children of a setting are visible, the setting becomes invisible as it no longer does anything. We also have something called an "inherit_function". You can put a python script there which should return a value. This is useful for values that need to be calculated based on other settings (eg; "wall_line_count"). Setting files can also be inherited, which you can see if you look at the ultimaker2.json, which inherits fdmprinter.json. This was done to even allow printers that dont use FDM (or even non printer machines. Uranium would be suited for CNC mills / laser cutters aswell)
  13. 1 point
    Did it! https://ultimaker.com/en/community/view/16373-lars-ultralight-xy-blocks
  14. 1 point
    Well if you choose some gold plated numbers to start with, you could have saved much much more than just 44$.
This leaderboard is set to Amsterdam/GMT+02:00
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!