A couple of General CMM Queries.

Hi Guys,

I appreciate all the feedback and I suppose I have only one more question really and hopefully I will be able to satisfy the powers that be.

Josh
The big question for me is that. Ok it's great to here that running a shared programme on multiple CMM's is not good. But I suppose I need to be able to tell them WHY it isnt good. If I cant give them a couple of reasons why running off a shared programme is bad then I wont have much clout for getting them to bring in an automated system!

So, any info on that would be great.

Thanks,

Cian

Like others here, I would not recommend trying to run multiple machines from the exact same program file. PC-DMIS frequently writes back to the program files, and you could run into a situation where multiple machines are trying to do so at once, and one flips out because the file is record-locked. I could also see he potential for data saved back to the program file by one machine causing a conflict on another.

We have a dozen or so Globals in our facility. All of their programs, probe files, etc. are stored on the network, but in individual shares for each machine - e.g. CMM #500 has all of its data in G:\PC-DMIS\MACHINES\500\... on our network, CMM #505 in G:\PC-DMIS\MACHINES\505\..., and so forth. Our CMM programmers can easily copy a program from one machine's share to another if they need to run it somewhere else.

Also, the stability and reliability of your network connection is paramount when running from a network share. We used to have a 3COM core switch for our company network that did double duty propagating our IP phone system, but it did neither well - intermittent network latencies would sometimes crash PC-DMIS and cause serialization issues with programs. When we switched to dedicated HP core switches and a CudaTel IP phone system, these problems went away.

Hi Guys,

I appreciate all the feedback and I suppose I have only one more question really and hopefully I will be able to satisfy the powers that be.

Josh
The big question for me is that. Ok it's great to here that running a shared programme on multiple CMM's is not good. But I suppose I need to be able to tell them WHY it isnt good. If I cant give them a couple of reasons why running off a shared programme is bad then I wont have much clout for getting them to bring in an automated system!

So, any info on that would be great.

Thanks,

Cian

Like others here, I would not recommend trying to run multiple machines from the exact same program file. PC-DMIS frequently writes back to the program files, and you could run into a situation where multiple machines are trying to do so at once, and one flips out because the file is record-locked. I could also see he potential for data saved back to the program file by one machine causing a conflict on another.

We have a dozen or so Globals in our facility. All of their programs, probe files, etc. are stored on the network, but in individual shares for each machine - e.g. CMM #500 has all of its data in G:\PC-DMIS\MACHINES\500\... on our network, CMM #505 in G:\PC-DMIS\MACHINES\505\..., and so forth. Our CMM programmers can easily copy a program from one machine's share to another if they need to run it somewhere else.

Also, the stability and reliability of your network connection is paramount when running from a network share. We used to have a 3COM core switch for our company network that did double duty propagating our IP phone system, but it did neither well - intermittent network latencies would sometimes crash PC-DMIS and cause serialization issues with programs. When we switched to dedicated HP core switches and a CudaTel IP phone system, these problems went away.