Piweb reporting

[[Ca...]]

Is there a way to not show _x, _y or _z when using caliper distance in Piweb reporting ?

[[Ma...]]

From what i know you can not remove that.

Maybe some formating in PiWeb editor, but i have no experience for that.

Try posting at PiWeb section - there are methods for removing unwanted things from protocol. Lookup in PiWeb section.

[[DW...]]

Please sign in to view this quote.

Seems like extra work but you could do result elements if you really don't want to see the Z

[[Ca...]]

yes I had the same idea.

[[Ma...]]

Also - if you want to get rid of it because of dimension name goes into QC app, then i am doing naming as "317_5; some text" - this will report dimension like you have, but i am saving that into QDAS and with LUA script i am getting rid of everything after ";"

So i reduce that like this "317_5; left_Z" -> "317_5"

[[Ri...]]

 

[[Mi...]]

Right click on the caterpillar distance and select "Rename subcharacteristics" and you can use a name of your choice.

[[Ri...]]

Dang - I always forget about that. So much simpler than my solution. Haha. 

[[Ma...]]

Please sign in to view this quote.

From what version is this possible? I also forgot that, but because of old Calypso it's gone from memory.
Funny note - available only for roughness and simple distance :-) not sure about that

[[Da...]]

Isn't that the difference between "caliper" and "virtual caliper"?

[[Je...]]

Please sign in to view this quote.

I realize this is the current standard way to hide the coordinate subtitle, but it's honestly tedious and makes me think that there must be a better way.

[[Ba...]]

I'm pretty sure it would report both features but to get our caliper distance characteristics to report to the SPC software we use, we have to use a result element with a formula to drop the coordinate subtitle. We don't use PIWeb other than to report out calibration results. The caliper distance characteristics may be able to be hidden after using the result element? Just an idea  

getActual("Caliper Distance Feature").actual 

[[Ri...]]

If you are exporting to a 3rd party SPC software via the Table File, I'd look into just creating a Python (or whatever coding language you want to) to parse the data for you.