Jump to content

burdickjp

Member
  • Posts

    35
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by burdickjp

  1. Just now, Enigma_M4 said:

    I'm sorry to say so, but you're wrong. If the distance between lowered bed and head is shorter than the controller thinks (which means, shorter than it should be), the bed hasn't lowered enough, it didn't lower too much.

    Check the Z switch as suggested, as it's easily be done, also check, if the Z enstop works at all (in systems menu).

     

    If the bed is driven past the bottom of its travel then the Z axis stepper motor stalls and skips steps. The controller thinks it kept moving. The mechanical distance between the bed and nozzle is less than the controller thinks.

  2. 1 minute ago, Enigma_M4 said:

    moving past the Z end stop (lowering the bed to much) would normally result in to much space between print bed and printhead at start of print.

    Your problem may result in the bed stopping before the Z end stop is reached.

    So you should check the small pit where the Z end switch is located for debries blocking the Z switch.

    Regards

     

    If the machine tries to go past the bottom of the Z travel then the head to bed distance is shorter than the controller thinks, and it crashes the nozzle into the bed.

    The bed is homing correctly during other operations, including print completion and automatic leveling.

     

  3. I have a UM3E which I've installed some buildtak print sheets on. I've turned off automatic leveling, as the nozzle would melt the print surface. This was behaving correctly for a long time, but recently it's started to misbehave.

     

    At print starts it will drive the Z axis down past the end stop. Since it's lost its Z position it will then drive the nozzle into the bed.

     

    When I turn on autoleveling and switch to a different bed material the startup sequence is a little different and it behaves normally.

     

    I'd like to go back to buildtak sheets. They worked before.

     

    Has anyone run into similar problems before? Any suggestions on fixes?

  4. I'm having trouble finding what is causing this.

    I've tried in Cura 4.1 and Cura 4.2. The first layer is over extruding to line widths of over 2 mm when they should be 1.2 mm. I checked my steps per mm by extruding 100 mm of filament. It was within 2%. I corrected it.

     

    I switched to a 0.8 mm nozzle and 0.6 mm layers and it seems to be behaving, so I'm thinking there's something buggy in Cura or I'm missing a setting somewhere.

    UMO_3DBenchy.3mf

  5. On 6/6/2019 at 6:09 PM, artistebot said:

    Looking forward to a 2.85mm solution for this mod, as I simply don't like using 1.75 in a bowden setup.  Cheers and great work.

     

    I am, too!

    It will be a short while as I am in the middle of a move. I've got some new ideas, but they're not mutually exclusive ideas.

    I intend to test the hotends in my ultimaker as it is before changing to the DXU.

  6. 5 hours ago, yyh1002 said:

    The 1.75 hotend runs with a custom 6.35 OD 2 ID PTFE bowden tube, sold by the same Taobao seller. The major advantage of this PTFE hotend is that there is pretty much no chance of nozzle jam or clog for PLA even with frequent long retractions. With the PI insulator ring applied, the PTFE last much longer and can also handle high temp materials.As for using E3D heatbreak, the current heatsink probably won't be able to cool it down properly because the surface area is much smaller. 

    You can consider trap a piece of 6.35 OD 3.2 ID or 5 OD 3 ID PTFE tube inside the heatsink. I think the 4*3 PTFE would deteriorate pretty quick due to thin wall thickness, and it is also too soft to hold up to the compression from filament. Making 1.75 and 2.85 hotend components swappable isn't all that necessary. You would need to make compromise on both sides to achieve that. I think it would be better to make two entire printheads with 12pin connector for quick swapping. That would be much less hustle, much more reliable and cost very little. 

     

    I'm not necessarily looking at being able to swap between 1.75 mm and 2.85 mm with the same hot end. I'm looking to use the same form factor for both. The same, or mechanically compatible, external dimensions.

    • Like 1
  7. 4 minutes ago, yyh1002 said:

    You can totally try the existing version first. Short bearing should last at least several months. For the blower fan, 3015 works as good as 3510 thanks to more accurate duct aiming the nozzle and better fan shape. 

     

    If the short bearings are wearing then something is wrong. The Ultimaker 3 uses a short bearing on the Y axis rod and lasts a long while. Maybe alignment isn't sufficient and it's wearing because of misalignment?

  8. 1 hour ago, ultiarjan said:

    You can use the um3 head on the um2 by simply making a PCB with only the connectors touching the core electronics and wire to the mainboards heater and pt100 connection. No need for any fancy electronics. I've shown it here somewhere including the link to the correct component but on the phone and too lazy to find a link now 🙂

     

    I'm thoroughly interested in doing this. I thought about designing and making the PCB necessary, but couldn't find the correct pogo pins. Care to share?

  9. Best that I can tell, it seems there are  a few different fits for this form factor of bearing. I'm guessing robotdigg has chosen a part with the wrong fit for this application.

    I checked the rods that I ordered and they're supposed to be a g6 fit, which means they're supposed to be 7.986-7.995 mm in diameter.

     

    I guess I could chuck the shafts in the lathe and polish them down just where the bearing will be fitted, like you suggest. I'd much rather find a better fit bearing and shaft combination, though. I don't think these should have much interference at all, just enough that there is no radial play in the shaft.

  10. I purchased F688ZZ bearings from robotdigg and 8 mm shafts from Misumi. The shafts are 7.998 mm in diameter and the F688ZZ bearings are less than 7.98 mm inside diameter. Those seem to be too tight of a press fit for the application.
    What have other people's experiences been?

    I'm looking at buying bearings from Misumi, but don't see ID tolerances anywhere to know if they're going to be a better fit or not.

  11. 42 minutes ago, nullsibnelf said:

    Got it.

    The failure was by me (shame)...

    Please look at https://github.com/nullsibnelf/Marlin

    temperature.cpp from line 2182 to line 2196.

     

    the fork is at the moment not for dual head (because i changed back to single nozzle e3d).
    But I added all the changed mentioned here in this post. so this should fix your compile error. In fact, it was a missing '}' at the right possition.

    Sorry for that.

     

    That looks good. I'll try it this evening and report back. Thank you very much for your help.

  12. 1 hour ago, lars86 said:

     

     

    I think the only change you will really need is changing:

     

    #define BOARD_ULTIMAKER       // Ultimaker

    to:

    #define BOARD_ULTIMAIN_2      // Ultimainboard 2.x (Uses TEMP_SENSOR 20)

     

    ...and using these for your temp sensor definitions:

     

    #define TEMP_SENSOR_0 20

    #define TEMP_SENSOR_1 20

    #define TEMP_SENSOR_2 0

    #define TEMP_SENSOR_BED 20

     

    For the most part, yes, that brings in 99% of the functionality. The only thing I've found to be different is that the UM2 board uses a pin which isn't used in the arduino for the hot end fan. To use it you have to address it directly, which Marlin isn't configured to do. nullsibnelf has shared the necessary code in a git repo:

     

  13. I copied your above code to the bottom of temperature.cpp and I get the following error on compile:

     

    Arduino: 1.8.5 (Windows 10), Board: "Arduino Mega ADK"

    In file included from c:\program files (x86)\arduino\hardware\tools\avr\avr\include\avr\io.h:99:0,

                     from c:\program files (x86)\arduino\hardware\tools\avr\avr\include\avr\pgmspace.h:90,

                     from sketch\Marlin.h:32,

                     from sketch\temperature.cpp:27:

    temperature.cpp:2289: error: expected unqualified-id before 'volatile'

     DDRJ |= _BV(6);

     ^

    temperature.cpp:2289: error: expected ')' before 'volatile'

    temperature.cpp:2289: error: expected ')' before 'volatile'

    temperature.cpp:2290: error: expected unqualified-id before 'if'

      if (current_temperature[0] > (EXTRUDER_AUTO_FAN_TEMPERATURE) || current_temperature[1] > (EXTRUDER_AUTO_FAN_TEMPERATURE))

      ^

    temperature.cpp:2294: error: expected unqualified-id before 'else'

      else if (current_temperature[0] < (EXTRUDER_AUTO_FAN_TEMPERATURE - 2 ) && current_temperature[1] < (EXTRUDER_AUTO_FAN_TEMPERATURE - 2 ))

      ^

    exit status 1
    expected unqualified-id before 'volatile'

    This report would have more information with
    "Show verbose output during compilation"
    option enabled in File -> Preferences.

     

    Any suggestion?

×
×
  • Create New...