XactMeasure, TP cylinder bug?

[MrComment]

Think I discovered another bug today.

In regards to v4.1 XactMeasure.

I'm dimensioning a cylinder. The dimension of size tolerance is immediately ignored and set to similar to "1XØ8 0/0". Also any datum features within the FCF also loose their dimensional tolerances as well.
Going to the edit window and editing this dimension, I re-enter the dimensional tolarance for the feature set then also click Advanced, set all the D1 and DF tolerances, check Update feature. Click apply, rerun the report.

I can then verify that that Xactly what I dont want has happened again, but with one minor difference, only the Datum feature tolerance is applied, and the tolerances for cylinders I want to TP of course still +/-0.

After Re-re-editing/verifying the dimension, the dimensional tolerance is still shown as I set it within the Advanced settings, but it doesnt show up on the report as shown in the advanced setting tab of the dimension.

If I construct a projected circle at the base of the cylinders. And do the TP of the circles instead, the tolerances come right in for all of the features, including the Datums.

[cmmguy]

Why do you insist on calling PCDMIS, XactMeasure. I am aware of the previous relationship of XactMeasure but what is your point?

[Jan d.]

Think I discovered another bug today.

In regards to v4.1 XactMeasure.

I'm dimensioning a cylinder. The dimension of size tolerance is immediately ignored and set to similar to "1XØ8 0/0". Also any datum features within the FCF also loose their dimensional tolerances as well.
Going to the edit window and editing this dimension, I re-enter the dimensional tolarance for the feature set then also click Advanced, set all the D1 and DF tolerances, check Update feature. Click apply, rerun the report.

I can then verify that that Xactly what I dont want has happened again, but with one minor difference, only the Datum feature tolerance is applied, and the tolerances for cylinders I want to TP of course still +/-0.

After Re-re-editing/verifying the dimension, the dimensional tolerance is still shown as I set it within the Advanced settings, but it doesnt show up on the report as shown in the advanced setting tab of the dimension.

If I construct a projected circle at the base of the cylinders. And do the TP of the circles instead, the tolerances come right in for all of the features, including the Datums.

Yes, I have found a similar issue.

It seems to me that inside the XactMeasure dimensioning, the software is trying to do some analysis whether the call is indeed valid. If it deems the call invlaid, it seems as if it does not accept it and reverts to something that is not what needs to be entered.

I think this one ought to be called in.


Jan.

[MrComment]

Why do you insist on calling PCDMIS, XactMeasure. I am aware of the previous relationship of XactMeasure but what is your point?

Im refering to the XactMeasure GD&T as a component within PCDMIS v4.1 as opposed to the Legacy style dimensions.

[JamesMannes]

As a side note, BNS bought a software company back in the early '90's that made a software called Xactmeasure and they must have integrated that software into their latest version DMIS.

Another side note,
Similar results have been noticed by myself re: portions of the Xactmeasure report not visible within the report window. Mr. Comment I believe that you made note of this last week. I have been working through this with Doug Sjogren for a couple weeks now and have, as of today contacted BNS again to remind them of this pervasive issue. At this time I will not be using Xactmeasure dimensioning until this is resolved.

[Jan d.]

As a side note, BNS bought a software company back in the early '90's that made a software called Xactmeasure and they must have integrated that software into their latest version DMIS.

Almost right.

Back in the bad old days, when B&S did NOT own Wilcox, B&S marketed a multitude of competing software packages (remember Tutor, Master, MM4, Avail, PC-DMIS (over which they had virtually no control), etc etc etc etc) that all did the same thing. Instead of chosing one, and focussing all the software efforts on that one, B&S choose to develop another piece of software. They hired Chris Garcia for that and set up a whole team of developers to focus on this new and exciting development. Their brainchild was called XactMeasure. But instead of offering the customer a clearer choice of software, they, in effect, added one more package to the already confusing and competing mix of software choices.

XactMeasure had a lot of potential, but B&S disintegrated around them before it was bullit proof and market ready. As always, timing is everything and they missed the boat: B&S was in terrible shape by the time they started to be ready for market.

When Hexagon bought B&S, they refused to buy XactMeasure and spun it off. Garcia consequently quit and is now with SolidWorks. Hexagon bought Wilcox instead. Cancelled all other packages and focussed all software development effort on PC-DMIS.

Somehow Hexagon must have brought XactMeasure back into the fold again, and they have resurrected that name when referring to the new style GD&T dimensions. Since there are so many problems with that new style GD&T, you see that name pop-up so much lately.



Jan.

[cmmguy]

Thanks Jan. I know the old connection but did not understand the new connection.

[MrComment]

Mr. Comment I believe that you made note of this last week.

Ya I know Ive found myself going on and on quite a bit these last couple of weeks. Sometimes about similar issues. With so many issues though and sometimes just not being sure if its me or the software, it makes for a painful learning curve.

Regardless I'm hopefully for the next version.

[JamesMannes]

Well, I was close (not). Thats what I gathered from some stuff on the net.

As a side note, my problem with Xactmeasure was rectified this morning when I did another uninstall of PC-DMIS 4.1, but when done with the uninstall I went back and made sure everything was deleted from the "program files" area. Lo and behold, no, everything was not deleted, in fact, the only thing left was the REPORTING folder and various files. I could not delete the WAI folder until I chose only the PCDShellextension.dll file, deleted that, and then I could delete the WAI folder and REPORTING folder. Did a restart, installed PC-DMIS 4.1 and now my Xactmeasure stuff looks correct. If I didn't say what was wrong before it was a problem from CMM to CMM. On my Chameleon I got the whole enchilada(Diameter, TP, datum shift, and summary of cartesian coordinates). On the LK, all I got to report was Diameter. Now both machines look the same. Ye ha!!!
Now you might ask why this happened, but at this point I don't care I was able to fix it and that's good enough for me. It has been reported to BNS Tech Support along with a detailed description of how I rectified the situation. Bill is in the mail.