Satel Integra 24-256 – RTI Driver

Version 3.00 – requires XP-8 runtime 14 or newer.

What this driver does

Network communication with Satel INTEGRA alarm panels (24 / 32 / 64 / 128 / 256 and Plus variants) through the ETHM-1 Plus module. ETHM-2 is not supported.

The driver detects the panel model automatically on connect. You no longer select it by hand.

Upgrading from satel_integra_24_128

A simple in-place driver upgrade will not work. The satel_integra_24_128 driver shares the same Driver ID as satel_integra_256, on which version 3.00 is based, so Integration Designer will not swap it in automatically while keeping your configuration.

Migration path: export the current driver settings to a .driverconfig file, run satel_skaner to adapt that file to version 3.00, then import it into a freshly added Satel Integra 3.00 driver. Note that variables and button macros must be rewritten by hand – the new version organises variables differently, so old macros do not carry over.

The previous versions will no longer be supported or developed. All new features and fixes go to version 3.00 only.

Before you start

1. In the ETHM-1 Plus module, integration encryption must be disabled – the integration key must be empty. This is set by the alarm installer in DLOADX.

2. The module accepts only one integration connection at a time. If another system or tool is connected, this driver will not communicate.

3. Enter the IP address of the ETHM-1 Plus module and the integration port (default 7094) in the driver configuration.

Licence

Without a licence key the driver is fully functional for 60 minutes after processor start, then stops.

One licence covers one processor (one MAC address) and one product. A key issued for this driver will not unlock other drivers on the same processor.

For v2 keys the Licensed To field is mandatory – the key will not validate without it. Enter the company name exactly as supplied.

The integrator finds the processor MAC address on the device label, on the box, or in Integration Designer.

User code

Enter the alarm user code in the User Code field. Both 4 and 6 digit codes are supported.

The code has one purpose only: the INTEGRA panel requires a user code with every control command, including switching outputs on, off and toggling them. Without a stored code the user would have to enter it manually every time a button is pressed.

Do not use the administrator code or any full-rights user code here. Ask the alarm installer to create a separate panel user dedicated to the integration – name it clearly, for example RTI_Outputs, so it is obviously a technical account and not the site owner – with permissions limited to output control and nothing else – no arming, disarming, alarm clearing or settings access. A code with that scope is not worth stealing: the critical functions of the panel stay out of reach.

Note that an output-only user cannot arm or disarm a partition. If the panel is also meant to arm the system, either grant that user arming rights as well, or design arming so that the code is entered on the panel keypad. Decide this before commissioning.

Configuration files exported from Integration Designer may contain this code. Do not send such a file by e-mail without clearing the field first.

Names and installation size – SatelNazwy tool

By default the driver exposes the full set of variables for the largest panel – 1982 items with generic names.

The companion tool SatelNazwy.exe connects to the panel, reads zone, output and partition names, and detects which elements actually exist. It writes a .driverconfig file that you import into the driver properties. A typical residential installation drops from 1982 variables to roughly 350, with real names instead of "Zone 47".

Disconnect the RTI processor while the tool is running – see the one-connection limit above. A full scan of an INTEGRA 256 takes about two minutes.

See the separate integrator guide for the full procedure.

Dynamic Scope settings

Six advanced fields control which elements the driver handles:

Used Zones / Used Outputs / Used Partitions – control which variables are visible in Integration Designer.

Runtime Used Zones / Outputs / Partitions – control which variables the driver actually writes on the processor.

Both sets are filled by SatelNazwy and must contain the same values. Format: 1:4,7,20:22

An empty field hides all variables of that group. To restore the full set, enter 1:256 for zones and outputs, 1:32 for partitions, in both sets.

Commands

Commands ending in "Specify" take a list of numbers separated by commas, for example: 1,3,12

Temperature readings are available only for zones served by the ABAX wireless system. You must know the zone number of the temperature sensor.

New in version 3.00

Troubles are now reported in two separate sets. The Trouble Memory category works exactly as in earlier versions – it shows that a trouble occurred and clears only via the Clear Trouble Memory command. The new Troubles (current state) category shows troubles present right now and clears by itself. Existing macros are unaffected; the new category was added alongside, not instead.

Troubles (radio, expanders, keyfobs) is a new category covering expanders, ACU jamming, radio device battery and communication, and keyfob batteries. Each kind provides one summary variable; the numbers of the affected devices appear on the shared list variable Troubles List (radio/expanders).

Zone antimasking adds the categories Zone Masked and Zone Masked Memory. Both are hidden by default. Set Show Zone Masked (ShowZM) and Show Zone Masked Memory (ShowZMM) to Show under Show Zone Variables, otherwise no variables appear at all.

Three new arming commands – Partition Arm Specify (instant), Partition Arm Mode 1 Specify (no exit delay) and Partition ForceArm Specify (instant). They require a sufficiently recent ETHM-1 Plus module. If the module does not report that capability, the driver sends the ordinary command instead and logs the fact as an error; the partition is armed, but without the selected option.

Not verified on hardware: the numbering of radio devices, expanders and keyfobs on the trouble list is adopted by analogy with zones; radio device troubles cover the first 120 devices only, so on larger installations the remainder is not reported; the three new arming commands have never been sent to a real panel. Please report anything that behaves differently to the driver author, with the panel model, the ETHM-1 Plus version and a processor log if you have one.

Troubleshooting

No communication: check in this order – another integration connection is open; integration encryption is enabled in ETHM-1 Plus; wrong IP or port. The first cause is the most common and the most misleading, because the module accepts the TCP connection and closes it immediately.

A variable never updates: check that its number is present in the matching Runtime Used field. If it is not, the driver deliberately skips the write.

Variable list is empty: an empty Dynamic Scope field hides the whole group. Enter the full range to restore it.

Magia Dzwieku – driver version 3.00, August 2026.