Messages

11

General Mach Discussion / Re: Settings

« on: February 23, 2008, 11:28:51 AM »

Thanks, I'll try it in a bit.
I did find my previous post and the replies then were to uncheck the copy G54 from ? on startup. I'll look at that too.
LEW

12

General Mach Discussion / Settings

« on: February 23, 2008, 11:15:36 AM »

Hi All:
I'm pleased to report that my retrofit using Mach works just great.
I've posted this question before but forget what the replies were.
What settings do I need to incorporate so that Mach remembers the DRO numbers when I last quit the program?
Thanks in advance.
Lew

13

General Mach Discussion / Re: Question regarding wav files

« on: August 02, 2007, 11:08:49 PM »

Thanks a million Brett.
I just saved it in the correct profile and it works. Simply awesome. So glad this forum and guys like you exist. Now I'm gonna have a blast. It's truly great to have so much functionality in this one package.
LEW

14

General Mach Discussion / Re: Question regarding wav files

« on: August 02, 2007, 10:54:28 PM »

Acutally, no.
I have only saved it in the directory "macros" under "mach".
I'll have a look and see if that does it.
Oh, I did try it from the mdi and it did not work there either.
I'll see about saving it in the profile directory.
Thanks
LEW

15

General Mach Discussion / Re: Question regarding wav files

« on: August 02, 2007, 10:34:26 PM »

Thanks Brett:
I just tried it also. Using the VB editor in Mach and I had to chuckle, it worked pretty good. It uses the built in voice reader which I'll probably change later. For now, though, while it works in the VB editor it does not work from the Gcode file. I didn't try it from the mdi screen but I ran the gcode file a number of times and it does not work. The syntax I used is exactly as typed in my previous email with this one exception. I noticed that I used a lower case "m" in the macro call. m90000. And I saved the file with an upper case "M". So, I changed the lower case "m" in the gcode to an upper case "M". But to no avail. Still confused.
It is pretty cool though.
Oh, I added some typed lines when I heard it work from the VB editor. None too flattering I might add. And, sure enough, it voiced exactly what I typed.
LEW

16

General Mach Discussion / Re: Question regarding wav files

« on: August 02, 2007, 10:10:34 PM »

Guys, thanks for the replies.
Here's what I've done so far.
I've made sure the speakers work.
I've made a simple Gcode file like this:
;program to test speech
g90
g0 x1.0 y1.0
m90000   ;this is the macro call. In the manual it explains that end users can use m90000 thru m99999 with no fear of overlapping assigned mcodes.
m01
g0 x0.0 y0.0
m30

I created a macro file with the extension ".m1s" I used the letter L between the "m" and "s"  first and saw that the extension is acutally the number 1 and not an L. I named it m90000.m1s
I put that file in the "macro" directory under the "Mach" directory as instructed in tne manual.
The macro file reads like this:
speak("change the part")

When I run the Gcode it runs through to the m01 and pauses but no audible.
I hit the run key and it finishes the program and sets it back at the start.
Sorry, for being so persistant about this. Just that I have the time now and it's beginning to crank me off a bit that I can't figure it out.
I'm sure I'm doing something wrong  - that's the case usually. But, that's just me. I don't like to back away unsuccessfully.
It's a good suggestion to use the vb editor to examine the file. I'll do that in a short bit.
Thanks again for being patient.
LEW

17

General Mach Discussion / Re: Question regarding wav files

« on: August 02, 2007, 01:17:47 PM »

Thanks again Brian. I guess I'm having difficulty seeing that I can type the word speak and then type ("say this") in a file and save it with a "mls" extension. Then call that file with an mcode in a gcode program and have the computer read what I've typed and convert it to sound.?
OK I'm a little low on the learning curve with this one but is what I've described correct? Or, do I have to set something else up so that my typed message can be audiblized? I do have speach toggled on in the general config. screen.
By the way I did just what was described but no sound.
Thanks for your patience.
LEW

18

General Mach Discussion / Re: Question regarding wav files

« on: August 01, 2007, 08:42:24 PM »

Thanks, Brian.
I wonder if you could show me what the exact syntax would be for the speak command in a gcode program. Or, is that actually the correct syntax which you posted?
LEW

19

General Mach Discussion / Question regarding wav files

« on: July 31, 2007, 08:49:55 PM »

Hi All:
I only read briefly the M-code calling of a macro. I was wondering if anyone has any suggestions or if it's possible to call a wav or other sound file using an M code in a program and making the macro somehow refer to the wav file?
Just thinking "out loud" here. I can see where it might be helpful if I can call a sound file at a program pause that says something like "change the part".
I know I posted something like this before but didn't figure on the possibiliity of using a macro.
Thanks
LEW

20

General Mach Discussion / Re: Cutter comp

« on: July 06, 2007, 10:52:54 PM »

Hi Bear:
The way I understand it, the M6 command when encountered in a g-code file signifies a tool change. The T command and the integer after it signifies which tool is installed. The tool info comes from the tool table which is entered previously from the config. menu. Once the software goes through these two commands, it knows what tool is in the spindle and subsequently makes offset calculations based on this info. If T8 is a 1/2" end mill then cutter comp takes into consideration the diameter of the tool and either offsets the toolpath to the left with a G41 or to the right with a G42. Left and right correspond to whatever direction the cut is progressing.
That's my understanding. My glitch is that on first startup and running of a program with cutter comp., the tool does not seem to get recognized and consequently no cutter comp. is built in. The toolpath if left alone will create a cut that is wrong. For whatever reason, if I restart the program the tool gets recognized and the toolpath works just fine.
LEW