Versions Compared

Old Version 1

changes.mady.by.user Roberto Vigiani

Saved on

compared with

New Version Current

changes.mady.by.user Roberto Vigiani

Saved on

Key

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


Page properties
hiddentrue
idconnector-metadata


Property

Value

Sector

Factory-Floor Interfaces

Group

Field Devices

Connector

Administration Management System

Name

AMS



AMS (Administration Management System) that is developed by TTC Informatik GmbH.

  • Name: AMSXE
  • Version: 1.1.0.0.4
  • Protocol: Proprietary
  • Interface: TCP/IP
  • Runtime: .NET 24.0 8 (MultiplatformWindows)
  • Configuration:
    • Devices / Protocols

Table of Contents
maxLevel2
minLevel2
stylenone

Overview

Communication Driver Information

Driver name

VerbaInfoAMSXE

Assembly Name

T.ProtocolDriver.VerbaInfoAMSXE

Assembly Version

1.1.0.0.4

Available for Linux

False

Devices supported VerbaInfo

ServiceAdministration Management System

ManufacturerAesys

TTC Informatik GmbH

Protocol

Proprietary over TCP/IP

PC Requirements

Ethernet board


Channel

Channels Configuration

Protocol Options

This configuration is not required

There is no protocol options configuration for the AMS Slave driver.


Nodes Configuration

Station Configuration 

IP:

Node 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)

target equipment.

Port: IP Port used in the target equipment. Default value: 9050E.g.: 192.168.1.1;23608


Points Configuration

Address

 The syntax for the PMV VerbaInfo AMS Slave communication points is: <Function><FunctionMode><Parameter><RunBlockNumber><RunParameter><ProgramBlockNumber><ProgramParameter>

  • <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>.
    To write two or more messages inside a tag is necessary to separate the messages with a semicolon ( ; ) too.

     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

    • Function: PROGRAMLIST, EQUIPMENTSTATUS, SENDLOAD, LOADSTATUS, LOADCANCEL;
    • FunctionMode: Read (R) and Write (W);
    • Parameter: Name, EquipID, Program, ProcessActive, StartTime, EndTime, ID_AMS, ID_PLS, ErrorCode, ErrorDesc, State, Run, MsgId, Trigger;
    • RunBlockNumber: Integer number (1-200) that identifies the execution block;
    • RunParameter: EquipId, Program, StartTime, EndTime; 
    • ProgramBlockNumber: Integer number that identifies the program block;
    • ProgramParameter: Id, Name, Info.

    Driver Revision History

    AMS Slave Driver

    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 (;).

    Image Removed

    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.

    Image Removed

    Driver Revision History

    VerbaInfo

    Revision History

    Version 

    Notes

    1.1.0.0

    .2

    Initial release on new documentation standards

    1.0.0.4Updated to several field variables


    In this section...

    Page Tree
    root@parent