Nano Rs-485 Fire Detection And Extinguishing Control Panel User Manual

Nano Rs-485 Fire Detection And Extinguishing Control Panel User Manual

NANO-LOGO

NANO RS-485 Fire Detection and Extinguishing Control Panel

NANO-RS-485-Fire-Detection-and-Extinguishing-Control-Panel

DOCUMENT REVISION DETAILS

IssueModification DetailAuthorDate
11st publishing documentCvT01 / 11 / 2022
2

IMPORTANT NOTES – READ CAREFULLY

This manual should be thoroughly read and understood before installation and commissioning of the system is undertaken. This MODBUS manual is an integral part of the NANO manual version 2.2 of October 1, 2022.

The NANO, with the associated connections, must be installed, commissioned, and maintained by a skilled, knowledgeable, and competent personnel that is trained to perform this work. It is assumed that the personnel who commission the system is familiar with objective of the equipment and the technical terminology associated with this. Except for the backup battery there are no user-serviceable parts in the NANO.

The NANO/MAR system is not to be regarded as properly used when it is used without regard to any relevant information or advice relating to its use that has been made available by the supplier. The NANO/MAR system and the associated connections must be installed, commissioned, and maintained by a skilled, knowledgeable, and competent person or organization that is qualified to perform this work and is familiar with the objective of the equipment and the associated technical terminology. This equipment is not guaranteed unless the complete installation is installed and commissioned in accordance with the laid down local and/or national standards.

Reservations
The diagrams of operating principles of the NANO fire-/extinguisher system, included in this manual, are intended to support this manual and are therefore not intended and suitable for technical implementation or realization. No part of this manual may be reproduced, stored in an automated database, or made public in any form or by any means either electronically, mechanically or by photocopying, recording, or in any other way, without prior written permission from N2KB BV. The policy of the N2KB BV is one of continuous improvement and as such we reserve the right to make changes to product specifications at any time and without prior notice. Errors and omissions excepted.

INTRODUCTION
The NANO is designed to be used in a fully integrated system. Remote devices can read the status and parameters of the NANO by a digital bus system. The technology used is MODBUS. This is a very well-established bus technology that uses RS-485 as the underlaying physical layer. Please read the NANO
User Manual before using the device. This manual only manages the data bus usage.

CONNECTING THE DATA BUS

RS-485 is a 3-wire bus. Two wires for the communication data and one wire for the ground connection.
Be aware that this ground wire must always be connected and physically kept together with the two data signal lines. Not connecting this wire can lead to communication faults and even damaged devices due to EFT or Surge events or Voltage level differences between different floating ground potentials.

Make sure the A and B date lines are not reversed. Although nothing can be damaged, the communication will not work that way.
It is strongly recommended to use a twisted pair cable to reduce the risk of communication failures due to Electro Magnetic Interference (EMI). Twisting all four lines together instead of twisting in pairs of 2 is also a good solution.

CONNECTION SETTING

The MODBUS type is RTU and the settings of the communication are 8N1 baudrate 9600.
This means:

NANO-RS-485-Fire-Detection-and-Extinguishing-Control-Panel-1

  • Baudrate 9600 bps
  • 1 start bit
  • 8 data bits
  • Geen pariteits bit
  • 1 stop bit

CHOOSE A MODBUS ADDRESS

It is possible to connect multiple devices to one data bus. It is very important to give each device in the data bus a unique address. This is done via the buttons on the NANO panel front.

  1. STEP 1 MODBUS SETTINGS
    Set the NANO in programming mode by pressing and holding the MODE NANO-RS-485-Fire-Detection-and-Extinguishing-Control-Panel-3 and the MUTE NANO-RS-485-Fire-Detection-and-Extinguishing-Control-Panel-4 button simultaneously for more than 3 seconds.NANO-RS-485-Fire-Detection-and-Extinguishing-Control-Panel-2
  2. STEP 2 INDICATION
    On the front of the NANO, the green power indicator will flash rapidly. This indicates the Modbus address of this NANO in the Modbus programming mode.NANO-RS-485-Fire-Detection-and-Extinguishing-Control-Panel-6
  3. STEP 3 CHANGE ADDRESS
    Press the Mute NANO-RS-485-Fire-Detection-and-Extinguishing-Control-Panel-4 button shortly to change the address from address 0 to address 1.
  4. STEP 4 CONFIRM CHOICE
    To confirm the address, press the MUTE NANO-RS-485-Fire-Detection-and-Extinguishing-Control-Panel-4 button for at least 3 seconds or press the Reset NANO-RS-485-Fire-Detection-and-Extinguishing-Control-Panel-5 button to cancel. If there is no button pressed for 60 seconds during this MODBUS address selection mode. The operation is automatically canceled.NANO-RS-485-Fire-Detection-and-Extinguishing-Control-Panel-7
  5. STEP 5 CHECK CONNECTION
    To test the connection and communication,various tools are available in the market. For example, the FTDI USB-RS485-WE-1800-BT cable can be used to connect the hardware to a PC. A simple and easy-to-use test application,among others, is the Schneider Electric Modbus Tester application for Windows.

MODBUS REGISTER

All parameters are read only holding registers and can be read by an external MODBUS RTU master device via “Read hold register” commands. It is possible to read multiple registers with one command by changing the requested data length. All register contains 16 bits data. If data is requested beyond the last available register the data is cut-off at the end and the reply will have the corrected data length.
The data has the most significant byte first (MSB first) as this is the most common way to format the 16 bits register content in MODBUS RTU.

RegisterNameDescriptionlength
40000Product nameAlways replies with the string “NKB1310”20
40020VersionFirmware version Major revision in high byte, minor revision in lower byte1
40021RebootsNumber of reboots since first started1
40023Sounder stateExternal sounder state:

0 = IDLE, 1 = OPEN, 2 = SHORTED, 3 = ACTIVATED

1
40030Current event state: fault exting open1 = Active, 0 = Not active1
40031Current event state: fault exting shorted1 = Active, 0 = Not active1
40032Current event state: fault firezone 1 open1 = Active, 0 = Not active1
40033Current event state: fault firezone 1 shorted1 = Active, 0 = Not active1
40034Current event state: fault firezone 2 open1 = Active, 0 = Not active1
40035Current event state: fault firezone 2 shorted1 = Active, 0 = Not active1
40036Current event state: fault sounder open1 = Active, 0 = Not active1
40037Current event state: fault sounder shorted1 = Active, 0 = Not active1
40038Current event state: fault external hold open1 = Active, 0 = Not active1
40039Current event state: fault external hold shorted1 = Active, 0 = Not active1
40040Current event state: fault external hold midrange1 = Active, 0 = Not active1
40041Current event state: fault external release open1 = Active, 0 = Not active1
40042Current event state: fault external release shorted1 = Active, 0 = Not active1
40043Current event state: fault external release midrange1 = Active, 0 = Not active1
40044Current event state: fault power disconnected1 = Active, 0 = Not active1
40045Current event state: external release1 = Active, 0 = Not active1
40046Current event state: external hold1 = Active, 0 = Not active1
40047Current event state: firezone0 fire1 = Active, 0 = Not active1
40048Current event state: firezone1 fire1 = Active, 0 = Not active1
40050Current event state: charged cap1 = Active, 0 = Not active1
40053Current event state: vehicle mode1 = Active, 0 = Not active1
40054Current event state: backup power mode1 = Active, 0 = Not active1
40055Current event state: usb power connected1 = Active, 0 = Not active1
40080Event count: fault exting openNr. Of events occurred since reboot1
40081Event count: fault exting shortedNr. Of events occurred since reboot1
40082Event count: fault firezone 1 openNr. Of events occurred since reboot1
40083Event count: fault firezone 1 shortedNr. Of events occurred since reboot1
40084Event count: fault firezone 2 openNr. Of events occurred since reboot1
40085Event count: fault firezone 2 shortedNr. Of events occurred since reboot1
40086Event count: fault sounder openNr. Of events occurred since reboot1
40087Event count: fault sounder shortedNr. Of events occurred since reboot1
40088Event count: fault external hold openNr. Of events occurred since reboot1
40089Event count: fault external hold shortedNr. Of events occurred since reboot1
40090Event count: fault external hold midrangeNr. Of events occurred since reboot1
40091Event count: fault external release openNr. Of events occurred since reboot1
40092Event count: fault external release shortedNr. Of events occurred since reboot1
40093Event count: fault external release midrangeNr. Of events occurred since reboot1
40094Event count: fault power disconnectedNr. Of events occurred since reboot1
40095Event count: external releaseNr. Of events occurred since reboot1
40096Event count: external holdNr. Of events occurred since reboot1
40097Event count: firezone 1 fireNr. Of events occurred since reboot1
40098Event count: firezone 2 fireNr. Of events occurred since reboot1
40100Event count: charged capNr. Of events occurred since reboot1
40103Event count: vehicle mode1 = Active, 0 = Not active1
40104Event count: backup power mode1 = Active, 0 = Not active1
40105Event count: usb power connected1 = Active, 0 = Not active1
40130Led state: ext release fault0 = off, 1 = on, 2 = blink, 3 = blink fast1
40131Led state: power0 = off, 1 = on, 2 = blink, 3 = blink fast1
40132Led state: manual mode0 = off, 1 = on, 2 = blink, 3 = blink fast1
40133Led state: zone 1 alarm0 = off, 1 = on, 2 = blink, 3 = blink fast1
40134Led state: zone2 alarm0 = off, 1 = on, 2 = blink, 3 = blink fast1
40135Led state: zone1 fault0 = off, 1 = on, 2 = blink, 3 = blink fast1
40136Led state: zone 2 fault0 = off, 1 = on, 2 = blink, 3 = blink fast1
40137Led state: general fault0 = off, 1 = on, 2 = blink, 3 = blink fast1
40138Led state: fire10 = off, 1 = on, 2 = blink, 3 = blink fast1
40139Led state: auto mode0 = off, 1 = on, 2 = blink, 3 = blink fast1
40140Led state: released0 = off, 1 = on, 2 = blink, 3 = blink fast1
40141Led state: delay0 = off, 1 = on, 2 = blink, 3 = blink fast1
40142Led state: hold0 = off, 1 = on, 2 = blink, 3 = blink fast1
40143Led state: exting fault0 = off, 1 = on, 2 = blink, 3 = blink fast1
40144Led state: sounder fault0 = off, 1 = on, 2 = blink, 3 = blink fast1
40145Led state: backup power0 = off, 1 = on, 2 = blink, 3 = blink fast1
40146Led state: ext hold fault0 = off, 1 = on, 2 = blink, 3 = blink fast1
40147Led state: fire20 = off, 1 = on, 2 = blink, 3 = blink fast1
40148Led state: fire30 = off, 1 = on, 2 = blink, 3 = blink fast1
40150VFC state: Fire1 = Active, 0 = Not active1
40151VFC state: Fault1 = Active, 0 = Not active1
40152VFC state: Fan1 = Active, 0 = Not active1
40153VFC state: Extinguish1 = Active, 0 = Not active1
40160Button state: Reset0 = not pushed, 1 = pushed, 2 = pushed long,

3 = pushed longer

1
40161Button state: Hold0 = not pushed, 1 = pushed, 2 = pushed long,

3 = pushed longer

1
40162Button state: Mode0 = not pushed, 1 = pushed, 2 = pushed long,

3 = pushed longer

1
40163Button state: Mute0 = not pushed, 1 = pushed, 2 = pushed long,

3 = pushed longer

1
40164Button state: Extinguish0 = not pushed, 1 = pushed, 2 = pushed long,

3 = pushed longer

1
40170Button pushed count: ResetNr. Of events occurred since reboot1
40171Button pushed count: HoldNr. Of events occurred since reboot1
40172Button pushed count: ModeNr. Of events occurred since reboot1
40173Button pushed count: MuteNr. Of events occurred since reboot1
40174Button pushed count: ExtinguishNr. Of events occurred since reboot1
40180Button pushed long count: ResetNr. Of events occurred since reboot1
40181Button pushed long count: HoldNr. Of events occurred since reboot1
40182Button pushed long count: ModeNr. Of events occurred since reboot1
40183Button pushed long count: MuteNr. Of events occurred since reboot1
40184Button pushed long count: ExtinguishNr. Of events occurred since reboot1
40190Button pushed longer count: ResetNr. Of events occurred since reboot1
40191Button pushed longer count: HoldNr. Of events occurred since reboot1
40192Button pushed longer count: ModeNr. Of events occurred since reboot1
40193Button pushed longer count: MuteNr. Of events occurred since reboot1
40194Button pushed longer count: ExtinguishNr. Of events occurred since reboot1
40220Main voltageunits: mV1
40221Internal voltageunits: mV1
40222Backup power voltageunits: mV1
40224Extinguish power capacitor voltageunits: mV1
40225Board temperatureunits: degrees Celcius * 101
40226Extinguish sense voltageunits: mV1
40227Sounder port voltage positive poleunits: mV1
40228Sounder port voltage negative poleunits: mV1
40229Firezone 1 Voltageunits: mV1
40230Firezone 2 Voltageunits: mV1
40231Firezone 1 Currentunits: uA1
40232Firezone 2 Currentunits: uA1
40233Firezone 1 Resistanceunits: Ohm1
40234Firezone 2 Resistanceunits: Ohm1
40235External release button resistanceunits: Ohm1
40236External hold button resistanceunits: Ohm1
40237Vehicle input Voltageunits: mV1
40250Reading above this register will return no answer

Modbus user manual
NANO-NL
November 1, 2022
version

www.N2KB.nl

References

Documents / Resouces

Download manual
Here you can download full pdf version of manual, it may contain additional safety instructions, warranty information, FCC rules, etc.


Related Manuals