Page Tree
Previous Releases
Running FactoryStudio Projects
The Run environment provides access to all project execution features. From the Main Menu, click on the “Run” icon. Then, click on the "Build" icon.
The Build feature compiles all of a project's displays and scripts for final verification before deploying the project for production. Build provides complete verification of an application's logics when preparing it for final production. However, this is not necessary during the development stage since all project modifications are automatically and transparently compiled in background while a project is edited.
The Build selection has two information tables:
| Column | ||
|---|---|---|
| ||
|
| Column | ||
|---|---|---|
| ||
Messages show the current status of each script and display regarding in regards to potential error errors or warnings on of the logic. History shows how many the number times you executed a whole build to for this project. |
| Tip |
|---|
It It not necessary to execute the Build command when editing the project, that happens in background. Only do a Build as a final verification before putting in production, or to create a Build Number for versioning. |
On this page
| Table of Contents | ||||
|---|---|---|---|---|
|
More on the QuickStartGuide
| Page Tree | ||
|---|---|---|
|
Test and Startup the Project
Test lets you run the project in test mode, which means enabling protections that allow it to run even on the same machine that the project is running in startup. The Historian and Alarm logging functions are directed to use temporary files instead of the defined database for the project production.
Optionally you can enable diagnostic tools to help resolve any issues you may be working through. You can also decide to disable any of the FactoryStudio modules during your test.
Running the Project
Startup is where you configure how your project will run in production mode. This means enabling the Historian and Alarm logging functions to use databases as defined in the project instead of the temporary files used in Test.
Optionally you can enable diagnostic tools to help resolve any issues you may be working through. You can also decide to disable any of the FactoryStudio modules during your test.
The Online Configuration checkbox allows you to establish on-line configuration. When the Project is running you can attach to the execution, which means modifications to the project we be shown in the running project when made.
Publishing Your Project
Click on the Publish icon.
Publish creates a read-only protected version of project suitable for deploying in the field.
When the Publish command is executed a new Project file (with extension "teng") is created with the version number selected. The Published Projects ("tproj" extensions) are similar to the current project (".proj" extension) and can be opened only in read-only mode. This provides you with a safe backup version of published applications.
| Info | ||
|---|---|---|
| ||
It is not necessary to publish the project, unless you want to create a read-only protected version of that file. Otherwise you can just copy the project file to the target computer. |
Overview
Content Tools
Tasks