Skip to content

Tab: Modules

Introduction

Instances of Modules

We call module instance to each of the 'connection' configurations with a group of devices. Each of these instances can communicate with one or several devices, always of the same protocol. To better understand it, we see what an instance is for any of the supported protocols:

Protocol Channel Details
Modbus RTU 1 rs485 port In the same port 485 you can only be configured 1 instance, It is not shared.
BACnet MS/TP 1 rs485 port In the same port 485 you can only be configured 1 instance, it is not shared.
Modbus TCP 1 remote IP At least one instance is needed for each remote IP with devices (automaton, router ...).
BACnet IP ethernet subnet At least one instance is needed for each subnet of Bacnet devices.
adquio master 1 remote IP At least one instance is needed for each adquio master of devices to which you want to connect.

Module management

In the Modules tab, the instances of the modules can be administered:

List of instances

From here we can:

  • Create instance: from the + button on the top right of the table.
  • For each instance:
  • Start
  • Stop
  • Restart
  • Edit
  • Remove

Instance edition

Instance edition

Identifier of the module instance

This section is common to all protocols. The fields it contains are:

  • Active: Indicates whether the instance should start automatically when the acquire is started. Even if it is not active, it can be started manually.
  • Type: The protocol of the module.
  • Code: Identifier of the instance. Must be unique.

Connection data

The parameters in this section are dependent on the type of module.

  • Port: Physical port connection with the device. It can be a network port or aRS-485, depending on the protocol.

Note: The physical ports RS-485 are exclusive access, that is, you can not access two modules simulataneously to the same port. It can, however, create them for reference or to alternate their use.

  • Baudios, bits, parity and stop bits: Connection parameters for serial communications.
  • Interval of silence: (Modbus RTU) Indicates the minimum silence time on the bus between protocol requests. This value is dependent on the connected devices, if the value is too small, some devices may not respond to requests. By default it is 5MS.
  • Address IP: (Modbus TCP and adquio remote) Network address of the remote device to which we want to connect.
  • Port: (Modbus TCP and remote adquio) Network port of the remote device.
  • User: (remote adquio)
  • Password: (remote adquio)
  • Instance number: (BACnet) Identifier of the local Bacnet device that is created with the instance. The identifier should not match that of no connected Bacnet device.
  • MAC address: (BACnet ) MAC address of the adquio inside the BACnet bus. You must not match any other bus master.
  • Network port: (BACnet IP) Local network port in which to lift the device. Default is 47808 (0xBAC0).
  • Timeout APDU: Waiting time before giving the petition by failed. By default 3 seconds.
  • Retries APDU: Faced with a fault in a request, number of retries before giving it by failed. By default 3.
  • BBMD Address: Network address of the BBMD through which the devices will be accessed.
  • BBMD Port: BBMD network port.
  • TTL BBMD: Life time of subscription in the BBMD. When this time ends, the subscription is automatically refreshed. By default, 1800 seconds.
  • Maximun Master: (BACnet) The maximum number of Master existing on the bus.
  • Maximun info frames: (BACnet) Maximum number of Bacnet messages that the acquirer will send before passing the token. By default 5.