1. Quick guide M!DGE3 is a widely configurable and compact cellular router. All you have to do to put it into operation is to connect it to an antenna and a power supply and configure it using a PC (tablet, smartphone) and a web browser.
Page 9
). The ETH/USB contains a built-in DHCP server, so if you have a DHCP client in your PC as most users, you do not need to set anything up. The default IP address of M!DGE3 unit, for access over the ETH/USB adapter, is 10.9.8.7.
HW button is located on the front panel as well (close to the upper edge). Fig. 2.4: Connectors 2.2.1. Antenna An antenna can be connected to M!DGE3 via SMA female 50 Ω connect- M!DGE3 is equipped with two connect- ors. The ANT1 connector will be used for common transmitting and receiving single antenna installation.
Page 14
This rugged connector connects to a power supply and it contains control signals. A plug with screw- terminals and retaining screws for power and control connector is supplied with each M!DGE3. It is Tyco 7 pin terminal block plug, part No. 1776192-7, contact pitch 3.81 mm. The connector is designed for electric wires with a cross section of 0.5 to 1.5 mm...
Page 16
The SFP modules listed in Accessories are thoroughly tested by RACOM and are guaranteed to function with M!DGE3 units. It is possible to use any other SFP module, but RACOM cannot guarantee they will be completely compatible with M!DGE3 units.
Page 17
A In/Out M!DGE3 keeps pin 6 DSR at the level of 0 (state ON, approx. +6.2 V) by RS232 standard permanently. Expansion board 'C' (2 x RS232) The 2nd and 3rd COM ports are available when the Expansion board 'C' (2 x RS232) is installed. In such a case: The DI/DO connector is used as a connector for COM2 and COM3.
Page 18
RxD COM3 TxD COM3 CTS COM2 RTS COM2 RxD COM2 TxD COM2 2.2.6. USB M!DGE3 uses USB 3.0, Host A interface. USB interface is wired as standard: Tab. 2.5: USB A Pinout Cable Assembly Signal Wire VBUS White Green Black...
• Press from 7 up to 20 seconds - Factory settings are performed on button release • Press more than 20 seconds - Nothing happens 2.2.9. SIM cards Two SIM card holders for Micro SIM (3FF) are available under the screwed cover on the M!DGE3 right side. Warning Disconnect M!DGE3 unit from a power supply before opening the cover and manipulating with SIM cards.
It is recommended to use both antennas (MIMO diversity) for the LTE connection. In case of using only one antenna, attach it to the ANT1 connector. 2.3.2. SIM card holders Two SIM card holders for Micro SIM (3FF) are available under the screwed cover on the M!DGE3 right side. 2.4. GPS M!DGE3 cellular router shall be equipped by the GPS receiver with time pulse output.
Page 24
Product Security – enables IPsec, GRE, RADIUS, Multiple users, Tamper detection; Part No.: M!DGE3- SW-SECURITY SFP – enables SFP interface; Part No.: M!DGE3-SW-SFP Type – specific product type Possible values: M!DGE3 Code – part of order code which is printed on Product label on the housing (SW keys are not HW dependent and can be ordered later on, so they are not printed on Product label).
4.1. Mounting 4.1.1. DIN rail mounting M!DGE3 cellular modem is directly mounted to the DIN rail by a holder (which comes with the modem). Fig. 4.1: DIN rail Using this mounting M!DGE3 can be mounted in different angles (by 90° clockwise/counter clockwise).
Use 50 Ω impedance cables only. The shorter the feed line, the better. If M!DGE3 is installed close to antenna, the data cable can be replaced by an Ethernet cable for other protocols utilizing the serial port, see Section 7.1.3, “Terminal servers”.
M!DGE3 may be powered from any well-filtered 10 to 50 VDC power source. The supply must be capable of providing the required input for the projected RF output. To avoid radio channel interference, the power supply must meet all relevant EMC standards.
5.1.1. Detailed Description Generally, a Terminal server (also referred to as Serial server) enables connection of devices with a serial interface to a M!DGE3 over the local area network (LAN). It is a virtual substitute for the devices used as serial-to-TCP(UDP) converters.
(via LAN) or a high-speed WAN (e.g. Internet). The M!DGE3 which you are logged-in to in this way is called Local. Then you can manage any remote M!DGE3 in the network over-the-air in a throughput-saving way: all the static data (e.g. Web page graphic objects) is downloaded from the Local M!DGE3 and only information specific to the remote unit is transferred over the Radio channel.
Page 34
Note Web interface for M!DGE3 is identical to RipEX 2. The login page informs you about the Unit name and IP address of the M!DGE3 unit you are trying to log in. The login page allows changing of the language of the whole web interface (English language is default).
6.2. Changes to commit M!DGE3 is capable of remembering changes, which were done in its configuration and collecting them in a Changes to commit "basket". All changes of configuration parameters are highlighted by different color.
Web interface 6.3. Notifications With M!DGE3 new way of showing important system events to the user is introduced. It is called Noti- fication Centre and is used consistently throughout the interface. Notification Centre is located on the top right corner of the interface. It exists in two forms: active notification display and full Notification Center.
It is strongly recommended to change the default password. 6.5. Remote access M!DGE3 unit management is designed to work smoothly even when the unit under configuration is connected via relatively slow radio channel. In case of locally connected unit - direct configuration of the unit (accessing the unit IP address directly from the web browser) works fine.
Page 39
Remote access can be activated via click on the Remote access button. The connection to remote radio proceeds... The IP address of the actually connected M!DGE3 unit is displayed as part of the Remote access button. All the configuration settings are remotely available using standard web interface. Some of the Diagnostic features are available via local connection only.
7.1. Interfaces 7.1.1. Ethernet M!DGE3 provides 5 physical Ethernet ports ETH1, ETH2, ETH3, ETH4 and ETH5. ETH1 - ETH4 ports are metallic. ETH5 port is a SFP port. There is a possibility to define an Ethernet bridge - a logical Network interface - by bridging (joining) together multiple physical Ethernet interfaces.
Settings 7.1.2. COM Data incoming to the M!DGE3 unit from the COM port are received by the Protocol module. The Protocol module behavior depends on the Protocol selected. In case of Transparent protocol (available in Bridge mode only), it is transparently transmitted to the M!DGE3 network and send out through all COM ports with Transparent protocol selected.
RTS/CTS (Request To Send / Clear To Send) hardware flow control (handshake) between the DTE (Data Terminal Equipment) and M!DGE3 (DCE - Data Communications Equipment) can be enabled in order to pause and resume the transmission of data. If RX buffer of M!DGE3 is full, the CTS goes down.
Page 48
UDP ports for COM or Terminal servers can be used or UDP port can be set manually. If the des- tination IP address belongs to a M!DGE3 and the UDP port is not assigned to COM or to a Terminal server or to any other special SW module running in the destination M!DGE3, the packet is discarded.
The None protocol switches the COM port off. All incoming data will be thrown away, No data will be send into the COM interface. 7.1.2.3.2. Transparent protocol Operates in Bridge mode only. All the traffic is bridged transparently to M!DGE3 network (see ??? for details). 7.1.2.3.3. Async link Async link creates an asynchronous link between two COM ports on different M!DGE3 units.
Each frame in the DNP3 protocol contains the source and destination addresses in its header, so there is no difference between Master and Slave in terms of the M!DGE3 configuration. The DNP3 allows both Master-Slave polling as well as spontaneous communication from the remote units.
Settings 7.1.2.3.6. DF1 Each frame in the Allen-Bradley DF1 protocol contains the source and destination addresses in its header, so there is no difference between Master and Slave in the Full duplex mode in terms of M!DGE3 configuration. Duplex mode List box {Full duplex;...
MARS-A was widely used by legacy RACOM radio modems in the MORSE system from the year 1999. The new implementation of this protocol in M!DGE3 is limited to the parts of the complex protocol which can be used together with modern packet type of radio routers: USER DATA (0x09) from router to the serial interface (e.g.
7.1.2.3.9. Modbus RTU Modbus RTU is a serial polling-type communication protocol used by Master-Slave application. When M!DGE3 radio network run in Router mode, more Modbus Masters can be used within one Radio network and one Slave can be polled by more Masters.
“SCADA address” as in UNI protocol. There is a handshake STX(0x02) – DLE(Ox10) on the start of communication and DLE+ETX – DLE on the end. This handshake is performed by M!DGE3 locally, it is not transferred over the M!DGE3 network.
Page 59
Address mode List box {Binary (1 B); Binary (2B LSB first); Binary (2B MSB first)}, default = "Binary (1 B)" M!DGE3 reads the Protocol address in the format and length set (in Bytes). Address position Specify the sequence number of the byte, where the Protocol address starts.
M!DGE3 checks (calculates itself) this byte while receiving a packet on COM. M!DGE3 transmits DLE (accepts the frame) only when the check result is OK. BCC byte is not transferred over the M!DGE3 network, it is calculated locally in the end M!DGE3 and appended to the received data.
Page 62
0x85 0xC500 0xC5 0xC501 Note See details of the RACOM’s implementation on https://www.racom.eu/eng/sup- port/prot/sbus/index.html Mode of Connected device: MASTER Transmission control timeout [ms] Number {0 – 65535}, default = 11500 Master timeout. This timeout is reseted after receiving of an answer from Slave or a frame in- coming from the connected master.
Settings 7.1.2.3.14. UNI UNI is the 'Universal' protocol utility designed for M!DGE3. It is supposed to be used when the required application protocol is not available in M!DGE3 and the network communication is using addressed mode (which is a typical scenario). The key prerequisite is: messages generated by the Master applic- ation device must always contain the respective Slave address and the address position, relative to the beginning of the message (packet, frame), is always the same (Address position).
TCP messages and processed like it comes from a COM port. When data reaches the destination M!DGE3, it can be transferred to the RTU either via a serial interface or via TCP (UDP), using the Terminal server again.
Up to 5 independent Terminal servers can be set up. Each one can be either TCP or UDP Type, TCP Inactivity is the timeout in seconds for which the TCP socket in M!DGE3 is kept active after the last data reception or transmission. As source IP address of a Terminal server will be used the IP address of the M!DGE3 ETH interface (Local preferred source address if exists see Section 7.2.1, “...
Settings M!DGE3 optionally provides cellular WWAN interface using embedded cellular module. Two SIM cards are available, only one can be active at a time. APN must always be set up, all other parameters can keep their default values. 7.1.4.1. MAIN/EXT Enable / Disable cellular MAIN/EXT: Enables / Disables the cellular MAIN/EXT.
Parameters Input interface and Output interface can filter the traffic either coming from WWAN or leaving to WWAN (List box WWAN or AUX). Only traffic coming through M!DGE3 (FORWARD) is filtered. • SNAT - parameter Output interface can filter the traffic (List box WWAN or AUX).
BABEL, OSPF and BGP standard routing protocols are available in M!DGE3 networks. 7.2.1. Static M!DGE3 works as a standard IP router with multiple independent interfaces: Radio interface, Network interfaces (bridging physical Ethernet interfaces), COM ports, Terminal servers, optional Cellular interface etc.
Local preferred source address Local IP address used as a source address for packets originating in the local M!DGE3 unit being routed by this routing rule. It might be for example packets originating from the COM port or from the Terminal Server.
Router ID IP address, default = 0.0.0.0 M!DGE3 unit acts in the BABEL network as a dynamic router. Every router is identified by an ID having the format of IP address. This IP address does not have to be ‘real’.
(AS). OSPF Version 2 defined in RFC 2328 (1998) for IPv4 is im- plemented in the M!DGE3 router. OSPF provides Layer 2 dynamic routing. In the context of M!DGE3 networks it is typically used for the backhaul network routing.
• It is possible to define exported routing rules aggregation or specific routing rule hiding. • It is possible to control the routing rules which are imported into the M!DGE3 unit from the OSPF protocol and those that are exported into the OSPF protocol from the unit by using ‘filters’.
It is possible to prescribe routing rules toward this router which will be spread across the network (Static rules). It is possible to control the routing rules which are imported into the M!DGE3 unit from the BGP protocol and those that are exported into the BGP protocol from the unit by using ‘filters’.
IP address, default = 0.0.0.0 M!DGE3 unit acts in the BGP network as a dynamic router. Every router is identified by an ID having the format of an IP address. This IP address does not have to be ‘real’. Router ID is shared with the OSPF protocol.
L3 Firewall settings do not impact packets received and redirected from/to Radio channel. The problem described in NOTE 2 will not happen, if the affected M!DGE3 router is a radio repeater, i.e. when it uses solely the radio channel for input and output.
Although there are 2 modes of operation, M!DGE3 only offers a Tunnel mode. In Tunnel mode, the entire IP packet is encrypted and authenticated. It is then encapsulated into a new IP packet (ESP –...
Page 110
NAT-T (NAT Traversal) or MOBIKE (MOBile IKE) are active, the UDP port 4500 is used instead. Note NAT-T is automatically recognized by IPsec implementation in M!DGE3. The IPsec tunnel is provided by Security Association (SA). There are 2 types of SA: •...
Page 113
Unfortunately, the more frequent the key exchange, the higher the network and CPU load. Note The M!DGE3 unit load is seriously affected when key exchange is in process. Phase 2 – IPsec Certain parameters are shared by all subordinate CHILD SA. IPsec Security Association provides...
Page 114
Note The M!DGE3 unit load is seriously affected when key exchange is in process. PSK (Pre-shared key) authentication is used for IKE SA authentication. The relevant peer is identified using it's "Peer ID". The key must be the same for both local and peer side of the IPsec.
(Path MTU discovery). 7.5. Security User authentication is required to access M!DGE3 unit management. There are two types of user au- thentication which differ in the user account location: Local authentication – user accounts are stored directly in the M!DGE3 unit Remote authentication –...
RADIUS accounts can be mapped to one of the four user roles. This is either managed by the server itself or by local M!DGE3 settings. Local accounts are checked first and if the account does not exist, RADIUS accounts will be used. If the RADIUS server is not accessible, users may use the local username/password to “fall back”...
Management-Privilege-Level the static account level option (for all users) has to be used. 7.5.4. Tamper reset Tamper is a detection service, which is triggered, when the M!DGE3 chassis is physically opened. There are 2 contacts (securing top and bottom casing) and the event is triggered even if the unit is without power.
Page 137
List box {Default; User defined}, default = "Default" Engine Id serves for unique identification of the SNMP instance (i.e. the M!DGE3 unit) according to RFC3411. When the "Default" Engine ID mode is selected the MAC address of the Eth1 interface is used for the unique part of the Engine Id (the whole Engine ID example: 800083130302a92006ef).
Number {1 – 65535}, default = 162 Notification packets destination port. 7.6.5. SMS M!DGE3, fully connected into the cellular network (status CONNECTED), is capable of receiving and sending SMS. • Receiving and sending SMS is provided by a linux service.
This command does not generate an automatic reply. 7.6.6. SW keys Certain M!DGE3 features needs to be activated by a SW key to be available. When the respective SW key is not present, the feature cannot be configured. If the feature is enabled in a configuration backup file and the file is loaded to a unit which is not equipped with the respective key, the configuration is refused (no changes are made in the unit).
Page 141
SW key is unique for the specific unit (specific serial number). Use Choose File dialog to select the file and Install key button to install the key(s) to unit. Differences with the previous generation of M!DGE3: - SW keys are always installed as a file (there is not a clipboard option)
Unit firmware defines the unit functionality. There are several principles for managing the firmware in the running network: • Maintain the same version of firmware in the network (recommended). M!DGE3 units are able to cooperate with different versions of firmware running, but using the same firmware version in all units is the best way to keep the network maintenance simple.
Page 143
4. Click the Upload firmware button to transfer the firmware file into the unit. The upload can take a long time – depending on the connection speed between the management PC and the M!DGE3 unit. In case of slow connection and file transfer longer than 120 s, the web browser will shut down the connection and the action will not finish successfully.
M!DGE3. Please note, that M!DGE3 is a very powerful device and it really shows all parameters in the Advanced section. When you visit the page for the first time, you will see a search field and below a tree of configuration pages.
Diagnostics 8. Diagnostics 8.1. Overview The Overview section serves to give general information about the M!DGE3. 8.1.1. Measurements Section Overview - Measurements contains current data measurement (obtained from sensors). • Card Temperature - provides data about temperature (on CPU, modem and radio).
Page 148
Diagnostics Intefaces used in M!DGE3 units are in general either Bridged ports (BP-L2) or Routed interfaces (RI- L3). All interfaces used by the linux router (internal interfaces excluded) are displayed in the following list. if_<LanIface_Name> LAN bridge interface RI-L3 type (SETTINGS>Interfaces>Ethernet>Network interfaces)
This menu serves for collecting data, either from local or remote station and storing them into a package (file). Diagnostic package serves primarily as a help tool, for RACOM’s technical support in case of any potential unit issues. Minimum size of a package is 5kB. Maximum size depends on the amount of radio links contained in the statistics.
Debug 8.4. Statistics M!DGE3 unit permanently monitors various system 'channels'. There are several types of those channels: Physical interfaces (Ethernet ports, serial ports, radio interface, additional module interface (e.g. LTE module) when installed), virtual interfaces (e.g. VLAN interfaces) and HW sensors (CPU temperature, supply voltage, ...).
'Correct' and 'Drop' Bytes provides the total amount of Bytes on the physical interface. Rx direction: from the connected (at the COM or ETH port) external device to the M!DGE3 unit (i.e. from the COM port module or Terminal server module to the Router module). Tx direction: from the M!DGE3 unit to the external device.
Only correctly received frames are handled. The counters correspond to the specific IP protocol types. Rx direction: from the physical Ethernet port to the M!DGE3 unit (i.e. to the Router module). Tx direction: from the M!DGE3 unit to the physical Ethernet port.
List box {LOW; NORMAL; HIGH; UNLIMITED}, default = "NORMAL" Monitoring bandwidth limit to prevent overload of management link between client PC and the M!DGE3 unit. LOW (up to ~300 kb/s), NORMAL (up to ~800 kb/s), HIGH (up to ~2 Mb/s), UNLIMITED (up to ~8 Mb/s)
The M!DGE3 cellular routers must not be opened. Only the replacement of the SIM card is permitted. Voltage at all connectors of the communication module is limited to SELV (Safety Extra Low Voltage) and must not be exceeded.
Safety, regulations, warranty 10.2. High temperature If the M!DGE3 is operated in an environment where the ambient temperature exceeds 55 °C, the M!DGE3 must be installed within a restricted access location to prevent human contact with the enclosure heatsink. 10.3. Battery disposal Battery Disposal - This product may contain a battery (e.g.
Page 175
(typically the files COPYING or LICENSE). You can obtain applicable machine-readable copies of source code of this software under GPL or LGPL li- censes on contacts listed on https://www.racom.eu. This product also includes software developed by the University of California, Berkeley and its contributors.
Page 178
Safety, regulations, warranty Tímto RACOM s.r.o. prohlašuje, že typ rádiového zařízení M!DGE3 je v souladu se směrnicí 2014/53/EU. Hermed erklærer RACOM s.r.o., at radioudstyrstypen M!DGE3 er i overensstemmelse med direktiv 2014/53/EU. Hiermit erklärt RACOM s.r.o., dass der Funkanlagentyp M!DGE3 der Richtlinie 2014/53/EU entspricht.
The serviced equipment shall be returned by RACOM to the customer by prepaid freight. If circumstances do not permit the equipment to be returned to RACOM, then the customer is liable and agrees to reim- burse RACOM for expenses incurred by RACOM during servicing the equipment on site. When equipment does not qualify for servicing under warranty, RACOM shall charge the customer and be reimbursed for costs incurred for parts and labour at prevailing rates.
Need help?
Do you have a question about the M!DGE3 and is the answer not in the manual?
Questions and answers