Innon Core Io Cr-io-16di 16 Point Modbus Input Or Output Module User Manual

Core IO – CR-IO-16DI
User Manual
16 Point Modbus I/O Module, 16 DI

INTRODUCTION

Overview
In many installations, having cost-effective, robust, and simple hardware becomes a key factor in winning a project. The Core lineup provides the perfect solution to meet these criteria. In has partnered with Atimus, a company with a wealth of experience in the field, and is proud to present Core IO!
The 16DI provides 16 digital inputs. As well as monitoring volt-free contacts, the device also allows the use of pulse counters.
BEMS communication is based on the robust and well-proven Modbus RTU over RS485 or Modbus TCP (IP model only).
The configuration of the device can be achieved through the network using either the web interface (IP version only) or Modbus configuration registers, or by using an Android device and connecting over Bluetooth using the dedicated app.

This Core IO model
Both the CR-IO-16DI-RS and the CR-IO-16DI-IP modules come with 8 digital inputs.
The CR-IO-16DI-RS only comes with the RS485 port, while the CR-IO-16DI-IP comes with both RS485 and IP ports.
Both models also come with Bluetooth on board, so configuration can be achieved using an Android device and the dedicated app.
The IP CR-IO-16DI-IP model also integrates a web server configuration interface, accessible via a PC web browser.

HARDWARE

Overview

Wiring Power Supply

Wiring Digital Inputs (DI)

Wiring the RS485 network
Some useful links to our knowledge base website:
How to wire an RS485 network
https://know.innon.com/howtowire-non-optoisolated
How to terminate and bias an RS485 network
https://know.innon.com/bias-termination-rs485-network
Please note – both IP and RS versions can use the RS485 port to respond to serial Modbus master comms from the BEMS, but neither version can use the RS485 port to act as a Modbus master or gateway.

Front LED Panel
The LEDs in the front panel can be used to get direct feedback on the status of the I/Os of Core IO and more general information.
Below are some tables that will help decode each LED behavior.

DI 1 to 16

BUS and RUN

CONFIGURE I/O

Digital Inputs

Digital Inputs can have a clean/volt-free contact connected to Core IO to read its open/closed status.
Each digital input can be configured to be either:

• Digital Input direct
• Digital Input reverse
• Pulse input

While the “direct” and “reverse” mode would basically return the status “False (0)” or “True (1)” when the contact is either open or closed, the third mode “pulse input” is used to return a counter value increasing by 1 unit every time the digital input closes; please read the section below for more details regarding pulse counting.

Pulse Counting
Digital Inputs and Universal Outputs can be configured specifically to work as pulse counting inputs.
The counting maximum readable frequency is 100Hz, with a duty cycle of 50%, and the maximum “contact closed” readable resistance is 50ohm.
When an input is configured to count pulses, a number of Modbus Registers are available with information and commands specifically for the pulse counting function.
The pulse input will, in fact, count 2 totalizers as follows –

• The first one is continuous; it will increase by one unit for every pulse received and will keep counting until a reset command is sent over Modbus
• The other totalizer is timed. Basically, it will also increase by one unit for every pulse received but will count only for a specified (adjustable) time (in minutes). When the time expires, Each pulse counting input has the following Modbus registers associated with it –
• counter (totalizer): this is the main totalizer. It will go back to “0” only if a reset command is sent, or if Core IO is power cycled – you can also write to this value to restore a previous count if replacing a module or to reset to 0
• counter (timer): this is the second totalizer, the timed one. It will go back to “0” every time the timer reaches the maximum set value (with a delay of 1 minute), or if Core IO is power cycled. If the counter reset is activated, the counts within the timed cycle will be ignored and the counter timer reset to 0. The reset will not reset this count to 0 after it has finished a timed cycle and is displaying the result for 1 minute
• counter timer: this data point returns the current time of the counter, in minutes. It will of course go back to “0” when it reaches the maximum set value
• counter timer set: using this data point you can configure the duration of the timer for the second totalizer (max set value), in minutes. This value is stored within the Core IO memory
• counter reset: using this data point you can reset the totalizer counter to value “0” and the timed counter will discard counts up to that point in the timed cycle and reset its timer to 0. Core IO will self-reset this data point to value “0” once the command has been executed

CONFIGURING THE DEVICE

FIXED SETTINGS
The RS485 Modbus Slave communication has some settings that are fixed as follows –

• 8-bit data length
• 1 stop bit
• Parity NONE

DIP SWITCH SETTING 
The DIP switches are used to configure the other RS485 settings and the Modbus slave address thus –

• RS485 End-Of-Line (EOL) resistor
• RS485 Bias resistors
• Modbus Slave Address
• RS485 Baud-Rate

The bank of two EOL (End-Of-Line) blue DIP switches is configured as follows –

Please check our dedicated knowledge base article available at the website http://know.innon.com where we explain in detail the use of the termination and bias resistors on RS485 networks.

The Modbus ID and baud rate DIP switches are configured as follows –

Slave address DIP switch settings continued.

Bluetooth and Android App
Core IO has built-in Bluetooth which allows the Core Settings app running on an Android device to configure the IP settings and I/O.
Please download the app from Google Play – search for “core settings”
Download and install the app, then check/make the following settings changes –

• Open your phone settings (drag down from the top, press the “cog” icon)
• Click on “Apps”
• Select the “Core Settings” app
• Press “Permissions”
• Press “Camera” – set it to “Allow only while using the app”
• Go back then press “Nearby devices” – set it to “Allow”

When you run the app, the camera will switch on, and you will need to use it to read the QR code on the module, you wish to set up, i.e. –

The Android device will ask you to allow the Bluetooth devices to pair on the first connection, watch out for the notifications on your device and accept them.

Once connected, you will land on the I/O setup screen, where you can set up the I/O and read input and output current values –

Use the drop-down arrows in the “I/O Mode” column to select the type of input type by clicking on the respective radio button –
Once you make a change or number of changes, the “UPDATE” button on the bottom right will go from greyed-out to white; press this to commit your changes.
Click on the “ETHERNET” button (bottom left) to set up the required IP settings.
Set and commit data as per the I/O method above.
Click on the “MODE” button (bottom left) to get back to the I/O settings.

Ethernet Port and Web Server Configuration (IP version only)
For the IP models of Core IO, a standard RJ45 socket is available to be used for:

• Modbus TCP (slave) communication
• Web server access to configure the device

The IP models still provide access to the RS485 port for Modbus RTU (slave) communication on these models, so the user can decide which one to use to connect the BEMS to Core IO.
The default settings of the IP port are:

IP address, subnet, and gateway address can be changed from the Bluetooth Android app or from the web server interface.
The web server interface looks and works in much the same way as the Core Settings app described in the previous section.

BEMS POINT LISTS

Modbus Register Types
Unless otherwise stated in the tables, all I/O point values/statuses and settings are held as Holding Register Modbus data type and use a single register (16 bit) to represent an Integer (Int, range 0 – 65535) type of data.
Pulse count registers are 32-bit long, unsigned registers, i.e. two consecutive 16-bit registers combined, and their byte order is sent in little endian, i.e. –

• Niagara/Sedona Modbus driver – 1032
• Teltonika RTU xxx – 3412 – also use 2 x “Register count/values” to obtain all 32 bits

For some Modbus master devices, the decimal and hex register addresses in the table will need to be incremented by 1 to read the correct register (e.g. Teltonika RTU xxx)
Bit-field data type uses individual bits from the 16 bits available on the Modbus register to provide multiple Boolean information by reading or writing a single register.

Modbus Register Tables

General Points

Digital Input Points

TECHNICAL DATA

Drawings

Specifications

Guidelines for Disposal

• The appliance (or the product) must be disposed of separately in accordance with the local waste disposal legislation in force.
• Do not dispose of the product as municipal waste; it must be disposed of through specialist waste disposal centers.
• Improper use or incorrect disposal of the product may negatively affect human health and the environment.
• In the event of illegal electrical and electronic waste disposal, the penalties are specified by local waste disposal legislation.

1.0 4/10/2021
Get help at http://innon.com/support
Learn more at http://know.innon.com

References

• Innon Knowledge Base
• Why and how do I use Bias resistors and Termination resistors on an RS485 network?
• How do I wire RS485 devices?