Hello Guest it is December 02, 2023, 07:55:58 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - rhtuttle

331
Mach4 General Discussion / Probe wizard on Lathe
« on: January 25, 2018, 05:44:30 PM »
I exported the probe tab in the mill screenset and imported it into the lathe screenset. Filled in the settings and ran a Z single surface probe. I get an error message 'Unknown GCode used'.

Is there a gcode being issued that is only applicable to mill usage?

TIA

RT

332
Mach4 General Discussion / Lathe probing screen
« on: January 25, 2018, 11:21:43 AM »
Has anyone ported the probing from mill to Lathe? 

Modified it so that makes sense for a lathe?

I know how to export the page from mill screenset and import it to lathe screenset but was hoping someone else would like to share their hard work and save me a lot of time  ;D

TIA

RT

333
Mach4 General Discussion / Re: How do I get to the center of 2 edges?
« on: January 24, 2018, 01:08:10 PM »
Not sure why I would want it on lathe but it doesn't work in the wxLathe.set

334
Mach4 General Discussion / Re: Lua Fails Me
« on: January 20, 2018, 06:01:02 PM »
As usual you are correct  ::)

Adding back one macro at a time  I found one m7791 that had the m6691 defined in it.  Right about now I wish I had remembered about those utilities to scan all files for a string.  That probably should have been one of the first attacks.  Guess I need to brush up on my ms-dos skills again.

Thank you for your patience Steve. 

RT

335
Mach4 General Discussion / Re: Lua Fails Me
« on: January 20, 2018, 03:33:28 PM »
Steve,

I totally believe you.

Attached is the actual file m6691.mcs as it stands now.

When I remove this from the macros directory, delete all mcs and bak files, load mach and  run m6691 from the mdi, nothing happens as expected.

Copy the m6691.mcs back into the macros directory, go into the operator->edit/debug scripts and select m6691.mcs the file opens, F7 to compile, save, close, run m6691 from the mdi... and... the spindle starts, the x moves in and then travels the Z just as in the code from my first entry here.

I know it is not possible... but it is happening.

RT

336
Mach4 General Discussion / Re: Lua Fails Me
« on: January 20, 2018, 01:20:16 PM »
Exited mach, removed the 'test.sav' which had the m6691() defined, deleted all mcc and bak files and started mach4, ran m6691 in the mdi and still same result.

337
Mach4 General Discussion / Re: Lua Fails Me
« on: January 20, 2018, 12:26:23 PM »
dbt3000files,

I thought you were on to something so I checked my macros directory and I had saved a copy of m6691.mcs as test.mcs.  So I changed it to test.sav so it wouldn't get compiled and deleted all mcc and bak files and fired up mach.

Ran m6691 in the mdi and same old s..t!! Drat.

I have a ticket in with MFS and James has been able to duplicate it with my package so hopefully they will find where I screwed up.


338
I just re-read the down and dirty doc and something caught my eye.

Screen Stuff: You can get the names of the object from within the screen designer to include property names
and values. Further note, you can access screen objects from within macros or wizards.

I don't believe you can access screen properties from a macro.  You  can from a button or screen script.  If I am wrong please post a small macro snippet as to how it is done.

TIA

RT

339
Mach4 General Discussion / Homing and Tool offsets on Lathe
« on: January 19, 2018, 03:34:03 PM »
Not being a machinist I have a question about homing and tool offsets.  I just started developing my tool table a couple of weeks ago and enjoy being able to swap tools and have confidence that It will continue on where you would expect it.  Whoop whoop!!

My assumption (big mistake) is that since turning is typically done on center and that all tool cutting points have their x axis offset from machine zero to the centerline.  I thought that when I homed/ref'd, that machine zero would be set, and, the XDRO would adjust to reflect the current tool offset in effect.  As an example,  if tool 1 has an offset from home and entry in the tool table of -3.1255 I would have thought that after homing the XDRO would read -6.251.  On my machine the DRO is unaffected.

a.  Was my thought process wrong?
b.  Should I change the ref x button to have a script that refs x and then reads the current offset and sets the xDro to that number?

TIA

RT

340
Mach4 General Discussion / Re: Mach 4 Feature Request
« on: January 19, 2018, 02:59:30 PM »
Default wxLathe.set, shouldn't the open Docs be enabled at all times.  Mine is now.