Page History

Creating an AccessType

To create and configure an AccessType, follow these steps:

1. Access Devices → AccessTypes.
2. Click on the plus icon.
3. Fill all the property fields with your desired configuration (see the table below for more details about each option).
4. Click Ok.

Image Added

AccessTypes Properties

The following table describes each configuration property when creating an AccessType:

OnDisplayOrServer setting

The OnDisplayOrServer AccessType is an excellent tool for solutions with many communication points but only requires data updates for some of them. It can help computers without the computational power to handle massive data exchange while maintaining other modules active. The OnDisplayOrServer operation process is divided into two aspects:

• On Display: On Display means that your DevicePoint will only begin reading or writing when the solution's display containing these tags is open.
  • Let us imagine a project with two displays, one for Line A and another for Line B. Each display has its specific Tags added to it.

Overview

Access types define the specific methods by which values are read and written for each specific data point, such as a polling rate, if a read is performed on startup, and if unsolicited input is accepted.

There are 3 predefined Access Types that you can use (Read, Write, and ReadWrite), or you can create your own.

Creating a New AccessType

To create or edit an AccessType:

• Go to Edit → Devices → AccessTypes.
• To edit an existing type, double-click a field and configure it as desired.
• To create a new type, click the Create New... button.

Image Removed

Configuring AccessType as OnDisplayOrServer

On the dialog window, you need to configure the ReadEnable field to OnDisplayOrServer.

This property is enough for the Reading portion of the communication. You can also enable Writing Events by selection the WriteEventEnable checkbox.

Image Removed

Access Type Characteristics

The OnDisplayOrServer Access Type is a great tool for projects that have a large amount of Communication Points but do not require the data to be constantly updated for all of them.

It can help computers that lack computational power to handle a huge volume of data exchange while also maintaining other modules (Scripts, Alarms, etc) at the same time.

In these situations, an OnDisplayOrServer Access Type can be beneficial to the Project's performance.

The OnDisplayOrServer Access Type operation process can be divided into two aspects:

• OnDisplay
• OnServer

On Display

The OnDisplay part means that your Communication Point will only begin Reading/Writing when the Project display that contains these tags is actually open.

• • When the Project is running, there is no need to send

• • or receive data for all

• • tags in the PLC. The

• • solution only needs to send

• • or receive data for the

• • opened displays of the visualizer. So, when

• • the Line A display is open, only

• • Line A tags will communicate. The same goes for LineB.

Or Server

• On Server: On Server or OPCServer means that if your

• solution runs as an OPC Server, the

• Access Type will behave as if its

• Read Enable property is set

• to Always. 
  If
  • • Suppose you have the tags on the server
  -
  • • side as
  Script Tasks
  • • ScriptTasks, Classes, Expression,
  Alarm Items, etc. You need to
  • • or AlarmItems. In that case, you must create a new AccessType specific for them with the
  ReadEnable
  • • Read Enable option in Always.

  Configuring an AccessType as OnDisplayOrServer

  To configure an Access type as On Display Or Server, follow these steps:

  1. Access Devices → AccessTypes.
  2. Click on the plus icon.
  3. On the ReadPolling property, choose OnDisplayOrServer. This property is enough for the Reading portion of the communication.
  4. Check the WriteEvents box to Enable Writing Events.

  Info
  Only when these options are met can the DevicePoints with this AccessType read/write data.

  Image Added

  
  

In this section

: