ModBus Transmission

Protocol for JunoNet

Version 2.0

2011 Global Fire Equipment SA. Version 2.0

 ModBus Transmission Protocol for JunoNet

Table of Contents

Part I J-Net - ModBus Implementation 4

1 Introduction
................................................................................................................................... 4
2 Funtion
...................................................................................................................................
Codes Description 5
Panel Current
.........................................................................................................................................................
Status 5
Device Information
......................................................................................................................................................... 7
Remote Switch
.........................................................................................................................................................
Operation 10
Output Device
.........................................................................................................................................................
Operation 12

Part II JunoNet Configuration 16

Part III Hardware Interfaces 18

1 JunoNet
...................................................................................................................................
Interfaces 18
J-NET-ADV-COMS-485
......................................................................................................................................................... 18
RS232 - Connections
..................................................................................................................................................
Diagram 19
RS485 - Connections
..................................................................................................................................................
Diagram 20
J-NET-ADV-COMS-FO
......................................................................................................................................................... 21
J-NET-ADV-COMS-TCP/IP
......................................................................................................................................................... 22
J-NET-ADV-COMS-TCP/IP
..................................................................................................................................................
Configuration 23

Index 0

Version 2.0 - page 2 2011 Global Fire Equipment SA

Part

I
ModBus Transmission Protocol for JunoNet

1 J-Net - ModBus Implementation

1.1 Introduction
This document describes the Modbus protocol automation supported by the JunoNET panel. The
Panel only supports being the controlled peer (slave).

Only the Serial Port communication is supported, in both ASCII and RTU modes. Use the
Installation Menu on the Panel to select the mode and serial port settings required.

Version 2.0 - page 4 2011 Global Fire Equipment SA

 J-Net - ModBus Implementation

1.2 Funtion Codes Description

Below are described all the functions supported by the JunoNet Panel.

1.2.1 Panel Current Status

This function is represented by either the code 01 (0x01 - Read Coils) or 02 (0x02 - Read Discrete
Inputs).

Using this function the user can get up to 6 variables from the Panel current status.
Below are represented all the available variables and its address.

Discrete Input Address Content Comments

0x0000 Fire statflg_fire
0x0001 Fault statflg_fault
0x0002 Pre Alarm statflg_prealarm
0x0003 Evacuate statflg_evacuate
0x0004 Silence statflg_silence
0x0005 Reset statflg_reset
Table.1 - Panel Status Variables.

The variables can be obtained from the panel one by one (requesting one coil at a time), or the six
variables at once.
Below is one example on how to get all the variables at once. In the example we used the Simply
Modbus because it shows what its traveling in the communication line.

Fig.1 - Simply Modbus Current Status

2011 Global Fire Equipment SA Version 2.0 - page 5

ModBus Transmission Protocol for JunoNet

Request Description:

Slave ID (1 byte) 0x01

Function Code (1 byte) 0x02
Starting Address (2 byte) 0x0000
Quantity of coils (2 byte) 0x0006
CRC (2 byte) 0xF808

Response Description:

Slave ID (1 byte) 0x01

Function Code (1 byte) 0x02
byte count (1 byte) 0x01
Coil Status (1 byte) 0x11
CRC (2 byte) 0x6184

In this example we got 0x11 for the Panel status. So coil 0 (fire status) and coil 4 (silence status)
are active.
That means that the panel is in alarm and the sounders have been silenced.

Version 2.0 - page 6 2011 Global Fire Equipment SA

 J-Net - ModBus Implementation

1.2.2 Device Information

This function is represented by either the code 03 (0x03 - Read Holding Registers) or 04 (0x04 -
Read Input Registers).

Using this function the user can get the type, condition and analogue value from any device
connected to the system.
Bellow are described the possible types and conditions.

Type Device Type Device

0 Not Fitted 15 Output Module
1 Sounder 16 IR Beam
2 I/O Unit 17 CO Detector
3 Ion Smoke 18 Sensor A
4 Zone Monitor 19 Sensor B
5 Smoke Detector 20 High Sens. Optical
6 Heat Detector 21 Multi Sensor
7 Call Point 22 Dual sensor
8 Nat Gas Detector 23 View Sensor
9 Fire Module 24 High Temp. Heat
10 Gas Module 25 HMO
11 Monitor Module 26 Elotecniq
12 Control Moodule 27 Aspirating
13 Sounder Module 28 Aspect
14 Module A 29 Unrecognised
Table.2 - Device types.

Condition Meaning
000 No Alarm
001 Fault
010 Pre Alarm
011 Fire
100 Sensor Changed
101 Sensor Removed
110 Double Address
111 ---
Table.3 - Device Conditions.

In order to get the data from the correct device you need to follow the addressing rule:

Loop calculation (Base Address): (0x0100) + ((Loop - 1) x (0x80))

Device Calculation (Final Address): Base Address + (Device - 1)

Example:
If we want to read from Device 9 on Loop 7 the address is:
Loop calc.: (0x0100) + ((7 - 1) x (0x80)) = 0x400
Dev. calc.: 0x400 + (9 - 1) = 0x408

Below is an example of how to get the information of some devices in Loop 1.

2011 Global Fire Equipment SA Version 2.0 - page 7

ModBus Transmission Protocol for JunoNet

Fig.2 - Simple Modbus Dev. Info.

In the above example we are requesting the data from 10 devices starting on the 1st device of Loop
1.

Request Description:

Slave ID (1 byte) 0x01

Function Code (1 byte) 0x03
Starting Address (2 byte) 0x0100
Quantity of coils (2 byte) 0x000A
CRC (2 byte) 0xC431

Response Description:

Slave ID (1 byte) 0x01

Function Code (1 byte) 0x03
byte count (1 byte) 0x14
Coil Status (1 byte) ... 0x3B10 ... 0x1010 ...
CRC (2 byte) 0xFCCB

Version 2.0 - page 8 2011 Global Fire Equipment SA

 J-Net - ModBus Implementation

To decode the device data see below:

Address 2, Data = 0x3B10 = 0011 1011 0001 0000

1st Byte 2nd Byte

0 0 1 1 1 0 1 1 0 0 0 1 0 0 0 0
Type Condition Analogue Value

Type = 111(binary) = 7. According to the devices table we have a Call Point.

Condition = 011(binary) = 3. according to the conditions table is in Fire (alarm).
Analogue Value = 10000 (binary) = 16.

Address 4, Data = 0x1010 = 0001 0000 0001 0000

1st Byte 2nd Byte

0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0
Type Condition Analogue Value

Type = 10(binary) = 2. According to the devices table we have a I/O unit.

Condition = 000(binary) = 0. according to the conditions table is No Alarm.
Analogue Value = 10000 (binary) = 16.

The remaining addresses have no devices connected.

2011 Global Fire Equipment SA Version 2.0 - page 9

ModBus Transmission Protocol for JunoNet

1.2.3 Remote Switch Operation

This function is represented by the code 05 (0x05 - Write Single Coil).

Using this function the user can operate the panel using 3 different buttons.
Bellow are described available buttons.

Discrete Input Address Content Comments

0x0003 Evacuate(1) statflg_evacuate
0x0004 Silence(2) statflg_silence
0x0005 Reset(2) statflg_reset
Table.4 - Available Buttons.

Notes:
1. Accepts coil states 0xFF00 and 0x0000 for SET and RESET the Evacuation.
2. Accepts coil state 0xFF00 as OPERATE.

Below is an example with the Reset button.

Fig.3 - Simple Modbus Buttons Operation

Version 2.0 - page 10 2011 Global Fire Equipment SA

 J-Net - ModBus Implementation

Request Description:

Slave ID (1 byte) 0x01

Function Code (1 byte) 0x05
Output address (2 byte) 0x0005
Output Value (2 byte) 0xFF00
CRC (2 byte) 0x9C3B

Response Description:

Slave ID (1 byte) 0x01

Function Code (1 byte) 0x05
Output address (2 byte) 0x0005
Output Value (2 byte) 0xFF00
CRC (2 byte) 0x9C3B

2011 Global Fire Equipment SA Version 2.0 - page 11

ModBus Transmission Protocol for JunoNet

1.2.4 Output Device Operation

This function is represented by the code 06 (0x06 - Write Single Register).

Using this function the user can operate on the Output (I/O units) of any address on the system.

To determine the Coil address you have to follow the same rule used in Device Information:

Loop calculation (Base Address): (0x0100) + ((Loop - 1) x (0x80))

Device Calculation (Final Address): Base Address + (Device - 1)

Example:
If we want to read from Device 9 on Loop 7 the address is:
Loop calc.: (0x0100) + ((7 - 1) x (0x80)) = 0x400
Dev. calc.: 0x400 + (9 - 1) = 0x408

Multiple outputs on the same device cannot at present be operated separately.

Possible write values:
· 0x00FF – Turn output on.
· 0x0000 – Turn output off.

Below is an example of how to Switch ON the Output of Device 4 on Loop 1:

Fig.4 - Simple Modbus Dev. Output ON

Version 2.0 - page 12 2011 Global Fire Equipment SA

 J-Net - ModBus Implementation

Request Description:

Slave ID (1 byte) 0x01

Function Code (1 byte) 0x06
Output address (2 byte) 0x0103
Output Value (2 byte) 0x00FF
CRC (2 byte) 0x3876

Response Description:

Slave ID (1 byte) 0x01

Function Code (1 byte) 0x06
Output address (2 byte) 0x0103
Output Value (2 byte) 0x00FF
CRC (2 byte) 0x3876

Other example of how to Switch OFF the Output of Device 4 on Loop 1:

Fig.5 - Simple Modbus Dev. Output OFF

Request Description:

Slave ID (1 byte) 0x01

Function Code (1 byte) 0x06
Output address (2 byte) 0x0103
Output Value (2 byte) 0x0000
CRC (2 byte) 0x3876

2011 Global Fire Equipment SA Version 2.0 - page 13

ModBus Transmission Protocol for JunoNet

Response Description:

Slave ID (1 byte) 0x01

Function Code (1 byte) 0x06
Output address (2 byte) 0x0103
Output Value (2 byte) 0x0000
CRC (2 byte) 0x3876

Version 2.0 - page 14 2011 Global Fire Equipment SA

Part

II
ModBus Transmission Protocol for JunoNet

2 JunoNet Configuration
In order to enable the Modbus communication in the panel you have to go to Diagnostics mode:
1. De-energize the panel;
2. Press SYSTEM RESET button;
3. Apply power to the panel;
4. When “Diagnostics mode” shows in the display release the SYSTEM RESET button;
5. Press ESC and Enter your Installer password;
6. Go to Installation Menu;
7. Change the autom.: to MODBUS RTU(1);
8. Change the com speed: to 115200(1);
9. Change the mode: to 8N2(1);
10.Press ENTER 5 Times to Save the configuration;
11.Restart the panel;
12.Configure panel address (can be configured @ function (8-5-1)).

Note 1: You can choose the settings that best fit your needs.

Version 2.0 - page 16 2011 Global Fire Equipment SA

Part

III
ModBus Transmission Protocol for JunoNet

3 Hardware Interfaces
Four different interfacing technologies are available, namely:

· RS-232
· RS-485
· Fibre Optics
· TCP/IP

3.1 JunoNet Interfaces

3.1.1 J-NET-ADV-COMS-485
The interface J-NET-ADV-COMS-485 can be configured to use either RS232 or RS485. Below is
illustrated both hardware configurations.

Fig.6 - ADV-COMS via RS232 and external Printer.

Fig.7 - ADV-COMS via RS485 and external Printer.

Version 2.0 - page 18 2011 Global Fire Equipment SA

 Hardware Interfaces

3.1.1.1 RS232 - Connections Diagram

Connecting JunoNet Panel through Modbus using RS232 protocol.

Fig.8 - Rs232 Connections Diagram

2011 Global Fire Equipment SA Version 2.0 - page 19

ModBus Transmission Protocol for JunoNet

3.1.1.2 RS485 - Connections Diagram

Connecting JunoNet Panel through Modbus using RS485 protocol.

Fig.9 - Rs485 Connections Diagram

Version 2.0 - page 20 2011 Global Fire Equipment SA

 Hardware Interfaces

3.1.2 J-NET-ADV-COMS-FO

Connecting JunoNet Panel through Modbus using Fiber Optics.

Fig.10 - Fiber-Optics Connections Diagram

2011 Global Fire Equipment SA Version 2.0 - page 21

ModBus Transmission Protocol for JunoNet

3.1.3 J-NET-ADV-COMS-TCP/IP

Connecting JunoNet Panel through Modbus using TCP/IP.

Fig.11 - TCP/IP Connections Diagram

Version 2.0 - page 22 2011 Global Fire Equipment SA

 Hardware Interfaces

3.1.3.1 J-NET-ADV-COMS-TCP/IP Configuration

The Lantronix (J-NET-ADV-COMS-TCP/IP) should be configured as shown in the pictures below.

Fig.12 - Lantronix Serial settings

The serial settings should match the configurations on the Panel, then press OK.

2011 Global Fire Equipment SA Version 2.0 - page 23

ModBus Transmission Protocol for JunoNet

Fig.13 - Lantronix Connection settings

Configure the local port according to your application, then press OK.

Version 2.0 - page 24 2011 Global Fire Equipment SA

 Hardware Interfaces

Fig.14 - Lantronix Network

Configure the Network setting according to the local network, then press OK.

Finally click on 'Apply Settings' to save the changes.

2011 Global Fire Equipment SA Version 2.0 - page 25