Zenitel AlphaCom Configuration (CSV) File
To integrate the AlphaCom equipment 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 configuration file.
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.
To obtain pre-configured CSV sample files to edit, contact the Technical Support team.
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.
Pre-configured sample files can be used to create custom configuration files by adding or removing servers, nodes, and stations.
As for the logical view, pre-configured sample files can be also modified to automatically create a user-defined view out of the import. This part is not provided in pre-configured CSV files because user views strictly depend on the customer’s requirements that can be easily added.
Zenitel AlphaCom CSV File Sections
Section | Description |
[SERVERS] | Includes AlphaCom OPC server data. One server per CSV file is allowed. |
[GROUPS] | Groups the AlphaCom OPC tags in components. |
[ITEMS] | Includes OPC tag data (AlphaCom OPC point read by the OPC server). |
Zenitel AlphaCom 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. |
Zenitel AlphaCom 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. |
Zenitel AlphaCom Items Data
The [ITEMS] section comprises the following data:
Data | Description |
[Parent Group Name] | Name of the OPC 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 OPC tag that is exposed by the OPC server. |
[Data Type] | Transformation type. Data format required by the OPC server. |
[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.
|
[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. |
The specific OPC tags are defined by the OPC server. For more details about the OPC tags provided by the Zenitel OPC server interface, see https://wiki.zenitel.com/wiki/OPC_Server.
