Close



Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 33

Hybrid View

  1. #1
    Staff Engineer printbus's Avatar
    Join Date
    May 2014
    Location
    Highlands Ranch, Colorado USA
    Posts
    1,437
    Add printbus on Thingiverse
    Have you measured how much change in height you get when you command a Z movement from software like pronterface or Repetier-Host? That'd be a way to keep testing the issue without burning time and filament on prints. That would also remove unknowns related to how much you're extruding and any issues you might have in the slicer software setup.

  2. #2
    Senior Engineer
    Join Date
    Jun 2014
    Location
    Burnley, UK
    Posts
    1,662
    Do you get the same height if you print the same thing twice?

  3. #3
    #define DEFAULT_AXIS_STEPS_PER_UNIT {98.98, 98.98, 4007.32, 700} // default steps per unit for ultimaker
    #define DEFAULT_MAX_FEEDRATE {500, 500, 5, 45} // (mm/sec)
    #define DEFAULT_MAX_ACCELERATION {9000,9000,100,10000} // X, Y, Z, E maximum start speed for accelerated moves. E default values are good for skeinforge 40+, for older versions raise them a lot.


    copied/pasted direct from arduino app and is current, when i measure 100mm command send from pronterface it measures out to 100.02mm which is quite good.

    printbus: i think the allthread is one of the weakest links in the chain have been giving thought to upgrading them to direct drive acme screws like the ones used in the davinci xyz (dad has one) so far ive replaced bed rods and bearings (went through 36 linear bearings to find 3 that had no wobble) 2 stop switches, and various other hardware. to be honest, the drill rod stock shipped with the unit is not what a drill maker would consider first quality and are probably seconds as i found variations throughout the length of the rods.. the endstop switches were rather junky (replaced with 69 cent bulk ones)
    as far as the ramps chips i have been thinking about swapping out the stock chip for the higher current one just to be safe, it is running 2 steppers on the same chip as the others that are running 1.

    mjoliner: used this http://youtu.be/wAL9d7FgInk as my guide for calibration and that calibration took me from rather poor prints to rather nice prints with sprinter firmware.

    as for now im going to crank out 2 consecutive 20mm cubes just to verify consistency and i have one i printed with the exact same filament before the firmware change ill post a pic of all 3 when done
    thanks guys

  4. #4
    heres the results:
    left cube was printed the other day under sprinter
    middle cube today first print
    right cube last print
    Attached Images Attached Images

  5. #5
    Super Moderator Roxy's Avatar
    Join Date
    Apr 2014
    Location
    Lone Star State
    Posts
    2,182
    What is the height of the right one? It looks like you need to scale up your Z-Axis DEFAULT_AXIS_STEPS_PER_UNIT. And until I had things working right, I would bump down:

    #define DEFAULT_MAX_FEEDRATE {500, 500, 2, 45} // (mm/sec)
    #define DEFAULT_MAX_ACCELERATION {9000,9000,30,10000}

  6. #6
    roxy thats the wierd thing, with that setting for z-axis default steps when i move it up 100mm in pronterface it measures out to 100.02mm but when i go to print something i get 50% print height

  7. #7
    Super Moderator Roxy's Avatar
    Join Date
    Apr 2014
    Location
    Lone Star State
    Posts
    2,182
    Quote Originally Posted by bigmikeinil View Post
    roxy thats the wierd thing, with that setting for z-axis default steps when i move it up 100mm in pronterface it measures out to 100.02mm but when i go to print something i get 50% print height
    And that is a big reason why you ought to try the smaller numbers for Feedrate and Acceleration. It is possible your stepper motors can't keep up. Pronterface isn't going to use highly aggressive numbers for manually moving the carriage around. They are going to use numbers that work for everybody. So if it works when you are manually moving things around in Pronterface but not with your GCode... It is possible the GCode numbers are too aggressive.

    I'm not saying this is the problem. But I am saying I would back off my numbers until the problem is understood.

  8. #8
    ive changed the values in arduino, re-uploaded the firmware, and am printing another cube now. ive yet to talk to a human at nwreprap, they have a nack for calling back while im at work and have just received a reply to an email to them on the subject... response so far "you have to calibrate #define DEFAULT_AXIS_STEPS_PER_UNIT {98.98, 98.98, 4007.32, 700}" even tho in the email i had said i had that within .02 mm of perfect, will let you know how this cube comes out
    thanks

  9. #9
    Hi Mike. I have those couplers sitting on my bench. I think they will make a world of difference. Those three cubes above are all different sizes and the two smaller ones were made with no changes between them - that can only mean those couplers are slipping or you are losing steps. I know how loose the slip coupler seemed to me, that's why I ordered the couplers. Swing by and pick them up in the morning. BTW, I printed out a couple knobs for the top of the 5mm threaded rod so that it will be easier to adjust them on the fly. I can't address the software issues, you know that's where I'm weak, but that stuff you are seeing appears hardware related to me.

    Dad

  10. #10
    Staff Engineer printbus's Avatar
    Join Date
    May 2014
    Location
    Highlands Ranch, Colorado USA
    Posts
    1,437
    Add printbus on Thingiverse
    So, what were the changes nwreprap had you make to the Marlin firmware that solved your problems?

Page 2 of 4 FirstFirst 1234 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •