[Sr...] Posted January 20 Share Posted January 20 Hi guys I receave program from our main factory and in the program , probe standing still about minute , before it go on the next feature. And it does that with every feature in program. any idea? tnx Link to comment Share on other sites More sharing options...
[Ma...] Posted January 20 Share Posted January 20 Are there any differences on CMMs? Version of Calypso is matching? Link to comment Share on other sites More sharing options...
[Ke...] Posted January 20 Share Posted January 20 Also: Look at how many points per feature that the program is collecting. The software lags when there is a lot of data that is being collected & processed (compared to CPU capabilities). There are also recommended computer specs, depending on which version of calypso that you are using. Link to comment Share on other sites More sharing options...
[Sr...] Posted January 20 Author Share Posted January 20 We had ethernet problem. Sorry guys 😄 Link to comment Share on other sites More sharing options...
[Mi...] Posted January 20 Share Posted January 20 I've also similarly seen this happen on DuraMax CMMs that just need a controller reboot, then they start behaving again. Ours run 24/7 so sometimes they need a nap. Link to comment Share on other sites More sharing options...
[No...] Posted January 21 Share Posted January 21 I've seen similar behavior once when I used a lot of manual point masking entries within a circle. Calypso seemed to have a hard time calculating them all. Link to comment Share on other sites More sharing options...
[Je...] Posted January 21 Share Posted January 21 Make sure your CALYPSO configuration has "Actuals" or "actual values" being stored locally. This should ALWAYS be set up this way. Do not ever store "Actuals" (in Paths setting) on a network drive, especially if it is a shared drive. Performance issues aside, this is not a matter "if" it will cause a physical machine crash but a matter of "when". Actuals are the temporary inspection data/machine navigation data. If it is shared between 2 or more CMMs running the same program simultaneously, CALYPSO has no idea which instance wrote the data and will use whatever is available. This isn't to be confused with "idMeasPoints" or "Saved Measured Points". They are not the same data or files. Link to comment Share on other sites More sharing options...
[ni...] Posted January 24 Share Posted January 24 Hi Jeffrey, Where is the menu to check if the Actuals are stored locally (all our programms are on network) thanks Link to comment Share on other sites More sharing options...
[To...] Posted January 24 Share Posted January 24 (edited) Extras > Settings > Environment > Paths Edited January 24 Link to comment Share on other sites More sharing options...
[Pe...] Posted January 24 Share Posted January 24 Please sign in to view this quote. My programs are saved on a shared network drive. Is there a universal setting I can use to save all idMeasPoints into the "same directory as measurment plan" but then keep the Actuals in a local folder? If I designate the Actuals environment path to a local folder, then the idMeasPoints go there as well. Link to comment Share on other sites More sharing options...
[To...] Posted January 24 Share Posted January 24 (edited) Please sign in to view this quote. I'm pretty sure the idMeasPoints are saved to the measurement plan folder by default. It is possible to control where the MP's are stored, if needed. The actuals are a separate set of points. Edited January 24 Link to comment Share on other sites More sharing options...
[Pe...] Posted January 24 Share Posted January 24 Please sign in to view this quote. If I set the Actuals in environment path to a specific local folder, the idMeasPoints go there as well. How do you control them independently? Link to comment Share on other sites More sharing options...
[Jo...] Posted January 24 Share Posted January 24 I see that the OP said he had ethernet problems, so it sounds like the problem was solved. Some additional two cents if I were to encounter this problem. I would double-check the pre/post settings of those features. Either the post-setting of the feature before the pause, or the pre-setting of the next feature to measure. Sometimes if it needs to compute some PCM it may pause in between features until it is done running that code. Link to comment Share on other sites More sharing options...
[To...] Posted January 24 Share Posted January 24 (edited) Please sign in to view this quote. You may want to create more folder structure to specific customer, drawing number, order number, etc. Edited January 24 Link to comment Share on other sites More sharing options...
[To...] Posted January 24 Share Posted January 24 A few years ago, I did a youtube video that might help, if needed. 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