hexagon logo

XMLStats to QC-Calc

Hello,

We recently switched to PC-DMIS 2023 and QC-Calc 4.0 and are trying to collect data using the GD&T features vs the old legacy dimensions.

We've been trying to get XMLStats/ON to work in a way that makes sense and we're constantly running into issues with it.

We run multiple parts in fixtures, we measure over a loop and so far, the only way we can get it to work is to put the Tracefield with the Part number at the very end of the program. If we put it anywhere else, it won't collect the data, or it will cause QC-Cal to crash.

When it works it does fine(ish) but if the program runs into an issue (parts not seated right, the probe not hitting the same on part 8 as part 1) it outputs to a blank QC-Calc file. If it crashes on part 8 and we start it on part 8 in the loop it then starts printing each measurement in its own window when it was collecting altogether before (Ie, part8_measure1[8], part8_measure2[8], part9_measure1[9], part9_measure[9], etc.). It's not the end of the world but it also is incredibly frustrating.

It also seems that XMLStats doesn't allow QC-Calc to measure in real time and we have to wait the hour and change for the program to run to see if we got what we wanted.

Does anyone have experience with how QC-Calc works with XMLStats or shed any light on how XMLStats works in PC-DMIS that may not be doing what I think it's doing?

In QC-Calc we're using the PC-DMIS 2012 XML Statistics (though I swear we updated QC-Calc to have the 2022 option).

I know this is a case of two different pieces of software trying to communicate with one another, but I feel like there's something simple I'm missing to get this to work the way we'd like it to.

Parents Reply Children