Messages

1781

G-Code, CAD, and CAM discussions / Re: BobCAD, Mach3, Plasma cutting

« on: December 06, 2014, 05:03:16 PM »

Your problem is with BOBCAD writing junky POST processors. It is not a MACh3 problem call BOBCAD and complain to them.

(;-) TP

1782

General Mach Discussion / Re: Rotaryaxis reference

« on: December 06, 2014, 04:44:49 PM »

Give this a try.

' Macro for Homing Machine
Dobutton(24)   ' Reference Z
While Ismoving()
Sleep(10)
Wend

DoButton(22)   'Reference X
While Ismoving()
Sleep(10)
Wend

DoButton(23)   'Reference Y
While Ismoving()
Sleep(10)
Wend

If GetLED(39) Then    'Check for A home LED IF so then

   Code"G91"
   Code"G0 A-45"
   Code"G90"
   While Ismoving()
   Sleep(10)
   Wend
   DoButton(25)
   While Ismoving()
   Sleep(10)
   Wend

Else         'Other wise reference A
 
   DoButton(25)
   While Ismoving()
   Sleep(10)
   Wend
   
End If

End
 


(;-) TP

1783

Mach4 General Discussion / Re: Trying to get the current Gcode line #

« on: December 05, 2014, 08:46:04 PM »

Thansks ALL I got the LIne# working. The odd thing is   The DRO that gives you the current line and the call to get the current line gives you 2 different values (;-) One is 1 based and the other 0 based.

NOW does anyone know IF the DRYRUN  feature works. I cannot get it to do anything in SIM()

AND I cannot get the goto page function to work either.

1784

Mach4 General Discussion / Trying to get the current Gcode line #

« on: December 05, 2014, 01:35:35 AM »

I am trying to get the current Gcode line Number. The book is not really clear about the parameters required.

ANY Ideas on the call ?

 buff, rc         = mc.mcCntlGetGcodeLine(number mInst, number LineNumber)
        --What Gcode line number is the interpreter on at present

Mach4 errors out on everything I tried . It says the call requires (number,number,string,number) but that does not make sense as you are looking for the number.

I tried LineNumber as the book says thinking is was an internal Parm but it is <nil> not a good param.

(;-) TP

1785

Mach4 General Discussion / Re: Mach 4 Feature Request

« on: December 04, 2014, 10:27:40 PM »

We need a on open /close script to open/close the Tool Table and FIxture Table from a PAGE.

Thanks (;-) TP

1786

Mach4 General Discussion / Re: Needing help with screens

« on: December 04, 2014, 02:30:54 PM »

Here is a tip unless it is an Mcode MOVE your test script to a seperate Directory. Mach4 does funny things if run from the Profile/macro directory. Also Mach4 will PRERUN the macros in the Proflie/macro directory on startup.

I set up Mach4hobby/MACROS directory and run tests from there MUCH better stablility and NO weird stuff happening on testing.

Just a thought, (;-) TP

1787

Mach4 General Discussion / Re: Needing help with screens

« on: December 04, 2014, 10:49:45 AM »

I think I remember seeing a SWITCH to change that mode to SYNC.

(;-)TP

1788

Mach4 General Discussion / Re: Needing help with screens

« on: December 04, 2014, 10:27:00 AM »

SO does this mean that me still have the same problem in Mach4 as we had with Mach3 macros. The macros will NOT stay in sync as to Gcode and Lua AND order of execution AND we end up with a race condition. I thought we were going to fix that this time

(;-) TP

1789

Mach4 General Discussion / Re: Needing help with screens

« on: December 03, 2014, 10:48:28 PM »

(;-) Its not doing ? what?

(;-) TP

1790

Mach4 General Discussion / Re: Needing help with screens

« on: December 03, 2014, 10:47:03 PM »

Now the real kicker is IF I load the code and run it once it runs ok. IF I then run it a 2nd time it runs the Gcode twice in a row(0 -10/0, 0-20/0, CRASH) . IF I run it the third time it locks up mach4.

Probably a SIM() problem, (;-) TP