Messages

2201

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: May 05, 2014, 12:13:08 PM »

Mach4 does not want to run the older Mach3 complex subs. It stalls and or cannot display the proper toolpath. I have examples of some that RUN fine in mach3 but not mach4 IF needed.

Also Mach4 does not want to run older fanuc macros that LOOK like it should run fine in Mach4 .

(;-) TP

2202

Mach4 General Discussion / Re: Lua Editor Crashing

« on: May 05, 2014, 11:59:27 AM »

That happened a LOT in the early versions have not seen it lately.  Lua is very sensistive to a rock head like me telling it to do things that it does not understand(;-). Made good sense to me BUT LUA did not have a sense of HUMOR ?

(;-) TP

2203

General Mach Discussion / Re: Current Hi/Lo setting?

« on: May 05, 2014, 11:54:18 AM »

I believe the "CurrentHigh/low is a signal that SHOWS when ANY axis is moving OR not moving. I used it for the lube pump signal. As long as it was ON the pump timer ran  IF it was just setting looking pretty the Pump timer did NOT run OR pump oil all over the floor(;-).

(;-) TP

2204

General Mach Discussion / Re: probe guard

« on: May 05, 2014, 11:44:10 AM »

HIYA Ian , Come on over I have a spare room here. The neighbors are already used to a smartA## redneck so you will fit in nicely. You will probably have to get a decent tan thought (;-)

So far the Protected move mode is working here. Probably NOT going to see it in Mach4 either. They looked at me like a crazy man when I asked for it so YOUR Solution could be a blessing to probers.

I had also asked for a solution for missed hits to create an error  and signalling the OP to a problem.  This would be a BIG help as I see it.  MOST problems in probing is missed trips creating BAD data.  A lot of the people I have helped with 3d probing could use it. It is HARD on them when I point out the proble with their point cloud is all the MISSED trips in the point cloud.  After LONG 12hr probing runs they tend to get pissed that the cloud is trash and unusable for the most part and have to start over.

ANY solutions for a missed trip notification  AND a error trapping code in the Program does not help as MOST of my/our routines are GCODE based (very dependable) and there is no IF in that code and no access to Systems #vars to compare to.

Just a thought,(;-) TP

2205

Mach4 General Discussion / Re: Mach4 Probing and reporting

« on: May 04, 2014, 06:32:02 PM »

HIYA Dave , NO offense taken (;-) We live in very different worlds.  DID you read the part about it being an option (;-)

(;-) TP

2206

General Mach Discussion / Re: probe guard

« on: May 04, 2014, 04:59:51 PM »

(;-) You do not sell used cars in your spare time do ya ??

(;-) TP

2207

General Mach Discussion / Re: probe guard

« on: May 04, 2014, 01:05:37 PM »

OK I am confused HOW is it to know wether it is a GOOD trip or a BAD trip. Do you turn it ON/OFF when needed like protected movemode on commercial controllers or

(;-) TP

2208

Mach4 General Discussion / Re: M4 screen set with user selectable 1 to 4 tool path views

« on: May 04, 2014, 01:01:18 PM »

Thanks Steve, SO would it be possible to release the LPT driver for further testing ?

(;-) TP

2209

General Mach Discussion / Re: Pin assignment

« on: May 04, 2014, 12:54:34 PM »

CAN you look in the OLD software for the pin assignments   SURELY the manf would know what they are, have you contacted them ?

Otherwise you will have to manually MAP out the pin assignments one by one.

(;-) TP

2210

General Mach Discussion / Re: probe guard

« on: May 04, 2014, 12:51:22 PM »

HIYA Ian , I like it.

Do you have a flow chart of the signal monitoring and control.??I worked on a software solution as a plugin and here it works well. BUT we all know that can change from PC to PC.

I tried to explain the IMPORTANCE of such things for MACH4 BUT you know how that went (;-)

IF I can help let me know, Us probers have to stick together or else we will all be running routers in Mach4.

(;-) TP