Advantronic AD300 Configuration (CSV) File

To integrate an Advantronic AD300 fire panel 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 configuration file.
NOTE: Use a comma (,) as separator.

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.

To obtain pre-configured CSV sample files to edit, contact the Technical Support team.

Having pre-configured CSV files with offsets already defined for each object reduces the risk of reading wrong addresses from the management station. Also, having examples of function mapping already defined can be useful when adding new points and starting from an example of an existing point type included in the CSV file with functions defined.

Pre-configured sample files can be used to create custom configuration files by adding or removing detectors and panels according to the specific configuration.

Additionally, since the device points are imported into Management View as a flat list, pre-configured sample files also provide a predefined logical view that can be used for the configuration required on the field site.

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.

Advantronic AD300 Configuration File Sections

Section	Description
[Connections]	Communication channels between Advantronic and Desigo CC. 1 interface for each device must be defined.
[Devices]	Advantronic fire panel.
[Points]	Physical points.

Advantronic AD300 Connections Data

The [Connections] section comprises the following data:

Data	Description
[ConnectionName]	Interface name. Special characters are not allowed.
[ConnectionDescription]	Interface description to display in System Browser.
[SlaveId]	Advantronic Modbus subordinate address.
[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)

Advantronic AD300 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]	Used to create a hierarchy in the logical view.
[UserHierarchy]	Used to create a hierarchy in the user-defined view.

Devices Section (When Not Used Fields Are Collapsed)

Advantronic AD300 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 Advantronic CSV configuration files: Offset = 0 (zero) is required for the Advantronic system in the first line. The first panel has offset 1. Max offset for panel is 16. The first detector of the first loop of the first panel has offset 1. Max offset for detectors of that group is 240. The next 16 offsets (241 to 256) are reserved and not to be used in the CSV. The first detector of the second loop of the first panel has offset 257. Max offset for detectors of that group is 496. The next 16 offsets (497 to 512) are reserved and not to be used in the CSV. For a summary of the offsets, see the following table.
	Detectors Offsets
	1-240	1st Loop 1st Panel	(240 Offsets to be used)
	241-256	Reserved	(16 Offsets NOT to be used)
	257-496	2nd Loop 1st Panel	(240 Offsets to be used)
	497-512	Reserved	(16 Offsets NOT to be used)
	513-752	3rd Loop 1st Panel	(240 Offsets to be used)
	753-768	Reserved	(16 Offsets NOT to be used)
	…
[SubIndex]	Not used.
[DataType]	Not used.
[Direction]	Not used.
[Object Model]	Name of the object model linked to this point. System: GMS_MODBUS_Advantronic_System_150 Panel: GMS_MODBUS_Advantronic_Panel_150 Detector: GMS_MODBUS_Advantronic_Detector_150
[Property]	Not used.
[Alias]	Not used.
[Function]	“Function name” used to automatically associate the function (for example, “Advantronic_AutomaticDetector_150”) to the point instance during the import of the CSV file. This field is optional. Leave it blank if no function should be assigned during the import.
[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.

Points Section (When Not Used Fields Are Collapsed)