Messages

151

General Mach Discussion / Re: Slow A-Axis motion

« on: June 05, 2008, 08:57:16 PM »

Try this:

Config>toolpath> [tick the box] Use diameter for feedrate

Then go to the Settings page and look for "rotational diameters" dro.  put in there the approx diameter.

now, it will spin the A at whatever is needed to keep the XY at 600 (dont use the 3000 or whatever for the A feedrate in the gcode)

-nick

152

VB and the development of wizards / Re: some VB questions

« on: April 20, 2008, 08:33:39 AM »

1. my macrocode runs but only if i start it manually. how can i let it run continuously when mach starts.
2. i want an extra button on a standard mach screen (lathe) to jump to my own developed screen. how can i edit de default mach screens.
3. i have a button and a button script on my own developed mach screen. but when i press the button (with my mouse) the VB buttonscript does not run?

1. name it "macropump.m1s" and put it in c:\mach\macros\mach3mill (or whatever profile folder you're using).  you then have to restart mach for it to take effect.  *edit* oops, just noticed youre using lathe, that goes in a different folder.  i dont use lathe, so i dont know what that folder is.
2.  look up "screen4" on the mach site.  thats the program that edits screens.  its located in c:\mach\screen4.  there is a movie on how to use it on the site here.
3. make sure the button is hooked to the script.  that can be set in screen4 too (make it an on-screen script or run a seperate macro).

153

FAQs / Re: Diagonal movements choppy

« on: April 02, 2008, 10:47:50 PM »

g64? (cv mode)

154

VB and the development of wizards / Re: How does the system wait for spindle reach full speed.

« on: March 27, 2008, 12:18:29 AM »

It's built in.  Mach>config>ports and pins>spindle setup (tab)>general parameters section.

155

General Mach Discussion / Re: VB Button and version R3.038 mach3

« on: March 23, 2008, 02:10:31 AM »

Brian, on the yahoo forum: "I have put Rev 3.039 online ... I have found an other error in the VB and would like to know if this will fix some of the trouble that we are seeing."

156

VB and the development of wizards / Re: Wanted: Status line

« on: March 22, 2008, 07:38:52 PM »

The answer is 'GetMessage'...

BUT

It only works in Mach3 3.036+. 

157

VB and the development of wizards / Wanted: Status line

« on: March 18, 2008, 01:09:31 PM »

Is there a VB variable to get the current 'status line'?

I mean: gcode is "g1 x1 y1 z1 (Finding)"

So I want the VB variable that would get "Finding".

thanks,
Nick

158

Screen designer tips and tutorials / Re: Act! - idea for screen design program. Extremely simple

« on: March 15, 2008, 05:32:29 PM »

I always got the feeling that is kind of what Jason is shooting for with Flash.  I know, you just said, "Flash? You're missing the point!".  This kind of Flash screen will use NO Flash on the user end, but you will just drag and drop from inside Mach.  At least thats always what I thought he meant. 

-Nick

159

VB and the development of wizards / Advice for writing a macro with SystemWaitFor (Start)

« on: March 13, 2008, 12:05:19 AM »

A word to newer macro writers (like myself)...

if you're going to use

Code: [Select]

SystemWaitFor (Start)
consider starting the macro with

Code: [Select]

dooembutton (169) 'close current file
and ending the macro with

Code: [Select]

dooembutton (170) 'open last file
This will close the current gcode file when the macro starts, and reload it when the macro ends.  This will keep you from starting the gcode program in the middle of the macro, when you press Start... NOT pretty.   

-Nick

ps- of course, you wouldnt want to use this in a macro that you call inside of a gcode routine as the macro is 'in focus'.

160

General Mach Discussion / Re: help with auto tool zero macro

« on: March 12, 2008, 11:54:05 PM »

I'd save your XML someplace safe or the desktop or whatever, just in case (although I think it should be OK, but why risk it?)

I only suggest the older version because I had weird problems with "G0 Z" when I went to 3.something (made my motor skip).  I switched back to v2.63 and everything was fine again.  I have not had the time to mess with it any more and try and figure out what the problem is... time is money!

-Nick