¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Constant Volume Threading


 

Art,
From reading the last couple of weeks posts, I think that the
problem with the constant volume macro that I sent you off list is
that the angular functions were in radians for previous versions. Is
that still the case with release 4.0? Have you had a chance to try
running that macro?
The only way that I am able to write a new macro is to load an
existing macro, delete its contents, write the new macro and save it
with a different name. Is it possible to use the Mach 2 editor to
write and save new macros?
Don


Art
 

Don:

Yes, It is still in radians, I can't change that because its a windows
scripting function. I do intend though to put the code you sent into the
main OCX code base and select Constant Volume as a G-Code switch. Hopefully
very soon....

Thanks,
Art
www.artofcnc.ca


 

Donald, in version 4.0 VBscript is in Radian (and i hope it will stay
because i wrote a big macro with it).

Olivier.


Robin Szemeti
 

On Monday 23 February 2004 01:38, Donald Hansen wrote:

The only way that I am able to write a new macro is to load an
existing macro, delete its contents, write the new macro and save it
with a different name. Is it possible to use the Mach 2 editor to
write and save new macros?
I have a more fundamental problem with macros ... they keep getting
overwritten. Also .. I find the having 2 sets of them M5.tis M5.mis a bit
weird ... I'm forever editing the worng one .. what I think answers this
problem and neatens up the layout a bit is: use directories.

so ..

mach2/
macros/
mill/
M3
M5
etc
lathe/
M3
M5
etc
plasma/
M3
M5
etc
OEM/
etc

the machine XML file could specify which directory was to be used to look for
the macros, if you wanted to write some new ones and be sure they werent
over written when you upgraded then just create a new directory and tell
mach2 to use that. this woudl be especially useful for OEM's where I'd like
to send update CD's out, but I know that I have lots of modified macros and
they get over written ... there is now enough specialist macros kicking about
that some one is going to get bitten and losing code you have written really
sucks :)

I keep mentioning this idea ... I haven't had a comment from Art yet .. I
guess that means he don;t like it ;)

--
RapidCut CNC Technology

CNC Plasma Cutter


 

I like it. It would solve the overwrite problem. The other option
it to make a copy of the macro and leave it in the Macro folder. Then when
you upgrade you only have to copy that macro back as M3 or M5, but the
separate folder would work much better.
Jim

----- Original Message -----
From: "Robin Szemeti" <list@...>
To: <mach1mach2cnc@...>
Sent: Monday, February 23, 2004 3:33 AM
Subject: Re: [mach1mach2cnc] Constant Volume Threading


On Monday 23 February 2004 01:38, Donald Hansen wrote:

The only way that I am able to write a new macro is to load an
existing macro, delete its contents, write the new macro and save it
with a different name. Is it possible to use the Mach 2 editor to
write and save new macros?
I have a more fundamental problem with macros ... they keep getting
overwritten. Also .. I find the having 2 sets of them M5.tis M5.mis a
bit
weird ... I'm forever editing the worng one .. what I think answers this
problem and neatens up the layout a bit is: use directories.

so ..

mach2/
macros/
mill/
M3
M5
etc
lathe/
M3
M5
etc
plasma/
M3
M5
etc
OEM/
etc

the machine XML file could specify which directory was to be used to look
for
the macros, if you wanted to write some new ones and be sure they werent
over written when you upgraded then just create a new directory and tell
mach2 to use that. this woudl be especially useful for OEM's where I'd
like
to send update CD's out, but I know that I have lots of modified macros
and
they get over written ... there is now enough specialist macros kicking
about
that some one is going to get bitten and losing code you have written
really
sucks :)

I keep mentioning this idea ... I haven't had a comment from Art yet .. I
guess that means he don;t like it ;)

--
RapidCut CNC Technology

CNC Plasma Cutter





Yahoo! Groups Links




Art
 

Olivier:

I won't (can't anyway) change it. I haven't a clue how yet, though there
may be a setting in the VB engine somewhere...

Art
www.artofcnc.ca

Donald, in version 4.0 VBscript is in Radian (and i hope it will stay
because i wrote a big macro with it).


Art
 

Robin:

You've convinced me, its coming..., though I have a couple of concerns...

Art
www.artofcnc.ca


Robin Szemeti
 

On Monday 23 February 2004 21:26, Art wrote:
Robin:

You've convinced me, its coming..., though I have a couple of concerns...
Thanks :)

the obvious concern is 'legacy' issues I guess?

Don't panic too much over this one, I think lockdown for 4.0 is more
important and that is now so close I can smell it. I think maybe after that,
the next testing series could include it ?

I can imagine that it will need a small transition period for people to move
their macros over to a directory structure rather than using .m1s, .t1s ..
but long term I htink it is the right answer to these issues. It will be
especially useful to OEMs I guess with their own custom macro sets.

Whatever, It will certainly help me anyway ... I hope it will help others too.

--
RapidCut CNC Technology

CNC Plasma Cutter


Art
 

Don't panic too much over this one, I think lockdown for 4.0 is more
important and that is now so close I can smell

Yes, lockdown of Version 4.0 is getting very close. Actual bugs are almost
non-existant. Not to say they don't exist, but as a comparison I think 4.0
is a world better than 2.0 at present. ...

Art
www.artofcnc.ca


 

Yes it will help me too.
Jim

----- Original Message -----
From: "Robin Szemeti" <list@...>
To: <mach1mach2cnc@...>
Sent: Monday, February 23, 2004 3:53 PM
Subject: Re: [mach1mach2cnc] Constant Volume Threading


On Monday 23 February 2004 21:26, Art wrote:
Robin:

You've convinced me, its coming..., though I have a couple of
concerns...

Thanks :)

the obvious concern is 'legacy' issues I guess?

Don't panic too much over this one, I think lockdown for 4.0 is more
important and that is now so close I can smell it. I think maybe after
that,
the next testing series could include it ?

I can imagine that it will need a small transition period for people to
move
their macros over to a directory structure rather than using .m1s, .t1s ..
but long term I htink it is the right answer to these issues. It will be
especially useful to OEMs I guess with their own custom macro sets.

Whatever, It will certainly help me anyway ... I hope it will help others
too.

--
RapidCut CNC Technology

CNC Plasma Cutter




Yahoo! Groups Links