Jump to content

How to suppress extra data from all PiWeb reports?


Recommended Posts

  • Replies 68
  • Created
  • Last Reply

Top Posters In This Topic

  • ---

    22

  • ---

    12

  • ---

    8

  • ---

    7

From what I see thru PiWeb, this simply masks the modifier from printing, but doesnt mask it from reporting,if it is out of tolerance you get a nice red dot.
A report is generated with no out of tolerance characteristics, I should say those that SHOULDNT be toleranced, will still report out of tolerance condtions via a Red Dot and a counter.
WHEN THEY ARE FALSE CONDITIONS!

This is so stupid that when stupid people see it, they say, thats stupid.
Hi Rick,

You are correct, we are only filtering on the table. We can apply the same filter to the container for the header and the counter and red dot should update there as well.

Could you clarify what you mean that the status is a false condition? The way that .M is calculated both TruePosition and TruePosition.(m) (or .l) should have the same status on the live Standard Protocol, if one is red both should be. This gets a little weird when you're looking at historical results, because the tolerance of the TruePosition changes, but the database only stores the latest tolerance value. So, when you're looking at historical values the .(m) characteristic is the only one that is valid.

How .(m) is calculated: (Measured Value)*(Tolerance without MMC/Tolearance with MMC)
Since Piweb, we have had too many reports showing the Red dot and 1 or more values out of tolerance.
When you go thru evey characteristic and or feature, none are out of tolerance or even close to rounding a high or low limit, yet Piweb still produces an out of tolerance report.
If I disable PiWeb, and use our original format, no problems.

The time spent on a part run to find an out of tolerance condition reported by PiWeb is becoming a cost issue.

How do I explain this to a customer?
Oh, this is just PiWeb, ignore the other 4 things Piweb says is OOT.
(I cant post an image due to this website limits)
  • 4 months later...
Hey some new info has emerged from watching the PiWeb training from the eCademy. The file names of the .ptx needs to remain the same as the Zeiss default name for the links to the graphics to "attach" to the report correctly. The training video is for 2017 so it might have changed but I am not 100& sure. Will have to do some testing but that is the first time I have heard that and thought I would pass it on.
  • 3 weeks later...
I had this problem as well, got in touch with Zeiss and although they try to push you into going for the training, I was able to get it out of one of the reps. Follow these directions and you should be all set, it has worked for me. If you need screenshots let me know.

Tested in PiWeb 6.2.15
Calypso 6.4.14

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

Remove .M or .L
{^((?!\.\(M|L\)).)*$}

Steps:
1. Highlight the table
2. Paste regex into Name field
3. Click blue arrow and select transfer name filter
4. Preview report to verify it worked
  • 1 month later...
  • 2 weeks later...
  • 2 weeks later...
Yeah, so I call Zeiss a LOT (Figured I might as well get that 7 grand worth of service packs out of them), if you save your report as a generic report then you do not have to do it individually, otherwise, you do. Also, I am having an issue now where the icons for my reports don't always show up. I told Zeiss and the response I got from them is we never seen this, weird, we are looking into it. That was 2 months ago 👩‍🏫
If you are using a custom PiWeb report from an older version to a new version you will end up with missing graphics some times.

Just a heads up for everyone Calypso 2019 removes the tolerances from the additional position results if you tell it to. I will write the exact path when I get back to the office but it is under Resources/Characteristic Settings Editor.
  • 1 month later...
It looks like there are some work arounds already for this. I didn't see anyone doing it the way I do it, so I attached a brief how to. It's really easy, let me know if any question and if it works for you.

Remove (M) with characteristic filter.pdf

  • 5 months later...
For the .(M) edit your StandardProtocol doing the following:

- Open your StandardProtocol for editing
- Click on Page structure on the left hand side
- Expand Main area
- Select Protocol
- With Protocol selected click on Data provider on the left hand side
- In the Name area at the top, enter {^((?!\.\(M\)).)*$}
- Click the blue arrow to the right
- Click on Only transfer name filter

That should remove it for you.
  • 3 years later...

×
×
  • Create New...