Messages

1601

General Mach Discussion / Re: edge finding/2.5D probing

« on: June 01, 2010, 04:27:20 AM »

Hi - mick - glad you've got it sorted. It's a shame that Mach doesn't throw an error message when it can't find a macro - that would have cleared this up straight away.

Cheers

Ian

1602

General Mach Discussion / Re: edge finding/2.5D probing

« on: May 31, 2010, 11:43:11 AM »

LOL - my apologies mick - You're quite rightly using the latest version and I'm not! OK - so when it's done the line - M90000 P1 it SHOULD have set all the gcode vars to what you specified in the config app. So, what's their values at that point?

Sorry again for the confusion - my memory's worse than I thought!

Ian

1603

General Mach Discussion / Re: edge finding/2.5D probing

« on: May 31, 2010, 06:59:35 AM »

single step to #1001=1, enter 1001 in var moniter and update, value returned 1
step to #1002=0  enter 1002 in var moniter and update, value returned 0

Sorry mick - still confused - there isn't any line that says #1001=1 or #1002=2 etc.

the line F#1001 will set your feedrate to whatever you set it in the config app, which you said above, it does i.e.

when i get to f#1001 the feed rate is loaded.

..and the line: G00 Z#1002 will move your Z axis to whatever you set safe Z to in the config app. etc. etc.

1604

General Mach Discussion / Re: cuting snails and helices (helixes?) - parametrics problems

« on: May 31, 2010, 06:39:56 AM »

To be honest I'd never realized until your post that Mach allowed this error. Thinking about it though, I suppose there has to be some margin for error else CAMs would have to be infinitely precise in order to do arcs, so I'm thinking it's more a neccessity than a bug. I'm guessing Art thought - what the heck - a half inch should do it!

Cheers

Ian

1605

General Mach Discussion / Re: edge finding/2.5D probing

« on: May 31, 2010, 05:46:50 AM »

yes Ian , m90000.m1s is in c:\mach3\macros\machmill

Just double check that. By default your profile would be mach3mill - not - machmill. You may have changed it of course which is fine.

by the way should i be able to see the values set , in the gcode

No - not in the actual gcode - i.e. you'll not see F#1001 changed to F3000 or whatever. - you have to use the var monitor if you want to check the gcode vars are what they should be.

because when i single step through the code
when i get to f#1001 the feed rate is loaded.but not visable in #1001=.

Then it sounds like it IS loading the gcode vars - sorry you've lost me now - you originally said

the problem seems to be, the variables are not loaded into the gcode

1606

General Mach Discussion / Re: cuting snails and helices (helixes?) - parametrics problems

« on: May 31, 2010, 05:09:01 AM »

Hi bp - You could take advantage of Art's "generosity" by instead of using the error once per circle - use it as many times as you like. Here's your code modified to use the error every quarter circle for example.

#1=45
G0 X0 Y[#1]
G0 Z1.00
M3 M8
G01 Z-1.0 F3000

M98 P1 L10

G0 Z10 M5 M9
M30
O1

G03 X[0-#1] Y0 I0 J0 F3000
#1=[#1+7.0]
G03 X0 Y[0-#1] I0 J0 F3000
#1=[#1+7.0]
G03 X[#1] Y0 I0 J0 F3000
#1=[#1+7.0]
G03 X0 Y[#1] I0 J0 F3000
#1=[#1+7.0]
M99
%

Hope this helps.

Cheers

Ian

1607

General Mach Discussion / Re: edge finding/2.5D probing

« on: May 31, 2010, 04:09:56 AM »

looks fine mick. So we know the config routine is posting the values to the registry ok but it looks like the probing routine is not pulling them out again.
Have you copied m90000.m1s to the correct folder?
Look bottom right of the main Mach screen and note the profile your using. Now check m90000.m1s is in folder C:\Mach3\macros\"your profile name" (assuming you installed mach in c:\mach3 that is).

Ian

1608

General Mach Discussion / Re: edge finding/2.5D probing

« on: May 30, 2010, 11:16:14 AM »

not quite - hit f3 and you should get something like the attached under VB and VBA Program Settings (just down a bit on your left pane).

1609

General Mach Discussion / Re: edge finding/2.5D probing

« on: May 30, 2010, 09:36:05 AM »

mick - do a search in the registry for PR25D and let me know what you find
Ian

1610

General Mach Discussion / Re: edge finding/2.5D probing

« on: May 30, 2010, 08:12:57 AM »

the problem seems to be, the variables are not loaded into the gcode

Hi mick - Let's check that out first.
I'm assuming you've run start/all programs/probe utilities/probectrl.
put Mach into single block mode and run the first line of probe25D.tap. Using the gcode var monitor in Mach, check the value of var 1001. Is it the feedrate you set in probectrl?
Cheers
Ian