Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Easy Heading Macro
headingIndent40
navigationTitleOn this page
selectorh2,h3
wrapNavigationTexttrue
navigationExpandOptiondisable-expand-collapse
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 scripts 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 the background while a project is edited. 

The Build selection has two information tables:


Column
width70%


Column
width30%

Messages show the current status of each script and display regarding in regards to potential error errors or warnings on the logic.

History shows how many the number times you executed a whole build to for this project.



Tip

 It not necessary to execute the Build command when editing the project, that happens in background. Only do a Build The Build command does not need to be executed after a project is edited as it happens automatically in the background. The Build command only needs to be used as a final verification before putting in production, or to create a Build Number for versioning.

On this page

Table of Contents
maxLevel2
stylecircle

More on the QuickStartGuide

Page Tree
rootProject Configuration Overview

a project is deployed or for when a build number is needed. 






Test and Startup the Project

The Test feature lets you run the a project in test mode, which means enabling . This enables protections that allow it a test project to run even on the same machine that where the project is running in the startup mode. The During test mode, the Historian and Alarm logging functions are directed to use temporary files instead of the database that is defined database for the project production.

Optionally you 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

The Startup command is where you configure how your project will run in production mode. This means enabling allows the Historian and Alarm logging functions to use the databases as that are defined in the project instead of the temporary files that were 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 mode.

The Online Configuration checkbox allows you to establish on-line an online configuration. When the Project project is running, you can attach to the execution, which means modifications to the project we be shown in the running project when madeaccess the project to debug or execute any modifications






Publishing Your Project

Click on the Publish icon.

The Publish command creates a read-only, protected version of a project suitable for deploying that is suitable to be deployed in the field.

When the Publish command is executed, a new Project file (with extension "tengtrun") is created with the version number selected. The Published Projects ("tprojtrun" extensions) are similar to the current project (".projtproj" extension) and can be opened only in read-only mode. This provides you with a safe backup version of published applications.

Info
titleNote

It is not necessary to publish the project, unless you want to create A project does not need to be published unless a read-only, protected version of that the file is warranted. Otherwise you can just copy , the project file just needs to be copied in the target computer.