You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

This page covers software licensing and product details. You'll learn about our three main licensing methods (Hardkey, Softkey, Online Activation), and the license migration and termination procedures. We'll detail the types of licenses we offer and classify our products by series, model, and family. Lastly, we'll touch on protocols integration using .NET-managed code.

On this page:


About Express Solutions

When you install the product, you can only edit and run Express family Solutions until your computer is licensed. 

Warning about Express Mode and unlicensed computers

When your Solution runs in Express mode, some advanced features are disabled and communication with external devices only runs for half-hour sessions. 

The Product Family Express is a useful option when you want to create Solution examples and demos to be shared with users that not necessarily will have a product license.

To license your computer, you need to either use a physical dongle (hard key) or create a softkey license, as described here.


Licensing Methods

Hardkey

A hardkey license is stored in a flash drive that is sent to the client. The advantage of using a hardkey is that the license is not linked to a single computer like it is with softkey licenses. 

If the flash drive goes missing, a new license must be acquired. There is no replacement. 

Softkey

The softkey license is generated by the equipment SiteCode. In order to obtain this file, do the following steps:

  • Go to the Solution Manager → License and click Get site code.
  • Send the generated file to a Tatsoft employee, and they will generate a license key.
  • Click the Load license key button on the License Information to load the received key.

Online Activation

With the online activation, a softkey license is generated, which is not linked to a computer.

The advantage of using an online activation license over the regular Softkey license is that it can be deactivated and reactivated in order to switch equipment.

To activate a license, go to the Solution Manager → License Information and click the OnlineActivation button. Enter your SerialNumber and ActivationCode in the popup window that appears. 



License Types

Engineering and Runtime

Users are allowed to both edit and run a Solution.

Runtime

Users are not allowed to edit a Solution. However, the ‘.tproj’ file can run without limitations.

A Solution can be edited even if it is located on equipment licensed for RuntimeOnly. To do so, a product with an Engineering license can perform a remote connection to the RuntimeOnly (through the Solution Manager → Server). That way, a single Engineering license can edit multiple Solutions deployed on site. 


Developer

A Developer license is only used for specific Solution development on site. 

Using a developer license is not recommended when the product is installed in local machines due to the short expiration date; it is set to expire 1 to 2 days after activation. 


Product Model and Family

The number of Max Communication Points available for a Solution can be changed according to the license type.

The existing licenses types are:

  • FrameworX
  • FactoryStudio
  • EdgeHMI
  • EdgeGateway

The current License type, designed Product Family, and Product Model can be found in the Your License. There are many communication protocols available regardless the license. However, some communication protocols must be acquired separately, such as OSIsoft PI and DNP 3.0.

FrameworX Unlimited

Product Specification
Product FamilyFrameworX
Product ModelUnlimited
Canary historian
Default CodeVB.NET and C#
FrameworX Unlimited
(tick)For Enterprise solutions
(tick)Everything included on FactoryStudio and more
(tick)Unlimited clients (.NET Smart Client, Web, HTML5, iOS)
(tick)Unlimited Points IO
(tick)Unlimited Drivers
(tick)Unlimited (256 channels) different for any model, in practice there is no limit.

FactoryStudio

Product Specification
Product FamilyFactoryStudio
Product Model15000
Canary historian
Default CodeVB.NET and C#
FactoryStudio
(tick)Powerful and flexible tool for data collection and management, dashboard and report creation, and more.
(tick)Everything included on Edge HMI and more.
(tick)Scalable, by the IO number & clients
(tick)70+ drivers included at no extra cost
(tick)Advanced scripting: C#, VB.NET, Python
(tick)Redundancy available
(tick)SDK Extensions/Toolkits included

EdgeHMI

Product Specification
Product FamilyEdgeHMI
Product Model1500
Canary historian
Default CodeVB.NET
EdgeHMI
(tick)Connect with drivers and PLCs, build HMIs, and more.
(tick)Everything included on EdgeGateway and more:
(tick)Scalable, by the IO number & clients
(tick)70+ drivers included at no extra cost
(tick)Build Dashboards and Reports
(tick)Thousands of Symbols
(tick)8 different channels for any model, as the number of points is limited to 1500, in practice this is also a hard limit to reach.

EdgeGateway

Product Specification
Product FamilyEdgeGateway
Product Model1500
Canary historian
Default CodeVB.NET
EdgeGateway
(tick)Embedded device communications and processing at the edge or as flexible secure gateway
(tick)70+ drivers included at no extra cost
(tick)OPC UA Client/Server
(tick)MTT Client / Broker
(tick)Device Redundancy available
(tick)Unlimited Model – Unlimited (256 channels),
15k points Model – 16 channels,
75 points to 5k points Model - 4 Channels

Supported Features Matrix

The table below clearly and concisely compares features across different product families. Its primary goal is to aid potential customers, stakeholders, or team members understand which features each product family offers to choose the best one according to each business's requirements.

Product Features

Enterprise

EdgeHMI

EdgeGateway

Developer

Express (Trial)

Linux (Platform)
*Runtime only

VB.NET language

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

C# language

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

Script Classes

(tick)

(tick)

(tick)

(tick)

(tick)

(info)

Script Task SingleThread

(tick)

(tick)

(error)

(tick)

(tick)

(info)

Script Task MultiThreading

(tick)

(error)

(error)

(tick)

(tick)

(info)

Script Expressions

(tick)

(tick)

(tick)

(tick)

(tick)

(info)

Python execution

(tick)

(error)

(error)

(tick)

(tick)

(error)

OneDimension Array

(tick)

(tick)

(tick)

(tick)

(tick)

(info)

Multidimensional Array

(tick)

(error)

(error)

(tick)

(tick)

(info)

Multi-Level Templates

(tick)

(tick)

(tick)

(tick)

(tick)

(info)

SDK Extension/Toolkits

(tick)

(error)

(error)

(tick)

(tick)

Not applicable

Historian Table

(tick)

(tick)

TagHistorian Only

(tick)

(tick)

(info)

SQL Database

(tick)

(tick)

(tick)

(tick)

(tick)

(info)

SQL, NoSQL, Historian Connections

(tick)

(tick)

(error)

(tick)

(tick)

(info)

Store and Forward

(tick)

(tick)

(tick)

(tick)

(tick)

(info)

Canary Historian

(tick)

(tick)

(tick)

(tick)

(tick)

Remote only

Server Redundancy

(tick)

(error)

(error)

(tick)

(tick)

(info)

Report Designer

(tick)

(tick)

(error)

(tick)

(tick)

Not applicable

Report Symbols

(tick)

(error)

(error)

(tick)

(tick)

(error)

Alarms and Alerts

(tick)

(tick)

(error)

(tick)

(tick)

(info)

SMS & Alarm Notification

(tick)

(tick)

(error)

(tick)

(tick)

(info)

Audit Trail

(tick)

(tick)

(error)

(tick)

(tick)

(info)

All Alarms conditions

(tick)

(error)

(error)

(tick)

(tick)

(info)

Assets

(tick)

(error)

(error)

(tick)

(tick)

(info)

Publish

(tick)

(error)

(error)

(tick)

(tick)

Not applicable

Tracking Changes and Releases

(tick)

(error)

(error)

(tick)

(tick)

Not applicable

WPF Control

(tick)

(tick)

(error)

(tick)

(tick)

HTML5 Only

Hot Start

(tick)

(error)

(error)

(tick)

(tick)

(error)

Test Mode

(tick)

(tick)

(error)

(tick)

(tick)

On Window

.NET Client

(tick)

(tick)

(error)

(tick)

(tick)

(error)

.NET Smart Client (Web)

(tick)

(tick)

(error)

(tick)

(tick)

(error)

iOS

(tick)

(tick)

(error)

(tick)

(tick)

(error)

HTML5

(tick)

(tick)

(error)

(tick)

(tick)

(tick)

Dashboard Display

(tick)

(tick)

(error)

(tick)

(tick)

(info)

Trending

(tick)

(tick)

(error)

(tick)

(tick)

(info)

Plugin/Components

(tick)

(tick)

(error)

(tick)

(tick)

(info)

100s of Symbols

(tick)

(tick)

(error)

(tick)

(tick)

(info)

Integrate External Controls

(tick)

(tick)

(error)

(tick)

(tick)

Remote only

Diagnostic Tools

(tick)

(tick)

(tick)

(tick)

(tick)

(info)

Communication Points

up to Unlimited

up to 5000

up to Unlimited

 up to Unlimited

 500 points

(info)

Any Standard Driver

(tick)

(tick)

(tick)

(tick)

(tick)

.NET managed only

OPC UA Client / Server

(tick)

(tick)

(tick)

(tick)

(tick)

(info)

Device Redundancy

(tick)

(error)

(tick)

(tick)

(tick)

(info)

MQTT Client / Broker

(tick)

(tick)

(tick)

(tick)

(tick)

(info)

TagProvider

(tick)

(tick)

(tick)

(tick)

(tick)

(info)

Runtime execution

Unlimited

Unlimited

Unlimited

110  hours

2 hours

(info)

Engineering execution

Unlimited

Unlimited

Unlimited

Unlimited

30 days

(error)

(tick) Supported

(error) Not supported

(info) License based


Procedures to Migrate or Kill a License

Migrating from One Computer to Another

  1. Send the SiteCode file from the original computer.
  2. The SiteCode will be processed, and you will receive a temporary license to install on the original computer.
  3. Install the temporary license on the original computer.
  4. After installing the temporary license on the original computer, generate and send the SiteCode file from the original computer again. This verifies that the temporary license has been installed properly.
  5. Generate and send the SiteCode file from the new computer.
  6. The SiteCode will be processed, and you will receive the license for the new computer.
  7. Install the new permanent license on the new computer.

Migrate a Softkey to Hardkey License

  1. Send the SiteCode file from the computer.
  2. The SiteCode will be processed, and you will receive a temporary license to install on the original computer.
  3. Install the temporary license on the computer.
  4. Attach the USB LicenseKey to the computer.
  5. Generate and send the new SiteCode file after the temporary license has been installed.
  6. The SiteCode will be processed, and you will receive a LicenseKey file for you to load onto the computer with the USB LicenseKey.

Killing a License

  1. Send the SiteCode file from the computer.
  2. The SiteCode will be processed, and you will receive a temporary (3-10 days) license to install on the original computer.
  3. Install the temporary license onto the original computer.
  4. After installing the temporary license on the original computer, generate and send the SiteCode file from the original computer again. This verifies that the license has been killed properly.

In this section:

The root page @parent could not be found in space 93Draft.

  • No labels