TOA IP Intercom System Configuration (CSV) File

To integrate the TOA IP Intercom System into Desigo CC you must first prepare a textual configuration file in CSV (comma separated values) format that defines the servers-groups-items structure.

To do this, use Microsoft Excel or a text editor to edit the provided CSV template file described below.

NOTE: Use a comma (,) as separator.

You can then use this file to import the configuration.

For reference information about the OPC configuration CSV file, see CSV File for Third-party OPC Devices.

TOA IP Intercom System Configuration File Template

The TOA IP Intercom CSV file template is deployed with the TOA IP Intercom extension installation and available at the following path:
[Installation Drive]:\[Installation Folder]\GMSMainProject\profiles\OPCDataTemplate\

CSV Template File

Description

OPC_template_4.0_TOA_Intercom_SampleConfiguration_10Stations.csv

It provides a small TOA IP Intercom system configuration with:

5 stations
2 links
2 I\O
2 Zones

Having a pre-configured CSV file with OPC tags already defined for each object reduces the risk of entering invalid OPC items names that might result in communication error when reading the OPC tags.

This template file can be used to create custom configuration files by adding or removing subsystems, stations, links, I\O, or zones, according to the specific configuration.

Additionally, since the device points are imported into Management View as a flat list, this CSV template also provides a pre-configured logical view hierarchical sample structure for two subsystems.

As for the logical view, any CSV templates can be also modified to automatically create a user-defined view out of the import. This part is not provided from any templates because user views strictly depend on the customer’s requirements, but they can be easily added.

TOA IP Intercom System CSV File Sections

Section	Description
[SERVERS]	Includes TOA IP Intercom System OPC server data. One server per CSV file is allowed.
[GROUPS]	Groups the TOA IP Intercom System OPC tags in components.
[ITEMS]	Includes tag data (TOA IP Intercom System OPC point read by the OPC server).

TOA IP Intercom System Servers Data

The [SERVERS] section comprises the following data:

Data	Description
[Name]	OPC server name to display in System Browser.
[Description]	OPC server description to display in System Browser.
[ProgId]	Program ID of the OPC server.
[Alias]	Not used.
[FunctionName]	Not used.
[Discipline ID]	Not used.
[Subdiscipline ID]	Not used.
[Type ID]	Not used.
[Subtype ID]	Not used.

Servers Section (When Not Used Fields Are Collapsed)

TOA IP Intercom System Groups Data

The [GROUPS] section comprises the following data:

Data	Description
[ParentServerName]	Name of the OPC server to which the point is connected.
[Name]	OPC group name to display in System Browser.
[Description]	OPC group description to display In System Browser.

Groups Section (When Not Used Fields Are Collapsed)

TOA IP Intercom System Items Data

The [ITEMS] section comprises the following data:

Data	Description
[Parent Group Name]	Name of the group to which the point belongs.
[Name]	OPC item name to display In System Browser.
[Description]	OPC item description to display In System Browser.
[Item Address]	Name of the tag that is exposed by the OPC server. This value must be unique and less than 100 characters.
[Data Type]	Transformation type. Data format required by the OPC Server. For details about the allowed values, in OPC Library Import Rules, see OPC Items Data Types.
[Direction (Access Level)]	Value that defines if the OPC item is input, output or input/output.
[Object Model]	Name of the object model used for this OPC tag. The TOA IP Intercom System extension provides the following object models: OPC Server: GMS_OPC_TOA_OPCServer_150 Subsystem: GMS_OPC_TOA_Subsystem_150 Station: GMS_OPC_TOA_Station_150 Link: GMS_OPC_TOA_Link_150 I\O: GMS_OPC_TOA_IO_150 Zone: GMS_OPC_TOA_Zone_150
[Object Model Property]	Name of the DPE associated to this OPC tag.
[Alias]	Not used.
[Function Name]	Not used.
[Discipline ID]	Not used.
[Subdiscipline ID]	Not used.
[Type ID]	Not used.
[Subtype ID]	Not used.
[Min]	Not used.
[Max]	Not used.
[MinRaw]	Not used.
[MaxRaw]	Not used.
[MinEng]	Not used.
[MaxEng]	Not used.
[Resolution]	Not used.
[Eng Unit]	Not used.
[StateText]	Not used.
[AlarmClass]	Not used.
[AlarmType]	Not used.
[AlarmValue]	Not used.
[EventText]	Not used.
[NormalText]	Not used.
[UpperHysteresis]	Not used.
[LowerHysteresis]	Not used.
[LogicalHierarchy]	Used to create a hierarchy in the logical view.
[UserHierarchy]	Used to create a hierarchy in the user-defined view.

Tags Section (When Not Used Fields Are Collapsed)

The specific OPC tags are defined by the OPC server. For more details about the OPC tags provided by the S4S OPC server interface, see the OPC Server TOA -Installation and Configuration manual distributed by S4S.