[Ja...] Posted February 11, 2021 Share Posted February 11, 2021 Thanks for the assist on that. Now just need to figure out how to have the value write to planner. Currently i have it saving under "Operator Note" (${Qdb.EditableMeasurement.Value(10099)}). But hen I need to go into planner and move the value over to the Actual column. Link to comment Share on other sites More sharing options...
[La...] Posted February 11, 2021 Share Posted February 11, 2021 Please sign in to view this quote. You need to right click on the text input field you have in your report and connect it to the Measured Value attribute. You have it writing the value to the wrong variable. Link to comment Share on other sites More sharing options...
[Ja...] Posted February 11, 2021 Share Posted February 11, 2021 I want to leave the Operator Note section as there are times when the operators need to write notes on parts that kick-out ( i.e. inspected with manual instruments andcome out good due to burrs/FOD etc). So are you thinking create a new text input field and have that one write the value? Link to comment Share on other sites More sharing options...
[To...] Posted February 11, 2021 Share Posted February 11, 2021 Please sign in to view this quote. Your signature states "Age is a physical Characteristic...." Is that a characteristic of size, orientation, form or location? Link to comment Share on other sites More sharing options...
[Ja...] Posted February 11, 2021 Share Posted February 11, 2021 Please sign in to view this quote. Definitely a characteristic of Form, lol. Link to comment Share on other sites More sharing options...
[La...] Posted February 11, 2021 Share Posted February 11, 2021 Please sign in to view this quote. My advice is to leave the actual text input field - where you want the measured value entered - as K1/Measured Value instead of Operator Note. Then, you can move the Operator Note field in your header. A measurement attribute is a note or piece of information that represents the entire measurement. If your Operator Note is set as a measurement attribute, the note that operators leave will represent information about the entire measurement and not just one characteristic. If you want the Operator to have a note field for every characteristic (ie. a note for Visual Inspection, a note for a Go/no Go, a note for height gauge measurement) that would essentially differ for every row in your table, then you will need to create a Measured Value attribute and that will tie the note to the actual characteristic instead of the entire measurement record. I hope that makes sense. Link to comment Share on other sites More sharing options...
[Ja...] Posted February 25, 2021 Share Posted February 25, 2021 OK, So I got the characteristics working, but now for some reason getting an error when trying to input the manuals (worked fine the first several times I tried it). The Error is in PiWeb Monitor "Value cannot be null. Parameter name source".PiWeb Planner.JPGPiWeb Monitor with error.JPG Link to comment Share on other sites More sharing options...
[Ja...] Posted March 2, 2021 Share Posted March 2, 2021 Please sign in to view this quote. FIXED - it was a known bug in 7.6.5, fixed in 7.6.6. So got a new wrinkle. I need to change it up a bit as I don't want the operators changing OOT characteristics without some sort of control. So I want to make a new line just for manual checks. I made a new Measured Value (#2, "New Value") that i want to use for the operators to put in the "corrected" value. Cant seem to get it to work. I have uploaded the .ptx file ( just need to rename it from .pptx to .ptx).Single Report.pptx 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