Welcome to Our Community

Some features disabled for guests. Register Today.

Job size is Tiny

Discussion in 'General Talk' started by Pidiln, Nov 16, 2019.

Tags:
  1. Pidiln

    Pidiln New
    Builder

    Joined:
    Sep 20, 2019
    Messages:
    13
    Likes Received:
    6
    I upgraded from VCarve Desktop to VCarve Pro and now my job size is tiny.
    I have checked my machine database and job settings and saved toolpaths after trying different settings but I get the same results when I load the code into BlackBox and check size or run a job using OB Control.
    I loaded a gcode file that was created using VCarve Desktop and it works as it should. Job size
    Is there a setting or setup I am missing ?
    I have not been verified on the Vetric forums yet so I was hoping someone here could help me figure this out.
    btw, I am new to CNC but am loving my Lead 1010 !

    Pidiln / Larry
     
  2. Alex Chambers

    Alex Chambers Master
    Moderator Builder

    Joined:
    Nov 1, 2018
    Messages:
    2,681
    Likes Received:
    1,321
    Hi @Pidiln /Larry, have you checked your settings in V-carve (mm/inch)? And are you using the same post processor?
    Alex.
     
  3. Pidiln

    Pidiln New
    Builder

    Joined:
    Sep 20, 2019
    Messages:
    13
    Likes Received:
    6
    I did. Heck those settings and even saved the tool path just to see if I had missed something, but I get the same results
     
  4. Alex Chambers

    Alex Chambers Master
    Moderator Builder

    Joined:
    Nov 1, 2018
    Messages:
    2,681
    Likes Received:
    1,321
    Hi @Pidiln, I have wound up my PC to have a look at the problem. Could you post your gcode file here (you might have to change the extension to *.txt).
    Are you designing in inches or mm?
    Alex.
     
  5. Pidiln

    Pidiln New
    Builder

    Joined:
    Sep 20, 2019
    Messages:
    13
    Likes Received:
    6
    I am using inches
    Also I am getting a T1M6 error code, but I was able to figure out how to edit that out, but it shouldn't be doing that.

    Thanks,
    Pidiln
     

    Attached Files:

  6. Alex Chambers

    Alex Chambers Master
    Moderator Builder

    Joined:
    Nov 1, 2018
    Messages:
    2,681
    Likes Received:
    1,321
    What post processor are you using - you should be using Grbl (inch) (*.gcode).
    I just did some experiments and Grbl (mm) (*.gcode) will happily convert designs in inches to g-code in mm (and Grbl (inch) (*.gcode) will convert designs in mm to g-code in inches)

    See also @sharmstr's post on modifying the Vectric post processor to remove that tool call that was giving you the T1M6 error.

    VCarve GRBL Post Processor Mods

    Alex.
     
  7. Alex Chambers

    Alex Chambers Master
    Moderator Builder

    Joined:
    Nov 1, 2018
    Messages:
    2,681
    Likes Received:
    1,321
    PS if you are using the G code (inch) (*.tap) post processor that processed a simple profile cut correctly (apart from the T1M6) but it didn't output the gcode for units (G20=inch G21=mm)
    Alex.
     
  8. Pidiln

    Pidiln New
    Builder

    Joined:
    Sep 20, 2019
    Messages:
    13
    Likes Received:
    6
    so are you telling me that my gcode is coming out in mm instead of inches ?
     
  9. Alex Chambers

    Alex Chambers Master
    Moderator Builder

    Joined:
    Nov 1, 2018
    Messages:
    2,681
    Likes Received:
    1,321
    Your gcode is coming out without specifying what units its in. If you use the Grbl (inch) (*.gcode) post processor in Vectric it will put a G20 code in the header of the gcode file. @sharmstr's post linked above tells you how to modify the post processor to remove the tool call (T1) that grbl doesn't like. Check that you are working in inches in OB control and everything should work.

    Alex.
     
    sharmstr likes this.
  10. sharmstr

    sharmstr OpenBuilds Team
    Staff Member Moderator Builder Resident Builder

    Joined:
    Mar 23, 2018
    Messages:
    2,030
    Likes Received:
    1,428
    No, that's not what he is telling you.

    Assuming you are using a BlackBox, when it starts up, GRBL will default to mm. Even if you change the display to inch-mode, GRBL is still in mm. If your gcode file doesnt tell it to switch to inches via a G20 command, all the moves will be interpreted as mm. That's why its so small.

    As Alex has said, you should be using the Grbl (inch) post processor NOT the G Code (inch) processor. If you use Grbl (inch), then it will correctly output a G20 command to tell GRBL that all movements are expressed in inches and your part will be the correct size.
     
    #10 sharmstr, Nov 16, 2019
    Last edited: Nov 16, 2019
    Pidiln and Alex Chambers like this.
  11. Pidiln

    Pidiln New
    Builder

    Joined:
    Sep 20, 2019
    Messages:
    13
    Likes Received:
    6
    Alex,

    I just realized that I am using G code (inch) instead of Grbl (inch) (*.gcode)

    I saved the gcode as Grbl (inch) (*.gcode) and that fixed all my issues, including the T1M6 code!

    thanks so much for helping out this newbie

    You Sir are a gentleman !

    Pidin
     
    sharmstr and Alex Chambers like this.
  12. Pidiln

    Pidiln New
    Builder

    Joined:
    Sep 20, 2019
    Messages:
    13
    Likes Received:
    6
    Thanks Sir, you are exactly correct.
    I have corrected my errors and was able to carve a file to the correct size and no T1M6 error code either.
    You bet I will remember, its the small things that count ! lol.
    Pidiln
     
    Giarc and sharmstr like this.

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