hexagon logo
Register Sign in
  • Replies 6 replies
  • Subscribers 225 subscribers
  • Views 193 views
  • Users 0 members are here
Options
Related

Memory problems when looping a program

niklas.ahl
Hello all of you,

We have three big jobs which is made of 3 different fixture's with almost 500 pieces in an even matrix. It's a simple piece and we are measuring two diameters in two different levels.

I have made the program with 4 futures and 4 evaluations and then I have made two loops.

The problem is that sometimes PC-DMIS will run 5 pieces and the next time it will run 15 pieces before it get some kind of memory problem. PC-DMIS is totally unusable (freezed) and XP is not responding as it should, immediately when I closed PC-DMIS with the task manager XP is responding as it should.

I have talked to the support and they tell me this "memory" problem is known by them and that they are working with it.

My question is if some one of you have encountered this problem and have a simple solution for it?

We are running PC-DMIS 2009 MR1 and the computer is a x86 XP with 4 GB of RAM. I don't think the computer is the problem because I am running much "bigger" programs with solids imported with no problems. The problems encountering with the loop!

Best regards / Niklas
Parents
  • Niklas, if there was a 'simple solution' we'd have told you Slight smile

    But some PC-DMIS versions are worse than others. I think an upgrade to 2011 MR1 would make the situation better (but not perfect). At least we have a customer running a loop (over one measuring point!) more than 8000 times with that version.

    Also, the suggestion I gave you two and a half years ago - using an external program to call up different PC-DMIS programs for each row (or column) - is still applicable, or did you already try that?

    Another thing that might be worth testing is a 64bit version of PC-DMIS (as soon as it is publicly available).
Reply
  • Niklas, if there was a 'simple solution' we'd have told you Slight smile

    But some PC-DMIS versions are worse than others. I think an upgrade to 2011 MR1 would make the situation better (but not perfect). At least we have a customer running a loop (over one measuring point!) more than 8000 times with that version.

    Also, the suggestion I gave you two and a half years ago - using an external program to call up different PC-DMIS programs for each row (or column) - is still applicable, or did you already try that?

    Another thing that might be worth testing is a 64bit version of PC-DMIS (as soon as it is publicly available).
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement