InimWay – Inim intrusion automation gateway – KNX, modbus, BACnet, API

665,50847,00

A bidirectional gateway for Inim intrusion panels. The interface supports three types of communication objects: – commands: send commands to the panel – status: get area, zone, … state info into your KNX – events: when particular things happens on the panel (this is currently not supported but will be made available through firwmare update) 100% flexible definition of each communication object: free choice of data type, telegram values, 1-n, n-1 or n-m relation, …

KNX Features

– EIB and KNXnet/IP, – Read, write and response support modbus features – modbus TCP and RTU slave – read (status & events) and write (commands) support

BACnet Features (InimWay Plus)

– acts as BACnet server,

Vizualisation (InimWay Plus)

The SPCway can serve as vizualisation engine for your SPC panel or even for your entire KNX installation

Other protocols

You need to intergrate the Inim with other protocols such as EnOcean, DMX, CEC, SMS … then check out our SPClib product or get in touch with us for an optimised solution.

Interface Languages

The SPCway user interface and documentation is currently available in English, Dutch and German (French, Italian, … added soon) If you prefer another language, then check out our 1 EUR offer. Or get direct support from our team.

Clear
SKU: InimWay Category: Tags: , , , , ,

Description

A fully configurable bidirectional gateway for Inim intrusion panels.

Features

The interface is fully bidirectional and supports three types of communication objects:

– commands: we support 8 different types of commands (on doors, areas, zones, users, panel, output, audio) that can be send to the panel. These can be configured to many hundreds of different communication objects. Eg. Arm area 2, Arm all areas, Momentarily open door 3, Silence all bells, …

– status: we support 12 different types of status informations. Combined with the numbers of elements (doors, zones, …) this results in many hundreds of possible status communication objects.

You can find details about all supported types of communication objects in the annexes of the setup guide, available in the Download section.

Due to the extreme flexibility of object configuration no external logic is needed to realise the entire functional integration. Features include: free choice of data type, telegram value conversions, 1-n, n-1 or n-m relation, value filtering, …

One can easily imagine 1000 different communication objects and group addresses. There is no real limitation.

Additional features

– KNX-IP router & tunnel, which can be used to connect ETS to the KNX bus, with advanced filtering options
– communication logger GUI
– alerts and technical logger for troubleshooting
– backup – restore – upgrade from GUI

modbus support

The main modbus features are:
– bidirectional modbus support (KNX & modbus are transparant)
– acts as modbus slave (server)
– support for modbus TCP and RTU (RS232-RS485)
– all SPCway communication objects are available (technically ‘limited’ to 8000 registers and 8000 coils)
– fully configurable from the embedded GUI, profile automatically generated

Vizualisation

Main characteristics:
– several building/floors/level structures can be set up
– support for objects, gauges, frames, cameras, links, graphs, labels, pincodes
– visual aspect is 100% freely configurable (layout, resolution, icons, graphics, CSS style, …)
– suits large projects where SPCanywhere is inadequate
– allows integration of entire KNX vizualisation

Contact us with question about all possibilities we support.

A basic HD example of the vizualisation that can be realised with the InimWay+ variant:

spcway_vizu_demo3D

BACnet & API: endless integration options

The InimWay can also be used in other integration schemes:
– the InimWay Plus fully supports BACnet (transparantly synchronised with KNX & modbus interface)
° acts as BACnet server, serving all objects to your BAcnet clients
° automatic conversion to Binary and Analog data types (BACnet has no support for text data type which KNX and modbus does)
° bidirectional: both status/events and commands are supported
– The InimWay has an easy to configure API for diverse intergration solutions
° http/https
° json/XML
° read/write
° rights configurable per object (security)

Configuration

Everything is easily configurable on the gateway; no need to get into the panel configuration to modify the communication objects.

In the panel you only need to configure the gateway once as a trusted EDP-client.

Screenshot of the main configuration tab:

SPCwayConfigGUI

Video of the entire GUI (SPCway but with identical lyout for InimWay):

Security – certification

If you need to limit the allowed commands for security reasons: this is configured inside the SPC panel, so this will not brake your system certification.

Installation time

The physical & electrical installation time is merely a few minutes: connect power, LAN & KNX. The time needed is mainly determined by the time to configure all needed communication objects.
All configuration is done through the embedded webserver, without need for ETS.
If you wish ETS support, then the dummy device technique is used.

Requirements

The product supports Inim intrusion panels which have at least the network & modbus module. In practice that requires:

– a panel with a LAN connection to your LAN network

– power : 12-24VDC, < 2Watt (from Inim panel, KNX or dedicated PSU)

Additional information

Weight N/A
Plus: Visualisation & BACnet

Yes, No

Reviews

There are no reviews yet.

Be the first to review “InimWay – Inim intrusion automation gateway – KNX, modbus, BACnet, API”

You may also like…

Translate »