[ger21]

OK, I did some testing.

Modified my macro to display the value of Var(2002), the probe trip point, and compare it to the Z axis DRO where the Z axis stops when probing.

When probing at 10ipm, the Z axis DRO reads .0035" lower than the trip point.

So a macro using the GetVar(2002) would set Z zero exactly at the top of your work, a macro using GetOEMDRO(802) would set Z zero .0035" below the surface of the work. (At 10 ipm)

The slower the probe move, the closer the values become.

At 1ipm, the deviation was less than .001".

So I guess that you could get acceptable results by substituting GetOEMDro(802) for GetVar(2002). But be aware that the results you get may not be correct, but they may be close enough.

[ger21]

Obviously the Plugin is the problem.

I was helping someone else with this same issue right a few weeks ago, and he eventually got a new plugin from the manufacturer that fixed his issue, as the suggestions from xhcchao still did not run correctly for him. Not sure if you have the same card or not, but you might want to try to get in touch with the manufacturer and check for a new plugin.

[rbraeking]

I'm sure it is the same card. There are 3 variations depending upon the number of axes. I modified the macros to work with my card. I replaced the GetVar(2002) with GetDro(802). Then I added a CallSet between each probing sequence to increase accuracy. I have the simple zero working fine. I'm looking for a location for my fixed block then will modify that macro as well.

Bob

[LouF]

Gerry I have a question I updated my VCarve Pro 7 from 6.5 will that make a difference on Mach3 with the 2010? I have noticed as posted in a different thread that I can not cut anything new that I use VCarve Pro 7 to edit or new design when I load a older file that I had cut before using VCarve Pro 6.5 they work on my machine so do older Vectric projects of the month that I edited prior using VCarve Pro 6.5?

[ger21]

Are you using a different post?
Neither the screenset nor the different version of V-Carve should make a difference.
You are either using a different post, or have some V-Carve settings different.

Email me an old program that works and a new one that doesn't.

[LouF]

Gerry can you give or PM me your Email so I can send you the files?

[ger21]

Check your Mach3 tool table, and make sure that there are no tool lengths for any of the tools.

[LouF]

Gerry no entries in the tool table.

[Foximus]

Where do I download this screenset? Sorry... new to the Mach3 Modding.

[rbraeking]

machsupport.com/software/downloads-updates/screensets/

Look for Mach3 2010

[ger21]

There's a link in my signature.

[bcer960]

Hello,

I am running the mach3 2010 screen set.
In the past two weeks I have been having this problem. I suspect it's the PC, but wanted to know if anyone else has had it, and if so how to fix it.

Randomly, Mach 3 will go into e-stop, but the probe LED will also come on and the spindle keeps running. When I hit my e-stop, the spindle will stop. No one is near the machine, and it can run for seconds, or hours before it happens. But today, I had to reset 23 times in a 6 hour period.
Simply turning Mach off doesn't re-set, I need to restart the PC.

This is very frustrating, and I would appreciate any help I can get.

Thanks
Ray

[ger21]

First thing I'd try is to go into your Mach3\xml backups folder, and find one from about a month ago and replace the current one with the old backup.

If that doesn't help, try a re-install of Mach3.

Could possibly be a noise issue too. I'd thoroughly check all of your wiring for loose connections.

[rbraeking]

I would suspect your cable between the computer and the Breakout Board. Or your pendant cable. Either can cause your symptoms. Also make sure that you have not updated Mach 3 to the latest version. Version R3.043.066 is one that works. I never update this. If it ain't broken don't fix it.

Bob

[ger21]

Also make sure that you have not updated Mach 3 to the latest version. Version R3.043.066 is one that works. I never update this. If it ain't broken don't fix it.

Did you mean to say 3.043.062?

3.043.066 is very buggy for a lot of people, and most recommend .062.

[bcer960]

I have not updated Mach in a few years, as you said, if it ain't broke..... I will check the printer cable. It sits on a shelf, and hasn't moved in a couple of years, other than maybe gets bumped every once in a while when i vacuum the shelf.

Gerry, I tried changing the mxl, and it still crashed this morning.. thanks thou.

I am thinking of getting a smooth stepper. I am wondering if the printer port is the problem. The PC did not come with one, and getting this one to work was a real bear. Any comments?

[ger21]

It's very hard to say, but if it was working before, I'd lean towards an electrical issue.

[bcer960]

well, I moved the cable, and checked both connections..... so far, it has not crashed.....
Thanks

[rbraeking]

You're correct, Gerry. .062 is the stable one. Somehow I had .066 on my simulation PC and provided bogus information. Sorry.

[rbraeking]

The cable that sends/receives from your spindle mount head back to controller may be the bad one. On my machine that is the one that does the most flexing. Although these cables are meant to flex they don't last forever.

The printer port could very well be the problem. Especially if Windows® is stealing utilities for some reason. I had serious problems with my system before adding a smoothstepper. Since they cost about the same I would go with the ethernet smoothstepper over the USB. Ethenet cables are less lossy and can be run for longer distances. The Warp9TD model is the one I use. They are working on the plugin for Mach4 if Mach4 ever goes prime time.

Bob