A great solution/s to interconnect Simplex 4100 devices on BACnet IPnetwork.

Simplex 4100 Client – BACnet IP Server Gateway
Simplex 4100
The Simplex 4100 (computer port protocol) is used to transfer data (alarms and events) from the Simplex Fire alarm panels (4020/4100U/4100ES/4010ES/NDU).
ProtoConvert can supply and support gateways that are capable of interfacing with the Simplex fire alarm panels using the Simplex 4100 Computer port protocol and capturing the alarms and events sent by the panel. The data received can be further published on another interface of the gateway using a different protocol like BACnet, Modbus, SNMP , LonWorks , HTTP/S or any other open protocol. Hence the gateway would provide the means to transmit the alarms and events from a Simplex Fire alarm panel (stand alone or networked) to a monitoring system like a SCADA or a Building Management System that cannot directly interface with the Simplex panel.
The Simplex 4100 protocol driver is a client only driver. Hence it is not possible to emulate a Simplex fire alarm panel.
BACnet IP
BACnet IP (Internet Protocol) is a communication protocol used for building automation and control networks. It is an open standard that provides a common language for building systems to communicate and exchange data. BACnet IP is based on the Internet Protocol (IP) and allows for communication over Ethernet networks.
In terms of network topology, BACnet IP supports both peer-to-peer and client-server communication models. In a peer-to-peer configuration, devices on the network can communicate directly with each other. In a client-server configuration, one device acts as the server, providing data and services to other devices on the network, which act as clients.
BACnet IP also supports broadcast communication, which allows for one device to send a message to all other devices on the network at the same time. This can be useful for network-wide announcements or updates.
ProtoConvert can supply and support gateways that can have a BACnet IP client or a server interface.
When a gateway is configured as a BACnet IP Client it would keep reading data from the field devices using BACnet IP protocol. It will also be possible to program the gateway to relay commands to the field device/s. Hence when configured as a BACnet IP Client the gateway reads data from BACnet IP devices like power meters, UPS’, PDUs, CRAC units, Thermostats and makes the data available on a variety of other protocols like Modbus, SNMP , LonWorks and many others
When a gateway is configured as a BACnet IP Server it can publish data on a BACnet IP network as a server and other BACnet IP clients can obtain data from the gateway. It would respond to the polls/COV Subscription requests from the BACnet IP Clients on the network and publish the data as per the internal configuration. Hence by using the gateway as a BACnet IP Server it is possible to publish data from other protocol networks on the BACnet IP network for the Building management system (BMS) or any other Building automation and Control system to consume.
The table below lists the various hardware options available with this protocol driver combination, please make a selection based on the point capacity, number of ports, and type of communication interfaces you require.
| Name of Hardware with Tail Code | Point Capacity | RS 485 ports | RS 232 ports | Ethernet Port | M-Bus | LonWorks | KNX | WiFi | 4G/LTE | Product Datasheet |
|---|---|---|---|---|---|---|---|---|---|---|
| FPA-C41 | 250 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | Attachment |
| FPA-C42 | 250 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | Attachment |
| FPA-C43 | 250 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | Attachment |
| FPA-W44-A | 250 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | Attachment |
| FPA-W44-B | 500 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | Attachment |
| FPA-W44-C | 1000 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | Attachment |
| FPA-W44-D | 3000 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | Attachment |
| FPA-W44-E | 5000 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | Attachment |
| FS-QS-2020-F | 250 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | Attachment |
| FS-QS-2120-F | 1000 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | Attachment |
| FS-QS-2220-F | 500 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | Attachment |
| FS-QS-2320-F | 3000 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | Attachment |
| FS-QS-2420-F | 5000 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | Attachment |
| FS-QS-3020-F | 250 | 1 | 1 | 2 | 0 | 0 | 0 | 0 | 0 | Attachment |
| FS-QS-3120-F | 500 | 1 | 1 | 2 | 0 | 0 | 0 | 0 | 0 | Attachment |
| FS-QS-3220-F | 1000 | 1 | 1 | 2 | 0 | 0 | 0 | 0 | 0 | Attachment |
| FS-QS-3320-F | 3000 | 1 | 1 | 2 | 0 | 0 | 0 | 0 | 0 | Attachment |
| FS-QS-3420-F | 5000 | 1 | 1 | 2 | 0 | 0 | 0 | 0 | 0 | Attachment |
| FS-QS-3520-F | 10000 | 1 | 1 | 2 | 0 | 0 | 0 | 0 | 0 | Attachment |
| PG-K30B-1K | 1000 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | – |
| PG-K30B-2K | 2000 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | – |
| PG-K30B-3K | 3000 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | – |
| PG-K30B-4K | 4000 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | – |
| PG-K30B-5K | 5000 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | – |
