Messages

161

General Mach Discussion / Re: G31 issue

« on: February 20, 2013, 09:06:47 PM »

Here's something a little wierd.  When I put the following code in a macropump, I can't scroll the code window.  Every time the code executes, the code window rewinds back to the top.  I tested by putting a sleep(5000) after the code and I could scroll for 5 seconds, but as soon at the code executed, it rewound to the top.

I ended up putting the code in a macro, then call the macro at the beginning of the program.

code "#1 =" & getUserDRO(1510)
code "#2 =" & getUserDRO(1508)
code "#3 =" & getUserDRO(1551)
code "#4 =" & getUserDRO(1520)
code "#5 =" & getUserDRO(1561)
code "#6 =" & getUserDRO(1570)
code "#7 =" & getOEMDRO(54)   
code "#8 =" & getUserDRO(1512)

162

General Mach Discussion / Re: G31 issue

« on: February 20, 2013, 08:53:02 PM »

No.  I didn't try RR but RFH fails when it does the simulation.  G28.1 seems to work with everything so I think that's the way I'll go.  I don't think we'll miss Z homing.  I'll just change the Ref All button to ref only the X and Y.

163

General Mach Discussion / Re: G31 issue

« on: February 20, 2013, 01:04:02 PM »

Might try G28.1.  We didn't go that route originally because of G68 issues, but I understand that this has been corrected.

164

General Mach Discussion / Re: G31 issue

« on: February 20, 2013, 01:02:44 PM »

I've decided to take G31 out of the macro and back to GCode.  The reason I had it in a macro is because we had a lot of the parameters used in the G31 set on the machine by the operator.  I'm doing the same thing by putting the G31 back in Gcode but using variables.  I set the variables equal to screen DRO's in a macropump.  I haven't looked to see if that could be done in a brain.

So far, it seems to be working very well.

165

General Mach Discussion / Re: G31 issue

« on: February 20, 2013, 10:27:28 AM »

I'm not sure we're talking about the same issue.  That thread seems to focus on 3D edge probing.  This is a plasma machine.  What's happening is that Mach will randomly ignore the probe input (even though it is active) and crash.  We have 3 machines set up with the same profiles, screensets, PC disc image, plasma power supply....These are identical machines down to the last wiring connector.  Two of them run without a hitch.  The third will run the TOM routine 2 or 3 times then crash o the G31.

I noticed that the thread you posted goes back to 2007.  Has anything transpired since then?  We've always used G31 but maybe G28 would be more reliable.  I forget the limitations, but I recall that G28 also had some sort of issue. 

166

General Mach Discussion / G31 issue

« on: February 19, 2013, 11:34:56 PM »

Has anyone ever had an issue where G31 ignored the digitize input?  Basically, the G31 is inside a macro and works a few times, then the G31 will initiate, the Z travels down, the digitize signal goes active, but the Z keeps going and crashes.  It seems to be a random thing.  There are no errors or warning in Mach3.  It acts as if the digitize signal is being ignored.

Any thoughts on the issie would be greatly appreciated.

Thanks

167

General Mach Discussion / Re: THC problems

« on: February 17, 2013, 04:13:52 PM »

If everything in Mach3 is correct then the wiring to the relay is wrong or the relay is bad.  Is the relay built into a BOB or is it separate?  What are you using for a BOB?  If the realy is built into the BOB then it's most likely a pin assignment issue.

Regarding the Hypertherm interface cable, Green/Black = Torch on/off, Red/Black = ArcOK, White/Black = Divided arc voltage.  We've had a number of interface cables come in recently that were wired wrong and had to remove the pins and put them in the correct place.

168

General Mach Discussion / Re: THC problems

« on: February 17, 2013, 10:29:07 AM »

AcrOK will not effect the torch firing, but it will prevent movement if there is no signal present.  In order to fire the torch, you need to drive a normally open relay from whatever output you are using on your BOB, then connect the THC torch on eds to the relay.

Can't the guy you bought the THC from help you with the Mach3 setup?

169

General Mach Discussion / Re: Cryptic Error Message....

« on: January 30, 2013, 10:36:47 PM »

Here's a little more info.  The error seems to be happening during a macro run that does a G31 Z-2.  It works 3 or 4 times, then fails.  When it fails, the probe trigger is ignored, the Z goes to -2 and stops.  Last time it did it, the next M code (M03) executed, but since the torch was bottomed out, it failed to light anyway.

I can execute this M code all day long in MDI and it will never fail.  It only fails during a program run.

I don't mind setting up another PC, but I'd like to know if this could be caused by something externally or if it is definitely a PC issue.

Thanks

170

General Mach Discussion / Cryptic Error Message....

« on: January 30, 2013, 05:14:34 PM »

All of a sudden we're getting the following error message.....

Error on line: ********* ‐ Application defined or object defined error

Has anyone seen this?  It seems to be happening inside a macro that has a few While isMoving() statements.  It doesn't happen all the time.  Usually after the 3rd or 4th time the macro runs.  This is on a fresh install of Mach3 on a clean XP computer.  Wiped the HD, installed windows and installed Mach3.  We set this PC up to replace one that was randomly scaling parts for no reason.    My instinct tells me that this has to be PC related because we run the same code on many PC's.

Any ideas?

Thanks