Overview
Access Types define the specific methods for reading and writing values for each Device Point in a solution, including settings such as polling rate, read on startup, and unsolicited input acceptance.
In addition, the platform provides On Display Or Server Access Type configurations that enable your solution to control the data read and write permissions. These configurations are useful for solutions with many Device Points but do not require constant data updates, reducing computational load and improving performance.
On this page:
Table of Contents maxLevel 3 style none
Creating an Access Type
To create and configure an Access Type, follow these steps:
- Access Devices → Access Types.
- Click on the plus icon.
- Fill all the property fields with your desired configuration (see the table below for more details about each option).
- Click Ok.
Access Types properties
The following table describes each configuration property when creating an Access Type:
Field | Description |
|---|---|
Name | Name of this Access Type. |
Read | |
Read Polling | Enables read polling. |
Read Polling Rate | Defines how often the address value is retrieved. |
Read Trigger | Enter an object property that tells the system when to read the value. |
On Startup | When selected, the system reads the value on startup. |
Write | |
Write Events | Enables the writing of values to the PLC. |
Write Event | Defines when is the value written. |
Write Trigger | Enter an object property that tells the system when to write the value. |
Settings | |
Accept Unsolicited | If enabled, the system accepts values from the PLC, even if the polling time has not yet elapsed. |
Use Static Blocks | Enables the use of the block command field. |
Block Command | A definition for each block that will be created. Check the driver documentation to see if the specific driver uses this field and the valid values. |
Description | Description of the access type. |
On Display Or Server type
The On Display Or Server Access Type is an excellent tool for projects 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 On Display Or Server operation process is divided into two aspects:
- On Display: On Display means that your Device Point 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. 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.
- On Server: OrServer 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.
- Suppose you have the tags on the server side as Script Tasks, Classes, Expression, or Alarm Items. In that case, you must create a new Access Type specific for them with the Read Enable option in Always.
Configuring an Access Type as On Display or Server
To configure an Access type as On Display Or Server, follow these steps:
- Access Devices → Access Types.
- Click on the plus icon.
- On the Read Polling property, choose On Display Or Server. This property is enough for the Reading portion of the communication.
- Check the Write Events box to Enable Writing Events.
| Info |
|---|
Only when these options are met can the Device Points with this Access Type read/write data. |
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|