Chipkin Siemens SBT-FSI (XLS) XML -> QuickServer Converter

What this tool does

It turns a Siemens XLS panel-database XML export into a ready-to-load FieldServer QuickServer configuration CSV — the file you upload to the gateway to publish fire-panel events on Modbus/TCP and BACnet/IP.

Ask the Siemens technician for the panel-database export and drop it in. The tool walks the panel tree, finds every XDLC device-loop card and Pseudo Module, sorts each device into its event category (alarm, trouble, supervisory), and writes both sides of the configuration: the Cerberus/XLS client side that polls the panel, and the Modbus/TCP and BACnet/IP server sides that publish it. Column names and legal values follow the FS-8700-40 driver manual, so the result loads into FieldServer Toolbox without hand-editing.

What you get

QuickServer CSV — the configuration file, serving Modbus/TCP and BACnet/IP at once.
Register map CSV — every served point with its Modbus register and BACnet object, for the BMS or PLC integrator.
Parsed JSON — the decoded panel database and the computed plan, for inspection.

Nothing is uploaded. Parsing and generation run entirely in your browser; the panel database never leaves your machine. Scope: XLS (Desigo Fire Safety Modular) panels. MXL exports generate a warning because the connection settings differ, and security (SEC) points still need Secur map descriptors added by hand — talk to us if you need either.

Gateways this configuration runs on

The generated CSV targets the FieldServer QuickServer. The part number decides which protocols the gateway can serve, so pick the model that matches the downstream network — then set the Server protocols checkboxes in step 3 to match it. A BACnet section will not load on a Modbus-only gateway, or the reverse. Each model comes in twelve capacities from 250 to 10,000 points.

SBT-FSI to BACnet/IP QuickServer Gateway

FS-QS-…-0187 · 12 models

Siemens MXL/XLS
BACnet/IP

Publishes panel events as BACnet objects. Leave BACnet/IP ticked and untick Modbus/TCP in step 3.

View product →

SBT-FSI to Modbus TCP QuickServer Gateway

FS-QS-…-0707 · 12 models

Siemens MXL/XLS
Modbus TCP

Serves panel events as Modbus holding registers over Ethernet. Leave Modbus/TCP ticked and untick BACnet/IP in step 3.

View product →

SBT-FSI to Modbus RTU QuickServer Gateway

FS-QS-…-0073 · 12 models

Siemens MXL/XLS
Modbus RTU

Serial Modbus rather than Ethernet. This tool generates the Modbus/TCP server side only — the RTU variant needs a serial connection block adding.

View product →

Step 1 Load a panel-database XML

Drag & drop a .xml or .txt file, or click to browse.

Download example XML

Accepts .xml or .txt files holding the Siemens XLS panel database export (<System Type="XLS"> root). Parsing happens locally in your browser — nothing is uploaded. Don't have the XML? Ask the Siemens technician or integrator for the panel-database export from the XLS programming tool, or request it through the Siemens branch that commissioned the panel. Background: Siemens XLS / Cerberus protocol guide and the FS-8700-40 SBT-FSI driver manual (PDF).

Step 2 Parsed panel database summary

File: -; Name of the uploaded XML export.
Project: -; Project name declared in the XML FileHeader, with the Siemens tool and database versions.
System: -; Panel family from the root element. This tool targets XLS (Desigo Fire Safety Modular). MXL exports generate a warning — connection settings differ.
Panels: -; Panel Node elements found. Each becomes a client-side Node with Node_ID = panel address. Confirm the panel count with the site — missing panels are the most common intake gap on XLS projects.
Mapped blocks: -; XDLC device-loop cards and Pseudo Modules. Each becomes a set of Fire/Trouble/Supervisory Bit arrays with Block_Number = module address. Pseudo Modules hold software points (system bypasses, alarm-sequence flags, door/speaker control) that the panel raises events for; they are served the same way as field devices.
Mapped devices: -; Addressable input devices (detectors, pull stations, monitored switches) and Pseudo Devices that get an event bit, a Modbus register, and a BACnet object. Output circuits, relays, and function keys are listed below but not mapped.

Point selection

Choose which blocks and event categories are read from the panel and served downstream — use this to stay inside the QuickServer's licensed point count (often only Alarms are needed). Register and object numbers of the remaining points do not move: a deselected set's addresses stay reserved, so re-including it later never renumbers a commissioned site. Status serves devices with no ALM/TBL/SUP event type via a Status map descriptor (FS-8700-40 §5.3.2); it is off by default.

Panel	Block	Label	Description	Fire	Trouble	Superv.	Status

Device table

One row per Device under each mapped block. Event is the panel event category (ALM fire alarm, SUP supervisory, SEC security, TBL trouble); devices without an event type (relays, sounder circuits) are not monitored points. The event location format on the wire is Panel^Block^Sub-module^Address^Component — see the driver manual, section 7.10.

Panel	Block	Addr	Type	Event	Description	Mapped

Step 3 Site configuration

Defaults follow Chipkin's SBT-FSI field conventions (the serial link to the panel is fixed by Siemens at 19200,E,7). Replace FSE##### in the title with your project's FSE number.

FieldServer title Appears in the Bridge.Title column and the generated filename. Use the project's FSE number and revision. System Node ID Internal node identifier for the FieldServer itself. Default 97 is the Chipkin convention. Serial port QuickServer serial port wired to the XLS panel's RS-232 FSI port (R1 or R2). Baud/parity/data bits are fixed at 19200,Even,7 by the panel. Panel node name prefix Client node names are this prefix plus the panel address, e.g. Panel_1. Modbus server node name Name of the Modbus/TCP server node the gateway exposes downstream. Modbus Unit ID Modbus slave/unit ID (1–247) that Modbus/TCP clients (PLC, ProSoft card, BMS) use to address this gateway. Counts base register First holding register for the 19 per-panel event counters (Modicon 5-digit addressing). Event bits base register First holding register for the per-device event bits. One register per device address; Fire, Trouble, and Supervisory each get their own block per mapped block (loop card or Pseudo Module). Server protocols The QuickServer serves both at once, so the same panel events are available to a Modbus master and a BACnet BMS simultaneously. Switch one off to leave its sections out of the file entirely — the other side is unaffected either way. Modbus/TCP BACnet/IP BACnet device instance Device instance the BMS uses to address this gateway on BACnet/IP. See BACnet Device Instance. BACnet node name Node name for the BACnet/IP server side. Counter AI base instance First Analog Input object instance for the 19 panel event counters served over BACnet/IP. Request-list polls (opcode 45) Re-fetches standing events after a power cycle or reconnect, so active alarms are not lost across a restart. Alarm Trouble Supervisory

Step 4 Output preview

The QuickServer CSV loads into the gateway via the configuration file upload workflow. The Register map CSV is the cross-reference to hand to the BMS or PLC integrator, listing every served point with its Modbus register and BACnet object. Always bench-test a generated config before commissioning.