[Je...] Posted December 6, 2022 Share Posted December 6, 2022 . Hello. What is the header variable to display the field labeled in Calypso as "Part Name." Currently, the "Part Name" variable in PiWeb shows the name of the measurement plan, which is not necessarily the part's name. . Link to comment Share on other sites More sharing options...
[To...] Posted December 6, 2022 Share Posted December 6, 2022 see attachedScreenshot 2022-12-06 150710.jpg Link to comment Share on other sites More sharing options...
[Je...] Posted December 6, 2022 Author Share Posted December 6, 2022 Please sign in to view this quote. . Thanks, Tom. Variable #1342 provided the text I was looking for. However, for some reason my PiWeb says that variable 1342 is "inspection plan name." It's like the two variables got switched somehow. It is probably localized to my install. I'll fiddle with it a bit and see if I can fix it. .title_of_part_name_variable_in_piweb_seems_backwards.png Link to comment Share on other sites More sharing options...
[Ka...] Posted December 7, 2022 Share Posted December 7, 2022 Hi Jeff, To be honest: ItΒ΄s a mess with this key-numbers! I just don't understand why there doesn't seem to be a simple list of all key-numbers! We run allways in the same issue: Where to find the right key. And if you thing you have found it, it will switch inside of PiWeb. π‘ OK: 1) Switch on the bubble help at top menu "?" 2) Jump to protocolhead parameters, move your mouse slowly along the right side of the description of the parameters. You will see the origin and key number ( hopfully ) 3) You must activate the protocol head parameter AND insert a value. Other wise you will get in PiWeb Designer the message that this key is not valid... 4) Set the origin and key and... sometimes it will work. Here the key which is working for partnumber: ${Qdb.Part(1342, -1)} But if you use the ${Localization.AttributeKey.Description(...)} for the description it will be set to 1342 too. But this is the "Creation date" in this case. Set ist to ${Localization.AttributeKey.Description(1002)} In the Example I set the partname to "Aalfred" π Regards Karsten5.png4.png3.png2.png1.png Link to comment Share on other sites More sharing options...
[Je...] Posted December 9, 2022 Share Posted December 9, 2022 Here is your list. It is on your hard drive as well. All manuals are by default for each Calypso installation. C:\Program Files (x86)\Zeiss\CALYPSO 7.0\userinfo\manuals\en Calypso_02_PCM.pdf Link to comment Share on other sites More sharing options...
[Ka...] Posted February 23, 2023 Share Posted February 23, 2023 Hi Jeffrey, Sorry to dig up this thread again... π We are looking for key-numbers again. I would like to reproduce the documentation you have given here myself. The documentation you listet can be find in file Calypso_basis.pdf not in Calypso_02_PCM.pdf. Nevertheless, I am familiar with this list. However, it is not complete. π Example: There is a K802 ( Qdb.Measurement() ) which can be used after extending PiWeb database in Extra->Configuration->Working Environment->PiWeb reporting->Database extension ( Sorry its just an English translation of German menue ). This valid key is not documented anywhere: At least not in one of the pdf files or in the html help for CALYPSO 7.4. Best regards Karsten Link to comment Share on other sites More sharing options...
[Gu...] Posted April 23, 2023 Share Posted April 23, 2023 The database extension is a function from the PiWeb Server solutions :PiWeb sbs/cloud/enterprise. Here are the PiWeb variables defined in the templates => PiWeb planner/Administration/Configuration/Templates CALYPSO can import the predefined templates from the PiWeb planner The K Number and description can also be found simply as follows: CALYPSO PiWeb reporting plus GUI: Show measurement (or show characteristics) Right mouse on column header => K Number and description 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