[Ry...] Posted March 9, 2020 Share Posted March 9, 2020 Hello, we have recently updated to Windows 10 and have started having issues and our trying to figure out if there is some correlation between the two. I have two Contura G2s identical except for length, we upgraded one to windows 10 and the other is still windows 7 the windows 10 computer is having repeatability issues and the windows 7 computer is not. It is forgetting measured points occasionally after it runs them and wants to rerun them at the end of the program, and occasionally one of the hole sizes will spit out an off the wall number like its suppose to be .500 inches and it checks 7.300 inches when the hole is clearly only .500 along with this it will forget where the base alignment is and so the features at the end of the run are all ridiculously high numbers and all out of tolerance. Run the same part again and clean report, and again a red report with 30 things out. Any help is appreciated. Running 6.4.28 Calypso 2017 Link to comment Share on other sites More sharing options...
[Ri...] Posted March 9, 2020 Share Posted March 9, 2020 Are you using Gage Correction (Under Evaluation of the feature)? Link to comment Share on other sites More sharing options...
[Ry...] Posted March 10, 2020 Author Share Posted March 10, 2020 I am not Link to comment Share on other sites More sharing options...
[Ke...] Posted March 10, 2020 Share Posted March 10, 2020 I have never seen that issue (but also have not upgraded to Windows 10, yet) Have you tried copying over the program from the Windows 7 computer, to see how that program performs? Maybe the program was corrupted, somehow (?) Link to comment Share on other sites More sharing options...
[Ry...] Posted March 10, 2020 Author Share Posted March 10, 2020 I actually store the programs on a central server drive and run the exact same program for both, making it even more confusing for me as to why one would run it properly and the other have so many deviations Link to comment Share on other sites More sharing options...
[Ri...] Posted March 10, 2020 Share Posted March 10, 2020 Make sure in Extras - Settings - Environment - Path is set to store the actuals locally. Otherwise both machines are reading/writing actuals to the same measurement plan. Link to comment Share on other sites More sharing options...
[No...] Posted March 10, 2020 Share Posted March 10, 2020 To me it sounds as if there's a problem accessing the actual points data and possibly some data in C:\users\public\... (workarea\basesystems?) Maybe some access restrictions have been applied by accident during the update? But then it'd be still unclear why it doesn't happen all the time. 😕 Link to comment Share on other sites More sharing options...
[To...] Posted March 10, 2020 Share Posted March 10, 2020 Please sign in to view this quote. The plot thickens.... Link to comment Share on other sites More sharing options...
[Ry...] Posted March 10, 2020 Author Share Posted March 10, 2020 And each one is set to local for measuring data, haha I can run a master gage ring a dozen times with the probe rotated in each +x, -x, -y, +y direction and drive it to the end of the hardware limits and back to the ring over and over and get repeatable results within .000025 of a inch but go to run the same part a dozen times and you get a dozen different reports with results varying up to .018 of an inch. Again no issues before the windows upgrade, and the other identical machine has no issues. I'm scratching my head with tech support right now. 🤣 Link to comment Share on other sites More sharing options...
[Ca...] Posted March 10, 2020 Share Posted March 10, 2020 We also store our programs on a server, and I have had VERY similar problems when running from the server directly. A while back, I started moving the programs to the local computer, and running from there. This solved those problems. Link to comment Share on other sites More sharing options...
[Ry...] Posted March 10, 2020 Author Share Posted March 10, 2020 I tried saving a few programs locally to the Computer running the CMM and though it did help some I was still having 1 out of 3 runs with incorrect reports, it's even set up to loop within .00005 with 5 loops for the base alignment. Sometimes it even forgets the measured points as I run the features and I have to go back and recheck features over and over again to get them to save the measure points that doesn't happen as often but at least 1 out of 10. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in