Jump to content

Dim3nsioneer

Ambassador
  • Posts

    4,297
  • Joined

  • Last visited

  • Days Won

    33

Posts posted by Dim3nsioneer

  1. Primarily, I am referring to the M92 Exxx value as it applies to extruder drive 1 vs 2, and that they should have individual settings.

    No need if you have identical extruders (same version!) which is the case with the Ultimaker Dual Extrusion Kit and a not too old UM Original.

    Additionally, all the settings that pertain to the first extruder axis should also be available on additional extruders including filament diameter, flow multplier, nozzle size, temp and steps per mm.

    filament diameter: strongly agree! (Daid is most probably hating my guts as I might have mentioned diameter2 once or twice before... :shock: )

    flow multiplier: must to have until Cura gets a proper implementation of diameter2 (oops, I did it again... :p ), from that point on: nice to have

    nozzle size: agree

    temp: already implemented

    steps per mm: see above

    I have an idea how to implement individual flow multipliers directly in Marlin (see http://umforum.ultimaker.com/index.php?/topic/3580-flow-rate-adjustment-ulticontroller/&do=findComment&comment=40780)... I hope I can realise a first version soon.

     

  2. [...]

    Will be in the 13.03 release. Which will be the least buggy release ever! (that doesn't sound as good as it is... maybe I need to do better marketing...)

     

    I guess you know Murphy's law... ;) It will destroy any least-buggy-marketing...

    btw: what about the save/print icon (http://umforum.ultimaker.com/index.php?/topic/4487-bring-me-your-bugs-cura-1402-rc2-ready-for-testing/page-8&do=findComment&comment=41143) and the diameter2-issue? Any chance we get a bugfix for those in 134.03?

     

  3. So I took a look at your files there gr5 and I was able to trace my DIR pin for the Z axis and on the Ultimaker board it wasn't even soldered... So a few seconds under the gun and it seems to work much better now. I spent more time taking apart the machine than I did troubleshooting or fixing it! Thanks for the help guys.

     

    Congratulations on your self-fix! You might want to give Ultimaker some short feedback as they probably will be interested to check why quality control of this board failed.

     

  4. Finally you should swap the drivers of the x and the z axis in addition to the swaped motors and end switches. Skip it if you swaped exactly these two drivers before.

    If the result is still the same, time has come to submit a ticket with this information to Ultimaker...unless someone else has a mind blowing idea...

    I think, the problem may be something like a bad solder point on one of the boards...

     

  5. Here is another new idea :wink: :

    Connect your z motor with the x-axis on the Ultimaker Arduino shield. Make sure the z stage is somewhere in the middle of the two end switches.

    Then try to move the motor in both directions, e.g.

    G91 (for relative positioning)

    G1 F9000 X15

    G1 X0

    If the motor skips reduce the speed (e.g. F4500 or even less). If this tests works (means the z stage drives in both directions) then its a broken DIR bit for the z axis (as gr5 said).

    Make sure, you switch the z motor back to the z axis afterwards before something really bad happens... ;)

     

  6. So ein 'Skript' gibt es in Cura. Die Option nennt sich 'Cool Head Lift' und findet sich in den 'expert settings'. Wenn Du gleichzeitig die Minimalgeschwindigkeit auf sagen wir mal 20mm/s oder so hochstellst, bekommst Du genau das, was Du möchtest.

    Allerdings dürften diese Optionen normalerweise nicht bei einem UM2 in Cura angezeigt werden. Du müsstest unter den 'machine settings' den 'flavor' auf 'RepRap' umstellen und darum einige Einstellungen, die Du Dir gewohnt bist, am Drucker selbst zu machen, in Cura vornehmen.

    EDIT: Wenn Du den flavor umstellst, kannst Du auch gleich das Flowthermostat-Plugin benutzen. Dieses stellt die Temperatur nach der 'aktuellen' Geschwindigkeit (im GCODE) ein.

     

  7. Quite a strange behaviour... a video indeed might help to get a better understanding. However, you already did some important checks. Sounds as if mechanics (motor and end switches) are fine.

    Which slicer did you use for gcode generation? Do you use the default firmware or a custom version?

    As a shot in the dark, it sounds to me as some strange gcode problem with a missing z-coordinate for the first print command.

     

  8. Hi!

    Great adaption!

    I have not mounted my heater pad yet so I had no chance to check the bendig behavior of my original cables - just tested it with some other cables and there it worked.

    Would be great if you could also publish this modified part. :smile:

     

    Oh, sure... the stl is here. Please feel free to include it in your published set on Thingiverse if you like it. I think there is not much sense in opening a new set on Thingiverse for such a minor modification.

     

  9. First of all, thanks drayson for adapting IRobertI's cable chain for the UM1! I implemented it with my new heated bed using 10 chain segments:

    Cable Chain UM Original

    However I had to modify the bed end part (yellow). With the original design, the radius for the chain segments was too small. Thus, I added 10mm on the bed end part and also moved the screw bore by these 10mm in order to get a larger radius for the chain segments. It works nice this way...

     

  10. It's some time ago... :wink:

    Such an implementation is possible in Marlin.

    I would suggest it that way:

    - keep the current multiplicator as it is (to keep things compatible)

    - add an additional multiplicator per extruder

    - extend gcode M221

    - M221 Sxxx sets the overall multiplicator

    - M221 Ty Sxxx sets the extruder-specific multiplicator for extruder 'y'

    What do you think?

     

  11. Really??? I have not recognized this...

    My experiance is that I adjusted inpropper flow via setting a much smaller diameter on the second nozzle - and I got better results in dual print...

    Independent settings would be really necessary - also for E-Steps and flow.

    Just for reference: http://umforum.ultimaker.com/index.php?/topic/3651-bigger-wipe-prime-tower/&do=findComment&comment=28360

     

  12. The change is instantly. I use http://gcode.ws for checking print speeds on individual layers.

    Sometimes a speed change is not completely obvious. It can e.g. be due to a different acceleration situation which needs more or less time than the layer before... a radical change is from solid infill of the bottom closed layers to the infill with less than 100%.

    If you have your fan(s) on 100%, a layer time of 5-7 seconds is usually sufficient if you print PLA.

     

  13. Thats an important info as I have not remembered/recognized this behavior and I'd like to get my HB working soon.

    Workarounds are always a second hand solution so hopefully there will be enough attention on this topic.

    Is there a way to switch the heating sequence in the FW permanently?

     

    It's not a question of the firmware but of the order the M109 and the M190 GCODE commands are placed by Cura. In newer versions of Cura, there are two commented lines a the top of the start.gcode which just have to be uncommented:

     

    
    

    ;M190 S{print_bed_temperature} ;Uncomment to add your own bed temperature line

    ;M109 S{print_temperature} ;Uncomment to add your own temperature line

  14. Unusual speed change.

    I print test model at 0.06. 10-20 layers after, speed drops down to 30% or so.

    Why is that ?

    Why cant it print at steady speed ?

    Its printing CURA robot and just starting to print feet at 10% fill @ 50mm/s

    Then out of nowhere speed picks up.

    Why is that ?

    Is this a bug or a speed changer of some sort ?

     

    Most probably it's a feature. I guess your print is small. If your nominal speed does not match the minimum layer time set in Cura, print speed is reduced to match the minimum layer time. But you can also set a minimum velocity. See the 'Cool' sections in both the advanced and the expert settings in Cura.

     

  15. [...]

    Meanwhile, I don't think a plugin would be very suitable, as those are just textual post-processors with very little contextual info; you wouldn't easily be able to identify the bridging part to adjust. If you knew the z-height of the bridge, then you could use something like the 'tweak at z' plugin to change the settings for those layers as a whole, but that would be a rather crude solution.

     

    Crude yes, but it works... ;)

    @Eli: Successful bridging depends on more than just the speed. You e.g. want to have the print temperature as low as possible and the fans on full throttle. Acceleration and flow also play their part...

    But I agree that bridging is something Cura might become better in. Maybe one day... but not too soon, I guess, as Daid and Nallath are currently working on a complete redesign of the GUI. I don't know if any improvements of the slicing engine are planned for Cura 14.x (x>3).

     

  16. Thats a great idea! I have my HB-parts already at my desktop, PSU is missing so I have to update mine soon.

    Would you share your code??

    Would be great if I could use it at my machine too... :smile:

    Thank you in advance!

     

    I'm currently trying to get some movement into this issue on Github. I just left a comment there... Preheating the bed is of general interest, I think, as e.g. Cura first heats the hotend and then the bed (yes, I know the work-around by using the start.gcode... :p ).

     

  17. As I was one of those who could not wait until the official kit arrives, I've built my own heated bed. It offers the possibility to print on the surface of choice. I started today with 3mm Aluminium with Kapton tape. Great stuff! The PLA I printed on it is sticking very well (maybe even too good). I could easily lower the print temperature for the first layer.

    Ok, as you guys usually want to have a photo... :grin: Here it is:

    Heated bed for Ultimaker Original by Dim3nsioneer

     

  18. Line width and Slic3r reminds me of a http://www.extrudable.me/2013/11/03/slic3r-strange-defaults-causing-qu-bd-woes/. There he is writing about line width settings in Slic3r.

    Maybe you found settings in Slic3r which give you a nice result with the original (0.65mm I think) line width settings? Taking all other settings such as e.g. a tweaked filament diameter to Cura which doesn't know a line width setting would then result in too thin lines.

    It's just a rough theory... :wink:

     

×
×
  • Create New...