Startup Dialog

The Startup dialog specifies job-related boot-time options for an In-Sight vision system, including the default job and Online/Offline status. User-related startup parameters are specified in the Options dialog.

Note:
  • In-Sight vision systems must be manually restarted before changes will take effect. Similarly, the In-Sight emulator must be disabled and re-enabled from the Options dialog before modified Startup settings will take effect.
  • No warning is given if the specified startup job does not exist (for example, after the job has been deleted or renamed).
  • A job saved in a Job Server can also be used as a default job, and automatically loaded to the vision system at startup. Use the Job Server Settings dialog to enable and configure the Job Server.

To Display the Startup Dialog

  • On the Sensor menu, click Startup.

     

     

    When a Job Server is enabled, the following dialog is displayed:

Startup Dialog Controls

  • Load Job on Startup: If this checkbox is checked, the selected job will be automatically loaded on startup. The list contains the jobs stored on the connected vision system/sensor, SD card installed to the connected vision system, or emulator.
  • Load Remote Job on Startup: If this checkbox is checked, the selected job will be automatically loaded on startup. The list contains the jobs stored on the Job Server.

    Note:
    • This checkbox is displayed only when the Job Server is enabled in the Job Server Settings dialog.
    • When the Job Server is enabled, a job saved in the Job Server can only be selected. If a job saved in the vision system should be loaded at startup, disable the Job Server.
  • Start the Sensor in Online Mode: If this checkbox is checked, the active In-Sight vision system/sensor will boot into Online mode.

    Note: As a safety precaution to prevent unintended activation of external devices such as robots, the In-Sight vision system will not automatically acquire an initialization image on job load when the Online checkbox is checked. This will result in slower than normal job processing time when the first acquisition trigger is received. Subsequent images will be processed at the normal speed.