Page Tree
Other Releases
Object Model and Namespaces
With most systems, you must create Most systems require creating a Tag or Variable for all internal properties , and you must create as well as custom logic for your projects. FactoryStudio allows your application to directly access all the business objects that were created in your project. This means that , i.e. user-created temporary tags are not required to manage the status of PLC network nodes status, the total number of alarms in a group, or the number of rows in a dataset. You Now you can now access runtime objects, and business objects (representing a network node), an alarm group or dataset, and then display the required information or take action directly through the object's built-in properties.
FactoryStudio has an underlying .NET object model with a 100% managed code, specifically targeting the development of Real-Time data management applications. The hierarchical object model includes the following top-level objects, which correspond to the main modules in FactoryStudio:
| Tags | Dataset |
Historian | Script |
Security | Server |
Alarm | Client |
Device | Info |
That The top-level hierarchy is implemented as .NET Namespaces. Each Namespace has the .NET classes and objects that are created when building a project configuration. Besides having the configuration settings, those objects also . These objects have runtime properties, methods, statuses, and statusconfiguration settings.
For instance that , the Tag namespace has contains all the tags that are in the application and each tag has of the tags have built-in field properties, such as Qualityas Quality, TimeStamp, Min, Max, Units and many others, etc.
| Info | ||
|---|---|---|
| ||
Tag.tagname1.bit0, tag.tagname2.timestamp |
When building the project configuration, filling input fields or creating scripts, the system always has the Intellisense auto-completion, which FactoryStudio has IntelliSense auto-completion for when you build a project, fill in input fields, or create scripts. This guides you to the any existing properties that are allowed to use according to what for the object you are editing . This feature allows and allows you to easily "drill down" to a specific property.
When accessing a project object in the .NET Script Editor, it is necessary to prefix the namespace with an "@" symbol in order to avoid conflict with the names of the .NET local variables names.
| Info | ||
|---|---|---|
| ||
In Script -> Tasks and CodeBehind, use:
|
The @ symbol at sign (“@”) is not necessary on Grids and Dialogs. Some input fields may require objects of only one type, such as Tag or Display. For these, the Intellisense IntelliSense will automatically guide you to the allowed required objects.
For some These concepts may seem abstract for users that don't do not have previous experience in .NET or similar object-oriented systems, those concepts are abstract at the beginning, but when learning . However, the power of these concepts will become clear when users learn the engineering configuration tools and the FactoryStudio modules, the power of those concepts will be clear. What is completely sure is that when getting used . When users get used to working with object models and Intellisense IntelliSense, the users realize that there is a huge productivity increment and you no longer accept working with systems lacking those features.increase in productivity so they no longer want to work with systems that lack these features.
SQL to the Core
Built-in Embedded SQL
Every FactoryStudio system includes a full-featured, embedded SQL engine. This which provides several the following advantages including:
- A It is a safe and secure location for your entire project configuration.
- It can be used as the historian database to log tags, alarms, and events on small to medium systems (up to 10GB of data).
- On Large large systems, it can be used as a local Store and Forward location , for when the remote database is not available.
- It provides an ideal system to store local runtime settings, retentive information, local recipes, schedules and tables, and queries when preparing reports.
Multiple Database Connections
FactoryStudio provides seamless integration with any third-party database, including Microsoft SQL Server, Oracle, MySQL, Informix, SQL Lite, PostgreSQL and others, etc.
Real-time Queries and Tables
Any data source with that supports ODBC, OLE-DB, or ADO. NET support can be connected with the application; an easy syntax allows you to create or customize any query or table search with real-time tags.
Advanced DataGrid
FactoryStudio provides a fully - featuredDataGrid object. The DataGrid object to present presents tables and queries from databases , as well as show shows the contents of any tag, asset, or real-time object. Just drop Drop the table, query, or tag to into the Grid Data Source to create front-end visualization or , edit any real-time object, or database.
Client-Server Architecture
Real-time queries can be processed either at from the server or from the client computer, asynchronously or synchronously. To achieve better performance, multiple requests from distributed clients are cached and synchronized at from the server.
Data Gateway
Connecting client queries through Firewall protected security zones, such as moving data between the Automation Network and the IT network, is no longer an issue. FactoryStudio provides a built-in firewall friendly data gateway. Data queries from clients are securely routed in a secure way through any FactoryStudio system.
| Tip | ||
|---|---|---|
| ||
Scheduling, Process Recipes, and real-time data consolidation made easy. |
.NET to the Core
Built-in Code Editor
FactoryStudio includes an integrated script editor for developers to create custom functionality for the an application. The editor provides a powerful set of tools to that help you test and evaluate your scripts. Debugging tools include assigning breakpoints, stepping into code, stepping over code, executing line by line, and watch watching values of objects changing change with each step.
Scripts are executed natively as managed code within the .NET framework, meaning you cannot create a script that would inadvertently cause the system to shut down. This provides a greater level of security and up-time for your application.
Server and Client Domains
Using the FactoryStudio script editor allows you can to create scripts that execute are executed on the server for a global reach, or they can execute be executed on the client side for a local reach.
Tasks, Classes and Expressions
You can create Tasks, .NET classes, and function libraries. In some cases, it may be more efficient or desirable to create one-line expressions, rather than full methods. For that purpose, FactoryStudio provides an expression editor allowing which allows access to all .NET operands and classes.
Object Orientation, Project Elements
All project elements , including (Tags, Datasets, Alarms, devices, and status of communications) are immediately accessible via IntelliSense, as they . As these are native .NET objects, no temporary tags calls are required. With a single move, you can transfer data from Tags to .NET external Data-data tables.
C#, VB.NET and Code Translation
FactoryStudio includes industry standard languages of , C# and VB.NET so engineers no longer have to suffer through using old , so engineers do not struggle to use old proprietary, single-threaded, or interpreted scripting editorseditors anymore.
Translate your code between C# and VB.NET anytime to better leverage your expertise.
Events and Scheduling
Tasks and expressions can be triggered to execute by date, time, condition, calendar, tag change, or interval. Execution is distributed among processes. For maximum system security and performance, each running process runs in its own application domain , and is isolated from the real-time database, for maximum system security and performance.
| Tip | ||
|---|---|---|
| ||
Online You can do online project changes and configuration configurations while running and debugging. |
Overview
Content Tools
Tasks