How to suppress extra data from all PiWeb reports?

[[Ri...]]

I need to suppress extra data from PiWeb reports in particular with True Position characteristics.
this "(M)" characteristic needs to go.

I know I need to take a class for PiWeb, because I can barely understand what the templates even have on them. They look nothing like the layout at display or print.

PiWeb mask Characteristics.jpg

[[Ja...]]

Bump. I would like to know how to do this also.

[[Br...]]

I wish the additional printout info looked better there too. It was nicely arranged in the custom printout. Now with the ".x" and ".y" along with tolerances on those, its really confusing to everyone who looks at it.

[[Te...]]

There is a way to get rid of the that line of the report. Let me double check if it something I can share. If I can't share the document I have, I will create a new one that I can. I have many customers who want this removed as well as the tolerances in the support data. Should be able to share the .ptx file when I get it done as well..

[[Te...]]

Here is my first attempt at changing the report NO MMC LINE, NO Tolerances and some other things to make the support data (additional results) a little easier to see.

There are some things I am not sure about, how it was done, like the removal the position icon and the covering up of the pass fail light and the bar graphic. I know that it is a box with probably uses the same string I created (to remove the upper and lower tolerances) to tell it when to generate I am just not sure how to do that....YET.

Let me know what you think please. I am curious of what you would change. I thought of replacing the upper and lower tolerance with BASIC and the other thing I am thinking about is the support data should I leave it just X, Y, or Z or change it to X Value, Y Value, or Z Value. Should I tab the support data another time to get it closer to the measured value?

I am pretty sure I could modify the code to remove the Radius and Angle tolerances if the position is cylindrical just haven't tried it yet.

I still have not had time to verify if I can share how I did this this yet because I did not do it all myself. If I can figure out how the boxes are created then I can create my own guide and can share that.

Please let me know what you all think.

In the attachment the top is the modified protocol and the bottom is the standard protocol

STANDARD COMPARED TO MODIFIED.JPG

[[Te...]]

Found out how to cover the icon and stuff it is a text box, colored white, with conditions.

I also have it working for cylindrical coordinates.

Just noticed on my report that the filtering method (GX, GG, etc...) is removed might be because the .ptx was created in an earlier version of Calypso will try again with the 2018 and see if they return.

ADDITIONAL RESULTS ANGLES AND RADIUS TOO.JPG

[[Ma...]]

Please sign in to view this quote.

💡 💡

Ted, wow cool report.Aber wie kann ich es abändern es ist so viel übersichtlicher 💡

[[No...]]

I've used text boxes to cover things in a similar way. You can define as many conditions as you want and format the box in different ways. But I wonder why all the other design elements are not nearly as versatile.

Personally, I think it's a VERY tedious way of solving such simple tasks as to cover up an icon. 30 years ago things were done like that and people were happy with it, but a 21st century software that comes with an "Industry 4.0" label on the box should be capable of more elaborate ways.

Nevertheless, here's something I also tried, making that condition thing a little more versatile. Maybe it can help:
Instead of just analyzing a single value or variable in the text box you can also make a more complex formula which encodes the results of a number of conditions ("Greater", "Less", "Equal" etc.) in a number by multiplying each boolean result with a distinctive value and adding up all the results. If a condition is false, the the value is multiplied by 0, so nothing gets added. If it's true, the distinctive value is multiplied by 1, so the value gets added. The resulting number represents the state of all the conditions and the formatting conditions can act accordingly. It's like setting single bits in a byte. The following simple example checks the state of the nominal dimension and spits out different values for different states:

1 = greater than zero
2 = less than zero
4 = equal to zero
8 = there is no nominal dimension

$((${Greater(${Qdb.Characteristic(2101)}, 0)}+2*${Less(${Qdb.Characteristic(2101)}, 0)}+4*${Equal(${Qdb.Characteristic(2101)}, 0)}+${ifnv(${0*${Qdb.Characteristic(2101)}}, 8)}))

You may be able to do this with formatting conditions alone, but with such a formula you can also check the state of many different variables at once.

[[Te...]]

I agree the box is very easy to use. You could use 3 separate boxes to cover the data you want to hide but I like the string to remove the tolerances and change the names.

The conditions are really easy for this. I have 5:

Contains .X
Contains .Y
Contains .Z
Contains .R
Contains .Angle

if any of these are in the name fill the box white.

[[Ri...]]

Thanks for the replies, but this is over my head. Its like a stealth helicopter just hovering and I dont know its there. 🤣

[[Te...]]

I can try and get you the .ptx file once I have it created and try it on a couple of machines. I am training and demoing for 9 out of the next 10 work days so you are looking at sometime late December before it is ready.

[[Ri...]]

Please sign in to view this quote.

Your offering help, I can wait.
Thank you.

[[Ri...]]

**Edited to fix error in expression.

Hey everyone. I get the question for removing the .(M) characteristic a lot, and I recently discovered that the name filters support regular expression.

If you're interested in trying this method. You need to highlight the table, copy and paste the string below into the Name filter, and click the blue arrow button to transfer all filters to the table.

Regular Expression to copy/paste:
{^((?!\.\(M\)).)*$}

[[Ja...]]

Is there a trick to high-lighting the table? I can only select small chunks at a time.

[[Ri...]]

I like to use the page structure tab.
You can also use escape to move up a level. If you click on an element in the row, then click escape you will have the row highlighted, press escape again and the table will be highlighted.

[[Ja...]]

Rita, I copied your name filter, pasted it, and transferred it. That eliminated the entire report. The only thing I get now is the header.

[[Ri...]]

Apologies, there was an error in the expression. This one should work.

{^((?!\.\(M\)).)*$}

[[Ja...]]

Thanks Rita. That works better.

[[Ri...]]

You're welcome. Glad it's working.

[[Ri...]]

Please sign in to view this quote.

Where can I find reading material on these codes?

[[Er...]]

It looks like regex in C# to me.

Thats why piweb is so "sharp" 🤣

[[Te...]]

Here is the fruits of my labor. I also made it so the Profile Support data is easier to read and modified the Name/Measured/Nominal/+ tol/- tol line so it looks cleaner. It is not letting me attach the .ptx does anyone know how I can attach it?

Let me know what you think of the final version. The .ptx file would go to C:\Users\Public\Documents\Zeiss\CALYPSO\protocol\PiWebReportingTemplates it should show up in the Generic Template section.

If I can't get it to attach on the forum I am happy to email the .ptx to you. Figured it out it is in the zip file. 😃

Normal.pdfModified PiWeb Report.zipNormal.pdfModified.pdf

[[Te...]]

So there are some cool side effects of my Custom PiWeb report. All the support data seems to be effected so when you do Perpendicularity, Coaxiality, and etc. you get the simplified view which helps it stand out as support data. I thing this makes the report a lot easier to read.

[[Ri...]]

I would start with Microsoft for resources on regex. Here is one I like:
https://docs.microsoft.com/en-us/dotnet ... -reference

You can also google things like, "What is ?! in regex?" There are a lot of discussions out there that have good examples.
(If you're curious, ?! says do not include the following string)

[[Ri...]]

Please sign in to view this quote.

I appreciate all the information, it looks as if your using Calypso 2018?
I'm currently on 2016 and 2017 on our offline seat and we will only be upgrading to 2017 for this new year.
Any chance of a version 2017 of the "ptx" file?