Hello Guest it is November 14, 2019, 09:08:59 PM

Author Topic: Shuttle v2 Mach3  (Read 6343 times)

0 Members and 1 Guest are viewing this topic.

Shuttle v2 Mach3
« on: November 14, 2011, 08:56:18 PM »
Hi
this is millguy
first time i post a question
I hook up a Shuttle v2 on Mach3 for my milling,every thing is ok
but try to program one button with custom macro #1
where is that custom macro #1 ?
How do i program it to have "Z+1
Thank
Re: Shuttle v2 Mach3
« Reply #1 on: March 30, 2013, 07:34:17 PM »
You have to create the macro.  The custom macro button calls the macro.
Re: Shuttle v2 Mach3
« Reply #2 on: March 31, 2013, 08:22:12 AM »

WHERE DO I WRITE THE''Z1.0''
IS THAT IN CONFIG/SYSTEM HOTKEYS EXTERNAL BUTTON OEM CODE
Re: Shuttle v2 Mach3
« Reply #3 on: March 31, 2013, 08:35:22 PM »
Hi,

create a macro e.g.  m1234.m1s

in your profile macro folder e.g.   C:\Mach3\macros\Mach3Mill

config plug in ( see image )

the macro may look like this

Call Code("G0 Z1")
While ismoving()
Sleep 100
Wend

be careful
when you hit the button the Z axis is going to Z0 with rapid traverse
the same when you code m1234 in MDI or within your G code.
The Z0 position depends on your coordinate system setting
( G54 G55 G56 ....  G53 G52 G92 )

the safest choice is to use a fix position in G53 ( machine coordinates )

just a thought

Alex

Re: Shuttle v2 Mach3
« Reply #4 on: June 29, 2013, 10:12:17 AM »
HI
subject:shuttlepro V2 , custom macro #1

I applied the info to the computer in my office that is not hook up to a machine tool and the shuttlepro V2 button work ok
when i applied that to the milling machine and the lathe in the garage the custom macro #1 does not work
I get in mach3 screen  ''STATUS =custom macro executed #1 and it flashed red''
in mach3 the config/general config page is all the same on the 3 computer
the office and the lathe are windows professionel and the milling is windows famely
can you hep me
thank you

MILGUY
Re: Shuttle v2 Mach3
« Reply #5 on: June 29, 2013, 10:14:06 PM »
Hi Millguy,

try calling custom macro#1  in MDI line and see if it is working.

Maybe your macro is not in the right folder.

Alex