Badge Scan for Employee

I would add here: with a bit more research you can add all these in an external subroutine to holds a header and a footer. All programs call this sub twice (beginning/end). This way when you need modifications you just do it to the subroutine and not all your programs (initial modification for the calling of the sub is needed though). This is what we do where I work.

Subroutines confuse me a bit. I could never find a true blue step by step guide to understanding them in a way that I could wrap my head around them. So I just use the same script/code in all my programs, then call in an external document for the variables

Well the gain is that by using them you can modify all programs just by modifying the subroutine. In our case where we have hundreds of programs stored in a server where modification is not possible and multiple steps are required (time also) to adjust anything, using a subroutine makes a big difference. Examples: do I need to add extra info in the header? Do I need to stop printing and use other exporting methods? Add a note? Add an operator input? Etc etc... All these realise just by modifying 1 easy to modify subroutine.

Well the gain is that by using them you can modify all programs just by modifying the subroutine. In our case where we have hundreds of programs stored in a server where modification is not possible and multiple steps are required (time also) to adjust anything, using a subroutine makes a big difference. Examples: do I need to add extra info in the header? Do I need to stop printing and use other exporting methods? Add a note? Add an operator input? Etc etc... All these realise just by modifying 1 easy to modify subroutine.

Is there edge cases where you will need different subroutines for certain programs? Or do you guys try to keep it all identical no matter what

Personally no. I use 1 master subroutine only for a header and footer in each program. They contain only none measuring commands (operator inputs, printing behavior etc). Each program is validated and "locked" after for their measuring commands, while the rest of the code (existing in the sub routine) is "free" to modify according to our needs.

If programs are created already would you still have to go into every program and add the code to call up said subroutine?

Yeah, you'd have to go in to every program to call the subroutine, and delete anything in the original program that the subroutine is controlling. It's great if you start there, and work it into all new programs, but adding it into every prior existing program still is tedious. I'm familiar with some tedium here and there. When we got our new CMM we had to adjust every single program's setups Y Fixturing position because we lost some Y distance. And we couldn't rely on operators to add 6 in Y for everything. I'd like to change how we do things, but we have so many programs. Some from when I barely got out of high school.

Well you already need to do so if a universal modif is needed either way. You can optimize this and do it next time you need to add something universally. Once and done :)

Sadly we already did all the modifications end of last year, once we do it again, I'll plan for this.

understood, i was just hoping you had some secret way to add subs to programs without opening them. we have a standard template that we use but some of our "older" programs don't have it so we have been updating as we come across them. 

You could probably do something fancy in a similar fashion to the probe finder macro that is here on the forums. It automatically opens and closes programs after it counts your tips + angles. I'm sure you could get it to add in subroutine commands fairly easily