← Back to product

MARCOS FIRE CORP · PANELTRAIL

BRS Studio · Getting started

Getting-started guide based on the owner’s September 11, 2026 manual. The original complete manual is available in Spanish.

Reference: LOTE33 · 11/09/2026 · Guide 1.0

Original complete BRS manual · Spanish (PDF)

01 Install and open

BRS Studio is a 64-bit Windows 10/11 application. Copy the entire BRS_Studio folder, including _internal; copying only the executable is insufficient. The interface uses WebView2.

Manufacturer tools do not need to be installed to read supported files. Importing a generated EST4 project requires 4-CU separately.

02 Sources and scope

Home > Open project accepts EST2/EST3 SDU, iO SAS, QuickStart XDU, EST4 4-CU ZIP, Fire-Lite/Notifier PS-Tools BIN, and Silent Knight SKC or supported Account files. Some families also accept companion PDF reports.

Features vary by family. Fire-Lite/Notifier and Silent Knight support reading and reporting, not EST4 conversion. EST4 conversion covers EST2, EST3, iO and QuickStart.

03 Navigate and review before generating

Choose the current source by date. Review devices, nodes, cards and Warnings. A large row count alone does not establish a correct reading.

The tree, Device List, Properties, SW/LED, Groups and Rules expose the information available for each family. Narrow results with searches such as serial:489* or dt:42.

Ordinary edits affect the session and reports. SDU Labels is a separate operation that generates a new SDU. Always keep the original source.

04 Generate reports

Reports > Barcode lets you select template, scope, symbol and output formats. The product documents PDF, Excel, Word, CSV and TXT depending on the tool.

For points without serials, choose a Message/Label template. These Fire-Lite and Silent Knight sources do not supply serials; serial-based templates must not invent them.

CAC IO, CAC FL and CAC SK generate central-station reports for their respective families. Check warnings and Silent Knight’s Data confidence: HIGH or MINED, depending on the source.

Quality, Record of Completion and CO Life / Dirty Level tools are part of the documented workflow; the latter two require HDT captures and sufficient matching data. Consult their requirements in the full manual.

05 Mapping and EST4 preparation

HDT / Mapping brings together Project > Map and the documented mapping modes. Review which connections exist in the source and which data remains unresolved.

Conversion > EST4 Exporter: select the source and base project, then run View plan before writing. Review routing, loop capacity and warnings.

After generation, read the entire report. Conversion > Rules prepares rules for supported cases; keep REVIEW, TODO and manual-action items as review tasks.

Import the output into 4-CU, check the tree, rules and Build warnings, and complete installation-specific data. Generated output does not remove the need for final 4-CU review.

06 Limits and reference documentation

Unknown fields remain unknown. Silent Knight Account files may include mined fields with medium confidence; verify zone, group and question-mark values.

Button availability depends on the version and family. If a documented feature is absent, confirm you have the complete folder for the relevant release.

This guide summarizes initial use. The owner’s complete Spanish PDF includes the per-family feature matrix, detailed workflows, limitations, traceability and planned features. Roadmap features are not presented as currently available.