Versions Compared

Old Version 14

changes.mady.by.user user-05e19

Saved on

compared with

New Version Current

changes.mady.by.user admin

Saved on

Key

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

Overview

Access types in Factory Studio define the specific methods The Device AccessType defines the defines the rules for reading and/or writing values for each data point in a project, including polling rate, read on startup, and unsolicited input acceptance. The OnDisplayOrServer Access Type controls data read and write in the project and allows it only when certain conditions are met.

It is useful for projects with many communication points but not requiring constant data updates, reducing computational load, and improving performance. The OnDisplayOrServer Access Type works by checking two conditions, OnDisplay and OnServer, before permitting data read or write.

Device Point. Each Point is associated with one AccessType.

Settings include among others: Polling Rate, Read on Startup, and if is enabled to do WritingOnDisplay means data can be read or written only when the display containing it is open, while OnServer means data can be read or written when the project is running as an OPC server.

On this page:

Table of Contents
maxLevel3
stylenone

Creating

a New

an AccessType

To create or edit and configure an AccessType, follow these steps:

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

    • Create New... buttonImage Removed

    Customizing The Pre-Defined AccessTypes 

    Our platform comes with several pre-defined access types that define the specific methods for reading and writing the values of each data point. To further optimize data exchange, users can customize these access types as needed. To customize pre-defined access types:

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

    Image Added

    AccessTypes Properties

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

    Field

    Description

    Name

    Name of this AccessType

    To configure access types:

    Device AccessType  Configuration Properties

    Field/Column

    Description

    Name

    Enter a name for this access type

    .

    Read

    ReadPolling

    Select when you want to enable

    Enables read polling.

    ReadPollingRate

    Enter

    Defines how often the address value is retrieved.

    ReadTrigger

    Enter an object property that tells the system when to read the value.

    OnStartup

    When selected, the system reads the value on startup.

    Write

    WriteEvents

    Select to enable

    Enables the writing of values to the PLC.

    WriteEvent

    Select

    Defines when is the value

    is

    written.

    WriteTrigger

    Enter an object property that tells the system when to write the value.

    Settings

    AcceptUnsolicited

    When selected

    If enabled, the system accepts values from the PLC, even if the polling time has not yet elapsed.

    UseStaticBlocks

    Select to

    Enables the use of the block command field.

    BlockCommand

    Enter a

    A definition for each block that will be created. Check the driver documentation to see if the specific driver uses this

    field and

    field and the valid values.

    Description

    Enter a description for

    Description of the access type

    .
    One very efficient AcceesType is to only read data when it is being used by the application

    .

    Unique Communication Tag Groups for Each AccessType: 

    A distinct feature of Factory Studio's AccessTypes is their ability to generate unique tag groups for communication. This ensures that every AccessType gets its dedicated communication group, facilitating streamlined communication processes. It's crucial for users to recognize this differentiation when configuring or customizing AccessTypes.

    Configuring AccessType as OnDisplayOrServer

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


    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.

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

    Create new AccessType optionsImage Removed

    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
    Info

    ONLY when and while ANY of these options are met, the Communication Points with this AccessType can Read/Write data.

    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.

    To illustrate, let us say we have a project with two displays: one for LineA and the other for LineB; Each display has its own specific Tags added to it (Tag.LineAProduct1..., Tag.LineBProduct1...)
      • When the Project is running, there is no need to send
    /
      • or receive data for all
    Tags
      • tags in the PLC. The
    Project
      • solution only needs to send
    /
      • or receive data for the
    ones that are in the display that is currently opened on the Visualizer.
      • opened displays of the visualizer. So, when
    LineA
      • the Line A display is open, only
    LineA The OrServer or
      • Line A tags will communicate. The same goes for LineB.

    Or Server

    • On Server: On Server or OPCServer means that if your
    Project is running
    • solution runs as an OPC Server, the
    AccessType
    • Access Type will behave as if its
    ReadEnable
    • Read Enable property is set
    to
    • 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

      ...

      :

      Page Tree
      root@parent
      spacesV10