Hello Guest it is April 19, 2024, 03:11:48 AM

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 - stirling

181
Mach SDK plugin questions and answers. / Re: VB6 Automation Sample
« on: February 10, 2016, 06:02:23 AM »
Welcome to the forum dz32.

Just had a quick look but this looks like it could be fun.

Thanks for sharing.

182
check your m3 macro isn't corrupt.

183
General Mach Discussion / Re: Mach3 VB Script Help
« on: February 10, 2016, 04:45:54 AM »
So If I did
Code "G1 X" & XZero "F30"

That is the most usual way.

watch your concatenation operators though, the line as written will fail.

184
General Mach Discussion / Re: coutinuous y movement seperate from z
« on: February 09, 2016, 09:06:25 AM »
 ;D

185
Tangent Corner / Re: Electro-Punch design
« on: February 09, 2016, 08:59:30 AM »
any progress Russ?

186
General Mach Discussion / Re: Mach3 VB Script Help
« on: February 09, 2016, 07:06:40 AM »
You may be over-complicating things. If we look at your various probe directions as being north, south, east and west. You seem to be going west, east, south, north, then again and then again.

Might be better if you did west, west, west, east, east, east etc. etc.

HOWEVER - Although some say for improved accuracy you should probe TWICE, once at some speed and then again at a a lower speed, I can't see any value in doing it THREE times.

You also shouldn't use the values in the DROs as your trip points. You should read the parameters 2000 (X) and 2001 (Y).

Here's a trivial example of a 1 shot probe which assumes you've placed the probe roughly at the centre of your circular pocket (you need to replace ? with some number):

code "G31 X?" 'where ? is some number guaranteed to get you to the circumference
while isMoving()
  sleep 10
wend
tripX = getVar(2000) 'variable tripX now holds the exact point of the trip

Now if you want to probe again, you'd just reverse a bit past the trip point and do exactly the same again.

Disclaimer: If any of the above breaks anything (including your heart) - you get to keep the pieces.


187
G-Code, CAD, and CAM discussions / Re: Macro for inputs and outputs
« on: February 09, 2016, 06:52:48 AM »
Terry - A good point well made. Apologies if I've confused things.

188
General Mach Discussion / Re: Physical buttons for plasma
« on: February 09, 2016, 05:30:58 AM »
Hood - AFAIK Mach3 THC anti-dive is plain simple ignore THCdown signal if the actual speed (of any axis) is less than the set % of feed.

They may well have added "pierce time anti-dive" and that MAY be what they're referring to. Personally I didn't read it that way but that's just me.

Whatever, the 1ms doesn't seem to fit with that somehow. I'm wondering if for some reason they've decided that when a slowed axis gets back up to speed, rather than immediately enable THC down commands again, they insert a delay. Can't see why at the moment but that's more how I'd read what they've written.

189
G-Code, CAD, and CAM discussions / Re: Macro for inputs and outputs
« on: February 08, 2016, 12:10:42 PM »
LOL - why thanks Terry BR549 - didn't know there was a concept of "lead" - nor that permission was needed.  :D

190
Hi Terry - I don't think this IS 3D though. Check out the code he posted. There's no Z going on.

Whatever though - what I'm getting at is there's no reason (that I can see at least) why the lines SUDDENLY change length dramatically. Check out the pic I posted again, There's NO detail there that would require it. Maybe I'm wrong - just thinking.

Anyway - as we've both now said - it's working so it doesn't really matter.