Welcome to Our Community

Some features disabled for guests. Register Today.

Scaling issue using the OB Interface Box

Discussion in 'CNC Mills/Routers' started by Convoyhank, Sep 28, 2021.

  1. Convoyhank

    Builder

    Joined:
    Jul 23, 2021
    Messages:
    4
    Likes Received:
    0
    I recently completed my 1515 build and started to do some test cuts of a small sign. I export the artwork
    from Aspire as G-code inches as sperate tool passes. My stock is 7" x 20" as is the Job stock size in Aspire. I noticed the Center Oval is not centered and too large in dimension.

    I decided to run this from a USB stick on the INTERFACE not driving it from my laptop. If I open the
    job in OB Control software it looks right and the dimensions are preserved. Is there something in the Interface
    module that could be causing this? I am on the newest Firmware on both the Controller and the INTERFACE.

    Thank You in Advance
     
  2. Peter Van Der Walt

    Peter Van Der Walt OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Mar 1, 2017
    Messages:
    14,923
    Likes Received:
    4,291
    You need to calibrate your machine's steps per mm. OpenBuilds-CONTROL > Wizards and Tools menu > Calibration
     
    David the swarfer likes this.
  3. Convoyhank

    Builder

    Joined:
    Jul 23, 2021
    Messages:
    4
    Likes Received:
    0
    Thank you for your quick reply. I will conduct the calibration. My friend has a 1010 and just did this not
    knowing it is needed to be done. His machine was only off 3mm before the re-cal was saved. I'm still a bit
    concerned as I cut as described above included a 10 in oval. On the job it cut 12 inches in the horizontal
    axis. Is it possible the calibration is that far off?
     
  4. Peter Van Der Walt

    Peter Van Der Walt OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Mar 1, 2017
    Messages:
    14,923
    Likes Received:
    4,291
    Check calibration first, if it's not that, we'll look into mechanical issues. But "too large" is usually more a calibration issue. Mechanical slippage or motor stalling both result in making cuts smaller, so it is the more likely cause
     
    #4 Peter Van Der Walt, Oct 1, 2021
    Last edited: Oct 1, 2021
  5. Convoyhank

    Builder

    Joined:
    Jul 23, 2021
    Messages:
    4
    Likes Received:
    0
    Ok fired up the machine. Did the calibration to no avail. Controlling via laptop USB not Interface (not even sure you can)

    X
    mark
    Jog 100
    Result 150mm
    Enter 100. Even tried 100:0
    Ran again
    Same result
    Several times

    tried restarting g code between calibrations and cold booted as well

    got even stranger trying the Y cal. My jog is correct with the arrows but inverted running the calibration.

    I assume the is being written to the controller and NVram. Is this controller bad ?

    3 months since ordered and yet to produce anything on this machine
     
  6. Peter Van Der Walt

    Peter Van Der Walt OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Mar 1, 2017
    Messages:
    14,923
    Likes Received:
    4,291
    Sounds like docs:blackbox:faq-identify-motor-coils [OpenBuilds Documentation]

    Address that first, then try again

    Did you load the machine profile (so that we have sane values for acceleration, etc in place prior to calibration)

    Any 3rd party parts involved, or all from openbuildspartstore.com

    Be sure to follow along with the Build Videos and it should be up and running in a couple hours :)
     
    #6 Peter Van Der Walt, Oct 2, 2021
    Last edited: Oct 2, 2021
  7. Peter Van Der Walt

    Peter Van Der Walt OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Mar 1, 2017
    Messages:
    14,923
    Likes Received:
    4,291
    You should enter the ACTUAL distance travelled when prompted, so it can work out the correction factor.

    What is your steps per mm values in Grbl Settings currently
     
  8. Convoyhank

    Builder

    Joined:
    Jul 23, 2021
    Messages:
    4
    Likes Received:
    0
    Ok think I'm in better shape. Not near the machine but here's what happened. Despite entering the actual measurement
    several times. I zeroed the axis and jogged 100 mm. It was very very close. I went back to the calibration and when the
    machine jogs itself either 100 mm (The default) or if i manually jog it i.e. 300 its off exactly the same amount like 100=155
    so I enter 155. It does seemingly write the now corrected offset to the Black Box.

    But if you go back to the calibration the 155 offset is still there.
     
  9. David the swarfer

    David the swarfer OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Aug 6, 2013
    Messages:
    3,438
    Likes Received:
    1,908
    Still where? Can you post a screen capture?
    I have just done a trial calibration and do not see the value I typed in repeated anywhere at all when I redo the calibration.
    The recalibrated steps/mm value is displayed in the serial console like this, as it should be
    [09:11:20] [ $$ ] $102=189.980 ;Z-axis steps per millimeter

    So, when YOU jog the machine, how fast does it move compared to when the wizard jogs it?
    What jog steps are you using?
    What are your acceleration settings? They should be around these values which are the ELAD1515 defaults
    Code:
    $100=198.109 ;X-axis steps per millimeter
    $101=198.109 ;Y-axis steps per millimeter
    $102=199.100 ;Z-axis steps per millimeter
    $110=3500.000 ;X-axis maximum rate, mm/min
    $111=3500.000 ;Y-axis maximum rate, mm/min
    $112=1000.000 ;Z-axis maximum rate, mm/min
    $120=350.000 ;X-axis acceleration, mm/sec^2
    $121=350.000 ;Y-axis acceleration, mm/sec^2
    $122=350.000 ;Z-axis acceleration, mm/sec^2
    
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice