EasyManua.ls Logo

ComAp InteliGen NT BaseBox User Manual

ComAp InteliGen NT BaseBox
152 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #91 background imageLoading...
Page #91 background image
IGS-NT Communication Guide
91
7.3.1 Data reading
The function Read Multiple Registers (page 133) has to be used for data reading. The terminal sends a query
and from the controller receives either the normal response containing the requested data or the exceptional
response indicating a read error.
It is possible to use function 3 for reading (see Read Multiple Registers on page 133).
It is not possible to read from the middle. The register number must correspond with the beginning of the
data object. The only exception are the objects of multipacket values“(registers 46367 46491) and data
part of the history record“(registers 46543 46667).
All read registers must be implemented. If an unimplemented register appears among the read registers, the
controller returns an error message.
Even unnamed values can be included among read registers. The read value must be treated as
meaningless.
The length of a block is 127 registers.
7.3.2 Data writing
All data can be written by the function Write Multiple Registers (page 138). Data up to 2 bytes can be written
by the function Write Single Registers (page 137), too. The terminal sends a query containing a written data
and the controller either confirms it (normal response) or refuses it (exceptional response).
For writing it is possible to use function 6 (Write Single Registers (page 137)) or function 16 (Write
Multiple Registers (page 138)).
Using function 16 it is possible to write maximum 16 registers at once.
Data cannot be written from the middle. Register number must correspond with the beginning of the data
object. Written data must be complete to perform writing of all requested data objects.
Writing to EEPROM is executed using a queue. The queue is common for writing from all terminals. The
request for next writing is accepted in case that there is empty space in the queue. Otherwise the controller
returns an error message and the terminal must repeat the request.
All written registers must be implemented. If an unimplemented register appears among the read registers,
the controller returns an error message.
It is possible to include also unnamed registers in the written sequence. The controller confirms this writing
but writing of unnamed registers is not performed.

Table of Contents

Question and Answer IconNeed help?

Do you have a question about the ComAp InteliGen NT BaseBox and is the answer not in the manual?

ComAp InteliGen NT BaseBox Specifications

General IconGeneral
ModelInteliGen NT BaseBox
Digital Inputs8
Analog Inputs4
Analog Outputs2
Operating Temperature-20 to +70 °C
Protection ClassIP20
Communication PortsRS232, RS485, Ethernet
Humidity95% non-condensing
Supported protocolsModbus, CAN, J1939
Storage Temperature-40 to +85 °C

Summary

Applications overview

Direct PC connection to Single gen-set

Methods for connecting a PC directly to a single gen-set for communication.

USB connection

Connecting controllers via USB for data transfer and configuration.

RS485 connection

Establishing communication using RS485 serial connections.

Direct PC connection to Multiple gen-sets

Methods for connecting a PC to multiple gen-sets for communication.

RS232/485 connection (I-LB+)

Connecting controllers via I-LB+ module using RS232/RS485.

USB connection via I-LB+ module

Connecting controllers via USB using the I-LB+ module.

Ethernet connection via IB-NT

Connecting controllers via Ethernet using the IB-NT bridge.

Ethernet connection (Direct)

Direct Ethernet connection for controller monitoring and configuration.

Monitoring Local on site - MODBUS

Describes local site monitoring using the MODBUS protocol.

ModBus - Multiple gen-sets

Explains Modbus communication for multiple gen-set systems.

RS232/RS485 – MODBUS (I-LB+)

Modbus communication via I-LB+ using RS232/RS485.

Ethernet - MODBUS (IB-NT)

Modbus communication via Ethernet using the IB-NT bridge.

Remote monitoring

Connection to Internet (Direct)

Setting up direct internet connection for controller monitoring.

Internet connection via AirGate

Using AirGate for internet connection without static IP addresses.

WebSupervisor

Overview of WebSupervisor system for monitoring and control.

Web interface

Accessing controller data and settings via a web browser.

Internet connection via cellular network

Connecting controllers via cellular networks using InternetBridge-NT.

Controller setup

Commands for IGS-NT

List and explanation of commands for IGS-NT controllers.

Commands for IM-NT

List and explanation of commands for IM-NT controllers.

Connection

Recommended CAN/RS485 connection

Guidelines for proper CAN and RS485 physical connections.

Communication

Modbus Communication

Overview of Modbus communication protocols and setup.

Examples of Modbus Communication

Practical examples of Modbus communication scenarios.

Modbus Connection

Modbus Step by Step

A step-by-step guide for establishing Modbus connection.

Important setpoints in the controller

Key controller settings required for Modbus communication.

Modbus communication via RS232 – single controller

Configuring Modbus communication over RS232 for a single controller.

Modbus communication via RS485

Configuring Modbus communication over RS485.

Related product manuals