Hello Guest it is October 21, 2019, 09:22:07 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - smurph

711
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: May 02, 2014, 02:13:15 PM »
Asked this before, but it again got missed - is there a way to have the DRO's persistent like it is in Mach3?

Also, a few other things:

1. Are there no settings for CV like there used to be in Mach3?
2. While running a program, all the buttons under the the File Ops tab should be grayed out or at least shouldn't do anything if clicked on, like it is in Mach3. Clicking one of them in Mach3 returns a message that you should first Stop the programme running.
3. Can the file loader be made to remember the last location and not default to the root directory of Mach4?
4.

Dan

1. No CV settings at this time.  CV is now using a much more advanced logic than it did in Mach 3.  For most cases, there is simply no need to tweak it.  However, we may add a setting or two soon.
2. This is controlled entirely by the screen set.  You can make it do whatever you want it to do.
3. I will make the file open "remember".

712
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: May 02, 2014, 02:08:31 PM »
Is MACH4 suspended while a SUB is running (as with MACH3 named SUBS) or is it still necessary to insert pauses/delays?

And as long as were on the topic, does MACH4 support named SUBS?

Mach 4 is not suspended.  But I'm not sure what you mean.

And by named subs do you mean the sub file named in the comment?  If so, then Mach 4 supports that.

Steve
Sorry for confusion. I tend to think of macros as subroutines and intermix the terms. 

...



The macros can be named anything.  However, to call one as an M code, it had better start with m!  :)  But inside the scripting environment, you can call a script with any name.

Mach4 syncs on M codes.  The M code may be a macro or it may not (M98 vs. M03, etc..  M codes break the CV chain.  And M codes run to completion before the interpreter advances.

713
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: May 01, 2014, 10:24:59 PM »
I think an old screen set was in the build.  It is probably a LED signal is wrong.  Edit the screen and check it out.  In any case, the screen set I'm using will be in the next update and all of that stuff will be fixed.

714
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: May 01, 2014, 08:40:15 PM »
Is MACH4 suspended while a SUB is running (as with MACH3 named SUBS) or is it still necessary to insert pauses/delays?

And as long as were on the topic, does MACH4 support named SUBS?

Mach 4 is not suspended.  But I'm not sure what you mean.

And by named subs do you mean the sub file named in the comment?  If so, then Mach 4 supports that.

Steve

715
Ain't it fun?  I can implement a Mach/Galil combo in my sleep now but I DO REMEMBER the first time.  All I can tell you is that it will all make sense AFTER you get it done the first time.  Until then...  patience.  The patience of a Saint!!!

Steve

716
And you are correct about the output numbers.  1-8 on 1st ICM, 9-16 on the other.

Steve

717
Oh wait...  Outputs not Inputs!!!  Hmm...  What kind of ICM?  Opto or not?  There is an application note on Galil's site that explains the output wiring.  It is different based on the OPTO option.

Steve

718
No reason for a new thread.  I'll see this one.  :)

You may have to invert the signal.  it all depends on the polarity of INCOM on the ICM.  INCOM == GND vs. INCOM == +V.  Try that and see if that gets you results.

Steve

719
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: May 01, 2014, 02:08:56 PM »
Also, a word on sub programs.  We now have the capability of calling system subroutines that are external to the main program.  These subroutines should be placed in the <mach dir>\Subroutines directory with the filename of "O" plus the program number.  No file extension.  For example:

Program number 8000 should be named "O8000" and placed in the Subroutines directory.

Then "M98 P8000" or "G65 P8000" in the main program can call the system sub "O8000" in the Subroutines directory.  Loading the comment on the M98 line with a file name is no longer required (however, it is still supported).  You can't mix the two methods, obviously.  Meaning that if you use the P address on M98 to call an external sub, you should not also use the comment to define it.

There is no limit on sub nesting now.  Well...  the limit is your PC and whatever resources it has.  But we don't confine you to only 5 levels of nesting or the like. 

This is a standard Mach 4 Hobby feature!!! 

720
Mach4 General Discussion / Re: Comments about Mach4 in Demo
« on: May 01, 2014, 01:56:29 PM »
Do you have a list of the Local G65 Parameters "A=#1 B=#2 C=#3 etc??

What Graham posted is what we use.  Standard Fanuc.  We won't get into mixing or shuffling them up for our own purposes.  We just reserve the E address because the interpreter will look at it as scientific notation.  When I get time, I may try and remove this restriction.  But for now, it is reserved. 

Most of the reserved addresses have a special meaning on the G65 line but they can be accessed in the sub.
E (Mach reserved) would be #8.  it will be loaded with NIL (undefined).
G (RESERVED SYSTEM WORD) would be #10.  It will be loaded with "650" as G65 is what called the sub!  This is how you can know if G65 called the sub or not.
L  (RESERVED SYSTEM WORD) would be #12.  It is loaded the the loop count from the G65 L address.
N  (RESERVED SYSTEM WORD) would be #14.  It is loaded with the sequence number of the G65 line (if provided).
O  (RESERVED SYSTEM WORD) would be #15.  It is not loaded with anything at the moment.
P  (RESERVED SYSTEM WORD) would be #16.  It is loaded with the program number from the G65 P address. (your called sub program number)

Steve