Is there an easy way to WATCH what is going on in PC DMIS3.73? I want to 'step' through line by line but I really hate the way PC DMIS utilizes step. Many commands are not steppable (which really sucks but that is another rant). I want to watch the flow as it jumps from line to line and pinpoint where the program is jumping track. STEP (CTRL E) is useless in that regard.
For a description of WHY it is jumping track please continue.
OK. I had a program to check the calibration of all stylus to each other. Worked great and life was good. This will be significant later
I also had a program that was migrated from 3.72 to 3.73 that 3.73 did not like. The backup file was 3.72 BUT my 2nd shift guy loaded it into 3.73 when the working copy had problems. Now it is also converted to 3.73.
So, I saved the copy back to a version 3.72 could read in an attempt to get a working version of the program. I seem to recall that the 3.7 option actually saves to 3.73 and will not work in 3.72 so I saved to 3.6. Well, doing so converted all probe files to 3.6. We noticed this when my 2nd shift guy tried to run a program yesterday. No problem, we converted all probes back to 3.73 as BOTH 3.72 AND 3.73 can use the probe files fine.
Now, everything seems to work EXCEPT the Cal Check Program. When it finds an out of tolerance condition it behaves improperly. It does not follow the code (which tells it to jusm to a label and calibrate all tips then jumpo back). Instead, it grabs the last probe combination and trys to calibrate the tips.
Sorry to bust your brains on Friday but tahnks in advance.
For a description of WHY it is jumping track please continue.
OK. I had a program to check the calibration of all stylus to each other. Worked great and life was good. This will be significant later
I also had a program that was migrated from 3.72 to 3.73 that 3.73 did not like. The backup file was 3.72 BUT my 2nd shift guy loaded it into 3.73 when the working copy had problems. Now it is also converted to 3.73.
So, I saved the copy back to a version 3.72 could read in an attempt to get a working version of the program. I seem to recall that the 3.7 option actually saves to 3.73 and will not work in 3.72 so I saved to 3.6. Well, doing so converted all probe files to 3.6. We noticed this when my 2nd shift guy tried to run a program yesterday. No problem, we converted all probes back to 3.73 as BOTH 3.72 AND 3.73 can use the probe files fine.
Now, everything seems to work EXCEPT the Cal Check Program. When it finds an out of tolerance condition it behaves improperly. It does not follow the code (which tells it to jusm to a label and calibrate all tips then jumpo back). Instead, it grabs the last probe combination and trys to calibrate the tips.
Sorry to bust your brains on Friday but tahnks in advance.
Comment