[Br...] Posted April 13, 2021 Share Posted April 13, 2021 I have a program that runs a qualification on every probe in the rack at every angle. The report just outputs the standard deviation of each qualification to verify if it was any good. However, sometimes a probe doesn't qualify for some reason. The sigma and diameter will show good, so it doesn't get caught in the report. It doesn't get noticed until. you go to run a program that uses that particular probe and angle at which it stop and gives a message that says the probe isn't qualified. So then you have to put the sphere back on the table and do the whole song and dance again. Alternatively I can just look in the probe management window and see if something isn't qualified. My question however- Does anyone know how to convey this into a report so it can be caught up front? Link to comment Share on other sites More sharing options...
[To...] Posted April 13, 2021 Share Posted April 13, 2021 Please sign in to view this quote. I think the Default Printout will show you which probes were not qualified? Link to comment Share on other sites More sharing options...
[SH...] Posted April 13, 2021 Share Posted April 13, 2021 Please sign in to view this quote. Yes, I use default printout..it is comprehensive. But condition with formula will not work for him? Link to comment Share on other sites More sharing options...
[Me...] Posted April 13, 2021 Share Posted April 13, 2021 Like Shabu mentioned, if you use a result element characteristic and the appropriate printout, that should suffice. That’s how I’ve always made my Cal programs. Link to comment Share on other sites More sharing options...
[Cl...] Posted April 13, 2021 Share Posted April 13, 2021 Create a result element for each stylus and all it's positions. This is the PCM that wil give you the Sigma result. getProbe("1","1.5_Z-").stdProbeDev/25.4 Link to comment Share on other sites More sharing options...
[Br...] Posted April 13, 2021 Author Share Posted April 13, 2021 As I previously stated, the program already outputs the standard deviation. That's what sigma means. The problem is that sometimes there is an error and the qualification fails. (you will see a little red X in the stylus system window when you activate it. Calypso considers this stylus " not qualified". In fact it logs the sigma value as perfect 0.0000. So on a report using result element, it shows a good qualification when it is not. Link to comment Share on other sites More sharing options...
[Br...] Posted April 13, 2021 Author Share Posted April 13, 2021 Please sign in to view this quote. Is there any way to get this into a piweb report though. Link to comment Share on other sites More sharing options...
[To...] Posted April 13, 2021 Share Posted April 13, 2021 Please sign in to view this quote. Geez. Give 'em an inch and they take a mile...LOL I don't know but you could generate a Multiple Report using 1 PiWeb report and 1 Default Printout. Sorry. Link to comment Share on other sites More sharing options...
[Ja...] Posted April 13, 2021 Share Posted April 13, 2021 Could an "If, Then" formula be added to the result element, so if the sigma equals 0.0, then 10? That way it will turn red on the report. Link to comment Share on other sites More sharing options...
[Pe...] Posted April 13, 2021 Share Posted April 13, 2021 You could put a ridiculously small low limit like 0.000001 in your sigma characteristic so that a perfect 0.0000 shows up red. It's been a while, but I think probes that randomly lose their qualification also lose their qualification date. You might investigate the value of getProbe().probeDate on a probe that you know has lost its qualification. The documentation also lists a getProbe().calibration that is supposed to provide a yes/no value for whether the probe is qualified or not. I haven't tested, but you could give that a try. Link to comment Share on other sites More sharing options...
[Ch...] Posted April 13, 2021 Share Posted April 13, 2021 I use result element with sigma tolerance max value(PCM getProbe, etc.). We report out to either 6 decimal places in inches. Calypso could use a better probe qual result printout.. Link to comment Share on other sites More sharing options...
[Cl...] Posted April 14, 2021 Share Posted April 14, 2021 Please sign in to view this quote. Sorry, didn't read the entire paragraph. I've had the same thing happen to me as stated above. Link to comment Share on other sites More sharing options...
[Me...] Posted April 14, 2021 Share Posted April 14, 2021 Please sign in to view this quote. Ahhh got ya. My Cal program is set in MM for decimal place purposes but I have a tolerance in the result element of ± 0,0005mm for the purpose of it calibrating to my liking. I may be overzealous with it but it gets the job done! I've never had an issue where it didn't complete the qualification that you're talking about. That would drive me insanse. 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