Temperature to Ethernet converter EI-122

Ethernet converter EI-122 with pulse inputs and temperature

EI-122 main purpose is to measure temperature and transfer data thourgh internet/LAN. Device has two channels for connecting Pt1000 sensors, with or without compensation. Main interface is 10/100 TCP, which can act as a server or client. In addition, 4 pulse inputs are provided. They are intended for reed-switch devices or outputs with open collector. As a second interface for setting the device locally serial RS-232 is provided. EI-122 works with special Gineers protocol for data transfers, which guarantee security. In one telegram all data is send - both temperature and pulse inputs counted value. Automatic readout can be set and performed among with other useful functions in remote reading systems. Device has built-in DHCP, which dramatically reduces setting time, making the device almost plug-and-play.

EI-122 is powered by external adapter (included) and is mounted on horizontal/vertical surfaces. DIN-rail mount is possibble on request.

user manual

Technical characteristics of EI-122

connection protocol TCP/IP
connection speed 10/100 MBit
DHCP function ON/OFF (default ON)
pulse inputs 4 (standard for reed relay/OC, but can be 12/24VDC)
temperature channels 2 independent, Pt1000 sensors
power supply 6-9 Vac/500mA or 5-12 Vdc/500mA, adapter 2 mm
power consumption @ 12Vdc < 1 W
serial port bps 300/1200/2400/4800/9600/19200/38400 bps
work temperature from -20° C to +50° C
storage temperature from -50° C to +90° C
humidity 40 ÷ 90 %
dimensions (HxWxD), mm 125/55/30 mm
protection class IP30
display 4 LEDs (on, link, comm /local communication/, line)
own weight 120 g

Operation of EI-122

MBET-2WR is powered by external adapter 6-9 Vac/200 mA or 5-12 Vdc/200mA. The central pin of the power connector is 2mm thick. We recommend adapter with power rating 6-12 Vdc/5W. Power supply voltage should not exceed 20 Vdc/ 15 Vac.

МBET-2WR begins operation immediately after power-up. After initialization (about 2s), MBET-2WR enters “Command mode” /checks for connection time/. MBET-2WR can act as a client or as a server. If MBET-2WR is set as a client, the connection with servers is initiated by the device, i.e. MBET-2WR can be connected in local network without real static IP-address. All of the contacted servers must have static real IP-addresses in order for MBET-2WR to be able to connect to them. MBET-2WR can contact up to six servers – two “control” operators and four “data” operators. The two control servers can program all network access settings and have no access to the transmitted data. Likewise, the data operators can access only the data, but cannot program any network parameters. If it is needed for an operator to have access both to the network settings and the data, its IP-address must be set both as control and data operator. Accessible mediums for every data operator may be programmed, so, for example, the operator which monitors water consumption, cannot access the data, monitored by gas supplier and vice-versa. MBET-2WR tries to connect to the servers after predetermined period of time (default 1h). Each of the servers can accept or reject the incoming connection. If the connection is accepted, MBET-2WR starts with identification data packet to identify the remote reading network, connected to this particular device. After identifying the network server can reprogram network parameters (for control operators) or access network data (data operators). When all parameters are programmed or needed data is read, server must send TCP packet for closing the connection. After receiving this packet, MBET-2WR closes the connection and tries to connect to the next server in the list until all the servers in the list are contacted. If no close connection packet is send or MBET-2WR cannot connect to the server, it waits for predetermined period of time and closes the connection, if no data exchange occur. This process is repeated continuously, connection attempts are programmable period of time.

If MBET-2WR is set as a server, it just waits for remote connections on specified port. After connection request arrives, MBET-2WR checks its internal IP list and if remote IP and port number are valid - establishes connection. If no communication occurs for predefined period of time, MBET-2WR closes the connection automatically.

Initial parameters programming is essential and includes setting the LAN/WAN-network parameters (IP-address, gateway IP-address, network mask, IP-address of the control server, etc, including setting new MAC-address if MAC-conflict occurs) and remote reading network parameters (baud rate and parity of serial connection, remote reading network number). These parameters must be set first via RS-232 port, and after successful connection all the parameters can be set remotely by the server, if needed. Since device has DHCP on by default, if the user has a router with enabled DHCP he can skip most of the settings - IP address, Mask and Gateway will be set automatically.

During normal work device tracks all three pulse inputs simultaneously. Pulse input data is saved in non-volatile memory. There is a remote server, host by Gineers, which can be used for automated readings. The devices connects every n-hour, data is saved and can be send via email to particular user - every day, day of a week or day of a month. The device memorizes only raw pulses. Additional info for every input such as pulse constant, unit measures, initial values, price-per-pulse, etc., are saved in a server database. Through unique ID, that every MBET-2WR has, server knows which device its talking to and calculate consumption properly.

Most of the connectors of MBЕТ-2 are at the back of the device - these are Power supply, RS-232 port and LAN connector. Three pulse inputs are on the opposite side, on a removable terminal block. Ground is common for the three inputs. The cable, connecting MBET-2WR to an m-bus converter type MBRS (RS-232 RJ45-RJ45 cross) is part of the package. The cable for initial programming (RS-232 DB9-RJ45 cross) is not delivered with MBET-2WR as it is part of the package of every m-bus converter type MBRS.

IP address of Gineers server is programmed in every MBET-2WR in the fabric. Of course, client can re-write it, if he does not want device to connect to remote Gineers server, but to maintain his own server and database.