Viltrus Electronics MX-10 User manual

MX-10 User Manual
2 / 64
Table of contents
Table of contents .........................................................................................................................................2
Introduction.................................................................................................................................................. 3
Abbreviations and explanations............................................................................................................3
Preface ....................................................................................................................................................... 3
Symbols ..................................................................................................................................................3
Safety instructions ...............................................................................................................................4
Top label information .............................................................................................................................. 5
Connecting to the device ........................................................................................................................ 5
Diagnostic archive .............................................................................................................................. 11
User defined archive ..........................................................................................................................12
TCP modules............................................................................................................................................17
FTP server ............................................................................................................................................17
FTP client..............................................................................................................................................18
MQTT client ..........................................................................................................................................21
TCP/IP connection table ................................................................................................................... 26
Routing TCP/IP - serial (request/answer)....................................................................................27
Routing TCP/IP - serial (transparent) ...........................................................................................29
Router 4G/GPRS<->Ethernet..........................................................................................................31
Gateway Modbus TCP<->Modbus RTU..........................................................................................33
Hardware ................................................................................................................................................. 37
microSD ................................................................................................................................................37
Time settings .......................................................................................................................................37
Ethernet configuration ...................................................................................................................... 37
4G/GPRS configuration ..................................................................................................................... 39
Limits ....................................................................................................................................................42
Alerts.....................................................................................................................................................43
Serial ports...........................................................................................................................................46
Virtual COM clients.............................................................................................................................48
Modbus RTU clients............................................................................................................................50
Modbus RTU servers ..........................................................................................................................52
Meters.......................................................................................................................................................53
M-bus meters ......................................................................................................................................53
Modbus devices...................................................................................................................................57
Overview ..............................................................................................................................................62
Firmware update ....................................................................................................................................62

MX-10 User Manual
3 / 64
Introduction
Abbreviations and explanations
Xn –is a number of sockets. This information are provided for manufacturer’s purpose and used in data
schemas and connection diagrams.
GSM –Global Standard for Mobile Communications. This interface is prepared for remote connections
and data bidirectional data transfer over Global Standard Mobile network.
GPRS - a packet oriented mobile data service on the 2G and 3G cellular communication system's global
system for mobile communications (GSM).
Ethernet - a family of computer networking technologies for local area networks (LANs) commercially
introduced in 1980. Standardized in IEEE 802.3, Ethernet has largely replaced competing wired LAN
technologies. This interface is prepared for connection LAN (Local Area Network).
IP address - An Internet Protocol (IP) address is a numerical label that is assigned to devices participating
in a network that uses the Internet Protocol for communication between its nodes.
TCP/IP –Transmission Control Protocol is for communication between computers, used as a standard for
transmitting data over networks and as the basis for standard Internet protocols.
MAC address –Media Access Control address is a unique identifier assigned to most network adapters.
UART –An Universal Asynchronous Receiver/Transmitter is a type of “asynchronous receiver/transmitter,
a part of computer hardware that translates data between parallel and serial forms. UART are commonly
used in conjunction with communication standards such as EIA RS-232, RS-422 or RS-485. Record
(UARTx) on top of enclosure also is used as serial interface number.
GND –ground wire contact
RS485 - standard defining the electrical characteristics of drivers and receivers for use in balanced digital
multipoint systems. The standard is published by the ANSI Telecommunications Industry
Association/Electronic Industries Alliance (TIA/EIA). Digital communications networks implementing the
EIA-485 standard can be used effectively over long distances and in electrically noisy environments.
Multiple receivers may be connected to such a network in a linear, multi-drop configuration. RS485
interfaces are prepared for connection of peripherical devices (example energy meters, controllers,
machines and etc.).
A+ –contact for positive wire of RS485 socket
B- –contact for negative wire of RS485 socket
USB –Universal Serial Bus is an industry standard, that defines the cables, connectors and protocols
used for connection, communication and power supply between computer and electronic devices. USB
type B socket is prepared for connection to PC(Personal Computer). USB type A socket is prepared for
connection to peripherical devices (example memory stick’s and etc.).
M-Bus - a European standard (EN 13757-2 physical and link layer, EN 13757-3 application layer) for the
remote reading of gas or electricity meters. The M-Bus interface is made for communication on two wires,
making it very cost effective.
MBUS+ –contact for M-Bus positive wire
MBUS- –contact for M-Bus negative wire
Socket –is an endpoint of a bidirectional inter-process communication flow across an Internet Protocol-
based computer network, such as the Internet.
Status –device status indicating LED
TX/RX –data transfer/receive indicating LED
TXD –data transferring LED indicator
RXD –data receiving LED indicator
100Mbs –Ethernet High speed connection indicating LED
“Alarm mode” – in state of alarm status Controller initiates an event notification for user selected discrete
input mode (Alarm mode: unconnected, connected, both events)
Central computer –server or a computer, where data can be sent.
Preface
Symbols
International electrical symbol list. Some or all symbols can be used on controller marking or in this user
manual.
Symbol
Explanation

MX-10 User Manual
4 / 64
With the CE marking on a product the manufacturer ensures that the product conforms with the
essential requirements of the applicable EC directives.
DC (Direct Current)
Caution
Grounding
LED indicator
Contact number on plug
Directive on the restriction of the use of certain hazardous substances in electrical and
electronic equipment 2002/95/EC. Commonly referred to as the Restriction of Hazardous
Substances Directive or RoHS)
Waste Electrical and Electronic Equipment Directive
Safety instructions
To install and setup device, special technical knowledges are needed. Call to seller or certified
professionals to connect and setup device!
Before connecting to power supply, be sure that:
1. Controller is not damaged (no cracks, melted, broken or exposed areas )
2. Controller is used with right and correct thickness cables.
3. Controller and antenna are installed indoor.
4. The controller is intended for supply from a Limited Power Source (LPS) with current
rating of over current protective device not greater than 2A
5. The highest transients on the DC secondary circuit of LPS, derived from AC main supply,
shall be less then 71V peak.
6. The associated equipments (AE): PC and PSU (LPS) shall comply with the requirements
of Standard EN 69050-1.
7. Controller is dry;
8. Ambient temperature and humidity is in normal range;
9. Other types of devices (counters, etc.) are connected correctly by using manufacturer‘s
regulations.
10. The end of stranded conductor shall not be consolidated by soft soldering and must to be
terminated
11. Device, PC and other peripherical devices are strictly connected through one double pole
breaker (current break less than 5A and space between breaker contacts more than 3mm.)
Pole breaker has to be in building‘s wiring and in reachable place with markings

MX-10 User Manual
5 / 64
Don‘t use:
1. Device under open water (in rain and if water are splashing on controller or connected
devices;
2. Device if enclosure, connected cables, or other connected devices are damaged;
Use device by manufacturer‘s regulations otherwise you can damage controller or
other devices. In that case manufacturer‘s warranty could not be obtained.
If you suspect that device doesn‘t operate correctly or has visible violations, please
contact manufacturer or your distributor to check or run maintenance.
Top label information
Overview
This label provides common information about controllers and if you will need any consultations from
technical center or manufacturer, please let them know full Manufacturer’s code and Serial No.
Connecting to the device
Overview
USB port is used for local configure of device. Also it is possible configure device via Ethernet, 3G modem
or any of UARTS if them are used as Modbus slaves. All configuration is made using Modbus protocol and
using device configuration tool software which can be downloaded from manufacture website.
Connecting over USB
Use USB Type-A to Type-B cable to connect device to computer.
•a) To device USB Type-B

MX-10 User Manual
6 / 64
•b) To computer USB Type-A
If USB drivers not installed automatically you need to install them manually. Follow these steps:
1. Double-click the device category, and then double-click the device you want.
2. Click Update Driver, and follow the instruction
3. Select "Browse my computer for driver software", click "Browse" and select configuration software
folder.

MX-10 User Manual
7 / 64
4. Click "Next".
5. Wait while Windows installs driver. If you see message "Windows can't verify the publisher ...." select
"Install this driver software anyway".
6. After installation you will see something like "USB serial device Virtual Com Port" and com port number.
Use this com port for connection with configuration tool.

MX-10 User Manual
8 / 64
On some Windows versions (Windows 8, windows 10) you will need to disable third party
driver signature checking before installing device driver. Please check on Internet how to do this.
Configuration tool software
After USB driver is installed run device configuration tool software.
Select connection type "Modbus RTU" and appropriate COM port. Press "Get all configuration" to read all
device configuration.
Other functions:
•"Get all configuration" button - read all configuration from device
•"Save to file" button - save all configuration to file. So later it is possible to load this configuration to
device.
•"Load from file" button - load saved configuration from file.
•"Write all configuration" - write loaded configuration to device.
•"Get all at connection" check box - reads all configuration when connecting over TCP/IP connection
•Connection type "Modbus RTU" - connect to device over USB or serial port.
•Connection type "Modbus TCP/IP" - connect to device over TCP/IP connection.
•"User identification" section - user configured device ID.
•"Number of controller" section - device serial number
•"Reserve power control" section - this is visible only if device has installed backup battery.
o"After which time switch off" time - power off device after configured time if main power supply
disconnects
•"Float number format" - floating point data byte order, E - exponent, M1, M2, M3 - Mantissa
•"Last restart information" - time of last reset and reset code. Reset code values:
1 - No TCP packet over GPRS in configured time
2 - GPRS task stops working
3 - Not enough heap memory
4 - Firmware update reset
5 - Modbus reset
6 - Unable connect to GPRS
7 - External pin reset
8 - Watchdog reset
9 - Brownout reset
10 - Power up reset
11 - No TCP packet over ETHERNET in configured time
12 - ETHERNET task stops working
13 - All TCP sockets is used (if defined UIP_RESET_ALL_CONN_USED)
14 - Periodic reset

MX-10 User Manual
9 / 64
Program modules
Archive
Overview
Device has several types of archives:
•Events archive. All events will be saved here (Analog inputs alarms, Discrete inputs alarms, Limits
verification). Events is used to generate SMS messages, MQTT event messages, emails.
•Diagnostic archive. It is a list of changes made in device. It's resets, configuration changes,
connection/disconnection to GPRS network and other
•User defined. It's user configured archive, user can add any existing data register archive.
All archives are saved to internal data flash memory. Maximum archive records count depends on memory
size and separated place. If Micro SD card presents archives is duplicated to SD card (For every day is
created new file with date stamp).
Events archive
Overview
All events are saved to events archive. Events sources can be:
•Analog input events
•Discrete input events
•Events generated from "Limits verification" module
Event archive is used to generate SMS, MQTT messages, emails. For every event ID you can configure
event message text.
Event message text can be configured in "Alerts->Transmission method"

MX-10 User Manual
10 / 64
Reading event archive over Modbus file system
Event archive can be read using Modbus read file function 20.
Modbus
function
Modbus ID
Modbus file
address
Max registers
in file
Records in file
Current record
count register
20 - Read File
Record
Modbus RTU -
254
Modbus TCP -
255
400 .. 499
10000
1250
4910
Event archive record structure:
The variable name
Purpose / Value
Type of value
Time
Time of alarm
Long int (32 bits)
Alarm identifier
Every identifier is change +1
Long int (32 bits)
Alarm source
The oldest byte value (alarm
source):
0 –Analog input alarm,
1 –Discrete input alarm,
4 -Limits alarm.
Youngest byte value:
if alarm source 0 or 1 then
channel number;
if alarm source 4 then index from
limits table (start from 0 to 99)
Int (16 bits)
Type of deviation
If alarm source 0 then:
if value 1 –Analog input deviation
below the lower alarm value.
2 - Analog input deviation above
the upper alarm value.
If alarm source 1 then value
always 0.
Int (16 bits)

MX-10 User Manual
11 / 64
If alarm source 4 then value is
limits alarm ID.
Deviation value
If alarm source 0 then Analog
input value.
If alarm source 1 then Discrete
input value.
If alarm source 4 then Limits
value.
Float
Total 16 bytes
Records transferred from newest to oldest. For example: to read the latest event archive record shall
contain the following information:
File address: 400
Register address: 0
Register count: 8 (16/2, event archive structure length/2)
If the 5 oldest then:
File address: 400 + (5/1250) (record number/record count in file)
Register address: 8*(5-1)
Register count: 8 (16/2, event archive structure length/2)
Diagnostic archive
Overview
Diagnostic archive is a list of changes made in device. It's useful for debug purpose
Reading diagnostic archive over Modbus file system
Diagnostic archive can be read using Modbus read file function 20.
Modbus
function
Modbus ID
Modbus file
address
Max registers
in file
Records in file
Current record
count register
20 - Read File
Record
Modbus RTU -
254
Modbus TCP -
255
900 .. 999
10000
1250
4911
Diagnostic archive record structure:
The variable name
Purpose / Value
Type of value
Time
Record time.
If event type=7 then new set time
Long int (32 bits)
Event type
1 - RESET event
2 - Firmware update event
3 –Archive counter change event
4 –Automatic time correction
5 –Time change over MODBUS
6 –Change of internal parameters
7 –Time correction
Long int (32 bits)
Event value (integer)
If event type:
1. Reason of last reset, values:
1. No TCP packet over GPRS in
configured time
2. GPRS task stops working
3. Not enough heap memory
4. Firmware update reset
5. Modbus reset
Long int (32 bits)

MX-10 User Manual
12 / 64
6. Unable connect to GPRS
7. External pin reset
8. Watchdog reset
9. Brownout reset
10. Power up reset
11. No TCP packet over
ETHERNET in configured time
12. ETHERNET task stops
working
13. All TCP sockets is used (if
defined
UIP_RESET_ALL_CONN_USED)
14. Periodic reset
3 Delete of archive index
0 - Alarm archive
1 - Diagnostic archive
2 - User defined archive
4 New time
5 New time
6 Always 0
7 Always 0
Event value (float)
If event type:
1 –always 0
3 –new set value(mostly 0, if
delete all storage)
4 and 5–always 0
6 –always 0
7 –Time correction value (-30s
+30s)
Float (32 bits)
Total 16 bytes
Records transferred from newest to oldest. For example: to read the latest event archive record shall
contain the following information:
File address: 900
Register address: 0
Register count: 8 (16/2, diagnostic archive structure length/2)
If the 5 oldest then:
File address: 900 + (5/1250) (record number/record count in file)
Register address: 8*(5-1)
Register count: 8 (16/2, diagnostic archive structure length/2)
User defined archive
Overview
User can add any device register(value) to user defined archive. So you can make periodic archive of
useful values.
Archive period is in minutes and can be from 1 min to 600 min (10 hours). You can configure it in
configuration tool in "Archives/Configuration" section.
User archive storage period
Archive period is synchronized with real time. If read period is 1 min, records will be generated every
minute (00:00:00, 00:01:00, 00:02:00 ....), If read period is 15 min, records will be generated every 15
minute (00:00:00, 00:15:00, 00:30:00 ....). Delay is used to delay archive time in seconds, for example
period 15 minutes, delay 30 seconds so archives will be made at 00:00:30, 00:15:30... Delay is used to
delay archive process if values is taken from meters, wait until read process ends.

MX-10 User Manual
13 / 64
User archive configuration with configuration software
You can add needed registers to archive using table in "Archives/User archive configuration"
1. "Count of parameters" - number of configured lines in table
2. In „Register" column configure start register of value
3. In "Count of parameters" column configure how many data values will be from start register.
4. In "Format" column configure data value type for current line. Value types can be:
•Signed char (8 bit)
•Unsigned char (8 bit)
•Signed int (16 bit)
•Unsigned int (16 bit)
•Signed long (32 bit)
•Unsigned long (32 bit)
•Signed double long (64 bit)
•Unsigned double long (64 bit)
•Float (32 bit)
•Double float (64 bit)
•Siemens float (32 bit), special siemens data format
•String
•New line, add new line with the same timestamp. Used to add new line record with the same time in
csv file
•Unix time
Reading user archive over Modbus file system
User defined archive can be read using Modbus read file function 20.
Modbus
function
Modbus ID
Modbus file
address
Max registers
in file
Records in file
Current record
count register
20 - Read File
Record
Modbus RTU -
254
Modbus TCP -
255
800 .. 899
Depends on
structure length
Depends on
structure length
4912
Diagnostic archive record structure:
The variable name
Purpose / Value
Type of value
Time
Record time.
Long int (32 bits)
Register values
Values of configured registers.
Register amount can be set in
Long int (32 bits)

MX-10 User Manual
14 / 64
4929 register or in configuration
tool "Archives/User archive
configuration"
How configure registers check
Total 4+2xregister count bytes
Records transferred from newest to oldest. For example: to read the latest user archive record (with 2
registers) shall contain the following information:
User archive structure length = 4+2 registers*2 = 8 bytes = 4 registers
Records in file = 10000/4 registers = 2500
File address: 800
Register address: 0
Register count: 4 (8/2, user archive structure length/2)
If the 5 oldest then:
File address: 800 + (5/2500) (record number/record count in file)
Register address: 4*(5-1)
Register count: 4 (8/2, user archive structure length/2)
If FTP or MQTT clients is used, archive is configured automatically using "Communication/Data
transfer/Common parameters" data table, then at below.
CSV files examples
The following is an example of an archive where data is grouped into a single line, by time stamp.

MX-10 User Manual
15 / 64
The following is an example CSV file where data is aggregated into a single line, by timestamp.
The following is an example of an archive where the data for each meter is added to a new row with common
Header.
This format can be used when all meters parameters names are the same because the file uses common
Headers.
The following is an example CSV file where the data for each meter is added to a new row.

MX-10 User Manual
16 / 64
The following is an example of an archive where the data for each meter is added to a new row without a
Header but with dimensions.
The following is an example CSV file where the data for each meter is added to a new row without a Header
but with dimensions.

MX-10 User Manual
17 / 64
TCP modules
FTP server
Overview
FTP server is used to access internal micro SD card data. You can connect to it using any ftp client
program like "FileZilla", "total commander" or any web browser. FTP server runs on standard 21 port
Connection to FTP server
Before connection you need to know your device IP address and FTP user name/password. FTP server
user name and password can be configured in "Communication/FTP server" tab. User name and password
is max 19 symbol length
Let’s try to connect to device IP 212.47.103.16 and google chrome browser. Use ftp://212.47.103.16 in
browser address line. You will be prompted to enter user name and password, enter them and log in.
Browser will load directory list of SD card. Where are some main directories in device:
•Storage - contains all archives (Contains folders "Alarms", "Diagnostic", "User defined" )
•Firmware - reserved for future (firmware update folder)
•Parameters - contains some device parameters (in some firmware version can be saved csv file
headers/dimensions and other)

MX-10 User Manual
18 / 64
•Device - contains device description file.
FTP client
Overview
FTP client is used to send user archive files to ftp server. Files are with .csv extension and is generated
from saved user archive.
Csv file creator
Overview
Device creates csv report file from user defined archive values, every record in file have it's time stamp
(value record time), it can have "Header" for every value, and dimension for every value. All data in file is
separated by a ";" symbol and every record is placed in new line. Standard file content looks like this:
Time;<Value Header 1>;<Value Header 2>;...<Value Header N>;
<Record 1 Date/Time>;<Value 1 data>;<Value 1 dimension>;<Value 2 data>;<Value 2
dimension>;...<Value N data>;<Value N dimension>;
<Record 2 Date/Time>;<Value 1 data>;<Value 1 dimension>;<Value 2 data>;<Value 2
dimension>;...<Value N data>;<Value N dimension>;
....................................................................................
<Record N Date/Time>;<Value 1 data>;<Value 1 dimension>;<Value 2 data>;<Value 2
dimension>;...<Value N data>;<Value N dimension>;
•<Value Header> - is configured header, from „Communication/Data transfer/Common parameters" tab.
•<Value data> - is configured parameter value taken from user archive.
•<Value dimension> - is configured dimension, from „Communication/Data transfer/Common
parameters" tab.
•<Record Date/Time> - is stored archive record time
CSV file creator table
Device creates csv report file from user defined archive values and data configured in
"Communication/Data transfer/Common parameters" tab or in "Archives/User archive configuration" (from
1.58 version).
•"Amount of groups of register" number field - table lines count
•"Set user archive" checkbox - always check this, it automatically configure user defined archive.
•"Register/Coil" column - value internal start register. You can configure any internal value register from
0 to 65535 (Function 3 - read holding registers) or from 100000 to 165535 (Function 4 - read input
registers)
•"Amount of parameters or string length" column - value count from start register. It can be from 1 to 50.
This can be used to configure up to 50 values from start register in one line, problem is what you get
the same header and the same dimension for every value.
•"Format" column - value format. In Modbus protocol you need know value format before to read it,
otherwise you will read hexadecimal values with whom it is difficult to operate. In some firmware
version not all formats can be supported. List of data formats:

MX-10 User Manual
19 / 64
oSigned char (8 bits)
oUnsigned char (8 bits)
oSigned integer (16 bits)
oUnsigned integer (16 bits)
oSigned long (32 bits)
oUnsigned long (32 bits)
oFloat (32 bits)
oDouble float (64 bits)
oSiemens float (32 bit), special siemens data format
oString
oNew line, add new line with the same timestamp. Used to add new line record with the same
time in csv file
oUnix time
•"Header" column - value header in csv file. If count of values is configured more than 1, for all of them
is used the same header.
•"Dimension" column - value dimension in csv file. If count of values is configured more than 1, for all of
them is used the same dimension.
•"Set" button - write configuration to device.
•"Get" button - read configuration from device.
•"Load from csv" button - load saved configuration table from csv file.
•"Save to csv" button - save configuration table to csv file.
Example
With this configuration received file will be like this:
Time;Value INT16;;Value INT32;;Value FLOAT;;
2017.11.22 12:00:00;123;m3;123456;kWh;1.0000;m3/h;
2017.11.22 13:00:00;124;m3;123459;kWh;1.0000;m3/h;
2017.11.22 14:00:00;125;m3;123468;kWh;1.0000;m3/h;
2017.11.22 15:00:00;128;m3;123475;kWh;1.0000;m3/h;
FTP client configuration
Overview
CCV file can be send up to 4 FTP servers. Supported only FTP protocol, passive mode, user/password
authentication, file format csv.

MX-10 User Manual
20 / 64
FTP client configuration
All configuration is made in "Communication/Data transfer/FTP" tab. Before configure you need to have
working ftp server and have some information like its IP address or URL address and connection user
name and password.
Where are some section in this tab:
•"File transfer configuration" section:
o"Enabled" checkbox - enable appropriate ftp server.
o"FTP port" - appropriate ftp server TCP port.
o"Transfer period (min)" - file send period. Value in minutes and can be from 1 min to 1440 min
(24 hours).
o"Repeat transfer if failure (min)" - try resend file after configured time if file transfer failed. Value
in minutes and can be from 1 min to 1440 min (24 hours). Recommended value is half transfer
period.
o"Max number of last records to be send" - maximum last records to include in csv file. Only new
records will be included in file. If it is time to send file and new records count is 25 and max
number of last records configured to 20, in file will be only 20 newest records, last 5 will be lost.
If new records count is 5 and max number of last records configured to 20, in file will be 5 new
records. Values can be from 1 to 200.
o"Transmission channel" - device can have 2 transfer channels Ethernet and GPRS. Select
which to use for appropriate FTP server.
•"FTP server address" section:
o"URL and directory" column - IP or URL address of FTP server (Up to 127 symbols). Can be
used as IP address - "127.0.0.1" or URL - "www.myftp.com". Also available to use directory
listing like : "www.myftp.com/MyFiles/"
•"User names" section:
o"User name" column - user name for appropriate FTP server.
•"Passwords" section:
o"Password" column - password for appropriate FTP server.
•"File send status" section:
o"Status" column - current status of FTP client. After file was send to server, status sets to "File
transmitted". Where are several other status for process check: "Connecting to server",
"Sending user", "Sending password", "Sending data file" and other.
o"Successful/attempt/last record transfer times" column - shows times of some operations.
"Successful" time is the time of last successful finished file send to FTP server operation.
"Attempt" time is the time of last attempt send file to FTP server (can be successful or not).
"Last record transfer" time is the last send record time.
•"File name template" section - file name can be up to 127 symbols with extension "csv". In file can be
fixed fields which will be changed to date and time. Fixed fields:
YYYY –year
MM –month
DD –day
HH –hour
NN –minute
for example template "Dev_YYYY_MM_DD__HH-NN.csv" and date is 2017.03.25 14:25, so file name
will be "Dev_2017_03_25__14-25.csv"
•"Set" button - write configuration to device.
•"Get" button - read configuration from device.