Fibrolaser III Modbus Configuration (CSV) File

To integrate a Fibrolaser III heat detection system into Desigo CC you must first prepare a textual configuration file in CSV (comma separated values) format that defines the data structure for the panel.

To do this, use Microsoft Excel or a text editor to edit the provided CSV template files described below. You can then use this file to import the configuration.

For reference information about the Modbus configuration CSV file, see CSV File for Modbus Device Import.

Fibrolaser III Modbus Configuration Template Files

The Fibrolaser III Modbus CSV template file is deployed with the Fibrolaser III extension installation and available at the following path:
[Installation Drive]:\[Installation Folder]\GMSMainProject\profiles\ModbusDataTemplate\

CSV Template File

Description

Modbus_template_4.0_Fibrolaser_MaxConfiguration_2Fibers.csv

It provides a fully configured Fibrolaser system with:

Max number of Inputs\Outputs: 40 In and 106 Out
2 fibres
Max number of zones per fibres: 1000 each fibre, for a total of 2000 zones

Having pre-configured CSV files with offsets already defined for each object, this reduces the possibility to read wrong addresses from the management station.

This template file can be used to create custom configuration files by adding or removing inputs/outputs for the related panel, and zones for the related fibre 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 that can be used for the configuration required on the field site.

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.

Fibrolaser III Modbus Configuration File Sections

Section	Description
[Connections]	Communication channels between Fibrolaser and Desigo CC. 1 interface for each device must be defined.
[Devices]	OTS panel device and fibre channels. Each fibre channel is represented as independent device.
[Points]	Physical points.

Fibrolaser III Connections Data

The [Connections] section comprises the following data:

Data	Description
[ConnectionName]	Interface name. Special characters are not allowed. Fibres InterfaceName must abide be the following naming convention: TCP_OTS<x>_Fibre<y> Fibre1 of the first OTS Panel: TCP_OTS1_Fibre1 Fibre2 of the first OTS Panel: TCP_OTS1_Fibre2 Fibre1 of a second OTS Panel: TCP_OTS2_Fibre1 And so on. NOTE: To obtain consistent imports of the OTS points in case of multiple OTS panels in the same project, it is very important that the OTS number (TCP_OTS<x>_) is changed along each OTS device. Therefore, every OTS must have a unique number, not necessarily consecutive, but mandatorily different from the others.
[ConnectionDescription]	Interface description to display in System Browser.
[SlaveId]	Fibrolaser Modbus slave addresses. One slave address for the OTS Panel and one for each Fibre is expected. For example: Fibrolaser OTS Panel has Slave ID = 1 Fibre1 has Slave ID = 2 Fibre2 has Slave ID = 3 Fibre3 has Slave ID = 4 … Fibre16 has Slave ID =17
[IP_Address]	Interface IP address.
[Port]	TCP Modbus port. Default value: 502.
[Alias]	Not used.
[FunctionName]	Not used.
[Discipline ID]	Not used.
[Subdiscipline ID]	Not used.
[Type ID]	Not used.
[Subtype ID]	Not used.

Connections Section (When Not Used Fields Are Collapsed)

NOTE 1:
The base Unit Identifier for the OTS panel must be set in the FibroManager configuration tool. The fibres automatically take the next continuous IDs. In the example above, the Unit Identifier for the OTS Panel was set to 1.

NOTE 2:
As mentioned in the [InterfaceName] section in the table above, any additional fibre in the configuration file requires a specific Interface entry, where its Slave ID is defined. The IP addresses and TCP Port must be the same as the one configured for the OTS device.

NOTICE

Abiding by Naming Conventions is Essential

Abiding by the above-mentioned naming convention for fibres interfaces is mandatory for the Modbus addresses to work properly for zones.

Fibrolaser III Devices Data

The [Devices] section comprises the following data:

Data	Description
[ParentConnectionName]	Name of the interface assigned to this device.
[DeviceName]	Device name.
[DeviceDescription]	Device description to display in System Browser.
[ObjectModel]	Not used.
[Alias]	Not used.
[Function Name]	Not used.
[Discipline ID]	Not used.
[Subdiscipline ID]	Not used.
[Type ID]	Not used.
[Subtype ID]	Not used.
[LogicalHierarchy]	Not used.
[UserHierarchy]	Not used.

03_Devices Section (When Not Used Fields Are Collapsed)

Fibrolaser III Points Data

The [Points] section comprises the following data:

Data	Description
[ParentDeviceName]	Name of the device to which the point is connected.
[Name]	Point name. Special characters are not allowed.
[Description]	Point description to display in System Browser.
[FunctionCode]	Not used.
[Offset]	Used in combination with the import rules table to achieve the correct value of the register. The following rules apply to Fibrolaser CSV configuration files: Offset = 0 (zero) is required for the Fibrolaser Panel in the first line. Offset = 0 (zero) is required for the Fibre Channels. Offset = 0 (zero) is required for Input 1. The following Inputs use consecutive offsets (Input 2 -> 1, Input 3 -> 2, and so on). Max Offset for Inputs is 39. Offset = 40 is required for Output 1. The following Outputs use consecutive offsets (Output 2 -> 41, Output 3 -> 42, and so on). Max Offset for Outputs is 145. Offest is not required for the Zones. The correct register is set during the driver restart.
[SubIndex]	Not used.
[DataType]	Not used.
[Direction]	Not used.
[Object Model]	Name of the object model linked to this point. Panel: GMS_MODBUS_Fibrolaser_Panel_150 Fibre Channel: GMS_MODBUS_Fibrolaser_FibreChannel_150 Zone: GMS_MODBUS_Fibrolaser_Zone_150 IO: GMS_MODBUS_Fibrolaser_IO_150
[Property]	Not used.
[Alias]	Not used.
[Function]	Not used. This field is optional . Since no functions are configured for Fibrolaser, [Function] is not configured in the CSV currently.
[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.
[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.

Points Section (Not Used Fields Are Collapsed)