Messages

1191

General Mach Discussion / Re: using a variable value directly in gcode

« on: May 03, 2015, 02:40:18 PM »

Always use the WHile Ismoving()  / Wend after each single motion call or Group of motion calls.

(;-) TP

1192

General Mach Discussion / Re: call subprogram from macro?

« on: May 03, 2015, 02:33:01 PM »

You will not find any mention of any redirection use or SUB use in a macro in ANY manual (;-) You just read the manual on that function.

THE #var info is in the Mach3 manuals .

To redirect BACK to the line after the Mcode you MUST put in the sub call line.


M100  ( the macro jumps to o100 in the Gcode)
o101
code
code
code
M30

o100
M101   ( this macro will Jump back to the o101 sub call line)

1193

Brains Development / Re: GCODE INPUT TO BRAIN

« on: May 03, 2015, 02:06:15 PM »

(;-) TP

1194

General Mach Discussion / Re: call subprogram from macro?

« on: May 03, 2015, 01:53:47 PM »

NO you CANNOT call a sub from a macro as it has nowhere to return to as the Gcode side cannot SEE the M98 that is in the macro. You will get an erro"SUB called with no return"  But that does not mean you cannot redirect the end of the sub back to another Sub call line. basically back to the line after the macro. You just have to be clever.

SO more notes on Macros.

When you read or write to dros or variable give it a bit of sleep time to get it all done

SetOemDro(10,GetVar(24))         I use 100ms for each function(read/write)
sleep(300)

Group your motion code and use   WHile Ismoving() to wait untill Mach3 is done with it.  This will HOLD the macro until motion stops. Use it with ANY and all motion codes. Use it with a single call or a group call for motion.

Code"G0 X0Y0"
Code" X10"
Code" Y10"
Code"X0"
Code"Y0"

While Ismoving()
Wend


Hope that helps, (;-) TP

1195

General Mach Discussion / Re: call subprogram from macro?

« on: May 03, 2015, 01:36:21 PM »

YES and NO (;-)   I use teh rediredtion fnctio of the M98 to move to another spot in Gcode from a macro. For example

G0 X0 Y0
M100         ( this macro is used to redirect to a o100 point in the Gcode. It is simply Code"M98 P100")
X10
Y10
X0
Y0
o100
x1 Y1

The macro will JUMPTO the sub call line o100 BUT it cannot return so the redirection is one way. Of course you could use the call again to JUMPTO back to another sub call line.

You can also add conditional CB code to make decisions as what you need to do . MUCH like conditional Gcode. You can also add outside param to eth macro to program the conditional Mcode on the fly as M100 Pxx Qxx Rxx  you have 3 params to work with for each Mcode. ALSO you have ALL the #vars you can add as well. Mcode PxxQxxRxx #1=100 #31=300.. THE #vars are solved FIRST in the call line so they WILL be available when the macro runs.

I will double check on a straight SUb call from a macro to be sure about it. it has been a LONG time last I played with that idea. (;-)

1196

General Mach Discussion / Re: how to stop macros from executing until 2nd cyclestart?

« on: May 02, 2015, 07:18:26 PM »

I think it assumes the macro will be in the Macro directory of the current profile you are running.

For a standard Mach3 load it would be C:\mach3\macros\Mach3mill\  . That is where you put your "M4000.m1s "macro.

Then call it with RunScript("M4000")   , Note the "  " and no extension.

You need to try that as that is from memory, (;-)

1197

General Mach Discussion / Re: Mach 3 Port 1 not working, Port 2 is working

« on: May 02, 2015, 06:39:35 PM »

Where are you changing the address at Mach3 or the PC ?

(;-) TP

1198

General Mach Discussion / Re: how to stop macros from executing until 2nd cyclestart?

« on: May 02, 2015, 01:47:03 PM »

Here is the problem in  a nut shell.. The Gocde side of Mach3 and the Macros side of Mach3 "CB" are NOT synced together well. One can get out of order sync from the other resulting in some ODD things occuring.  The key is you have to Safeguard the operational order of execution with wait states OR code to prevent it from happening. Also when you apply a wait state you never really know how LONG to allow so you have to add time to it incase of it running short. What can happen is it can skip OVER sections of code and the skipped code either does NOT run or is run out of order.

Another problem is the more you protect the script the LONGER it takes to run (;-) This can add unwated delays to some scripts making it drag along .


Same problem with calling a macro from a macro only worse. That is why RunScript() was developed it helps ensure the order of execution is maintained. RUNscipt() will HOLD the execution of the next line from  running UNTIL the execution of the RunScript() is finished.

NOT saying you should not run Motion and CB macro in the same script BUT be warned "There be Dragons in the woods".

I personally make the bulk of motion in a gcode program then use macros to make decisions or to program a function  and occasionally have the emacro make a NON important Motion move (positional) with safeguards.  Remember that mach3 was designed as a CNC controller not a general purpose motion controller.  Straight Gcode it does Well. Mixed not so well.

Just my opinion, Your mileage may vary (;-).

(;-) TP

(;-) TP

1199

General Mach Discussion / Re: Mach 3 Port 1 not working, Port 2 is working

« on: May 02, 2015, 11:55:53 AM »

That is because some PCs use roving address settings for ports. It can be different each time the PC starts  It sets it to whatever it wants to use. You can change this to use a standard address each time it opens.

(;-) TP

1200

General Mach Discussion / Re: Cancel the A axis

« on: May 02, 2015, 11:43:21 AM »

If you do not want the A axis to move do not give it any motion commands. It will NOT move until you tell it to.

(;-) TP