Manuals+

SENECA Z-KEY MBUS and R-KEY MBUS User Manual

1. Introduction

This user manual extends the information from the installation manual to the configuration of the device. Use the installation manual for more information.

ATTENTION! SENECA s.r.l. or its suppliers will not be responsible for the loss of data/revenue or consequential or incidental damages due to negligence or bad/improper management of the device, even if SENECA is well aware of these possible damages. SENECA, its subsidiaries, affiliates, group companies, suppliers and distributors do not guarantee that the functions fully meet the customer's expectations or that the device, firmware and software should have no errors or operate continuously.

ATTENTION! Button PS1 is not used at the moment in the Z-KEY-MBUS instrument.

1.1. Description

The Z-KEY-MBUS / R-KEY-MBUS products autonomously read (they are Meter Bus masters) the registers of the Meter Bus slave devices (M-BUS, max 25 slaves) and make them available for access via the serial ports, the USB port (Z-KEY-MBUS only) or via the Ethernet port.

At the serial/USB ports, the Meter Bus bus values can be accessed via the Modbus Master protocol (the Modbus RTU Slave protocol is implemented in the KEY device).

The Ethernet port can be accessed via the Modbus TCP-IP Client protocol (the Modbus TCP-IP server protocol is implemented in the KEY device).

Seneca devices can be connected to a maximum of 25 M-BUS slave devices and can manage up to 500 M-BUS variables (tags). An M-BUS variable can occupy up to 4 Modbus registers, making available up to 2000 Modbus registers (to which 32 Modbus diagnostic registers must be added).

To configure the device, the integrated webserver can be used without the need for external software. The connection configurations working simultaneously for both models are shown below.

Diagram showing connection configurations for Z-KEY-MBUS and R-KEY-MBUS devices. The Z-KEY-MBUS connects to a network via Ethernet (Modbus TCP-IP) and to M-BUS devices via RS485. It also has a USB port for Modbus RTU. Multiple clients can connect via Modbus TCP-IP. The R-KEY-MBUS connects similarly via Ethernet and M-BUS.

2. Application Fields

2.1. Connection with a PLC

The most common application is the Z/R-KEY-MBUS connection with a PLC. The PLC must support one of the following protocols:

The following example is related to Z-KEY-MBUS but is interchangeable with R-KEY-MBUS:

Diagram illustrating the connection of a Z-KEY-MBUS device to a PLC. The PLC communicates with the Z-KEY-MBUS via Modbus TCP-IP over Ethernet, and the Z-KEY-MBUS communicates with M-Bus devices via RS485. Multiple M-Bus devices can be connected.

2.2. Connection with a SCADA

To connect a SCADA to the Z/R-KEY-MBUS gateway, the SCADA must support at least one of the following protocols:

Practically all SCADAs support these protocols. There are virtually no limits to the number of Z/R-KEY-MBUS gateways that can be connected to a SCADA.

Diagram illustrating the connection of a SCADA system to Z/R-KEY-MBUS gateways. The SCADA communicates with the gateways via Modbus TCP-IP over Ethernet. The gateways, in turn, communicate with M-Bus devices via RS485. Multiple gateways can be connected to a single SCADA.

3. Ethernet Port

The factory configuration of the Ethernet port is:

Multiple devices must not be inserted on the same network with the same static IP. If you want to connect multiple devices on the same network, you need to change the IP address configuration using the Webserver or the Seneca Discovery software.

ATTENTION! DO NOT CONNECT 2 OR MORE FACTORY-CONFIGURED DEVICES ON THE SAME NETWORK, OR THE DEVICE WILL NOT WORK (CONFLICT OF IP ADDRESSES 192.168.90.101)

If the addressing mode with DHCP is activated and an IP address is not received within 2 minutes, the device will set an error IP address such as: 169.254.x.y, where x.y are the last two values of the MAC ADDRESS.

4. Step-by-Step Guide for First Access to the Webserver

STEP 1: Power and Connect the Ethernet Port

STEP 2: Seneca Discovery Device Software Installation

Download the Seneca Discovery Device software from the Seneca website in the Z/R-KEY-MBUS section.

STEP 3: Search for the Device

Run the software and press the “SCAN” button. The software will search for the Ethernet devices in the network. Locate the Z/R-KEY-MBUS device (factory default address 192.168.90.101).

Screenshot of the Seneca Discovery Device software showing a found Z-KEY-MBUS device with its IP address, MAC address, and firmware version.

The software works at Ethernet Layer 2 level, so an Ethernet configuration compatible with the device is not necessary.

STEP 4: Change of IP Address

Select the device and press the “Assign IP” button. Set a configuration compatible with your PC, for instance:

Screenshot of the Assign IP dialog in the Seneca Discovery Device software, allowing the user to set a new IP address, Netmask, and Gateway for the device.

Confirm with OK. The device can now be reached via Ethernet from your PC.

STEP 5: Access to the Configuration Webserver

Wait for the device to restart and press the “Open Webserver” button. Enter your access credentials:

ATTENTION! THE WEB BROWSERS WHICH HAVE BEEN TESTED FOR COMPATIBILITY WITH THE DEVICE WEBSERVER ARE: MOZILLA FIREFOX AND GOOGLE CHROME. THEREFORE, THE OPERATION WITH OTHER BROWSERS IS NOT GUARANTEED.

5. Webserver Device Configuration

For further information on accessing the webserver of a new device, refer to chapter 4.

ATTENTION! THE WEB BROWSERS WHICH HAVE BEEN TESTED FOR COMPATIBILITY WITH THE DEVICE WEBSERVER ARE: MOZILLA FIREFOX AND GOOGLE CHROME. THEREFORE, THE OPERATION WITH OTHER BROWSERS IS NOT GUARANTEED.

5.1. Access to the Web Server

Access the web server using a web browser and entering the IP address of the device. To find the IP address, use the "search" function of the "Seneca Discovery Device" software (see chapter 4).

On first access, the username and password will be requested. The default values are:

ATTENTION! AFTER THE FIRST ACCESS, CHANGE USERNAME AND PASSWORD IN ORDER TO PREVENT ACCESS TO THE DEVICE TO UNAUTHORIZED PEOPLE.

Screenshot of the webserver login page, showing fields for username and password, with default values provided.

ATTENTION! IF THE PARAMETERS TO ACCESS THE WEBSERVER HAVE BEEN LOST, TO ACCESS IT, IT IS NECESSARY TO GO THROUGH THE PROCEDURE TO RESET THE FACTORY-SET CONFIGURATION.

5.2. Webserver Sections

The Webserver is divided into pages (sections) representing the various gateway functions:

Webserver interface screenshot showing different sections: Status, Setup, M-Bus Devices, Scan M-Bus, Setup Tag, and Update.

5.3. "Status" Section

In the status section, it is possible to view the tag values in real time together with their fail/ok status:

Status section of the webserver displaying real-time tag values, firmware version, network configuration (IP, Mask, Gateway, MAC), and M-Bus loop time. It also shows a table with Tag Name, Gateway Tag NR, Modbus Register, Tag Data Type, Tag Value, and Tag Reading Status.

50 tags per page maximum can be displayed, with a maximum of 10 pages. Basic information, including the device interrogation loop time, is displayed in the top part of the page.

5.4. "Setup" Section

This section allows for the basic configuration of the device.

Exception: The response to the Modbus request of the tag in fail will be an exception.

Last Value Read: The response to the Modbus request of the tag in fail will be the last valid value.

Max: The response to the tag Modbus request will be the maximum value that can be represented by the type of data.

Min: The response to the tag Modbus request will be the minimum value that can be represented by the type of data.

Zero: The response to the tag Modbus request will be 0.

In addition, a configuration can be exported / imported via the webserver.

5.4.1. Saving a Configuration on a File

A configuration that includes: CONFIGURATION, M-BUS DEVICE, TAG can be saved to a file. Go to the "Setup" section, select the file to save, and press the “Save config" button.

Webserver interface showing the 'Setup' section with options to choose a file, save configuration, and load configuration.

5.4.2. Importing a Configuration from a File

A configuration that includes: CONFIGURATION, M-BUS DEVICE, TAG can be imported from a file. Go to the Update section and select the file to load, press the "Load config" button.

Webserver interface showing the 'Update' section with options to choose a file, load configuration, and save configuration.

5.5. "M-BUS Devices" Section

This section shows the M-BUS devices inserted in the gateway. It is possible to delete all the tags related to a device by deleting the device from the list of devices.

5.5.1. Replacement of an M-Bus Device

It is also possible to change the address (for example in case of replacement) using the "MODIFY" button.

Webserver interface for modifying M-Bus device details, including Device Description Name, Address Type, Identification Number, Manufacturer Number, Version Number, Medium, Baudrate, and Manufacturer.

5.5.2. Manual Addition of an M-Bus Device

By means of the "ADD" button, it is possible to access the addition of an M-BUS device in manual mode. Z/R-KEY-MBUS has a database growing continuously with the devices of the main brands.

Webserver interface for adding an M-Bus device manually. It shows fields for Device Description Name, Address Type, Primary Address, Baudrate, Manufacturer, and Model. Options to apply with or without data points are available.

A = Select the brand of the device to insert

B = Select the model of the device to insert

C = Select if the device must be interrogated via primary or secondary address

D = Device address

E = Device Baud rate

If you only want to insert the device without the tags, press the "APPLY WITHOUT DATA POINTS SELECTED" button.

If you only want to insert both the device and the selected tags, press the "APPLY WITH DATA POINTS SELECTED" button.

5.6. "Scan M-Bus" Section

5.6.1. Scanning the M-Bus

In the SCAN M-BUS section, it is possible to automatically scan the bus.

Webserver interface for scanning the M-Bus. Options include Scan Baud mode, Scan Primary, Scan Secondary, Stop Scan, and Add Selected Device. A table displays found M-Bus devices with their Number, Address Type, Address, and Baudrate.

If you do not know the primary address nor the baudrate of the M-BUS devices, it is recommended to perform a secondary scan at all baud rates (it may take several minutes). If it is known that there are no conflicts of primary address, a scan by primary address can be carried out.

As devices are found, they appear on the screen, for example:

Table showing a list of discovered M-Bus devices, including their M-Bus Device Number, Address Type, M-Bus Address, and M-Bus Baudrate.

The scan remains saved in the flash memory of the device until a new scan is requested.

5.6.2. Addition of an M-Bus Device and Your Tags

Once the bus has been scanned, it can be added to the list of M-BUS devices by selecting it from the list and pressing the "Add Selected Device" button.

Webserver interface showing the scan status and a list of found M-Bus devices. The user can select a device and add it with its data points.

At this point, you can choose which device tags to add to the Z/R-KEY-MBUS device.

Webserver interface for adding M-Bus device tags. It displays device information and a list of data points with options to select and convert them to Modbus registers.

DATA POINT NUMBER: Represents the number of the variable in the datagram.

TYPE: Represents the type of the variable; parameters are also available.

Storage number: Indicates the identification number of the memory location where data is stored. If a counter has multiple values of the same type, the storage number differentiates them.

Tariff: Indicates the tariff number associated with the value, used for consumption with multiple tariff bands (e.g., differentiated day/night tariffs). A tariff of 0 indicates no tariff differentiation.

Unit: Specifies the unit of measurement for the transmitted value (e.g., litres, m³, kWh).

Data Field: Contains the numerical value of the measurement (e.g., energy consumption, water volume, temperature). It can include various data formats like numeric, date/time, or special values (error/status code).

Function Field: Specifies the type of measured value and how it was detected:

DIF (Data Information Field): Mandatory field describing the size, format, and structure of the transmitted data (e.g., length in bytes, integer/real, date-time, presence of DIFE extensions).

VIF (Value Information Field): Mandatory field defining the physical type of the data and its unit of measurement (e.g., volume (litres), energy (kWh), temperature (°C)). Additional extensions (VIFE) may be used if the description is insufficient.

DIFE (Data Information Field Extension): Optional field for additional information not included in DIF, such as Storage number, Tariff, historical memory indication.

VIFE (Value Information Field Extension): Optional field expanding the VIF by providing additional details, scale factors, or precision of the measured data.

VALUE: Represents the numeric value of the variable at the time of the scan.

CONVERT TO DATA TYPE: Represents the data type to which the variable must be converted in the Modbus registers.

SCALE TO BASE UNIT: If enabled, scales the measurement in the base unit of measurement (e.g., converts Wh*E-2 to Wh).

SELECT: Selects which variable to import into the Modbus registers.

TAG NAME: It is the mnemonic of the variable.

ATTENTION! IF NO TAG IS SELECTED, THE SYSTEM WOULD ADD TO THE LIST ONLY THE M-BUS DEVICE.

Now press the "ADD DEVICE WITH DATA POINT SELECTED" button. The tags and the device are automatically added to the Z/R-KEY-MBUS list. To verify the addition, you are automatically returned to the M-BUS DEVICES section.

Webserver interface showing the list of added M-Bus devices, with options to add, modify, or delete devices.

Added tags can be seen in the instant view (Status section) and/or in the Tag Setup section.

5.7. "Tag Setup" Section

In this section, it is possible to modify the tags manually.

Webserver interface for setting up tags, showing a table with Gateway Tag NR, Gateway Modbus Start Register Address, Gateway Tag Name, Target M-Bus Device, Target Register Data Type, and Target Scaling Mode.

It is possible to delete all tags related to a device by deleting the device from the list in the M-BUS Devices section.

With the “ADD” button, a new tag related to an M-BUS device can be added.

The "CLONE" button allows cloning and editing a previous tag.

The "DELETE" button allows deleting a tag.

The MOVE UP/DOWN button allows moving the tag's position.

GATEWAY TAG NR: This is the number of set tags.

GATEWAY MODBUS START REGISTER ADDRESS: It is the address of the starting Modbus register in the Modbus registers with the convention 1-BASED (1=40001/30001) etc.

GATEWAY TAG NAME: It is the mnemonic of the variable.

TARGET M-BUS DEVICE: It is the MBUS device to which the variable is associated.

TARGET REGISTER DATA TYPE: It is the data type of the Modbus register associated with the MeterBUS variable.

TARGET SCALING MODE: If enabled, it allows scaling the variable with a GAIN and an OFFSET. The scaling obtained is of the type: Variabile Scalata = (Variabile * GAIN) + OFFSET.

ATTENTION! Scaling will only take effect if the “Target Register Data Type” is REAL.

TARGET SCALE GAIN: Represents the Gain of the scaling.

TARGET SCALE OFFSET: Represents the offset of the scaling.

5.8. "Firmware Update" Section

5.8.1. Firmware Update

To improve, add, and optimize the product's functions, Seneca releases firmware updates on the device section of the www.seneca.it website.

Select the new firmware file and press the "Update firmware" button.

Webserver interface for firmware update, with options to select a firmware file and update.

ATTENTION! NOT TO DAMAGE THE DEVICE, DO NOT REMOVE THE POWER SUPPLY DURING THE FIRMWARE UPDATE OPERATION.

5.8.2. Database Update

Seneca releases new updated Database tool files on the device section of the website www.seneca.it. The Database is used when a new M-BUS device is entered in manual mode.

To update the database, select the file and press the "Update Database" button. The device is already updated at the factory with the most recent database at the time of production.

6. Supported Modbus Communication Protocols

The Modbus communication protocols supported are:

For more information on these protocols, see the website: http://www.modbus.org/specs.php.

6.1. Supported Modbus Function Codes

The following Modbus functions are supported:

ATTENTION! All 32-bit values are contained in 2 consecutive registers.

7. Modbus Register Mapping

Z/R-KEY-MBUS provides two different data areas accessible via Modbus RTU / Modbus TCP-IP protocols: The TAG area and the Diagnostic area. In the Tag area, the values coming from the M-BUS are contained; in the diagnostic area, the fail/ok statuses of the tags are contained:

REGISTER TAG AREA START TAG AREA END DIAGNOSTIC AREA START DIAGNOSTIC AREA END
40001 (4x 0001) (offset 0) TAG AREA START
41001 (4x 1001) (offset 1000) TAG AREA END
41002 (4x 1002) (offset 1001) Reserved Area start
49000 (4x 9000) (offset 8999) Reserved Area end
49001 (4x 9001) (offset 9000) DIAGNOSTIC AREA START
49032 (4x 9032) (offset 9031) DIAGNOSTIC AREA END

7.1. Mapping of the Tag Area (Holding Registers)

Measurement variables from M-BUS are converted into tags accessible from the Modbus bus. The Seneca product will add new tags in the area as new M-BUS devices or new tags are entered. Each variable from M-BUS can occupy 1 or more Modbus registers depending on the type of conversion carried out (for further details, see the following table):

TYPE OF M-BUS DATA CONVERSION MODBUS RTU/TCP-IP (AUTOMATIC) NUMBER OF MODBUS REGISTERS OCCUPIED
SIGNED 8-BIT INTEGER SIGNED 16-BIT INTEGER 1
SIGNED 16-BIT INTEGER SIGNED 16-BIT INTEGER 1
SIGNED 32-BIT INTEGER SIGNED 32-BIT INTEGER 2
SIGNED 48-BIT INTEGER 32-BIT UNSIGNED INTEGER 2
SIGNED 64-BIT INTEGER 64-BIT UNSIGNED INTEGER 2
FLOATING POINT 32 BIT REAL 32 BIT (MSW FIRST) 2
DATE / HOUR 32-BIT DATE/TIME TYPE 2
BCD (BINARY CODED DECIMAL) FROM 2 TO 4 FIGURES 16-BIT UNSIGNED INTEGER 1
BCD (BINARY CODED DECIMAL) 8 FIGURES 32-BIT UNSIGNED INTEGER 2
BCD (BINARY CODED DECIMAL) 12 FIGURES 64-BIT UNSIGNED INTEGER 4

ATTENTION! When converting to a 32-bit Floating Point data type, precision losses may occur. This conversion can lead to differences between the readings on the M-BUS device and those converted on Modbus.

The Modbus register for which the tag is found and the type of data is automatically calculated by Z/R-KEY-MBUS; it is however possible to modify it in the "Setup Tag" section:

Webserver interface for Tag Setup, showing a table with Gateway Tag NR, Modbus Register, Tag Name, Target M-Bus Device, Target Register Data Type, and Target Register.

The types of data converted automatically are:

16-BIT SIGNED INTEGER DATA TYPE
RANGE NUMBER OF HOLDING REGISTER MODBUS REGISTERS
-32768/+32767 1 1
16-BIT UNSIGNED INTEGER DATA TYPE
RANGE NUMBER OF HOLDING REGISTER MODBUS REGISTERS
0/+65535 1 1
32-BIT SIGNED INTEGER DATA TYPE
RANGE NUMBER OF HOLDING REGISTER MODBUS REGISTERS
-2147483648 / +2147483647 2 2

Occupying 2 modbus registers, the data is represented as follows:

REGISTER n REGISTER n+1
Most significant part Least significant part
32-BIT UNSIGNED INTEGER DATA TYPE
RANGE NUMBER OF HOLDING REGISTER MODBUS REGISTERS
0 / +4294967295 2 2

Occupying 2 modbus registers, the data is represented as follows:

REGISTER n REGISTER n+1
Most significant part Least significant part
64-BIT UNSIGNED INTEGER DATA TYPE
RANGE NUMBER OF HOLDING REGISTER MODBUS REGISTERS
0 / +18446744073709551615 4 4

Occupying 4 modbus registers, the data is represented as follows:

REGISTER n REGISTER n+1 REGISTER n+2 REGISTER n+3
Most significant part Most significant part Least significant part Least significant part
REAL 32-BIT MSW DATA TYPE (FLOATING POINT IEEE-754)
RANGE NUMBER OF HOLDING REGISTER MODBUS REGISTERS
1.175495e-38 / 3.40282346e+38 2 2

Occupying 2 modbus registers, the data is represented as follows:

ADDRESS REGISTER n ADDRESS REGISTER n+1
Most significant part Least significant part

For further information on the type of 32-bit Real data, refer to the following website: https://en.wikipedia.org/wiki/IEEE_754. For online conversion tools, refer to the website: https://www.h-schmidt.net/FloatConverter/IEEE754.html.

DATE/TIME DATA TYPE
RANGE NUMBER OF HOLDING REGISTER MODBUS REGISTERS
01/01/2000 / 31 December 2127 2 2

It is possible to change the type of data selected automatically by Z/R-KEY-MBUS in the "TAG Setup" section. In particular, it is possible, for instance, to change the data type from Real 32 BIT MSW to LSW (Reverse Real).

REAL 32-BIT LSW DATA TYPE (FLOATING POINT IEEE-754)
RANGE NUMBER OF HOLDING REGISTER MODBUS REGISTERS
1.175495e-38 / 3.40282346e+38 2 2

Occupying 2 modbus registers, the data is represented as follows:

ADDRESS REGISTER n ADDRESS REGISTER n+1
Most significant part Least significant part

7.2. Mapping of the Diagnostic Area (Holding Registers)

A diagnostic bit is available in the holding registers for each tag. For example, in the 16-bits register 49001 (offset 9000), the statuses of the first 16 tags are contained in this way:

TAG
16151413121110987654321
TAGTAGTAGTAGTAGTAGTAGTAGTAGTAGTAGTAGTAGTAGTAGTAG
16151413121110987654321

Where the meaning of the bit is the following:

ADDRESS (4x) OFFSET REGISTER W/R REGISTER TYPE
49001 4x9001 9000 DIAGNOSTIC TAG 1..16 RO UNSIGNED 16 BIT
49002 4x9002 9001 DIAGNOSTIC TAG 17..32 RO UNSIGNED 16 BIT
49031 4x9031 9031 DIAGNOSTIC TAG 481..496 RO UNSIGNED 16 BIT
49032 4x9032 9032 DIAGNOSTIC TAG 497..500 RO UNSIGNED 16 BIT

8. Resetting to Factory Configuration

If the credentials to access the webserver are lost, it is always possible to return the device to its factory conditions:

This way:

  1. Turn off the device.
  2. Turn all SW1 dip switches ON:
    Illustration of SW1 dip switches, with switches 1 and 2 shown in the ON position.
  3. Turn on the device.
  4. Wait at least 10 seconds.
  5. Turn off the device.
  6. Turn all SW1 dip switches OFF:
    Illustration of SW1 dip switches, with switches 1 and 2 shown in the OFF position.

When the device is switched on again, it will start with its factory configuration.

ATTENTION! In some models there are 4 dip switches, in this case dip switches 3 and 4 must ALWAYS be kept in the "OFF" state.

Models: TCP-IP RTU ModBUS RTU TCP-IP I O Module, TCP-IP RTU, ModBUS RTU TCP-IP I O Module, TCP-IP I O Module, Module

File Info : application/pdf, 33 Pages, 1.27MB

PDF preview unavailable. Download the PDF instead.

mi00592-3-en ?srsltid=AfmBOoqSybDK0rCM8DIxnItrqaydxVR8watmzqyTsAAW1ssOiaJhi4B9

References

Microsoft Word 2019

Related Documents

Preview Manuale Utente Z-KEY MBUS R-KEY MBUS - SENECA
Manuale utente per i gateway SENECA Z-KEY MBUS e R-KEY MBUS, che convertono protocolli MODBUS (TCP-IP / RTU) in M-BUS (Meter Bus). Include guide alla configurazione, connessione, gestione dei dispositivi e protocolli supportati.
Preview SENECA Industrial Gateways: Protocol Converters for R-KEY & Z-KEY Models
Explore SENECA's range of Industrial Gateways, including R-KEY and Z-KEY models. These protocol converters facilitate seamless data transfer between various industrial networks and fieldbuses, supporting protocols like Modbus, Profinet, Ethernet/IP, OPC UA, and IEC 61850.
Preview Seneca KEY Series Gateways User Manual: OPC-UA / Modbus RTU&TCP
Comprehensive user manual for Seneca's KEY series multiprotocol gateways, detailing configuration, operation, and features for OPC-UA and Modbus communication protocols. Covers hardware, firmware, operating modes, web server access, and Modbus register information.
Preview SENECA KEY Series Multiprotocol Gateways User Manual - IEC 61850 & Modbus
Explore the SENECA KEY series multiprotocol gateways with this user manual. Learn about IEC 61850 and Modbus protocol conversion, device configuration, FLEX technology, firmware updates, and more for industrial automation.
Preview SENECA Gateway Industriali: Convertitori di Protocollo R-KEY e Z-KEY
Scopri la gamma di Gateway Industriali SENECA, convertitori di protocollo R-KEY e Z-KEY. Soluzioni flessibili per la comunicazione tra reti industriali, supportando Modbus, Profinet, Ethernet/IP, OPC UA e IEC 61850.
Preview SENECA R-KEY-LT / R-KEY-LT-P Installation Manual
Installation manual for SENECA R-KEY-LT and R-KEY-LT-P industrial gateways, detailing module layout, LED signals, device configuration, technical specifications, DIP-switch settings, and electrical connections.
Preview SENECA Z-10-D-IN Digital Input Module User Manual
Detailed user manual for the SENECA Z-10-D-IN, a 10-channel digital input module with Modbus RTU communication. Covers features, connections, configuration, and Modbus register mapping.
Preview SENECA IIoT Edge Gateways User Manual: Configuration and Operation Guide
Comprehensive user manual for SENECA's IIoT Edge Gateways (SSD, R-PASS, Z-PASS series). Covers setup, configuration, industrial protocols (Modbus, OPC-UA), data acquisition, security, and advanced features for industrial automation.