X and Y Axis 5mm off

Home › Forums › TinyG › TinyG Support › X and Y Axis 5mm off

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • August 17, 2014 at 3:11 pm #6626
    shaputer
    Member

    Hello,

    I love the TinyG and it’s performance. I have Version 8 and I’m using 435.10 firmware. I’m controlling a Shapeoko 2 setup with a Raspberry PI and a VGA monitor. Everything works perfectly, jogging, homing, my limit switches, running jobs……..all work fine. Just one problem. Every design offsets 5mm in the X and Y directions and my object that is cut is 5mm larger than it should be. I’ve looked at every setting and can’t find where to adjust this.

    How can I adjust this in TinyG. With gshield that was easy by adjusting the steps/mm values slightly. I tried adjusting the revolutions/mm in TinyG and it didn’t change my problem.

    I appreciate your time and any assistance you can offer.

    Again WONDERFUL PRODUCT ! :=}

    August 17, 2014 at 4:43 pm #6627
    cmcgrath5035
    Moderator

    It’s not perfectly clear what you are describing.
    Are you saying that a design (Gcode) that should draw a 10mm diameter circle centered at (10,10) draws a 15mm circle centered at (15,15)? (for example).

    Perhaps post your settings ($$ dump) to a text file in a dropbox location?

    By the way, what are you using to deliver Gcode and jog commands?

    August 17, 2014 at 5:31 pm #6629
    shaputer
    Member

    Yes, you are exactly right. That’s what I’m describing.
    I’m using the simplest approach I can think of because all I want is accuracy and reliability. I use minicom to send jogging commands. cat jogright.nc | minicom -batch All my jogging commands are like this and are controlled with keyboard characters defined in a shell script. jogright.nc would contain G0 X500 then $df=1. ‘h’ is used to halt when I want to stop it. I send cutting files through plink because it has XON/XOFF.

    Here the link to my settings

    https://www.dropbox.com/s/zrpdg2ri8vbwujx/chgsettings.txt

    Here’s the link to my Shapeoko Post Processor

    https://www.dropbox.com/s/4e78k1dyilur0ht/Shapeoko_mm.pp

    August 17, 2014 at 8:20 pm #6630
    alden
    Member

    For starters the travel per revolution on motors 1, 2 and 3 is set for the Shapeoko1 which had smaller wheels. (We need to update the wiki with a page especially for the Shapeoko2)

    I believe the Shapeoko2 has 20 teeth pre revolution at 2mm per tooth. So the $_tr value should be 40. I’m not sure that will account for all the difference you are seeing, though. Set the value and try lines of defined length, like 100mm. I can’t see anything else incorrect in your settings.

    The settings don’t list the firmware revision or build. What $fv and $fb are you running?

    August 18, 2014 at 8:50 am #6633
    cmcgrath5035
    Moderator

    shaputer

    I use minicom to send jogging commands. cat jogright.nc | minicom -batch All my jogging commands are like this and are controlled with keyboard characters defined in a shell script. jogright.nc would contain G0 X500 then $df=1. ‘h’ is used to halt when I want to stop it. I send cutting files through plink because it has XON/XOFF.

    I understand (I think) you jog implementation, which I’ll paraphrase as “start a large move and stop it with an ‘h’. But what command does ‘h’ send?
    What does $df=1 do? I have not used that, and can’t seem to find a reference to it.

    August 18, 2014 at 10:09 am #6635
    shaputer
    Member

    Alden – Thanks for the info. I’ll try that. I have Version 8 and I’m using 435.10 firmware build, 0.97 firmware version and 1.00 Hardware platform. My TinyG ID=2u2971-YQY. The reason my settings file doesn’t list that is because I use the file in the above (chgsettings.txt) to update my TinyG. It’s based on the output from tgfx. TGFX caused me too many problems and didn’t always update settings when I changed them. So, I dumped it from tgfx and deleted tgfx totally. I took that dumped file and added the “$” in the front of the value and an “=” after the value and deleted all other text after it’s number value. I cat chsettings.txt to the TinyG which updates every time without fail. chsettings.txt is what is currently loaded on my TinyG.
    ================================
    cmcgrath5035 – I used the “!” to halt. $df=1 clears the buffer in TinyG. I read this on a blog somewhere. When I don’t use $df=1 and press “r” to go right — halt –then I can’t go right again until I go in another direction first. With the $df=1 I can keep pressing “r” then “h” then “r” then “h” until I get where I want to be.

    Thanks for your help ! Will update you if I fix it alden.

    August 18, 2014 at 10:27 am #6637
    shaputer
    Member

    I’m a happy damn camper ! ;=} Alden your suggestion fixed it. I figured it was something easy and I just couldn’t see it. I changed that value before too, but not to 40….Thanks again !

    August 18, 2014 at 10:57 am #6639
    alden
    Member

    Glad it worked. We have an item to update the wiki with special instructions for Shapeoko2

    August 18, 2014 at 12:10 pm #6640
    cmcgrath5035
    Moderator

    shaputer
    I did a little more searching, you might find this thread interesting:

    and also

    Note Riley’s comments on how tgFX implements jogging.

    I have not yet found a reference to $df=1, appears % is the intended queue flush command. Note also the section on jogging with queue hold and flush in the second reference

    Good find!

    August 18, 2014 at 1:01 pm #6642
    shaputer
    Member

    Interesting. “~” didn’t work for me. I used “%” and that worked as well as $df=1.
    As for the other stuff. I”ll keep it for reference, but my setup works perfect now and I’m not going to mess with it. I’m done with cool term which didn’t work well for me either. Too many glitches like tgfx. That’s why I decided to bypass all that and write something real simple. Thanks !

    • This reply was modified 10 years, 3 months ago by shaputer.
  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.