Interface Manual DIN Gateway SignalFire Part Numbers: GW-DIN, GW-DIN-STATICIP The SignalFire DIN Gateway has the following features: - RS485 connection to Modbus master device - Optional Modbus-TCP Ethernet gateway module - Wide range DC power input.
Connections and Components DIN Gateway Connections The DIN Gateway has a 6-position pluggable terminal block for power and serial communications.
Status LEDs The DIN Gateway has three LED Available for field diagnostics. The RS485 TX/RX LEDs will blink in response to RS485 traffic, the status LED is described below. STATUS LED 3 Description Slow Flash (3 second pause) System is running and in communication with radio network Fast Flash (0.
Remote Modbus Stick Node Re-Scan It is possible to cause a remote Modbus Stick to re-scan for attached Modbus devices by writing to one of the gateway’s configuration registers. This is useful to discover a Modbus device that is added to an existing Modbus node. The scan may be initiated by one of the two methods. First, if the radio address of the Modbus Stick is known, writing this address to gateway register 3000 will result in a scan.
Setup The DIN Gateway requires an initial configuration over the debug port. The supplied SignalFire Toolkit PC application will be used to configure the device over the serial port. The following item must be configured: - Radio Network and Group Selection NOTE: If used with an Ethernet Gateway module the DB9 on the Ethernet module must be used for ToolKit access. Using the SignalFire Toolkit The SignalFire Toolkit application can be downloaded at www.signal-fire.com/customer.
Network Setting The network address can be used to create separate networks using multiple gateways (that are in close proximity with one another). The network is set using the SignalFire Toolkit. The Network Group setting is used when more than 8 networks are needed. Both the network and network group must match those of other nodes for nodes to communicate. 6 Checking Remote Nodes If one or more remote nodes are configured with the correct network settings they will send their data to the gateway.
Modbus Gateway Register Map The SignalFire Modbus Gateway by default is assigned Modbus Slave ID number 247. Only the Gateway status/configuration registers are read at this address. All remote node registers are read from the slave ID and register address of the remote node, unless slave register remapping used. 7 Gateway Configuration and Status Messages Boolean Registers – These are 1-bit coil registers. They can only be written to by Modbus opcode 0x05 (Write Single Coil).
Read Only Registers – These are 16-bit read only registers. They can be read with Modbus opcode 0x03 or 0x04 (Read Discrete Input and Holding Registers, respectively). The register map can be found on the next page. If the gateway has a large total number of registers approaching 4700, register 2008 should be monitored to ensure that free registers are available before adding a new node.
43001 3000 43004 3003 44002 44003 … 4001 4002 … 44241 4240 Rev 1.
Firmware Upgrades Firmware updates for both the gateway (ARM) and the built-in radio are possible over the RS-232 debug interface using the SignalFire Toolkit, or over a remote TCP connection if an Ethernet Gateway module is used. 10 Gateway (ARM) Firmware update steps 1 Open the SignalFire Toolkit application. 2 Open the correct COM port connected to the RS-232 port of the gateway. 3 Go to the Update menu and select Update Gateway Firmware. 4 The latest gateway firmware file will be selected by default.
Remote Shutdown (RSD) and Local Digital Output Control The SignalFire Gateway supports Internal Logic Control capability which enables the Gateway to control output relays on SignalFire RSD sticks as well as the two digital outputs local to the Gateway 11 The SignalFire Gateway Stick receives data from multiple remote nodes. It can use the data from those remote nodes to set the relay output on one or more remote RSD sticks.
RSD Configuration From the Gateway configuration window within the SignalFire Toolkit, go to the Settings menu and select Remote Shutdown Settings. This will open the RSD configuration window. 12 Source Node Section The source node section is used to select the source register for the logic rule. Slave ID – The Modbus Slave ID of the remote source node. Node Type – Drop-down list of standard SignalFire remote nodes. Select the type of remote node here, or select Custom for manual data entry.
Relay Control Logic Section The relay control logic section is used to set the trigger thresholds for the selected source data register. Run System (Energize Relay) – Select the logic operand to use for the “energize” logic evaluation. Value – The value that the relay will be energized. Note that the energized state is the normal “operating” state of the relay. Shutdown System (De-Energize Relay) – The logic operand to use for the “de-energize” logic evaluation.
Destination RSD Stick Section Slave ID – The Slave ID of the destination RSD Stick, or the slave ID of the Gateway (default 247) for the local digital outputs. Relay Channel – Select the relay or digital output channel to switch Current Relay State – Shows the last value of the relay or digital output as reported to the gateway. Clicking the Update button will refresh this value. After filling out the table click Write Remote Shutdown Settings to Gateway to store the setting in the gateway Stick.
Example Line 1 has been configured with a source data node as a Sentinel-Analog with the loop current (in μA) as the selected register. The relay will energize when the loop current is above 1400μA (14mA) and de-energize when the loop current is below 1300μA (13mA). Note that this configuration has a 1000μA (1mA) hysteresis factor.
Options There are two check boxes for additional logic options. 16 Failsafe Enabled – If this option is selected all rules must have valid data for the relay to be energized. If one or more of the nodes times-out or does not exist the relay will be de-energized. If this option is not selected, then a node that is not installed or fails to check in will be ignored and the relay will be energized using logic only from the units that are active.
Slave Register Remapping The gateway allows any of the remote register data to be remapped to a single block of registers available at the Gateway’s slave ID (default is 247). This is useful for collecting a subset of register data from multiple nodes and making it readable in a single block of registers. Up to 750 registers can be remapped to the gateway’s slave ID starting at register 5000. To configure the remapping, first select Slave Register Remapping from the Settings dropdown menu.
Remote Node Configuration The SignalFire Gateway allows configuration changes to be made to any of the connected SignalFire remote nodes wirelessly. To use this feature, access to the Gateway debug port is required. This may be accessed over a TCP/IP network using a SignalFire Ethernet Gateway module, or by a direct connection to the Gateway RS232 port. To start a remote configuration session with a remote node, select the check-box next to the node to configure and click Start Configuration. Rev 1.
If the node has an awake radio the remote configuration session will be ready immediately. If it is a sleeping node you must wait for the node to either check-in or send a “beacon” so that it can be commanded into configuration mode. The Sentinel nodes send a beacon every 2.5 minutes, while all other sleeping nodes send a beacon every 5.5 minutes. When the node has entered a remote configuration session you will see a message indicating the slave is ready.
Example Remote Configuration Window Rev 1.
Gateway Event Log Starting with Gateway Firmware version 7.81 the Gateway keeps an internal log of events. The event log can be viewed from the gateway window of the ToolKit by selecting ‘View Gateway Log’ from the Tools menu. The gateway log events such as reboots, remote nodes joining/timing out, local RSD control events, remote configuration sessions, firmware updates, and more. Revision History Revision Date Changes/Updates 1.0 10/02/15 Initial Release for DIN Gateway 1.
APPENDIX - FCC and IC Statements Changes or modifications not expressly approved by SignalFire Telemetry, Inc could void the user’s authority to operate the equipment. 22 This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
