[kenickie22]

sinha_nsit, I thought the samples from your book looked great. I liked the G66 explanation. I haven't ever used it, because I didn't know how. The only thing I can think of to add would be P #'s at the end of a sub-program (M99P1) to return to a different line in the main program. Thanks for the opportunity to review your book before buying it - I definitely will be.

[sinha_nsit]

The only thing I can think of to add would be P #'s at the end of a sub-program (M99P1) to return to a different line in the main program.

Thanks.
You are very much right. I missed this point. It can only be added in the next edition. There can be some logic when it might be necessary to jump to some other block other than the block following M98, though I have to think about some practical example. If you have something in your mind, pl pass on to me.
Thanks again for your useful suggestion.

[kenickie22]

%
O0100(AUTOMATION PROGRAM)
(27SEP10 - KN)

N1( PROGRAM RESET )
G65P10A1.

N2( INITIALIZE TIMER )
#3002=0
IF[#910EQ#3011]GOTO3
G65P200D99.

........

M99P2
%

The majority of our machines are robot loaded HMC's, that are running the same part on both pallets. I typically loop a main program with M99 that has (2) macro driven work offset load programs and (1) machining program runnning as subs. This way, I only have to prove out/maintain 1 machining program for all of the machines/fixtures that are running a particular part. In this example, I'm using it to tell if a machine has been reset. I have a DNC software hooked to our machines for data collection. Our Makino HMC's have a function you can turn on to rewind the program anytime RESET is pushed. When N1 is ran, I output things like N#, T#, Pallet #, part serial #, etc. for traceability purposes. If the machine is not interrupted, it skips over this line and goes to N2. Hope this makes sense.

[christinandavid]

Another similar example: -

We have fixtures that take a complete set/multiples of parts required for an assembly, but we don't always have an equal amount of parts, so we program the complete set in our main program and use a separate sub to store the actual extended work offset (P1-P48) we are using for each individual part.

The main program calls a standard macro at each N (sequence restart position) that looks at the particular offset specified. If it finds that the offset has been set as zero it jumps back into the main program at N +5.

So a single program can now run in many different configurations, skipping through the parts that are not required. It just means a bit of discipline in the format of the main program - N5, N10, N15 etc

DP

[kenickie22]

Sinha,
Just wanted to let you know I just received your new book today. Looks great so far.

[sinha_nsit]

Thank you. Hope you would find it quite informative.

Download the attached files, having additional reference material.

Sinha

[romer]

I'm mostly just a lurker on this forum, searching and learning as I go from many of the knowledgeable and learned posters.

I'm looking to write a few macros that are more complex (for my tiny mind) than the simple ones I have written and used in the past. So here I am once again, searching and reading.

What caught my attention and I believe deserves to be recognized is the fact that on 3/20/2006 sinha_nsit made this post
https://en.industryarena.com/forum/showthread.php?t=18698

4 years later, he has written and published a book on the same subject!

Way to go! :cheers:

After reading the chapters he has posted, this may be just what I am looking for.

romer