开云体育

Art,

I pulled Mach2 RC10 down and tried to install it. When it came up it said
wrong driver version, so I attempted to remove and re-install the non apic
driver. It keeps trying to install the Mach2.sys drive which does not work
on my machine, and when I try to install the special driver it only wants to
install Mach2.sys, not Mach1.sys. What do I do to correct this problem? I
have tried to follow the instructions in the manual beginning on page 15 but
it is not working with RC10.

John Guenther
'Ye Olde Pen Maker'
Sterling, Virginia

Hi All,
At 2000 RPM cutting 20 threads per inch, my Z axis would have to move
at 100 IPM, ( I think).
Although my top speed is 180 IPM I wonder what distance it would take
to reach that speed. I think my acceleration is set at 3.5 but I
don't know 3.5 what. Can someone tell me what distance it would take
to reach 100 IPM at that setting?

I assume the deceleration would be the same so that potion of the
thread would be useless, No?

Jerry






--- In mach1mach2cnc@..., Art <fenerty@a...> wrote:

LatheHeads...

to thread with and I couldn't get the spindle speed where it

had to

be to get the best finish

Interesting note here on speed. Early on I was told that flashcut

had a

problem with threading above a certain speed, so I tried to design

the

compensator to allow any speed. This is, of course, impossible, but

I am

interested in any experience in this area. The technique is a

little unique.

I use a bresenham algorithm within the main bresenham algorithm to

slow down

time if the spindle slows. The design assumes the spindle will not

speed up

above the starting RPM during a thread (hopefully a good

assumption) so time

simply slows down for the pulser which has already computed the

pulse timing

using the original algorithm based on the originating spindle speed
feedback. This time slowing is done useing a time constant derived

on each

revolution as the adder to the bresenham. There is no way that one

pulse per

rev can do the job in the end I think, but I am interested in how

fast

anyone CAN do a thread using this technique.
This algorithm within an algorithm was the only way I could

think of to

do this reliably in a buffered pulse engine, the results will be
interesting.

To see your theoretical maximum thread pitch at any speed easily ,

you need

only set a spindle speed, and then jog back and forth in the Z

axis. The

reading of the Velocity/Rev DRO at full speed jog is your maximum

threading

pitch in your setup. This, of course, is because your rapid speed as
compared to the spindle speed is your maximum pitch per

revolution.You'd

need a fast Z carriage to do 2000RPM threading at any but a very

fine pitch.

The engine uses the number of 40us intervals between rotations as

the

constant for the algorithm as measured when the G32 is begun. So at

500RPM,

the engine has a count of 3000 intervals per rotation, It can

correct pretty

finely at that high a number, but at 2000RPM, the count is only 750

so the

ability to compensate has dropped by almost 75% from the 500RPM

mark. This

is all at 25Khz. At 45Khz you have 22us periods so the numbers get

better.

At 500RPM you get 5454 pulses per rev and at 2000RPM you get 1363

pulses per

revolution. So the quality at 500RPM in 25Khz mode should be equal

to the

quality of the cut at 909RPM in 45Khz mode. So just in case you were
wondering if 45Khz mode was any better even if you can't drive your

motors

faster, in this case it is because the thread compensation will be

more

accurate even at lower speeds.

Just an application note on threading...
Art
www.artofcnc.ca

Oh, and
13) Lathe Display improved.

Thanks
Art
www.artofcnc.ca

Yeah, I know, you never got to see 8.0 and 9.0, they went away never got
time to release them.

New Features and Bugs fixed:

1) DXF layer is improved, plunge rates added.
2) DXF stutter problem gone. (Multiple lines generated)
3) DXF Spindle speed per layer and empty layer removal.
4) DXF improved optimization
5) Macro's changed to multi-threading design. They now run in parallel to
the engine.
6) New Macro Commands:
IsMoving Returns a 1 if the interpreter is processing movement.
GetPortByte( address ) returns the byte at that port address
PutPortByte( address, byte ) puts the byte into that port.
7) Dwell Bug checked and repaired.
8) OverRide input pin is repaired
9) When in ToolChange, Estop will stop that state
10) G28.1 repaired. It is now repeatable in its operation. G28.1 X1 will
move rapid to 1, then home to switch ,move off switch and stop.
11) Flood Mist setting repaired
12) M30 offset removal bug. Only X was being removed when commanded by
Ancillary logic setting.

I have left RC2 as the most stable version until this is tested,
particularly the macro control. If all goes well, RC2 will be removed after
the next release. I still have some bugs on the list, but wanted to get this
general maintenance release out. (Its been almost a month.)

Thanks,
Art
www.artofcnc.ca

On Wed, 13 Aug 2003 20:55:09 -0300, you wrote:

Interesting note here on speed. Early on I was told that flashcut had a
problem with threading above a certain speed, so I tried to design the
compensator to allow any speed. This is, of course, impossible, but I am
interested in any experience in this area. The technique is a little unique.
I use a bresenham algorithm within the main bresenham algorithm to slow down
time if the spindle slows. The design assumes the spindle will not speed up
above the starting RPM during a thread (hopefully a good assumption) so time
simply slows down for the pulser which has already computed the pulse timing
using the original algorithm based on the originating spindle speed
feedback. This time slowing is done useing a time constant derived on each
revolution as the adder to the bresenham. There is no way that one pulse per
rev can do the job in the end I think, but I am interested in how fast
anyone CAN do a thread using this technique.

The old controller was quite happy to thread all the pitches I tried
at between 500-800 rpm, with it's limits of 1100rpm top speed, and max
400mm/min axis speed I thought it was pretty good. It was remarkably
accurate too with only one pulse per rev.

I think the limitations in this case were down to a 2Mhz processor and
OS, rather than lathe hardware.

This algorithm within an algorithm was the only way I could think of to
do this reliably in a buffered pulse engine, the results will be
interesting.

How is your basic? That's what the old program was written in <G>. If
you understand it, it may be worth a look to see how it was done?

I think I can retrieve it off the 5 1/4" floppies (If the drive I have
still works).

To see your theoretical maximum thread pitch at any speed easily , you need
only set a spindle speed, and then jog back and forth in the Z axis.

I'll have a play tomorrow and report back.
--
Steve Blackmore

LatheHeads...

to thread with and I couldn't get the spindle speed where it had to

be to get the best finish

Interesting note here on speed. Early on I was told that flashcut had a
problem with threading above a certain speed, so I tried to design the
compensator to allow any speed. This is, of course, impossible, but I am
interested in any experience in this area. The technique is a little unique.
I use a bresenham algorithm within the main bresenham algorithm to slow down
time if the spindle slows. The design assumes the spindle will not speed up
above the starting RPM during a thread (hopefully a good assumption) so time
simply slows down for the pulser which has already computed the pulse timing
using the original algorithm based on the originating spindle speed
feedback. This time slowing is done useing a time constant derived on each
revolution as the adder to the bresenham. There is no way that one pulse per
rev can do the job in the end I think, but I am interested in how fast
anyone CAN do a thread using this technique.
This algorithm within an algorithm was the only way I could think of to
do this reliably in a buffered pulse engine, the results will be
interesting.

To see your theoretical maximum thread pitch at any speed easily , you need
only set a spindle speed, and then jog back and forth in the Z axis. The
reading of the Velocity/Rev DRO at full speed jog is your maximum threading
pitch in your setup. This, of course, is because your rapid speed as
compared to the spindle speed is your maximum pitch per revolution.You'd
need a fast Z carriage to do 2000RPM threading at any but a very fine pitch.
The engine uses the number of 40us intervals between rotations as the
constant for the algorithm as measured when the G32 is begun. So at 500RPM,
the engine has a count of 3000 intervals per rotation, It can correct pretty
finely at that high a number, but at 2000RPM, the count is only 750 so the
ability to compensate has dropped by almost 75% from the 500RPM mark. This
is all at 25Khz. At 45Khz you have 22us periods so the numbers get better.
At 500RPM you get 5454 pulses per rev and at 2000RPM you get 1363 pulses per
revolution. So the quality at 500RPM in 25Khz mode should be equal to the
quality of the cut at 909RPM in 45Khz mode. So just in case you were
wondering if 45Khz mode was any better even if you can't drive your motors
faster, in this case it is because the thread compensation will be more
accurate even at lower speeds.

Just an application note on threading...
Art
www.artofcnc.ca

I don't think anybody thought you were putting it down.
Bob

I would say the thread Looks GREAT as well!! because I have used

AHHA

to thread with and I couldn't get the spindle speed where it had to
be to get the best finish. If mach2 can do threads fast that would

be

nice for all the people doing the small parts.

I am in hopes of setting up a toolroom lathe with Mach2 in the next

6

months for my small work.

Sorry if it sounded like I was putting down the thread because I
understand the hours of work that has been put into those threads.
And I think it is GREAT that there is going to be something that

will

work well for threading that will not cost thousands.

Happy chips
Brian

--- In mach1mach2cnc@..., "Robert Hansberger"
<rhansberger@c...> wrote:

You didn't say the type of steel you were threading. The drill rod
steels (silversteel)O-1 W-1, are not the easiest to cut threads on
when compared to free machining steels. I think yours looks just
fine, especially for an early effort with a new program.
Bob

I would say the thread Looks GREAT as well!! because I have used AHHA
to thread with and I couldn't get the spindle speed where it had to
be to get the best finish. If mach2 can do threads fast that would be
nice for all the people doing the small parts.

I am in hopes of setting up a toolroom lathe with Mach2 in the next 6
months for my small work.

Sorry if it sounded like I was putting down the thread because I
understand the hours of work that has been put into those threads.
And I think it is GREAT that there is going to be something that will
work well for threading that will not cost thousands.

Happy chips
Brian

Art

Just a small one,When using software limits and they are
activated,if you hit the limit the status shows this but when moving
off the message is left on the status line or error line at the
bottom of screen.Also what happened to the box in the logic screen
that enabled you to input a figure for the machine to move off limit
switches so the machine did not sit on the switch or is this now the
debounce box?.

Mark

Hi

I suspect that a bug has crept into Mach2 RC 7 (I know not when). If you set up a Tool or Fixture on Tables screen and click the relevant button to save/make it persistent then you get the dialog box with already saved tools/fixtures but the entry for the tool/fixture defined in the DROs is not loaded with data and so is not easy to save. You have to type values into dialog to save them. At one time the values were put in the dialog grid from the Tables screen DROs.

Best wishes

John Prentice

You didn't say the type of steel you were threading. The drill rod
steels (silversteel)O-1 W-1, are not the easiest to cut threads on
when compared to free machining steels. I think yours looks just
fine, especially for an early effort with a new program.
Bob

Bob,

There were 2 terms I used Home and Reference.

The Mach1/2 "Home" switches are used for referencing. When you reference the
machine, The machine moves in the direction configured in the software. The
machine keeps moving until it activates the home switch for each axis. These
switches can be at any position you like. i.e. X=2, Y= -4.3, Z=6.

When the machine activates these switches it knows where it is. i.e.
2,-4.3,6. Without the reference switches the software doesn't now where the
machine is when it powers up. With the switches, you 'Ref all" as the first
operation when you power up. the machine moves until the switches are
activated, and the software now knows where the machine is.

Then, when you instruct the machine to home it goes to 0,0,0 relative to the
reference position, 2,-4.3,6

A lot of machines have the reference position at x=0,y=0. I guess that's why
the reference switches are called home switches in the mach1/2 set-up
screens.

Without the switches, you need to manually jog the machine to a position,
say 0,0,0. type 0,0,0 into the DROs, then press "REF All" The software now
knows where the machine is.

Yes, the accuracy of your reference switches will determine how accurate
your reference positioning is,

Cheers,

Peter Homann
mailto:Peter.Homann@...
Adacel Technologies Limited,
250 Bay St, BRIGHTON, 3186, AUSTRALIA
<>
Telephone +61 (3) 8530 7777, Facsimile +61 (3) 9596 2960
Mobile 0421-601 665

Bob:

Imagine turning on a machine which has a tool sitting in the middle of the
bed. If you have home switches, you can say "ref axis" and the axis will
move to home and then zero the DRO's. Or it can put any amount in the DRO's.
So if the switch is 2 inches away from limit, the DRO's can then be
programmed to read 2".
Its a handy way to make sure that 0,0,0 today is the same as every other
day. The switches do not need to be great, once hit, the axis moves off the
switch before zeroing. You can share the limits with this on some systems.

Hope this helps,
Art
www.artofcnc.ca

I thought when you homed, it was based on where you told mach2 home
was originaly, Perhaps x0, y0, z0? so what do you need the switches
for? also would the switches have to trigger precisley?

--- In mach1mach2cnc@..., "Peter Homann"
<peter.homann@a...> wrote:

The simple answer is, in normal operation home switches are meant

to be

activated. Limit switches are not.

When the machined is commanded to reference (or "home") the

machine, the

software moves the machine towards the home switches until they are
activated. The software now knows where the machine is.

The limit switches should only be activated if something is wrong

and the

machine has travelled too far. This is how your machine is wired.

Mach1/2 allows the home and limit functions to use the same

switches.

If you tell the machine to "Reference" then the software is

expecting the

switches to e activated. It therefore treats the switches as home

switches

and nudges the machine off the switch.

During normal operation the switches are treated as limit switches.

If

activated, the software stops the machine in an ESTOP operation.


So, if you want to use the referencing feature of Mach1/2 you have

two

options.

1 - Install a 2nd set of switches for the home switches.

2 - Rewire your machine so that the limit switches are not in

series with

the big red button.

Cheers,




Peter Homann
mailto:Peter.Homann@a...
Adacel Technologies Limited,
250 Bay St, BRIGHTON, 3186, AUSTRALIA
<>
Telephone +61 (3) 8530 7777, Facsimile +61 (3) 9596 2960
Mobile 0421-601 665

-----Original Message-----
From: bob_quale [mailto:Robert.Quale@c...]
Sent: Wednesday, 13 August 2003 10:38 AM
To: mach1mach2cnc@...
Subject: [mach1mach2cnc] Limit switches and home switches


I'm not sure the difference between limit and home switches. I

have

a bridgeport with limit switches, they are in series with a

mushroom

switch. If one is off, it kills the power to the power supply for
the motors, via a contactor, stopping all motion. I then have a

over

ride to jog off the switch. Where do the home switches come into
play and how do they work?

Bob



To unsubscribe from this group, send an email to:
mach1mach2cnc-unsubscribe@...



Your use of Yahoo! Groups is subject to

Bob,

I sent you a long private note, but Comcast does not like you. It returned
the note.

Bob Campbell

Hello All:

I have implemented a major change in the Macro functionallity, so the next
version has the Macro execution as a separate Windows thread (till now I
thought it was..it wasn't). It means that code such as the following will
function properly...

N = Question ("Number of Holes")
D= Question ("Diameter of hole pattern")
Z = Question ("What it the hole Depth")
A = Question ("Offset start angle")
Q = Question ("Peck Depth")
R = Question ("Rapid Plane")
F = Question ("Feed Rate")
Nc = 1
PI = 3.1415926535898
A = (A*PI)/180
An = 2*PI/N
Y = (D/2)*Sin (A)
X = (D/2)*Cos (A)
Do
While IsMoving
Wend
Code ("G91")
Code ("G00 X"&X&"Y"&Y)
Code ("G90")
Code ("G83 Z"&Z&"Q"&Q&"R"&R&"F" &F)
Code ("G80")
Y = ((D/2)*Sin (A+An*N)) - Y
X = ((D/2)*Cos (A+An*N)) - X
Nc = Nc+1
Loop While N >= Nc

(This is a users code, it is flawed (Sorry Brian) by the fact that
entering a zero strt angle will not do anything. A bit of work is needed on
the math, but you get the idea. A script like this would peck drill a series
of holes in a manifold configuration.)

This change is important in that it means the engine is still running
while the script is running. It will make it much more versatile in its use.
When a macro is encountered, the currently running program is suspended
while the macro executes. Any commands send via the macro script to the
engine are interpreted and run as they go in. When the macro exits, the
running program continues...

This is in preperation for more complex wizardry functions. Sorry for any
bugs encountered, or for any scripts it affects, but it should cure many
ill's as well. You can see the new command
IsMoving in use in the example. This function when used in the way it is
above:

Do
While IsMoving
Wend

will stop the script from adding anything more to the queue until the
previous code has finished execution. While not necessary, it will be
necessary to make sure you do not overflow the 1000 commands or so you can
put in to be executed. The Do/While statement will keep the buffer from
filling until it is empty. Used stategically, it is a valuable tool to make
a macro more stable. This combined with the new Portin Portout macro's make
it possible to control fairly complex tool changers and external devices
from a second port or IO card. With this change a macro COULD take control
forever and do a continuous movement that lasts for hours before ending and
passing control back to Mach2. Or, in the case of a toolchanger, it can
start movment, wait for the appropriate feedback from external devices and
then continue the program.

(For those Macro heads emailing me lately, let me know if you need more....)

Just a heads up. I can't release yet as I find myself in a spurt of
post-vacation productivity. Probably this weekend or earlier...

Art
www.artofcnc.ca

The simple answer is, in normal operation home switches are meant to be
activated. Limit switches are not.

When the machined is commanded to reference (or "home") the machine, the
software moves the machine towards the home switches until they are
activated. The software now knows where the machine is.

The limit switches should only be activated if something is wrong and the
machine has travelled too far. This is how your machine is wired.

Mach1/2 allows the home and limit functions to use the same switches.

If you tell the machine to "Reference" then the software is expecting the
switches to e activated. It therefore treats the switches as home switches
and nudges the machine off the switch.

During normal operation the switches are treated as limit switches. If
activated, the software stops the machine in an ESTOP operation.


So, if you want to use the referencing feature of Mach1/2 you have two
options.

1 - Install a 2nd set of switches for the home switches.

2 - Rewire your machine so that the limit switches are not in series with
the big red button.

Cheers,




Peter Homann
mailto:Peter.Homann@...
Adacel Technologies Limited,
250 Bay St, BRIGHTON, 3186, AUSTRALIA
<>
Telephone +61 (3) 8530 7777, Facsimile +61 (3) 9596 2960
Mobile 0421-601 665

I'm not sure the difference between limit and home switches. I have
a bridgeport with limit switches, they are in series with a mushroom
switch. If one is off, it kills the power to the power supply for
the motors, via a contactor, stopping all motion. I then have a over
ride to jog off the switch. Where do the home switches come into
play and how do they work?

Bob

On Tue, 12 Aug 2003 14:30:07 -0000, you wrote:

I think I may be a bit out there but I run about 2000 RPM for a
thread that small..

No your probably right, my old controller would only run at 1100 RPM
and 16ipm, but since I converted it to PC it will now do 2000RPM and
more than 100ipm! If I change the headstock bearings I can get it to
4000 but for my use it's probably not worth it.

I've been playing with the post processor tonight and reconfigured and
it suggested 2000 rpm :)

That is only about 325 FPM. That is SLOW for Carbide and you will get
a better finish at that speed. We run the SECO threading inserts and
that is what it calls for.

So the question is will it Thread at the Higher speeds? A crash at
that speed would not be good...

No I agree and haven't tried it in anger yet, until I've dry run and
seen what Mach2 thinks it's going to do with the toolpath display I'm
holding fire.

--
Steve Blackmore

Dry running Threads is a great, But every lathe I have run will not
let you just run the code without the spindle turning. I have found
the BEST way is to give a slow spindle speed of like 50 RPM to test
(This will give ample E-STOP time). Once the test is done I give the
proper Speed.

Just what I do …
Brian