In order to use the VS2 to begin inspecting products, you will need to first build specific programs for the products or SKUs that will be evaluated. Programs contain the business logic for what the camera should be evaluating when running. As an example, you can build a specific program to verify that the labels on Product XYZ are being placed correctly. Programs are composed of four components: camera settings, inspection steps, trigger configuration, and output configuration. Once you have everything configured, you can begin running the programs to perform your inspections in real time.
Programs are configured on a per camera basis, so the programs that should be built depend on the type of evaluation being done and where it is being mounted on the line. If you have multiple cameras performing the exact same inspections, we have a tool called Cloud Sync that can be used to copy programs across cameras. This is discussed in more detail in the Cloud Sync section.
Depending on your use case, you can set up programs to match individual SKUs or multiple SKUs depending on the type of inspection being performed and how changeovers are done.