Running Programs off of a network

Another option to using programs on a network is to use Inspect 5.0 with the Measure option - Use temporary routines when executing. (Copies your routine and any related files with the same name but with a different extension to a temporary folder for execution. This option is recommended when routines are located on a server, or when you want to keep the original routine untouched.)

I've been running programs from the network for over 15 years and have no issues until the network goes down.... Load time here is slightly slower than running from the hard drive but anything significant

Another option to using programs on a network is to use Inspect 5.0 with the Measure option - Use temporary routines when executing. (Copies your routine and any related files with the same name but with a different extension to a temporary folder for execution. This option is recommended when routines are located on a server, or when you want to keep the original routine untouched.)

My biggest complaint with using Inspect (we run it on 17 CMMs) is the time it takes to execute the DEMON each time that you execute the program. I used to use ReMeasure but one of programmers here was told by a Hexagon AE that we were not to use ReMeasure as it may not recall the program last used (not sure what BS this is). I wish Inspect had an option like MulitExecute

dwade,
If you use Inspect with the Measure option on and select Re-Measure, Inspect will create another temporary routine overwriting the previous temporary routine. The process I use with Inspect is to select the routine that’s on the network drive and execute it.
Inspect will create a temporary routine from the Network and execute that routine.
After the first part is complete, I will select done and then open the temporary routine that’s saved on the local drive.
C:\Users\<user>AppData\Local\Temp\Hexagon\Inspect\ TempExecutionLocation
<user> represents your Windows username.
I will set this temporary folder location to the Folder Explorer within Inspect settings.
The temporary routine will maintain the last executed settings even when using Re-Measure.
I will also see an improvement in the execution speed. If you’re only measuring one part, you can execute until it reaches a user input and then select cancel. Then select the temporary routine from the TempExecutionLocation folder. Now in the Help files the way it's written the temporary routine should be the one it will continue using until Inspect closes. But that's not always the case.
​

One could also use a script to copy the routine from the network drive. I have change NinjaBadger AUTOARCHIVE.BAS script to save the routine using the Save As method to the local drive.

This is 100% why we save "Masters" to the network. open pcd, save to local, run program from local save data to local then COPY to network, verify copy is complete delete local. if network goes down we are still running parts.

You dont need cad to run your program. Actually your program will faster without it. And if you have a program using large cad file sizes it may not load. I have had that a few times.

Try creating a new program and load the cad then go to Cad levels and put the levels you don't need on a separate level and than delete it from cad. Save the program and cad. Than delete the cad for your program and then import the new .CAD save it as another name and see if you can open and close that without any issues

we only ever load in 1 layer of CAD on our programs and not using cad thats asking a lot of some of our operators.

We use windows "RoboCopy" works great copies masters from one place and copies to local c drive on cmm if a file has changed or updated only.

open notepad, update your network shared ID's and locations and save as ".BAS"

@echo off

for %%T in (
CMM-endeavor
CMM-global
CMM-global2
) do (
robocopy \\CMM-global2\CMM-Shared\PC-DMIS-Program-List \\%%T\CMM-Shared$\PC-DMIS-Program-List /MIR /R:5 /W:15 /MT:32 /copy: DAT/LOG+:CopyJobBackup.log

)​​

robocopy is a great tool, just learned about it recently myself. cool to see it applied for this type of control.

".bat" not ".BAS"

Just an added note. The temporary routine will also be listed in the Recent Tab after the first Execution. Not sure why Inspect program doesn't have a condition to check the temporary folder first before copying, pasting and executing the routine.