开云体育

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

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.

What do I do if I hit the limit switch while jogging? I can?t get
out of the e-stop condition.
I thought that if I hit the low switch, the machine stops movent to
this direction and should let me move the machine off the switch.
Does it performs this way? If yes, how can I get it work?

I am using Lim--X, HomeX (same pin); lim--Y, HomeY (same pin) and at
end of the positive way, I put the e-stop switch. Reference works
fine here.

Daniel.

Steve:

Your right, of course, I have only put in Radius programming, so the
number to enter in the correction box is the radius of the stock, plus the
guage thickness. The reason I recommend doing it this way is so the end
result gives you a DRO reading of the outside radius point of the piece. It
shouldn't matter if previous G92's happened along the way, the end result
should be anb easy acces to "zero" to the piece so that the new coordinate
is the actual coordinate of the outside or face of the stock.

As to the tooltables, you are probably correct, I have not played with
them yet as to the changes in logic needed between mill and lathe. Mill
seems very stable at this point and now I need to make the lathe specific
changes to its logic, the only one done so far, is that in lathe mode, the
tool x length offset is added to the X instaed of the Z. I have not used it
personally so it could be backwards or otherwise buggy. I will now check it
out.
Let me know how the zeroing experience goes, its the easiest method I
(with others help) could come up with to easily zero to the face and radisu
of lathe stock. If you have a better idea, feel free to discuss it here, I
have no problem changing it to conform to easier methods, but I have to
conform to multiple usage patterns and mutiple patterns of G92 and fixture
usage. The "correction" DRO seemed the most logical.

Don't worry about the numbers that appear in the offsets when zeroing,
they are simply the additive numbers required to create your requested zero
point when all offsets are considered.

I WILL fix the tool offsets though. Should they be , in lathe, a positive
length which is added to the X (so the DRO reads the proper distance away
from zero when retooling) or a negative number which is subtracted to get
the same end result?

Thanks,
Art
www.artofcnc.ca

Hello all,

Today I kill a 1 by 0.5 mts aluminum sheet...

I had backup my files some time ago and today I get it from the CD.
Well, XP change the properties of the tap file to read only (this is
normal).

So, Mach2 opened the file and executed it. While it was doing G0 and
G1 it ran OK, but it was jumping the G2 and G3 commands and doing
the G1s...

I just set the properties to normal file and ran it again, same
file, no problem here.


I didn?t make more tests, but be carefull with read only files...

Rgrds,
Daniel.

Hi Art

There appears to be a problem with tool offsets and also maybe your
instructions for setting up work offsets.

Using your example

Put in a piece of stock. Jog to the edge, If the stock is 30mms thick, type
30 into the Touch Correction box and turn it on. The LED shoudl flash. Now
press Touch X on the Fixture offsets at the bottom. Does the display on X
now read 30?

That will put the outside of the stock at +30 (diameter of 60) - it
should be +15 (diameter of 30) shouldn't it?

Either way - the tool offsets in X seem to be confused (or I do ;).

I set up a piece of bar and with tool 0 I faced it, zero'd Z then
turned a bit off the diameter and zero'd X. I then jogged away and put
in tool 1. Jogged in until the tool just touched the end, noted the
reading and entered that in the Z offset. Did the same on diameter and
entered that in X offset.

Now when I run my tcollet file, the Z axis appeared to be ok, but the
X axis missed the job completely.

The Z axis may NOT have been ok as there is very little difference
between tool 0 and tool 1 in X, but tool 1 is 10mm longer

Do I have to reverse the signs of the offsets as I did with the old
controller?

ie if X read +10.74 on tool 1, I enter -10.74 in tool table.

--
Steve Blackmore

Steve:

The "jog not on all screens" was a user request from some people who feel
the opposite. They despise having a Jog on an MDI screen, so your right,
they are pretty much identical. Its like a safety screen so you don't hit an
arrow key by mistake.

There are some controls missing as well, regen is probably one of them.

The zero'ing is because there are a few ways to zero, in one method (diag)
G92 is performed, this sets the axis offset, on another screen a G54 is
performed to set an origin offset and it is also possibel to use a tool
offset. All three will zero the display and have slightly differetn effects,
I need to consolidate the design so only G92's are used for zero'ing and the
part and tool offsets are used for zeroing to a piece of stock.

Thanks,
Art
www.artofcnc.ca

On Fri, 15 Aug 2003 09:25:02 -0300, you wrote:

Thanks for the tests. Let me know what you find on the spindle.

Nothing yet - still playing

As to the distorion, does hitting regen do any good. Regen was put in so
that if offsets are added that are not in the actual G-Code, but applied
after loading, the regen'ed display will match the offsets.

There doesn't appear to be one off those in Lathe (or I can't find it)

Something else odd, zero X or Z on jog screen zero's dro, but puts
whatever is in there in part X or Z box, on diag screen it does as I
expect and zeros DRO without sticking anything anywhere.

A goto 0,0 would be useful somewhere too. IF I get chance I may have a
play with screen designer this evening. I have also found jog doesn't
work on all screens either?

To me it seems that MDI and jog screens are almost identical, the MDI
screen could go if an MDI box was put on Jog screen - as it stands to
me the MDI screen is useless without jog capability as well.

I find myself jumping between, jog, toolpath and diags all the time
for the different bits I need.

--
Steve Blackmore

Jerry:

Good idea. I will try to change the display code to display the actual JOG
rate from the percentage calculation. Its now on the list. (Which is
shrinking...thank god...)

Art
www.artofcnc.ca

Hi Art
As I use Mach2 more, (both Mill and Turn), I often find myself making
simple short cuts semi-automatically by using jog buttons.
The problem is that without notes, or a good memory, or a quick
calculation, ( I can't find any of these), I don't know what
a "percentage jog" relates to in inches per minute.
Therefore I think it would be a good idea to change that display from
percentage jog, to jog speed. Whatthink?

Jerry

Mark:

Thanks, I did miss this one. I will look into removing the softlimit
warning. Also, there never was a box to set the distance from the switch,
but if you set the debounce interval higher, this will cause the ais to move
further off the switch when it de-ref's after homing. I'm still looking into
a way to set a distance.

thanks,
Art
www.artofcnc.ca

Steve:

Thanks for the tests. Let me know what you find on the spindle.

As to the distorion, does hitting regen do any good. Regen was put in so
that if offsets are added that are not in the actual G-Code, but applied
after loading, the regen'ed display will match the offsets.
This is a difficult thing to take care of as the display has got to
display offsets in the file, but when offsets are applied after the display
is generated, then the display has no way of knowing this. I could
auto-regen, but I thought that may hurt someone with long files as the regen
time can be long on a slow machine and a long file.

Thanks,
Art
www.artofcnc.ca

Ouch!!!!

Art
www.artofcnc.ca

On Fri, 15 Aug 2003 11:37:34 -0000, you wrote:

No chance you have photos of the event? <:-)

No - but my neighbour is now sulking after hearing the language <G>

I'm going back out in a minute to check my tool offsets again and then
test run some blank collets off all being well. I put a new blade in
the parting tool so it needs re-setting.

There's only two outstanding things now I think (apart from threading
which I may try later - gulp) neither of which are show stoppers.

One is display is distorted if tools have offsets - minor detail.

The other is slightly more serious, but I think maybe the problem is
at my end, I'm getting a slow down or speed up of the spindle when the
steppers move (it's depends on which way they go).

I think it may be down to something limiting current or voltage, I'll
have to check all the values of the components on my board - it's
quite possible I've put a wrong resistor in somewhere :)

--
Steve Blackmore

No chance you have photos of the event? <:-)

--- In mach1mach2cnc@..., Steve Blackmore <steve@p...>
wrote:

Hi Art, re-downloaded RC10, removed all traces of old version
including XML files and re-installed. Now working.

I'm wondering if it was because I'd saved the old xml?

Manually re-input everything and it now seems ok.

Go figure :(

Also managed to get myself a nice burn and a sore elbow when I

touched

a 10000uF capacitor that still had 240V in it !! The burn is on my
finger, the sore elbow was a result of the reaction and smashing it
into the lathe stand :/

--
Steve Blackmore

Hi Art, re-downloaded RC10, removed all traces of old version
including XML files and re-installed. Now working.

I'm wondering if it was because I'd saved the old xml?

Manually re-input everything and it now seems ok.

Go figure :(

Also managed to get myself a nice burn and a sore elbow when I touched
a 10000uF capacitor that still had 240V in it !! The burn is on my
finger, the sore elbow was a result of the reaction and smashing it
into the lathe stand :/

--
Steve Blackmore

--- In mach1mach2cnc@..., "rmtuckeruk" <mrtucker@l...>
wrote:

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 ref
switches so the machine did not sit on the switch.

Mark

Art
Don,t know if you missed this one or you just so busy you didn't
notice.Any help would be appreciated.

Mark

On Thu, 14 Aug 2003 22:56:13 -0300, you wrote:

The error is from the macro threader. Part of the new code. It is saying
that for some reason your macro facility is not initializing in that file.
Perhaps its being called from within a macro or something. Doe shti sonly
happen on some files.

Nope - Any file as long as it's the first file of a session. Just
tried loading several files, after it has happened, it doesn't do it
again until after a restart of Mach2.

I have run your file several times and cannot repeat this reversal. Let
me understand this, you start the program and the spindle pin is high (low
active but spindle is off). Then you type M3 and the spindle pin goes low.
type M4 and the spindle goes high again. But when you load the program, the
pin changes to low, but the diags page shows no flashing?

Is this accurate...??

Yes,but reversed and it's M4 for counterclockwise and M5 for off.

Start program, pin 6 extern1 is low (high active)
Type M4 pin 6 goes high, spindle runs if speed set (pin 9 step out),
extern1 led flashes as does spindle on led

Type M5 pin 6 goes low, spindle stops, extern 1 led & spindle led off

Load Gcode file, pin 6 goes high, no led's light
(spindle doesn't turn initially as no steps being sent from step pin 9
until program runs)

Run GCode on M4 pin 6 now goes low and led's flash.
(spindle doesn't turn, although steps being sent on pin 9 it also
needs pin 6 high).

--
Steve Blackmore

It surely can't be true that the eastcoast blackouts are caused by too many Mach2 users running at once?

John Prentice :=)

Hi:

Is anyone else getting an Script Init Error when loading files in RC10?

Just trying to track one of the nasty ones. I really want this
multi-threading of the Macro's to work out, it seems the perfect way to do
canned cycles. I will be able to create each canned cycle as a macro written
in VB so changing Cycles and having wizards will be much easier.

Thanks,
Art
www.artofcnc.ca

Todd:

I think what your seeing is the zero ( or whatever you have in the
corrections page under home switch position) being set into the DRO for that
axis, MINUS whatever offset you have active. When you zero all or type a
number in an axis, you are executing a g92. For example, if you are at a z
of 10, and zero all, then you have set a G92Z0 into the system, which will
give you a z of 0. Now, when you command the G28.1Z0 , the Z will home, set
itself to zero and promptly display -10.0 as you have a G92 set to 10 for
the Z axis. Typing a G92.1 to remove the G92 offset system will now display
zero.
If you have a home switch setting of 5 on the corrections tab and hit
G28.1z0, then the Z will have 5 put in it when it comes off the switch,
MINUS 10 which is still in the G92 registers. You can see this in the Axis
Offset DRO's on the diags page. Each time you "zero", you are really only
changeing the axis offset to get a zero readout. G92.1 will undo zeroing in
this way. By not using the G92.1, the G28.1 can be used as a verify
proceedure. If you zero at a z of 15 , for example, then perform a G28.1z1,
followed by a g0z0, you should end up where you started. In other words, the
DRO readout after a g28.1 will be the distance from where you had your zero
last set.

This is a mach2 thing, where all coordinate systems are respected and
reversable. Try putting a
G28.1z1 G92.1 as your control line. It should give you the right reading at
that point. (0.00) This is different than Mach1 which did not respect the
coordinate systems properly.

This may seem more complex, but in reality it makes better sense. After
all, you can't really "zero" an axis, the interpreter MUST know where it is
in relation to the home switches, so it does so by keeping track of the G92
offsets and the origin offsets, and the tool offsets. All three go into
making up the DRO reading depending on your DRO mode. This is kinda related
to your extremae question.

I know this is confusing, so let me know if I explained it badly.
Thanks,
Art
www.artofcnc.ca

Todd:

Sorry about that , I will check the code again on G28.1

The extremea seems to work for me. Remember the extrema numbers are in
machine absolute coordinates. This means if you jog to X10, then zero, when
loading the file, the interpreter will see all movements being from your
zero, so the extrema, which lists the machine coordinates max and min, will
have 10 added to min and to max. This makes the number appear to change, but
they should as the actual machine coordinates will change during that run.
Hitting regen after zero'ing will display the new extrema. Its easy this
way to see if you will go over your limits. If you have a negative number in
any min, you will pass the limits of your machine. If you have a max larger
than your table size, the same will occur on the other side.

I will let you know on the G28.1.
Thanks,
Art
www.artofcnc.ca