[Jo...] Posted Monday at 04:56 PM Share Posted Monday at 04:56 PM Hi, I looked through the help file and am not finding the proper way to change a header line (if it's possible). I created a copy of the standard protocol.ptx. For this, lets say I want to change "variant" to read "cavity" on the report. It looks as though there are attribute key #'s assigned to some of the standards. Thanks! Link to comment Share on other sites More sharing options...
[Th...] Posted Monday at 05:25 PM Share Posted Monday at 05:25 PM If you just want that to say "Cavity" then you delete the variable text and type what you want. You don't need to change attribute key values or anything. Link to comment Share on other sites More sharing options...
[Jo...] Posted Monday at 05:44 PM Author Share Posted Monday at 05:44 PM Ok. I just need the header to populate next to the line "cavity" with any number I input and show on the report... Link to comment Share on other sites More sharing options...
[Th...] Posted Monday at 08:17 PM Share Posted Monday at 08:17 PM Oh, this is one of the existing parameters. In that case, you should be able to replace the variable text with other variable text. The line you had boxed in your first picture would be ${Localization.AttributeKey.Description(41)} or you can directly type Cavity, and your actual cavity number would be called with ${Qdb.Measurement(41, -1)} Cavity also doesn't need to be checked for measurement plan, only for run. 2 Link to comment Share on other sites More sharing options...
[Jo...] Posted Monday at 08:26 PM Author Share Posted Monday at 08:26 PM Thanks Thomas. So I'm assuming there is a list of these existing parameters and their associated attribute number(s)? i.e. Cavity & 41 Link to comment Share on other sites More sharing options...
[Th...] Posted Monday at 08:45 PM Share Posted Monday at 08:45 PM Sort of? If you have the bubble help option enabled on Calypso proper, which is under the ? menu, then when you have the header parameter window open you can hover over a spot that will show its associated variable. There used to be a little icon that would appear, but now you have to eyeball it. 2 Link to comment Share on other sites More sharing options...
[Is...] Posted Wednesday at 08:53 PM Share Posted Wednesday at 08:53 PM (edited) Sort of building off of this, I created a txt file with my own individual inputs @ the start of a program run. Those being Serial Number, Operator, and CMM. Mainly due to wanting to pull into Gear Pro at the same time. Calypso reads my header parameters, start of program input works fine, and I have the report header updated to reflect the PiWeb reporting target. However I cannot get it to show up in the header. Screenshots will be attached, any help is appreciated. Edited Wednesday at 08:54 PM Full scope of issue Link to comment Share on other sites More sharing options...
[Ma...] Posted Wednesday at 09:27 PM Share Posted Wednesday at 09:27 PM Please sign in to view this username. Please use steps as Thomas Gorman posted right above you. You move mouse cursor above "?" column and row of your headers and it will show popup hint what needs to be written in PiWeb protocol. Then it should work if you have filled this header value in start parameters or when running. Link to comment Share on other sites More sharing options...
[Is...] Posted Wednesday at 09:33 PM Share Posted Wednesday at 09:33 PM Please sign in to view this username. Please see attached Link to comment Share on other sites More sharing options...
[Ma...] Posted yesterday at 06:18 AM Share Posted yesterday at 06:18 AM Please sign in to view this username. Can you show how your problem looks like? From posted pics it looks fine and as it should be. Link to comment Share on other sites More sharing options...
[Is...] Posted 22 hours ago Share Posted 22 hours ago When I run my program and the calypso report comes out, all of the fields that I have put in are coming up as blank. I have verified that the correct template is being used and I even created an additional one in case the one I was using was corrupted. Link to comment Share on other sites More sharing options...
[Sv...] Posted 21 hours ago Share Posted 21 hours ago (edited) Ist bei Vorbereiten-Ergebnispräsentation-Editor für Benutzerdefinierte Protokollkopfvariablen die Eingabe erlaubt und die Zuordnung richtig? Edited 21 hours ago 1 Link to comment Share on other sites More sharing options...
[Ri...] Posted 20 hours ago Share Posted 20 hours ago Yes. It is better to just map them, and use the K value instead. I'd only rely on the Qdb.Property if I went beyond (10) userfields. 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