 | Update Inspection UI FAQs |
Q: Why do controls on the custom Inspection Interface not appear in the Inspection Interface Indicators table?
The Inspection Interface Indicators table only contains indicators because the Update Inspection UI step is used to update the indicator values displayed on the selected custom Inspection Interface. Numeric, string, and boolean controls on a custom Inspection Interface can be accessed by any step that supports variables or previous measurement results.
Q: Why are some of the indicators on the custom Inspection Interface not listed in the Inspection Interface table?
The Inspection Interface table only displays indicators that can be updated by the Update Inspection UI step. Currently, Vision Builder AI supports numeric, string, boolean, and image display datatypes.
Q: How do I deploy an inspection using a custom Inspection Interface?
Once you select an Inspection Interface template or VI as the Inspection Interface for an inspection, the template or VI becomes part of the inspection file. If you make any changes to the selected interface, you must re-add the file to the inspection for the changes to take affect.
Q: Why does the custom Inspection Interface behave differently on the development computer than it does on the remote target?
When you are connected to a remote target, Vision Builder AI uses a local copy of the custom Inspection Interface VI on the remote target. This VI is not run, so any attributes that change when the VI executes or any control values that change programmatically, will not be reflected in the interface shown on the development computer. Connect to the remote target using a Web server to fully view the inspection behavior on the remote target.