Stringing Together Multiple Controller Macros for Sequenced Operations
From contributor J:
You need the Fanuc Basic operation package and the DNC operation management package.
From contributor M:
Best of my knowledge it would take a macro and some discipline setting up your file system, but my thought is that it a barcode reader would be easier, more reliable and more versatile. The issue you are bringing up is my one gripe with the Anderson machines. I really like the hardware a lot, having used one for a year, and the Fanuc controller is very reliable and solid. But the user interface is clunky, slow and not operator friendly. It takes forever to call a sheet, and treeing through a directory of 60 files 9 lines at a time, 5 to 10 seconds per scroll is maddening
There is another way if you are using CV or CW or Alpha Cam, though it has its own problems too. You can output your nested runs as one large file running over DNC with a pause between each sheet. This can work pretty well, but if you have an error or an issue that needs attention on sheet 7 of a 30 sheet run, you have a problem picking that up in the middle again. The Macro solution may present this issue in a different way, depending on how you write it.
From contributor T:
It would seem to me that if you batched all of the sheets together and made sure they each included a start/stop command at the beginning and end, that this should be somewhat easy to accomplish. The overall program will be quite large and could possibly be spoon fed into the control with some simple DNC software.
From contributor O:
Contributor L - FYI, that program you use is a KOMO program. The Fanuc Basic Operation Package and the DNC software is all you need. Since you have an Andi already, you probably have the B.O.P. software. It’s pretty simple to set up.
From contributor K:
Hopefully you will have had this addressed to your satisfaction, but if you have not , here is what I would recommend - typically my recommendations are using the software of the control itself, because it’s cheap, you already have it and once you get used to it it really isn't a huge undertaking! I am assuming you have a standard Fanuc or standard EIA/ISO control.
1.) Transfer all nest programs to the control memory.
I know it’s not the preferred option for many, but if you’re on a budget it works pretty well. It does take some studying of the way you code your machine - which I recommend to most people anyway. If you do not understand the code, it is very difficult to troubleshoot anything. It is worth the investment to understand how your control interprets code!
From contributor K:
Revision # 1 – I forgot to put this in the original post, but inserting an M00 in-between the subprogram call lines will provide for you to unload/load then press cycle start to continue with next nest. My apologies for overlooking that!
Would you like to add information to this article?
Interested in writing or submitting an article?
Have a question about this article?
Have you reviewed the related Knowledge Base areas below?