Search the Community
Showing results for tags 'X7 MU2'.
Found 2 results
-
So these weird things are always the most frustrating. Total of seven programmers running similar hardware and all running the same install of X7MU2 and all hasps carry the same options. We started the migration to X7 a short time ago and have begun using it for all new parts. One programmer gets dirty operations for no apparent reason and operations that floated in the tree. He was the only one so I did a repair install of X7MU2 to be certain nothing had happened we couldn't account for, or that it would be restored. I am copying the direct information below of a different programmer from last night. ***************************** SPONTANEOUS CREATION OF MACHINE GROUPS SAVED A FILE BEING WORKED IN X7 AND CLOSED SO I COULD OPEN X5 FOR FIXTURE DIMENSION CHECKS TO QUALIFY A FIXTURE. RE-OPENED X7 FILE BEING WORKED AND GOT 8 WARNING MESSAGES THAT MACHINE DEFINITION FILE DOES NOT EXIST. X7 SPONTANEOUSLY CREATED 4 GROUPS: “MACHINE GROUP-11”, -111, -1112, & -11123 WITH GENERIC MILL DEFINITIONS. CLOSED X7 AND RE-OPENED THE FILE WITH THE SAME RESULT. I DELETED THE 4 NEW MACHINE GROUPS AND RE-SAVED THE FILE. CLOSED X7 AND RE-OPENED WITH NO ERRORS. NO OTHER EFFECTS NOTICED ************************************* Ok so now the previous guy is having this problem, after I had done the repair install though things seemed to be fine for a day. We had spent a considerable amount of time in X5 and the bug where machine defs were regrouped and operations all dropped into one group we could narrow to file imports from MCX where solids had history. We dealt with it by either dumping history or importing through another format, which in effect dumped history. In this case there is no import involved, or at least when the corruption happens. Just wondering if anyone else has seen this or experienced it? If so did you find resolution and what was that action? I have tried every search combination I can think of and found nothing here addressing this so we could be freaks.
-
Has any know how to fix this problem? retarting MC does work on this one (stops me dead in my tracks)... Any help would be greatly appreciated.
