[Ri...] Posted February 22, 2019 Share Posted February 22, 2019 Hm, interesting. This one worked for me: {^((?!\.\(M|L\)).)*$} Link to comment Share on other sites More sharing options...
[Ri...] Posted February 22, 2019 Author Share Posted February 22, 2019 Please sign in to view this quote. Still not working in Calypso 2016 Only the MMC modifier is masked. Seems I can only do one or the other. Link to comment Share on other sites More sharing options...
[Ri...] Posted February 22, 2019 Share Posted February 22, 2019 Hopefully it's not an issue with 2016. I forgot the first few times to transfer the filter to the table. Can you verify that the new filter transferred by double clicking the icon on the table. Link to comment Share on other sites More sharing options...
[Ri...] Posted February 23, 2019 Author Share Posted February 23, 2019 Initial testing appears to be working now with either string: {^((?!\.\(M|L\)).)*$} or {^((?!\.\(M\)).((?!\.\(L\))))*$} Not sure why one has to verify the transfer after transfering the filter? Link to comment Share on other sites More sharing options...
[Ri...] Posted February 28, 2019 Author Share Posted February 28, 2019 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. Link to comment Share on other sites More sharing options...
[Ri...] Posted February 28, 2019 Share Posted February 28, 2019 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) Link to comment Share on other sites More sharing options...
[Ri...] Posted March 1, 2019 Author Share Posted March 1, 2019 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) Link to comment Share on other sites More sharing options...
[Te...] Posted July 22, 2019 Share Posted July 22, 2019 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. Link to comment Share on other sites More sharing options...
[Ma...] Posted August 8, 2019 Share Posted August 8, 2019 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 Link to comment Share on other sites More sharing options...
[Me...] Posted September 20, 2019 Share Posted September 20, 2019 Please sign in to view this quote. Does this method require you to do this for every inspection plan, or just once? Or does the filter apply to the template itself? I cannot believe this is still an issue. Link to comment Share on other sites More sharing options...
[Te...] Posted September 30, 2019 Share Posted September 30, 2019 If save it as a generic template you just need to chose the generic template in each program. Somewhere in the chain is the link to my Modifying PiWeb Report document should help Link to comment Share on other sites More sharing options...
[Ma...] Posted October 15, 2019 Share Posted October 15, 2019 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 👩🏫 Link to comment Share on other sites More sharing options...
[Te...] Posted October 16, 2019 Share Posted October 16, 2019 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. Link to comment Share on other sites More sharing options...
[Ng...] Posted November 25, 2019 Share Posted November 25, 2019 I would like to know how to run a sample of 20 parts and report it into PiWweb as a single report? Link to comment Share on other sites More sharing options...
[Du...] Posted November 26, 2019 Share Posted November 26, 2019 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 Link to comment Share on other sites More sharing options...
[Ed...] Posted May 7, 2020 Share Posted May 7, 2020 Please sign in to view this quote. Did you ever find out how to delete the 'M' ? Link to comment Share on other sites More sharing options...
[Ri...] Posted May 12, 2020 Author Share Posted May 12, 2020 Look up one post. Although I have found my current code doesn't work all the time and sometimes only partially. Link to comment Share on other sites More sharing options...
[Ri...] Posted May 15, 2020 Share Posted May 15, 2020 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. Link to comment Share on other sites More sharing options...
[Ch...] Posted March 28 Share Posted March 28 Can you show me how to change the name to: Contains .X Contains .Y Contains .Z Contains .R Contains .Angle if any of these are in the name fill the box white. and how to group XYZ positions. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in