| Easy Heading Macro | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
This document has only the specific
information about the device connection settings and its address syntax.
Refer to the User
Guide for more information on the Device Module.
On this page:
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Summary
Communication Driver Information | |
|---|---|
Driver name | VerbaInfo |
Assembly Name | T.ProtocolDriver.VerbaInfo |
Assembly Version | 1.0.0. 24 |
Available for Linux | False |
Devices supported | VerbaInfo Service |
Manufacturer | Aesys |
Protocol | Proprietary over TCP/IP |
PC Requirements | Ethernet board |
Channels Configuration
Protocol Options
This configuration is not supported for this Driver.
Nodes Configuration
Primary Station
PrimaryStation: <IP> ; <Port>
Where:
<IP> = IP address of the VerbaInfo Service
<Port> = TCP Port where the VerbaInfo Service is listening (default is 23608)
E.g.: 192.168.1.1;23608
Points Configuration
Address
The syntax for the PMV VerbaInfo communication points is:
- <Command>:<VMS>:<Code>:<Variable>
<Command>: There are three commands: ActivateTemplate, WriteMessage, and CheckIfAlive.
ActivateTemplate is used to choose the predefined message in VerbaInfo.
Note In VerbaInfo Client, each predefined message has a code, this code must be used as the value to be passed to the tag to select the desired message. When this command is used, it is necessary to fill just the Command and VMS parameters.
The tag used in this command must need to be the type Text.- WriteMessage is used to write a new message in the PMV. The tag used in this command must need to be the type Text.
- CheckIfAlive is used to check if there is communication between FS and VerbaInfo Service. The tag used in this command must need to be the type Digital.
| Note |
|---|
| When CheckIfAlive command is used, is not necessary to fill other parameters. |
<VMS>: This parameter is the name of each PMV used in the configuration of the VerbaInfo Client.
<Code>: Each preset message inside VerbaInfo contain a code, this Code is necessary to be configured when the WriteMessage command is used.
<Variable>: When creating a preset message that can be alterable in VerbaInfo, it is necessary to create this message like @Text or @A or another letter, this word or letter is configured in this parameter in the platform. This Variable has to be configured when the WriteMessage command is used.
| Info |
|---|
To PMV that have more than one message, you can configure several Variables separated with a semicolon ( ; ), for example: <Variable1>;<Variable2>. |
Examples
| VerbaInfo Address Configurations Examples | ||||
|---|---|---|---|---|
TagName | Node | Address | DataType | AccessType |
WriteMessage | VerbaInfo | WriteMessage:TESTE:code:Text | Native | Write |
ActivateTemplate | VerbaInfo | ActivateTemplate:TESTE | Native | Write |
CheckIfAlive | VerbaInfo | CheckIfAlive | Native | Write |
Configuration of Message Quantity
To configure the number of messages that will be sent in the same command, you can separate the variables by a semicolon (;). In the image below, we have SUP01;SUP02 that are separated by a semicolon (;). Within a PMV, these two variables must be configured for the messages to be exchanged.
Note: You can configure 1, 2, 3, or more variables for the same panel, just separate them with a semicolon (;).
To send the messages, they need to be in the same tag and also separated by a semicolon (;).
Continuing with the same example, but now in the image below, we have Msg01;Msg02, where Msg01 will be directed to the SUP01 variable, and Msg02 will be directed to the SUP02 variable.
Driver Revision History
| VerbaInfo Revision History | |
|---|---|
| Version | Notes |
| 1.0.0.2 | Initial release on new documentation standards |
| 1.0.0.4 | Updated to several field variables |
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|