Hello Guest it is October 13, 2019, 09:50:03 PM

Author Topic: Physical Size  (Read 8155 times)

0 Members and 1 Guest are viewing this topic.

Offline kolias

*
  •  1,011 1,011
    • View Profile
Re: Physical Size
« Reply #10 on: August 19, 2009, 06:22:55 PM »
Nicely said Dave

Thank you both
Nicolas
Nicolas
Re: Physical Size
« Reply #11 on: September 12, 2009, 06:44:00 PM »
I have a question about the min and max DRO's.  I put a set for X (OEM's 4 and 10), Y (OEM's 5 and 11) and Z (OEM's 6 and 12) on the main page of my Tormach screenset.

The DRO's don't reflect the actual motion extents of the loaded gcode file.  Is there anything special I need to do, or are the DRO's supposed to automatically parse the file and find the limits?  I couldn't find any documentation in the PDF's or Wiki, and this was the closest thread I could find.

Thanks,

Randy

Offline Hood

*
  •  25,855 25,855
  • Carnoustie, Scotland
    • View Profile
Re: Physical Size
« Reply #12 on: September 12, 2009, 06:57:05 PM »
Please attach your screenset.
Hood
Re: Physical Size
« Reply #13 on: September 12, 2009, 07:57:54 PM »
It's at http://www.machsupport.com/forum/index.php?action=dlattach;topic=11968.0;attach=16166 already and the board won't let me upload another copy.

Thanks,

Randy

Offline poppabear

*
  • *
  •  2,233 2,233
  • Briceville, TN, USA
    • View Profile
    • S S Systems, LLC
Re: Physical Size
« Reply #14 on: September 12, 2009, 07:58:30 PM »
Randy,

    Once you "Load the G code" into Mach 3, the program extends will already show, NOTE it goes by the current work offset when you load the code.

scott
Commercial Mach3 & Mach 4, Design/Build/Retrofit CNC and Industrial machines.
http://www.ss-systems-llc.com/

Offline Hood

*
  •  25,855 25,855
  • Carnoustie, Scotland
    • View Profile
Re: Physical Size
« Reply #15 on: September 12, 2009, 08:02:10 PM »
Your screenset is working fine here and showing correctly when I load code. If you are still having issues can you post your xml so I can check with your settings.
Hood
Re: Physical Size
« Reply #16 on: September 12, 2009, 08:34:57 PM »
Scott, then my setup is not working correctly.  When I load a new gcode, the mins and maxes are way off what I know are the extents of even the rawstock.  And the mins and maxes are generally the same number.

Hood, can I copy the XML while Mach is running?  It's doing a 4+ hour contouring job right now.

Thanks,

Randy

Offline Hood

*
  •  25,855 25,855
  • Carnoustie, Scotland
    • View Profile
Re: Physical Size
« Reply #17 on: September 12, 2009, 08:38:12 PM »
Shouldn't be a problem but probably best just to wait. I will check in the morning, or I should say I will check back later in the morning as its 01:40 here ;D
Hood

Offline Chris.Botha

*
  •  486 486
  • wine me.. dine me.. tram my mill for me...
    • View Profile
    • Digital-Jeweller
Re: Physical Size
« Reply #18 on: September 12, 2009, 10:00:33 PM »
try zeroĆ­ng all axis's and regenerate the the path. works for me. if x is at say +100 when i load the code and the code has an actual X- of 20 and a X+ of 20 mach will show it as being X-20min and X+120max

if you use arcs forget it. still not figured out how to get that working properly. i had to switch off softlimit because when i load arc codes my min and max on all the axis's can be as far out as 1200mm sometimes.. and i only cut jewellery ;)

Re: Physical Size
« Reply #19 on: September 13, 2009, 01:19:25 AM »
Hood, here's my XML.

Chris, I'll read about how to regen the toolpath.  I always start by touching the first tool in x, y, and z (in that order) on the rawstock so the tool does end up within the x-y machining envelope, but above in Z.  My toolpaths are usually a combination of lines and arcs.

Thanks,

Randy