Deploying with a ViDi Tool Editor
If you will be deploying your application with a ViDi Tool Editor, you will need to make sure that the Deploy Training Workspace property of the associated ViDi Sub Task is set to True.
This will ensure that an additional folder, TrainingArchives, is added to your Runtime project deployment folder. This will ensure that when you access the ViDi Tool Editor in your deployed application, the associated training archive is exported, and the associated Workspace is loaded.
This ensures that if the ViDi tools are retrained during deployment, you can then import the updated training Workspace back to your project, and export an updated runtime Workspace (or redeploy the application).
- You must have a training license if you will allow operators to retrain tools during Run Time Mode.
- If you have multiple ViDi Suite Sub Task blocks in your project, and you only have a runtime license for your deployed application, each ViDi Suite Sub Task block must have the Deploy Training Workspace parameter set to False. If one of the ViDi Suite Sub Task block's Deploy Training Workspace parameter is set to True, the deployed application will attempt to create the components for a train license, and then fail when that license type is not available.
- If you will be deploying your application on a separate PC, the entire Deployment Folder must be copied to the new PC. In addition, you must have Designer, VisionPro and ViDi installed on the PC, as well as a Cognex Security Dongle attached.