Hello Guest it is March 28, 2024, 10:04:33 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 - Greolt

131
General Mach Discussion / Re: 2 stage homing script
« on: August 15, 2011, 06:13:01 AM »
RefCombination command will do that.

Right now I can not get the Mach3 Wiki page to load for some reason.  That has info on using this command.

Greg

PS:  The following is from the Mach3 Macro Reference Manual PDF

RefCombination 
Sub RefCombination(Axes As Integer)
 
This function allows any combination of axes to be simultaneously referenced (homed). 
Which axes will be referenced is determined by the Axes argument, which is a bit-
mapped variable, with the bits mapped as defined below.
 
Arguments:
Axes is a bit-mapped value the defines which axes are to be referenced.  The
value of Axes can be calculated by adding the values corresponding to the
individual axes to be referenced.   The axis values are:
 
 X = 1
 Y = 2
 Z = 4
 A = 8
 B = 16
 C = 32
 
So, for example, to reference the X, Z and B axes, Axes = 1 + 4 + 16 = 21.
Return Value:
 None
Example:
‘ Define some constants
RefX = 1
RefY = 2
RefZ = 4
RefZ = 8
RefB = 16
RefC = 32
‘ Reference Y, Z and C axes
RefCombination(RefY + RefZ + RefC)

132
General Mach Discussion / Re: 2 stage homing script
« on: August 15, 2011, 05:01:55 AM »
Try this,

SetParam ("YRefPer",100)
DoOEMButton (1023)  'home at 100%
While IsMoving()
Wend
Code "G53 Y5"  'move off switch 5mm
While IsMoving()
Wend
SetParam ("YRefPer",5)
Sleep 200
DoOEMButton (1023)  'home at 5%
While IsMoving()
Wend
SetParam ("YRefPer",100)


This is for the Y axis,   you will need to write similar for other axis.

Greg

133
General Mach Discussion / Re: 4th axis setup
« on: June 21, 2011, 06:48:22 PM »
Here is a copy of an explanation I wrote somewhere else,

====================================================================================

All axis move in units per min.   With a rotary axis those units are degrees. 

So what is 60 ipm on the linear axis (desired speed of the tool in the work), is 60 degrees per min for the rotary.

That 60 degrees per min angular feedrate will make the tool move through the work at a speed dependant on the distance the tool is away from the centre of rotation. (in your case, very slowly)

So Mach has a feature to compensate the rotary axis feedrate, to accommodate differing radius that the tool is cutting at.

It is activated via the Toolpath Setup menu.   Check "Use Radius for Feedrate"  All the other settings in this box are to do with the toolpath display window.

On the Settings page there are three DROs labelled "Rotation Radius".  IMO they would be better labelled "Rotation Radius Offset"

They are to tell Mach the distance that the relevant axis origin (Z in this case) is offset from the centre of rotation.  (A axis in this case)

So if you are machining on the outer surface of a 10 unit diameter job and Z axis origin (zero) is set on that outer surface, then the correct value for the "Rotation Radius Offset" DRO is 5.  The distance that Z origin is OFFSET from centre of rotation.

If, on the other hand, the Z axis origin is at the centre of rotation (my preferred method for most jobs) then the correct value for "Rotation Radius Offset" DRO is zero.  The distance that Z origin is OFFSET from centre of rotation is zero.

Mach takes the Z axis DRO value and the "Rotation Offset Radius" DRO value and adds them together to ascertain at what radius the tool is cutting at any one time.  Then compensates the angular feedrate to have the tool move through the material at the desired speed.

Maximum velocity as set in motor tuning is honoured, so that will always be the upper feedrate limit.

Now there is one little "Gotcha".   A zero value in the "Rotation Radius Offset" DRO will automatically disable the entire feedrate compensation feature.  This is a known bug and is being addressed by Artsoft at this time.  Hopefully it will be fixed soon.

The workaround for this, is to use a very small value (eg. 0.001) in the "Rotation Radius Offset" DRO when zero is the correct and desired value.  Small enough to have no measurable effect on feedrate, but not zero.

===========================================================================================

The last bit about the zero value disabling the feature has been mostly fixed in the dev version, but does apply to the lockdown version.

Hope this is of some help.

Greg

134
General Mach Discussion / Re: 4th axis setup
« on: June 21, 2011, 05:57:39 AM »
Sorry for slow reply.   Elderly Mother is in hospital for emergency heart operation.


The documentation as far as I can find is scant.  The web site includes the following,

Using Mach3 Mill pdf for version 1.84+.
Section 6.2.2.7 mentions "Diameter/Radius correction" but it is vague and does
not explain its use. No explanation that this is an offset value.

Mach3 Install and Config Guide pdf
Has no mention of this feature.

Greg

135
General Mach Discussion / Re: 4th axis setup
« on: June 16, 2011, 12:32:07 AM »
It always uses both values.  Adds them together.

Greg

136
General Mach Discussion / Re: 4th axis setup
« on: June 15, 2011, 11:51:29 PM »
OK COOL but if it runs from the Z height what is the DRO for ?? I'll have to do some testing next week.


It is needed if Z axis origin is not at the centre of rotation.  So in effect it is an offset value.

Greg

137
General Mach Discussion / Re: 4th axis setup
« on: June 15, 2011, 11:44:44 PM »
Yes.

It gives the called for feedrate of the tool through the material at any given radius.  Within certain constraints.

Ascertains the radius by taking the value of the Z axis DRO, together with the  "Rotation Radius" DRO.  (IMO this DRO could be better named)

Greg

138
General Mach Discussion / Re: 4th axis setup
« on: June 15, 2011, 11:11:08 PM »
Now an interesting side bit.Long ago I did play with a macro to monitor the Z height and apply a FRO based on Z height above the A. That was before Brains and the macro was a bit slow. BUT it did help.

Might be time for someone to try a Brain or a plugin.

You could base it on IF A & XorY are moving then Zheight x PIE =area.  That might be able to help adjust the FRO to speed up the comp in 3d moves.

Hopefully Ver 4 will properly adress the issues. (;-)


Unless I am having a bad day and completely miss the intent of what you are saying, this feature already exists in Mach3.

It is often referred to as  "Use Radius for Feedrate".   The calculations were all wrong for a long time, but were fixed Christmas before last, and now works great for me.

Greg

139
I use the sset format with my screens all the time with the following,

ToggleScreens()

There is some info here,

http://www.machsupport.com/MachCustomizeWiki/index.php?title=Mach_specific_Subroutines/Functions_grouped_by_purpose

However I think I'll try the Button code number that TP pointed to.  Thanks TP.

Greg

140
Modbus / Re: Hitachi X200
« on: June 03, 2011, 10:20:28 PM »
If anyone else is as tight fisted as I am, then these can be had on ebay for a few dollars.

Example,

http://cgi.ebay.com/RS232-RS485-1-2KM-Data-Interface-Adapter-Converter-/260758890393?pt=LH_DefaultDomain_0&hash=item3cb670e799

Greg