Messages

1891

Mach4 Toolbox / Re: #var (Pound Var) parameters list docs..

« on: June 05, 2014, 09:11:34 AM »

YOU did not notice that the  vars were being updated by the Axis motion calls AND every Gcode WOrd letter. TOp screen look at the last line of Gcode N6 X1.50 Y4.5   NOW look at the VAr values for Xand Y  #24 =1.5 #24 =4.500.

Now look at #19(S) == Spindle speed call S311, and #13(M) = 5 the last Mcode called M5

Can't have that happening, The letters can ONLY populate the #vars from the G65 LINE and NO other time or place.  AND the #vars should not be able to be populated OUTSIDE of the G65 MACRO. THAT is why they are suppose to be LOCAL vars. bUT IN MACH4 you can populate ANY local var any time or place.

JUST A THOUGHT,

(;-) TP

1892

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: June 05, 2014, 12:28:25 AM »

THIS is about the 3rd time today I got this error. HOW should I respond

(;-) TP

1893

Mach4 General Discussion / Serious problem with G65 #vars

« on: June 05, 2014, 12:01:53 AM »

When you call G65 for a MACRO you are allowed to set #vars through Letter calls   A-Z  == #1-#26.  During the G65 call is the ONLY time you should be able to make the Letter calls update #vars.

In Mach4 ANYTIME you use a Gcode word X Y Z A B C U V W G F H M N Q P R S L etc ,  you are updating the #1-#26 VARS. This SERIOUSLY messes up the parametric Gcode in the G65 macro.

(;-) TP

1894

Mach4 Toolbox / Re: #var (Pound Var) parameters list docs..

« on: June 04, 2014, 10:24:18 PM »

HIYA Craig I JUST ran this program that populates the Vars with eth same value as the Var#. Makes it easy to track. You can see that there are many VARS EMPTY and 2 with the WRONG values applied. Look at D and P. AND I just spotted one more wrong value M

1895

Mach4 General Discussion / Loading SUBS or G65 macro

« on: June 04, 2014, 10:11:01 PM »

OK I found the problem in the M98 calls it seems Mach4 Fails on the starting of 2nd nest of the Sub. It does NOT even start the 2nd level.

It SHOULD be able to do 4 levels of sub nesting. Most modern controller do MUCH more levels of nesting.

(;-) TP

1896

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: June 04, 2014, 07:55:54 PM »

OH I fought with that one last night for about about 2 hours. It will ERROR everytime you push a button or try to do a function.

EVEN if you put THAT file back where it says it should be you will STILL get that error.

(;-) TP

1897

Mach4 Toolbox / Re: #var (Pound Var) parameters list docs..

« on: June 04, 2014, 07:37:37 PM »

There are problems with the G65 local #vars The following do not populate the #var when called. Some are reserved such as e and g

e g n o p q r s t u v x x y z

Also there is a range of Global Persistant Vars  starting at 500 and I got as high as 1100 that WERE persistant. 

The ranges should be
1-34 G65 local #vars NON persistant
100-199 Global NON persistant
500-999 Global Persistant

Above 1000 = system Parameters

1898

General Mach Discussion / Re: About Plasma Sheet Angle

« on: June 04, 2014, 12:17:58 PM »

It can if you write a script(Mcode) to do it. There is probably a script example somewhere on this site to do it.

(;-) TP

1899

Mach4 General Discussion / Re: system errors displayed

« on: June 04, 2014, 12:06:22 PM »

Does anyone know if there is a Lua call to access the Status History window. I see there is a BUTTON call but that is not what I need.

OR can you call the BUTTON from a script like the old DOButton() Mach3 call ?

(;-) TP

1900

Mach4 General Discussion / Single Block

« on: June 04, 2014, 12:03:30 PM »

Glad to see it does NOT crash anymore. I do have one suggestion in how it works. When you have single block SET and you are stepping though code you SHOULD be able to release it by just pressing the Single block button again and then CYCLE Start one last time(safety) and off it goes slinging chips.

As is you press Feedhold then STOP and THEN you can press single block to release it.

Just a thought, (;-) TP