Mach2 Demo

[Enos Shenk]

What exactly does Mach2 do when it wont process any more code as a result of running a demo version?

I was running a part on my taig with mach2 demo, and everything was going just fine. Until about halfway through on a normal G01 move, mach2 showed the toolpath going off into orbit to the right for some reason, my motor control beeped at me and shut my machine off. I checked over my code, and my dimensions are absolutely not anywhere near it was trying to go (something like 5 inches right).

I was confused and hit the goto z's button and somehow my home position had been reset to an equally insane position about 6 inches left, i managed to hit mach2's reset button about half an inch before my mill table ran off the ways.

Is this normal behavior? I assumed if mach2 reached the limit of code it would let you run it would simply stop. Im pretty sure this program isnt even near 1000 lines total, let alone halfway through. But judging by mach2 resetting my positions and all that, im curious if the blame lies with the software.


Also on another note is there ANY way to squish the mach2 interface smaller? The only machine i have available to run my machine is an old gateway laptop, which has a native resolution of 800x600. Im forced to use that horribly annoying over-resolution mode where you pan the virutal screen around.

[JFettig]

I have not personally seen what it does at the end of 1000 lines,
The goto z's button will make it go to a specified spot, default its somewhere like 3" above g53 z0(most home locations) Its in the settings page.

It would be a good idea to put a screw or something in the way of letting your machine travel off of its ways.
At first I was having troubles getting things to work right, eventually I figured everything out. If your doing tool changes, make sure to use your G43 H# offset(# is your tool number)
When I change a lot of settings, or even one, I always exit the program and make sure it saves, then it should be good even if something weird ends up happening afterwards.

Jon

[buscht]

Enos Shenk, you should be able to do a line count on your CNC program by calling it up in Microsoft word. Line count is an option in that program. Or change your post to insert line numbers.

I don't know what happens when Mach 2 hits the 1000 line limit. Sorry.

Also, if you are running on an old computer, you might want to try TurboCNC instead.
http://www.dakeng.com/

[Enos Shenk]

Im honestly baffled. As far as i can tell from eyeing the code (admittedly im not THAT great) and running it through a neat little freeware CNC simulator package, my code is fine.

But in the preview box in mach2 when i load the program, at that point in my program it shows the blue toolpath line heading off into no mans land. Its not even a real position as far as i can tell, panning around in the window you can never see the end of the toolpath. It literally seems to be trying to move to infinity. When i run the simulate option in mach2, it reaches that point and basically considers it the end of the program, even though its about the halfway point in the entire program. Its around line 183, so that rules out the demo restriction getting in the way.

Im really really avoiding using any other control software. Im not too keen at all on using dos in this day and age. I definately like mach2, its just problems like this make me nervous about the software freaking out and messing things up.

[ynneb]

Load the code into Mach2 and view it in the tool path display. If you see the complete picture along with the tool returning to zero then the code is less than 1000 lines.
If you only see part of the path then you will know you have exceded the 1000lines.

On top of this, do an air cut first , so as to physically verify its all ok.

If you are doing 2d cutting then you will get an amazing amount of cutting done within the limit. 3d work....4get it.

About your stopping problem at line 183, this could be the fault of your post processor in your CAM program. Mach2 probably doesnt reconise that part of the code.

[Enos Shenk]

I wrote this program by hand, i havent found any CAM software that im actually happy with.

Most definately the entire program is not being displayed. But its also most definately nowhere near 1000 lines of code, the entire program is only 300 some lines, and everything past 183 or so is being ignored.

Im thinking its just the demo limit kicking in, but it would be nice if it would process the advertised 1000 or so lines, as opposed to 180 some.

[ynneb]

Maybe you should try the latest version on Mach3 and not use mach2.

Im thinking its just the demo limit kicking in, but it would be nice if it would process the advertised 1000 or so lines, as opposed to 180 some.

I think you would be hard pressed to find anyone to speak out against Art, ( The program writer) for deliberately trying to misslead anyone. I am sure it is just a simple problem, and not a case of midnight skull duggery and deception

You could try asking Art himself in this forum http://groupyahoo.com/group/mach1mach2cnc/

[mark c]

Could you post the section of code (say lines 170-200) so we can look at it?
By the way motion will stop at the limit of 1000 lines. Thats what prompted me to get off my butt & pay Art for it

[ger21]

If you're code is more than 1000 lines, the display will not show anything past 1000 lines, and it will stop at 1000. If the toolpath display is going off the screen, it's a problem with your g-code.

[joecnc2006]

When i Used the program in demo mode befor ei bought it, it DOES go all the way to 1,000 lines, it must be something you put inside the file you wrote, I never had that problem with any code i ran (which was several), I would sujest to post the g-code so we can check it out for you.

Joe

[JFettig]

It could be a bad character, like a GO instead of a G0, it has happened to me. when you load your file, watch the bottom near the buttons, sometimes it will say something about it.

Its something to check for.

Jon

[Enos Shenk]

One of these days ill learn not to open my mouth.

I had removed some lines fixing things up and accidently deleted a G40, so the problem was compensation being called one, then again when it was already on.

I guess im just not used to having one program saying everything is fine, and mach saying it isnt. Really threw me off there.

Thanks for all the help, ive got this problem worked out i think (just this one, still need to figure out why the cutter comp gets shut off later and ends up plunging into the material)