2
SATEL XPRS IP RADIO ROUTER
CENTRAL UNIT
USER GUIDE VERSION 1.9
CU
USER GUIDE
Copyright: 2019 SATEL Oy
No part of this document may be reproduced, transmitted or stored in a retrieval system in any form or by any means
without the prior written permission of SATEL Oy. This document is provided in condence and must not be distributed
to third parties without the express permission of SATEL Oy.
3SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
2
Contents
Important notice 7
Product conformity 8
Warranty and safety instructions 9
1. Introduction to the SATEL XPRS radio router product family 10
1.1 Mounting 14
2. Technical specications 15
3. Typical setup 16
4. Mechanical assembly, modular construction 17
5. Interfaces 19
5.1 Ethernet 20
5.2 USB 20
5.3 Diagnostics, monitoring, changing settings 20
5.4 LED indicators 21
5.5 Function button 22
5.6 Graphical user interface 24
5.6.1 Booting screen 24
5.6.2 LCD display, information and button menu areas 25
5.6.3 Main menu 26
5.6.4 Status screen 26
5.6.5 Screen save mode 27
4
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
2
5.7 WWW User interface 27
5.7.1 Login 27
5.7.2 Main menu 27
5.7.3 Status area 28
5.7.4 Categories list 28
5.7.5 Category page 29
5.7.6 Changing settings 29
5.8 SATEL NMS 30
5.9 SSH 30
6. Data transmission 31
6.1 Internet protocol 31
6.1.1 Example 31
6.1.2 Forming the tun0 IP address 33
6.1.3 Choosing the eth0 IP address 33
6.1.4 Setting IP routes 34
6.2 Proxy Arp 35
7. Settings 36
7.1 Modem Settings 36
7.1.1 Radio Unit Settings categories 36
7.1.2 General 36
7.1.3 Services 38
7.1.4 Commands 40
7.1.5 Remote Devices 42
7.1.6 SNMP 42
7.1.7 Time Control 42
7.1.8 ATPC 43
7.1.9 NMS Modbus 44
7.1.10 Testing and Calibration 46
7.2 Modem Info 48
7.2.1 Status 48
7.2.2 Services 50
7.2.3 Radio Unit 50
7.2.4 Central Unit 50
7.3 Routing 52
7.3.1 Packet Routing Tables 52
5SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
2
7.3.2 IP 57
7.3.3 IP Routes 60
7.4 Serial IP 66
7.4.1 Serial IP RS-232 / USB-A 66
7.4.2 UDP and TCP protocols 69
7.4.3 Ethernet to serial converter 70
7.4.4 Notes 71
7.5 Virtual Local Area Network (VLAN) 73
7.5.1 VLAN settings 73
7.6 WLAN 76
7.7 Redundant Routing 76
7.7.1 Route monitoring 77
7.7.2 VRRP 79
7.7.3 Building a redundant network 81
7.7.4 Redundancy related SNMP notications 87
7.8 Application Routing 87
7.8.1 Protocols 91
7.9 OSPF 93
7.10 QoS 94
7.10.1 Bandwidth allocation 95
7.10.2 Creating QoS rules 97
7.11 Bridge mode 100
7.11.1 Bridge conguration 100
7.11.2 Open and Restricted modes 102
7.11.3 Gretap modes 108
7.11.4 Broadcast modes: Broadcast and Broadcast All 110
7.11.5 Ethernet rewall 110
7.11.6 S TP 114
7.11.7 Notes and exceptions 114
7.12 TCP/UDP Proxy 115
7.13 IEC 104-101 116
7.14 VPN 117
6
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
2
7.15 DHCP 117
8. Applications 120
8.1 Diagnostics 120
8.1.1 Diagnostics application in WWW interface 121
8.1.2 Diagnostics application in the GUI 121
8.2 Simple Network Management Protocol (SNMP) 122
8.2.1 SNMP category 124
8.2.2 MIB 127
8.2.3 Reading and writing values with SNMP 127
8.2.4 SNMP Timeout 128
8.2.5 Notications (traps) 128
8.3 Firmware updating 130
8.3.1 Firmware updater application 130
8.3.2 USB Stick during boot CU update method 134
8.3.3 Firmware update over-the-air 134
8.4 Remote settings 140
8.5 NMS Import 140
8.5.1 Exporting settings from modem 140
8.5.2 NMS Export advanced features 141
8.5.3 The export/import le contents 141
8.5.4 Managing export les 142
8.5.5 Importing settings to a modem 143
8.5.6 Importing les from USB stick 144
8.6 Encryption 145
8.7 Logs 145
8.8 Administration 146
8.8.1 General 146
8.8.2 IP 148
8.9 Tools 149
8.9.1 Ping 149
8.9.2 Traceroute 150
8.9.3 NMS Value 150
8.9.4 Firewall and NAT 152
8.9.5 Ethernet Firewall 155
8.9.6 Blacklist status 155
8.9.7 SATELLAR CU Settings Wizard 156
7SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
2
All rights to this manual are owned solely by SATEL
OY (referred to in this user guide as SATEL). All
rights reserved. The copying of this manual (with-
out written permission from the owner) by printing,
copying, recording or by any other means, or the
full or partial translation of the manual to any other
language, including all programming languages,
using any electrical, mechanical, magnetic, optical,
manual or other methods or devices is forbidden.
SATEL reserves the right to change the technical
specications or functions of its products, or to
discontinue the manufacture of any of its products
or to discontinue the support of any of its products,
without any written announcement and urges its
customers to ensure that the information at their
disposal is valid.
SATEL soware and programs are delivered ”as
is”. The manufacturer does not grant any kind of
warranty including guarantees on suitability and
applicability to a certain application. Under no cir-
cumstances is the manufacturer or the developer
of a program responsible for any possible damages
caused by the use of a program. The names of
the programs as well as all copyrights relating to
the programs are the sole property of SATEL. Any
transfer, licensing to a third party, leasing, rent-
ing, transportation, copying, editing, translating,
modifying into another programming language
or reverse engineering for any intent is forbidden
without the written consent of SATEL.
SATEL PRODUCTS HAVE NOT BEEN DESIGNED,
INTENDED NOR INSPECTED TO BE USED IN ANY
LIFE SUPPORT - RELATED DEVICE OR SYSTEM
- RELATED FUNCTION NOR AS A PART OF ANY
OTHER CRITICAL SYSTEM AND ARE GRANTED NO
FUNCTIONAL WARRANTY IF THEY ARE USED IN ANY
OF THE APPLICATIONS MENTIONED.
Salo, Finland 2019
Important notice
9. Type designation 159
10. Troubleshooting 160
10.1 Error codes 160
11. SATEL open source statements 162
11.1 LGPL and GPL software 162
11.2 Written oer for LGPL and GPL source code 162
12. Settings selection guide 163
12.1 Modem Settings 163
12.2 Routing 168
12.3 Administration 171
8
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
2
Product conformity
SATELLAR CU
SATEL Oy hereby declares that SATELLAR Central Unit is in compliance with the essential requirements
(electromagnetic compatibility and electrical safety) and other relevant provisions of Directive 1999/5/EC.
Therefore the equipment is labelled with the following CE-marking.
9SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
2
Warranty and safety instructions
Read these safety instructions carefully before using the product:
– The warranty will be void if the product is used in any way that is in
contradiction with the instructions given in this manual, or if the housing of the
radio modem has been opened or tampered with.
– The devices mentioned in this manual are to be used only according to the
instructions described in this manual. Faultless and safe operation of the
devices can be guaranteed only if the transport, storage, operation and
handling of the device is appropriate. This also applies to the maintenance of
the products.
– To prevent damage the Central Unit (referred to in this user guide as CU)
must always be switched OFF before connecting or disconnecting the serial
connection cable. It should be ascertained that dierent devices used have the
same ground potential. Before connecting any power cables the output voltage
of the power supply should be checked.
– To be protected against all veried adverse eects the separation distance of
at least 44 cm must be maintained between the antenna of SATELLAR radio
modems and all persons.
10
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
1. Introduction to the SATEL XPRS radio router product family
2
1. Introduction to the SATEL XPRS radio router
product family
SATEL XPRS radio router is a new generation narrow band radio router that consists of separate units:
– Central unit (CU)
– Radio unit (RU)
Figure 1.1 SATEL XPRS radio router product family:
1. SATELLAR XT 5RC with display:
Central unit (CU) with display and keypad + radio unit (RU)
2. SATELLAR XT 5RC without display:
Central unit (CU) w/o display and keypad + radio unit (RU)
3. SATELLAR XT 5R: Radio unit (RU)
Using SATELLAR the customer builds an own independent radio data communication network. This docu-
ment presents the specications and usage of the CU. The properties of other units are described in the
extent, which is necessary to read in order to understand the operation of the CU.
SA00057
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
1 2
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
3
TD
RD
PWR
STAT
RX
TX
CTS
RTS
11
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
1. Introduction to the SATEL XPRS radio router product family
2
Data communication
SATELLAR operates either as a transparent radio link, essentially replacing a wire, for classic RS-232,
RS-485 or RS-422 based protocols, or as a wireless router in an IP-based network. Using SATELLAR many
network topologies are possible, everything from a point-to-point connection to a nationwide chain with
multiple branches.
Security
Data security is oen a concern when using radio communication. In SATELLAR there are 128-bit and 256-
bit encryptions available on the air-interface ensures privacy in the radio network.
Display and keypad
The CU is available with or without a display and keypad. The size of the display is 2.4 “, resolution is 320
x 240 pixels, and the amount of colors is 65k. The keypad has seven buttons: le, right, up, and down
arrows, OK button, and two soware dened buttons.
Diagnostics and conguration
Radio modems are oen used in applications where reliability and independence are key properties. To
support this demand, SATELLAR has built-in diagnostic and remote conguration features.
Figure 1.2 Display and keypad
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
Size: 2,4”
Resolution: 320x240 pixels
Amount of colors: 65 k
SA00002
OK
Left, right, up and down arrows
Software define buttons
OK button
12
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
1. Introduction to the SATEL XPRS radio router product family
2
Local use
The status of the CU can be seen from the LED indicators, which are located on the other narrow side of
the unit. More detailed information is available using the graphical user interface with a QVGA display and
7 pushbuttons.
Remote use
Once deployed, status monitoring and conguration can be performed using one of the following meth-
ods:
1. The SATELLAR CU provides WWW pages for conguration and diagnostic, acces-
sible using IP connectivity (the Ethernet interface of the CU)
2. Using the Windows based SATEL NMS PC soware through the serial data in-
terface of the RU, the USB device port of the CU, or TCP/IP port 55555 of the CU.
(Check SW availability from SATEL)
SATELLAR can also be accessed over the air by the methods described above.
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
PWR
STAT
ETH
USB
Figure 1.3 The status of the CU can be seen from the LED indicators
13
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
1. Introduction to the SATEL XPRS radio router product family
2
Flexible and expandable
SATELLAR concept has been designed to be exible and expandable both in terms of hardware and
soware functions.
Soware
In the RU the modulation method, channel spacing (i.e. air interface data rate), and forward error correc-
tion can be selected by changing the modem settings by soware. Also the RF output power can be set.
Hardware
Due to the modular mechanical structure of SATELLAR, it is possible to add hardware expansion units. The
idea is that this could be done as an update aer the initial deployment. At the moment, however, the RU
does not support the update. Schedule for this will be informed later.
USB host and device connectors oer a possibility to connect commercially available USB devices like
Bluetooth and WLAN modules to the modem or e.g. to show the modem as an external memory device to
the PC.
Ruggedized
SATELLAR is constructed of die-cast aluminum to withstand the abuse typical to rough industrial environ-
ments. It operates over a wide temperature range and under severe vibration conditions to meet the
requirements of vehicular and process industry applications.
14
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
1. Introduction to the SATEL XPRS radio router product family
2
1.1 Mounting
The SATELLAR XT 5R and 5RC can be mounted as follows:
• On a DIN-rail using SATELLAR specic DIN rail adapters (two pieces needed) connected at the other
edge or at the bottom of the unit.
• NOTE! The DIN rail adapters have to be ordered separately.
Please contact manufacturer to get more information regarding mounting of the units.
NOTE!
1. The equipment must be installed in restricted access location due to high touch
temperatures of metal enclosure.
2. The screen of coaxial antenna cable must be grounded to protect from over
voltages from outdoor antenna.
15
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
2. Technical specications
2
2. Technical specications
Electrical
CPU ARM 9 @ approx. 200 MHz
RAM 64 MB
ROM 128 MB
Display 2.4 ”, 320 x 240 pixel resolution, 65 k colours
Keypad up, down, le, right, OK (select), and two SW dened keys
Power consumption No USB device connected:
2.0 W with the display
1.4 W without the display
USB connected:
+ maximum additional 2.5 W
USB interfaces USB-host & USB-device
USB2.0 high speed
Ethernet interface 10/100 Mbps Ethernet RJ-45 with Auto-MDIX
Start time from power on For CU/RU combination: 65 s until IP communication works
(locally and over the air). 130 s until LCD/GUI works.
Mechanical and environmental
Mechanical dimensions 130 x 21.7 x 76.5 mm
Weight 260 g
Temperature ranges -25 - +55 deg °C, complies with the standards
-30 - +75 deg °C, functional
-40 - +85 deg °C, storage
Humidity < 95 % @ 25 deg °C, non-condensing
Vibration At least 10 – 500 Hz/5g without degradation in data transfer capability
Shock resistivity Dropping height 1 m, all directions
IP rating IP 52
Mounting: DIN rail (side or back), two piece mounting clip, or directly on at surface
Standards compliance
Emissions IEC 61600-6-4
Immunity IEC 61000-6-2
ESD IEC 61000-4-2 level 4 for external connections
EIC 61000-4-2 level 2 for internal unit-to-unit connector
RoHS 2002/95/EC
Table 2.1 SATELLAR Central Unit technical specications
16
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
3. Typical setup
2
3. Typical setup
The gure below shows a typical setup when transferring IP data through the CU. When using the RU
together with the CU the recommended minimum distance between the antenna and CU is 2 m in order to
avoid degradation of the receiver sensitivity due to interference from the CU.
Figure 3.1 Transferring IP data through the CU, cabling
E
T
H
USB-A USB-B
RU
CU
+
_
SATELLAR XT 5RC
+
_
1.
RF cable
with TNC
male
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
RF
10.6-30
VDC
ETH
2.
3.
CAT-5 Cable
Data
terminal
equipment
Power
supply
10.6-30 VDC
17.9 W
SA00007
RU
CU
min
2 m
+ -
17
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
5. Interfaces
The CU oers three data interfaces: Ethernet, USB host and USB device. LED indicator shows the status
of the unit and graphical user interface can be used to check and change device settings and to see the
diagnostics data.
Ethernet interface:
10/100 Mb/s, 100BASE-TX, Auto-MDIX,
full duplex capability
USB interfaces:
USB2.0, full speed 12.0 Mb/s
USB Host:
A-type connector
The current drive capability is 500 mA
USB Device Interface:
B-type connector
Mass memory device:
Acts as a removable disc in the PC
Virtual serial port:
Acts as as serial port = SATEL NMS port
Figure 5.1 Three data interfaces: Ethernet, USB host and USB device
18
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
The USB interfaces support USB2.0 Full Speed
(12.0 Mb/s) data rates. Both USB host and device
interfaces are available. For USB host the A type
connector is used and for USB device the connec-
tor is B type. The current drive capability of the USB
host interface is 500 mA. The USB device interface
has two modes: Mass memory device and Virtual
serial port. The mode can be selected in Modem
Settings, General category and in addition by the
function button as described in chapter 5.5.
In the Mass memory device -mode a PC can
be connected to the USB device interface and
SATELLAR acts as a Removable Disc in the PC. The
removable disk contains copies of system log les,
which can be copied to the PC. Update les can be
copied to the removable disk and be used in the
Firmware Updater (see chapter 8.3). Any other les
copied to the removable disk are removed when
the cable is disconnected.
In Virtual serial port -mode, the USB port acts as
a serial port. When the USB port is connected to a
PC, the virtual serial port device is created in the
PC. This virtual port appears to windows as a nor-
mal serial port: the only dierence is that an actual
D9 connector is not used. This allows programs to
connect to serial ports in order to access the CU via
the USB connection.
Windows PC requires a special driver, available
from SATEL. The Virtual Serial port acts as a SATEL
NMS port, allowing a program such as SATEL
NETCO Design stack or Netco to be used to change
the settings of SATELLAR. The driver can be found
in the WWW UI under the Administration tab. It can
be downloaded by following the “Download USB
Drivers” link.
5.1 Ethernet
Ethernet interface is 10/100 Mb/s 100BASE-TX with Auto-MDIX and full-duplex capability.
5.2 USB
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
SA00008
CU equipped with a display and keypad oers an
easy way to check or change device settings and
see diagnostics information. The same is possible
using the Web interface of the CU. Graphical user
interface is explained more in chapter 5.6.
Display
Keypad
Figure 5.2 Display and keypad
5.3 Diagnostics, monitoring, changing settings
19
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
5.4 LED indicators
The CU provides four LED indicators that are located on one of the narrow sides of the unit. They are listed
and described in the table below.
LED Label Status Description
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
SA00008
USB OFF USB host disabled
ON USB host enabled, USB device detected
Blinking (0.25 s interval) USB host enabled, no USB device detected
Blinking (0.50 s interval) USB device setting override using function
button, see chapter 5.5
Blinking (1.0 s interval) USB is a mass memory device
ETH OFF Ethernet port disabled
ON Ethernet port enabled and connected
Blinking (0.25 s interval) Ethernet port enabled but not connected or
operational
Blinking (0.50 s interval) Ethernet port setting override using function
button, see chapter 5.5
STAT ON Normal operation mode
Blinking (0.25 s interval) Device is starting up
PWR OFF Device is powered o
ON Device is powered on
Table 5.1 LED indicators
NOTE: In normal operation the USB LED indicates the status of the USB host interface. When operating
with the function button (chapter 5.5), the USB LED refers to the state changes in the USB device interface.
20
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
5.5 Function button
The function button is located below the LED indicators. It is used to control the operation of the USB
device and Ethernet interfaces as described below. The CU must be allowed to boot up completely before
the button will work.
When the button is pressed for more than a second, all the LEDs turn on indicating the start of the pro-
cess. The eect depends on how long the button is kept depressed, and is indicated by turning the LEDs
o one by one. When the LEDs indicate the desired function, release the button. Aer the button has been
released, press the button once more quickly (less than a second) to nish the operation.
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
Function button
SA00015
Figure 5.3 Location of the Function button
Figure 5.4 LED indications, see the Table 5.2
PWR
STAT
ETH
USB
PWR
STAT
ETH
USB
STAT
ETH
USB
PWR PWR
STAT
USB
ETH
PWR
STAT
ETH
USB
21
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
Length of
press
Action [seconds] LED indication Effect
1 to 2 All LEDs ON.
•
•
•
•
The USB device and Ethernet interface settings
are reset to states dened by user settings.
2 to 4 The uppermost
LED (USB) is
switched o.
•
•
•
•
The USB device setting is changed so that if
the user setting is Mass memory device, the
setting changes to Virtual serial port and vice
versa. Thereaer the USB LED starts to blink
until the setting is reset to the original value.
Blinking interval is 0.5 seconds if the new
device setting is Virtual serial port and 1.0
seconds if the setting is Mass memory device.
4 to 6 The next lower
LED (ETH) is
switched o.
•
•
•
•
The CU IP address settings are changed.
Thereaer the IP address is 192.168.1.1, the net
mask is 255.255.255.0, and DHCP is switched
to o mode. All rewall rules preventing access
to the WWW UI are removed. The ETH LED
blinks until the settins is reset to the original
value. Blinking interval is 0.5 seconds.
6 to 8 The next lower
LED (STAT) is
switched o.
•
•
•
•
No specic operation dened.
8 to 10 The fourth LED
(PWR) is switched
o.
•
•
•
•
All the LEDs start to blink rapidly until the MCU
restarts. SATELLAR CU then reboots.
> 10 All LEDs ON.
•
•
•
•
> 20 All LEDs turn ON
and remain on
even if the button
is kept down.
The selection process starts from the
beginning (11 to 12 seconds counts as 1 to 2
seconds etc.).
Table 5.2 Function button operation
22
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
5.6 Graphical user interface
In SATELLAR device equipped with LCD display and keypad, GUI can be used to change settings and
access the various applications.
Figure 5.5 Central Unit equipped with LCD display and keypad
5.6.1 Booting screen
This screen is visible while the CU is starting up.
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
SA00008
23
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
5.6.2 LCD display, information and button menu areas
Figure 5.6 Information and button menu areas
Figure 5.7 Red font indicating a value lower than the dened threshold
The top of the screen is the Information area. The following information is available (From le to right).
– Modem name: Default value is “SATELLAR”. It can be changed in Modem
Settings, General category (see chapter 7.1.2).
– Current date and time, if enabled (see chapter 7.1.6)
– RSSI value: The signal level of the last received message. If no message has been
received in the last 5 seconds, the value is set to -128. If the reading is lower than
the dened minimum threshold value, this value is shown with red font. The
threshold can be set in Modems Settings, General category (see chapter 7.1.2).
– Voltage reading. A numeric value or a voltage bar depending on the setting in
Modem Settings, General category (see chapter 7.1.2).
On the bottom of the screen is the button menu area operated by soware dened keypad buttons. The
le (round) button command is displayed on the le bottom corner of the screen and the right (square)
button command on the bottom right corner of the screen.
OK
SA00003
Figure 5.8 Soware dened buttons on keypad
Soware dened buttons
Information area
Button menu area
24
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
5.6.3 Main menu
Figure 5.9 Main menu view
This menu screen contains icons which can be used to start the dierent applications.
– Modem Settings: See chapter 7.1
– Modem Info: See chapter 7.2
– Routing: See chapter 7.3
– Diagnostics: See chapter 8.1
– Admin Tools: See chapter 8.8
– Remote settings: See chapter 8.4
– Firmware updater: See chapter 8.3
To start an application, use the cursor keys to select the icon and press the round button or OK button.
5.6.4 Status screen
Figure 5.10 Status screen view
If “Lock Screen” command is given in main menu, or the dened time passes without keyboard input, the
screen goes to the status/lock screen mode.
In this screen some basic status values are displayed.
– RX Frequency
– TX Frequency
– RF Output Power
– Tun0 IP Address
– Eth0 IP Address
– Forward Error Correction (FEC) mode (with FSK-product)
25
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
No input is allowed in this screen, except to unlock the screen. To do this, follow the instruction on screen.
If PIN code has been enabled, the correct code must be entered to unlock.
5.6.5 Screen save mode
Aer a timeout set in Modem Settings, General category (see chapter 7.1.2), the display is turned o. When
any button is pressed, the Status screen is displayed and the UI can be unlocked as normal.
5.7 WWW User interface
This interface can be used with a web browser application, such as Mozilla Firefox. The url to access the
WWW -page is http://<modem’s IP address>. By default this is http://192.168.1.1. If the current IP address is
unknown, it can be forced to 192.168.1.1 by using the function button as explained in chapter 5.5, or using
the Graphical user interface, if present. The WWW interface can also be used across the radio link, once
routes have been set (see chapter 6). In this case either of the IP addresses dened can be used (both the
eth0 and tun0 addresses work).
5.7.1 Login
The rst screen of the WWW interface is the login screen. The user name is satellar and the default pass-
word is Satel123. (The password can be changed in settings, see chapter 7.1.2)
You can also log in using the name admin and default password is Satel456. In this case an additional
application called Administration is available, see chapter 8.8.
5.7.2 Main menu
The main menu lists all the “applications” available in the WWW interface. An additional Administration
tab is available when logged in with user name admin as explained in chapter 5.7.1.
26
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
5.7.3 Status area
The area immediately below the main menu shows the name of the radio station (settable in the General
Settings category, see chapter 7.1.2). Current status information is also available:
– Voltage
– Received signal strength (RSSI)
– Current system time
More status information may be visible depending on the rmware versions installed.
5.7.4 Categories list
Once a Main menu application (see chapter 5.7.2) is selected, the categories related to that application are
listed in the dark grey area on the le. The category labels can be clicked to open the category page, which
contain settings and information related to that category. More details about categories can be found
beginning from chapter 7.
There is also one button in the category area: Reload NMS
values. It can be used to force a reload of settings from the RU
and CU settings databases to be displayed on the WWW User
Interface.
Loading operation takes several minutes, so it
should only be used if some of the settings seems to
be incorrectly displayed.
27
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
5.7.5 Category page
This area to the right of Categories list shows the contents of the currently selected category. It contains
settings or other information.
FSK-model QAM-model
5.7.6 Changing settings
When changing settings in the WWW interface, select rst the correct application and category, then
change the desired settings found on the category page. Finally click the Apply Changes button.
Some settings are text or numbers which can be changed by typing, while others are drop down lists,
allowing you to select from a few choices. Any changes you make are lost if you change the category or
application without clicking the Apply Changes -button.
When the Apply Changes button is clicked, all changes on the current page are added to the list of uncom-
mitted changes. You can then navigate to another page and Apply more changes, which are also added to
the list. When you have nished making changes, store and take the new settings into use by clicking the
Commit Changes button. You can also discard all applied changes by clicking the Cancel applied changes
28
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
5. Interfaces
2
button. In this case all settings are removed from the list of uncommitted changes and all settings of all
units remain as they were.
When Commit Changes is clicked, the CU will store settings into the settings database and the Radio Unit,
and restart all necessary Linux processes. Therefore the committing process may take a relatively long
time, sometimes up to a minute.
NOTE: If the IP Address has been changed, the browser will be automatically redirected to the new
address, but in case the network address part of the IP address has changed, you’ll need to modify your
computer’s IP settings so that it is again in the same LAN as the modem to be able to continue using the
WWW interface.
5.8 SATEL NMS
SATEL NMS is a Network Management System. Devices that support SATEL NMS can be congured and
monitored using external soware provided by SATEL. One such program is SATEL NETCO Design stack.
Conguration and monitoring can be performed either locally using a cable, or remotely via a radio link.
Other option is NETCO, WEB-based tool that can be used for conguration either locally using a USB or
Ethernet cable, or remotely via a radio link.
The SATELLAR Central Unit supports SATEL NMS, and provides the following features.
Connection options:
– Connect via TCP/IP Port 55555
– Connect via USB Device port when the USB port is in Virtual Serial port mode.
(See chapters 5.2 and 7.1.2 for details)
– Remote connection via radio network is available when the routing settings are
correctly dened.
Most settings available via the User Interfaces of the CU are also accessible using SATEL NMS. For this pur-
pose, the NMSID (Network Management System IDentier) as well as Sub-Unit number of each setting is
listed in this manual, see chapter 7. The NMSIDs are also used by the NMS Import application (see chapter
8.5).
Note that the NMS Address of the CU is the same as the RMAC Address of the attached Radio Unit. See the
Radio Unit user manual for details.
5.9 SSH
SATELLAR’s linux command line can be accessed using the SSH protocol. To do this you need a SSH client,
such as putty.exe. The user name is satellar and the password is Satel123.
29
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
6. Data transmission
2
6. Data transmission
The CU is used to transfer data over the IP protocol. Multiple IP protocols are supported, such as TCP/IP,
UDP and ICMP. A prerequisite for wireless IP transmission is that the RU is congured to packet routing
protocol mode as explained in the RU user manual.
6.1 Internet protocol
Each CU has an IP address belonging to the Local Area Network (LAN) to which they are connected via
their Ethernet interface. Each CU also has another IP address belonging to a second LAN, the SATELLAR
RU LAN. This LAN is formed by the radio protocol. These two interfaces are called eth0 and tun0 according
to standard Linux naming conventions. The CU acts as an IP router device, routing IP packets between its
Ethernet interface (eth0) and the radio network provided by SATELLAR RUs (tun0).
6.1.1 Example
In the Figure 6.1 shown on the next page is presented a network which has three (3) data terminal equip-
ment devices (DTEs) connected to CU through Ethernet. Each CU is connected to a RU, together forming
a SATELLAR XT 5RC Radio Station (in this case RU type is: 1 W, with display and keypad). In addition there
are two standalone RUs acting as repeater stations. Each of the stations has a unique station address
(RMAC) which is a number freely selectable in the range of 1 … 4094. The station addresses are used at the
radio protocol level when sending messages through the radio path. (The radio protocol is explained in
the RU user manual.)
Each DTE belongs to a LAN on the eth0 interface of a SATELLAR. To be able to communicate with each
other, IP routing must be correctly congured in each DTE and each SATELLAR.
How the station addresses are used for routing the data through the radio path, is explained in the RU
user manual. This is called Packet Routing. For the network topology seen on Figure 6.1 the Packet Routes
routing table looks like the following:
Radio unit Next hop (neighbor) Addresses behind (remotes)
A 2 3, 4, 5
B 3 1, 2, 5
C 3 1, 2, 4
D 1 -
3 4, 5
E 2 1
4 -
5 -
Table 6.1 Packet Routes routing table for Figure 6.1
30
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
6. Data transmission
2
Figure 6.1 Routing example
TD
RD
PWR
STAT
RU-145000
RX
TX
CTS
RTS
Station D
(RU)
Station address: 2
SA00020
Station E
(RU)
Station address: 3
TD
RD
PWR
STAT
RU-145000
RX
TX
CTS
RTS
TD
RD
PWR
STAT
RU-145000
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
CU-1U2100
OK
Station B
(RU+CU)
Eth0: 192.168.4.1/24
Tun0: 10.10.32.4/19
Station address: 4
DTE B
IP: 192.168.4.100
Default gateway:
192.168.4.1
Station C
(RU+CU)
Eth0: 192.168.5.1/24
Tun0: 10.10.32.5/19
Station address: 5
DTE C
IP: 192.168.5.100
Default gateway:
192.168.5.1
TD
RD
PWR
STAT
RU-145000
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
CU-1U2100
OK
Station A
(RU+CU)
Eth0: 192.168. 1.1/24
Tun0: 10.10.32.1/19
Station address: 1
DTE A
IP: 192.168.1.100
Default gateway:
192.168.1.1
TD
RD
PWR
STAT
RU-145000
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
CU-1U2100
OK
31
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
6. Data transmission
2
6.1.2 Forming the tun0 IP address
Whenever the station address (RMAC) of a SATELLAR is changed, the IP address for the tun0 interface is
automatically determined: If the station address is X, the tun0 IP address is set to 10.10.32.X, netmask 19.
In case the station address (X) is larger than 254, the tun0 address is of the form 10.10.A.B, where A = 32
+ (X / 254), rounded down and B = 1 + (X % 254) [% being the modulus operator]. For example, RMAC 500
translates to tun0 address 10.10.33.247.
In case a subnet with network address 10.10.32.0/19 is already in use in a system, a SATELLAR radio
network can be congured to use another tun0 network Base Address. To do this, use the Admin Settings
application (see chapter 8.8.2). All modems MUST use the same tun0 Base Address.
6.1.3 Choosing the eth0 IP address
The picture examples in this capter are made by utilizing the Routing –mode of the radio router. To set
the radio router into same subnet with connected devices, see chapter 6.2 for Proxy ARP –mode (recom-
mended mode for radio routers in the same subnet) or Bridge –mode details from chapter 7.10.
Eth0 IP addresses must be selected according to two rules.
– The IP address is not used by another device in the LAN.
– The CU and the corresponding DTE must belong to the same subnet.
Additionally
– The default gateway for the DTE should be the corresponding CU, unless there
is another gateway present in the LAN. In this case the routing tables of the
gateway must be modied accordingly.
The rules can be claried with the help of Figure 6.1: Routing example.
The station A has
– Station address (RMAC) 1 à tun0 address is 10.10.32.1
– Eth0 address 192.168.1.1/24 (i.e. subnet mask is 255.255.255.0)
– Therefore DTE A must have an address 192.168.1.X, e.g. 192.168.1.100 and its
default gateway must be 192.168.1.1
32
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
6. Data transmission
2
The station B has
– Station address (RMAC) 4 à tun0 address is 10.10.32.4
– Eth0 address must be chosen so that it belongs to a subnet dierent from
station A, e.g. 192.168.4.1/24
– Therefore DTE B must have an address 192.168.4.X, e.g. 192.168.4.100 and its
default gateway must be 192.168.4.1
The station C has
– Station address (RMAC) 5 à tun0 address is 10.10.32.5
– Eth0 address must be chosen so that it belongs to a subnet dierent from
stations A and B, e.g. 192.168.5.1/24
– Therefore DTE C must have an address 192.168.5.X, e.g. 192.168.5.100 and its
default gateway must be 192.168.5.1
Stations D and E act only as repeaters without a CU and therefore no local Ethernet connection.
So they have no IP addresses – just station addresses.
6.1.4 Setting IP routes
Aer all the addresses have been set it is still required to dene IP routes for each of the CU. Routing data
must include the address and net mask of each of the destination subnets (LANs) that need to be reached
and the gateway it can be reached through. The gateway address is the tun0 address of the target CU.
For the network in the Figure 6.1 the IP routing tables of each CU equipped station are:
Station Destination/net mask Gateway
A 192.168.4.0/24 10.10.32.4
192.168.5.0/24 10.10.32.5
B 192.168.1.0/24 10.10.32.1
192.168.5.0/24 10.10.32.5
C 192.168.1.0/24 10.10.32.1
192.168.4.0/24 10.10.32.4
Table 6.2 IP routing tables for each CU in Figure 6.1
33
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
6. Data transmission
2
The usage of dierent addresses and routing tables can be claried by an example where DTE A wants to
send a message to DTE B.
1. The destination IP address, 192.168.4.100, belongs to a subnet dierent from the
source address, 192.168.1.100. The message is therefore routed to the default
gateway of DTE A, i.e. to CU of station A.
2. CU of station A recognizes that the destination address belongs to sub network
192.168.4.0 which is reachable through gateway 10.10.32.4. The message is
therefore forwarded to tun0 interface which translates the gateway address to
the RMAC address, 4 in this case.
3. At this point the packet routing protocol of the RU enters the picture: it reads the
destination RMAC address and consults the packet routing table to nd out that
a message to address 4 must be sent to address 2. (Address of station D).
4. Station A’s RU now reserves the radio path using the CSMA/CA algorithm to send
the data to station D.
5. Station D receives the data and recognizes that the nal destination address
is 4. Station D consults its packet routing table and sees that the message to
address 4 must be sent to address 3 (station E) and then reserves the radio path
to send the message.
6. Station E receives the message and then forwards it to station B (as above)
which is the nal destination station.
7. The packet routing protocol in station B recognizes that the received data is in-
tended for this station and therefore forwards the data to the CU/tun0 interface.
8. The IP router soware component of the CU of station B recognizes that the
destination IP address diers from its own IP address but belongs to the same
sub network. Therefore it forwards the message to eth0 interface and then the
message nally reaches the destination, i.e. DTE B.
6.2 Proxy Arp
Proxy ARP option enables SATELLAR to act as a “Pseudo-bridge” or a hidden router. When this option is
enabled, SATELLAR responses with its own MAC address to all ARP (Address Resolution Protocol) requests
addressed to a remote network. This causes the other hosts in the same local network to send their
packets to the SATELLAR, which then routes those packets according to its congured IP Routes. This
behavior makes it look like the hosts on each side of the bridge belong to the same physical network seg-
ment (Default=OFF).
36
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
7. Settings
The CU has several settings, which aect the operation of the IP routing and other things. The CU can also
be used to change the settings of the RU as well as any other units present. There are several interfaces to
use when viewing info and changing settings (see chapter 5.6)
The settings are grouped into categories used in the LCD and WWW GUIs. Each setting is
also listed with the sub-unit number and NMSID for use with NMS Protocol and NMS Import
features. See chapter 5.8 for information about NMSIDs and chapter 8.5 for information about NMS Import.
NOTE: See the settings selection quide at the end of the manual.
7.1 Modem Settings
Figure 7.1 Modem Settings by CU: Graphical user interface (GUI/LCD)
7.1.1 Radio Unit Settings categories
For explanation of categories Network Protocol Mode, Radio, Serial Connector Conguration, Data Port
Settings, Serial Data Flow Control and Packet Mode Radio Access Control, see the RU user manual chapter
7, subchapters 7.1 through 7.3 respectively.
7.1.2 General
These are general and miscellaneous settings of the radio station and CU.
Attribute Explanation Sub unit NMSID
Name Name of the radio station. This is freely selectable by the user, up
to a maximum length of 32 characters. The name can be used to
identify the radio station. It is shown in the WWW interface and
GUI/LCD screen, for example.
0 1.769
PIN Code Code to unlock the GUI/LCD Screen of the CU (if present). 1 1.3200
37
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Attribute Explanation Sub unit NMSID
Temperature unit Fahrenheit, Kelvin or Celsius. Used by the Diagnostics graph for
modem temperature.
1 1.3201
UI Voltage Critical Level When the Voltage reading drops to this level, it is displayed in red
in the GUI/LCD and WWW interfaces.
1 1.3202
UI RSSI Critical Level When RSSI drops to this level it is displayed in red. 1 1.3203
UI Voltage Display mode Select the way to display voltage in the GUI/LCD: either numeric
or as a bar
1 1.3204
UI Voltage Bar Min If display mode is set to Bar, this Voltage level corresponds to the
minimum level of the voltage indicator, i.e. no bars. Value is also
used as a minimum threshold for SNMP Voltage. See chapter 8.2
for more details.
1 1.3205
UI Voltage Bar Max If display mode is Bar, this Voltage level corresponds to Maximum
bars
1 1.3206
PIN Code Required If set to Yes, user must enter PIN code to unlock the GUI/LCD and
keyboard.
1 1.3224
USB Device Mode Choose how the CU will act when connected to a PC: Mass
memory or Serial port. See also chapter 7.3.
1 1.3225
Display Brightness A value from 0 to 255, this setting controls the brightness of the
LCD screen’s backlight.
1 1.3258
Web GUI Password Set the password of user “satellar”. This aects the WWW
password and linux command line login password for this user.
The password is case-sensitive. Default password is “Satel123”.
1 1.3259
GUI Color prole Choose a color prole for the GUI/LCD. Default is “Black” 1 1.3261
LCD Timeout The time in seconds without keys pressed before the LCD (if
present) of the CU is powered o.
1 1.3275
Table 7.1 Modem settings, General
Figure 7.2 Modem Settings, General by CU: Graphical user interface (GUI/LCD)
38
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
7.1.3 Services
This category can be used to disable unused features of the CU and ne-tune some operational param-
eters. Usually these settings should not be modied, as some of the settings disable essential services of
the device.
Attribute Explanation Sub unit NMSID
SSHD State Turn the SSH server ON or OFF 1 1.3230
HTTPD State Turn the Web server ON or OFF. WARNING: If this is turned o, the WWW
interface becomes unavailable. It can be turned back on using the GUI/
LCD (if present) or SATEL NMS protocol.
1 1.3231
NMSBluetoothd
State
Turn ON or OFF the possibility of giving SATEL NMS commands to the
device using a wireless Bluetooth serial connection. A supported USB
Bluetooth dongle must be connected to the CU. (List of supported
devices available separately)
1 1.3232
NMSTcpsocketd
State
Turn ON or OFF the possibility of using SATEL NMS commands over a
TCP/IP connection to the device. The default TCP port is 55555.
1 1.3233
NMSLoggerd State This service is required by the diagnostics features. It monitors
diagnostic values and stores them in a database, where they can be
viewed using the Diagnostics application.
If this service is disabled, the status bar RSSI and Voltage readings are
also disabled.
1 1.3234
Linklayer State This feature is required by IP data transfer. WARNING: IF THIS
IS DISABLED, NO IP DATA CAN BE TRANSMITTED TO THE RADIO
NETWORK. Diagnostics can still be gathered and settings can still be
changed.
1 1.3235
NMSGathererd
timeout
Time in milliseconds to wait for NMS messages sent to the RU before
giving up. It is usually not necessary to modify this value
1 1.3237
NMSLoggerd
Interval
How oen the Diagnostic values are updated, in milliseconds. 1 1.3238
NMSLoggerd
Timeout
Time in milliseconds to wait for diagnostic NMS messages before
giving up. In case a CU is set up to monitor other devices in the network
(using the “Modem Settings/Remote Devices” settings category), it
may become necessary to increase this value if the network is very
large.
1 1.3239
NMSLoggerd
Retries
Number of times to retry lost diagnostic NMS messages. This value
should be kept low to avoid congestion in heavy traic situations.
1 1.3240
RU Commslogd
State
Set logging of NMS messages between the CU and the RU ON or OFF.
The log can be viewed in the “Logs” page of the WWW interface.
1 1.3262
USB Host Control When USB Host Control is OFF, the USB host port power is turned
o and no devices can be connected. When the value is ON, the port
works normally.
1 1.3269
UI Power Control When UI Power Control is ON, the GUI/LCD Screen is turned o aer the
dened timeout (See Modem Settings/General). When the value is OFF,
the screen is always turned o and the device uses less power.
1 1.3274
Table 7.2 Modem settings, Services
39
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Attribute Explanation Sub unit NMSID
SNMPD State Select SNMPD (SNMP Daemon or agent) ON or OFF 1 1.3266
OSPFD State Turns ON the OSPFD service. See section 7.8 for more information
about OSPFD.
1 1.3349
OSPFD Telnet Port The conguration port for OSPFD. Port 0 turns the Telnet server OFF 1 1.3350
RT Logger RT Logger collects certain radio specic information into the log le.
The log le is collected rst to device and can be seen in RT Logger at
Logs sheet.
Local log is cleared and restarted in certain time periods dened
by Query Interval and Backup Interval. In case a USB drive (stick) is
attached to device, the current log is copied to a USB drive to the end
of the le named as name_address_date_rtlogger.log. E.g. device
SATELLAR5 with RMAC address 2 which is having a log started at
rst day of January 2018 at 10:00 would have a log le SATELLAR5_
RMAC_0002_2018-01-01_00-10-00_rtlogger.log.
Default is OFF
1 1.3355
RT Logger Query
Interval
Query Interval is the period of time between two log information
queries in seconds.
Default is 10 s, scope 1...65535.
1 1.3356
RT Logger Backup
Interval
Backup interval denes the amount of query rounds before current
log in device is copied to end of current log at USB-Stick, aer which
current log is cleared and restarted.
Default is 30 rounds. Together with 10 seconds query interval it means
that backup is done in every 10 s x 30 = 300 seconds i.e. in every 5
minutes.
Scope 1..65535.
1 1.3357
Automatic
Modulation
Monitoring
Automatic modulation monitoring is intended for use when
automatic modulation is enabled. It enables gathering of automatic
modulation states against the neighbors of device. NOTE: If automatic
modulation is not enabled for radio (Modem Settings – Radio – Link
Specic Modulation -> Auto), this feature does not provide any useful
information and is thus not recommended in such case.
Modulation state and changes can be seen from Diagnostics sheet
(Local Modulation and Remote Modulation) as well as from Automatic
QAM Modulations at Logs sheet.
Default is OFF.
1 1.3361
Auto-modulation
Monitoring Timer
The time between the queries of current modulation states. Default is
10 seconds, scope 0..3600.
HTTPD IP Address Binding IP Address for the Web server 1 1.3400
SSHD IP Address Binding IP Address for the SSH server 1 1.3401
NMSTcpsocketd IP
Address
Binding IP Address for the NMS TCP socket 1 1.3402
OSPFD IP Address Binding IP Address for OSPFD 1 1.3403
Table 7.2 Modem settings, Services
40
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Figure 7.3 Modem Settings, Services by CU: Graphical user interface (GUI/LCD)
7.1.4 Commands
This chapter has commands to reset the unit(s) or restore settings to various states, for example to initial-
ize a device to its original status or reboot device.
Use only one command at the time and do not to save any other settings at the same time.
Also, refresh NMS values aer Radio Unit value restore.
To issue a command, select “Reset” or “Reboot”, for example. The command is sent when settings are
committed, as detailed in chapter 5.7.6.
Command Explanation Sub unit NMSID
Restore Default Factory Settings Radio Unit The RU’s settings, including Frequency,
Packet routing tables, RMAC etc. are
restored to the state they were in when the
unit le the factory.
0 1.3085
Restore Default Factory Settings Central Unit The CU’s settings, including IP, routing etc.
are restored to the state they were in when
the unit le the factory.
1 1.3085
Reset Radio Unit Resets the Radio Unit. This command is
mostly used by NMS Protocol to discard
unsaved changes. It is not usually
necessary to use this command when
conguring the modem using the WWW or
LCD user interfaces.
0 1.3090
41
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Command Explanation Sub unit NMSID
Reset Central Unit Resets the Central Unit. This command
is mostly used by NMS Protocol to
discard unsaved changes. It is not usually
necessary to use this command when
conguring the modem using the WWW or
LCD user interfaces.
(Note that despite being called the Reset
command, the CU is not actually reset.
Only unsaved settings are cleared. )
1 1.3090
Reboot Central Unit Reboot the CU (by resetting the MCU). The
reboot lasts approximately one a minute
(see technical specication for accurate
values)
1 1.3093
Statistical Counters Clear Clears (resets to zero) all Radio Unit
statistical counters. Statistical counters
include the variables whose values
increase due to some activity. These
variables are Bytes to Radio, Bytes from
Radio, Transmitted Packet Count and
Received Packet Count. Setting of this
patameter to value Clear resets those
counters to zero. Note that the value is
automatically restored back to do not
clear aer commit. Reset of values can be
observed from Modem Info page values (as
soon as the countres are updated).
1 1.3109
Table 7.3 Modem settings, Commands
There are also three buttons at the bottom of the WWW interface page: Reboot RU+CU, Reboot CU and
Reboot RU. Select the corresponding button to reboot the CU, RU or both. In this case there is no need to
select Apply or Commit buttons, but the reboot happens immediately.
Figure 7.4 Modem Settings, Commands by CU: Graphical user interface (GUI/LCD)
42
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
7.1.5 Remote Devices
This controls how the CU diagnostics service (NMSLoggerd) handles remote radio stations. By default, no
online remote monitoring is done.
Setting Explanation Sub unit NMSID
Pre-cache All Settings of Device N (N equals the RMAC address of the radio
station). Enable this to have the CU remotely
fetch all settings from the remote device. This
will cause signicant radio traic. (Not usually
recommended)
1 1.3264
Diagnostics Polling of Device N (N equals the RMAC address of the radio station).
Enable this to have the CU monitor the diagnostics
values of the remote device. The diagnostics
become available in the Diagnostics page. This
will cause additional radio traic which may be
signicant depending on the size of the network,
dened time intervals, timeouts and retries
(see chapter 7.1.3) and the number of devices
monitored. This setting is not shown, unless at
least one Packet Route is dened (see chapter
7.3.1)
1 1.3265
Table 7.4 Modem settings, Remote devices
Figure 7.5 Modem Settings, Remote devices by CU: Graphical user interface (GUI/LCD)
7.1.6 SNMP
The usage of SNMP is described in chapter 8.2.
7.1.7 Time Control
Control current date and time, time zone and Network Time Protocol (NTP) settings.
Note that SATELLAR does not have battery-backed real time clock hardware, therefore time is not accu-
43
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
rately preserved during power o and reboot. Using an external NTP server can help mitigate this.
Time is used mainly for logging purposes and accurate real-time is not essential for the operation of
SATELL AR.
Setting Explanation Sub unit NMSID
Time
Operation
Mode
No time operation – default. Other time settings have no eect. 1 1.3282
Manual time operation. Time and time zone settings are used, NTP settings are
not used.
NTP Time. Time setting is not used; instead the NTP protocol is used.
NTP Server AddressCurrent time is fetched from the dened NTP Server Address. Only works if
Time operation mode is set to NTP time.
1 1.3283
NTP Interval Time is refreshed from the NTP server aer the interval dened in this settings
has passed. Default is 100 seconds. Please be aware this setting will consume
some radio bandwidth if used in remote SATELLARs, therefore very small
values are not recommended.
1 1.3284
Time Current time given in “YYYY-MM-DD hh:mm:ss” format. This setting is only taken
into use if Time operation mode is set to Manual time operation.
1 1.3285
Time Zone Select time zone. Used in both NTP time and Manual time modes. 1 1.3286
NTP Request
Source IP Address
Source IP address of the NTP requests 1 1.3347
Table 7.5 Modem settings, Time control
NTP time setup can be veried from System Messages at Logs sheet.
Successful connection to NTP server generates the line:
May 26 08:06:03 (none) user.notice ntpclient: 29279 10391.478 55115.0 20.0 1080364372505324.6 1709.0 0
7.1.8 ATPC
This category controls Automatic TX Power Optimization, a feature that allows the SATELLAR to use the
minimum power required to get the wanted signal level and thus optimizing power consumption.
A remote SATELLAR is needed for reference. If there are multiple SATELLARs in range, the one that has
the weakest radio link should be selected so that when the transmit power is set based on that device, all
other devices should get at least as good signal as well.
44
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
The criteria for the correct transmit power are based on RSSI oor and RSSI range. Floor is the minimum
allowed RSSI value, and Range depicts how much that value is allowed to vary. If RSSI oor is -100 dBm
and the allowed range 10 dBm, then the transmit power is increased if the measured RSSI drops below
-100 dBm. If the measured RSSI rises above -90 dBm, the transmit power is lowered. The power steps
depend on the device, and the values are the same as in the menu Modem Settings -> Radio.
The logic of ATPC goes like this:
Every update period, the RSSI seen by the target device is measured
• If the target device cannot be connected to, do nothing. If there is no reply aer 5 periods, increase
power
• If the measured RSSI is lower than the lower limit for two queries in a row, increase power
• If the measured RSSI is higher than the upper limit for two queries in a row, decrease power
• Otherwise do nothing
Setting Explanation Sub unit NMSID
Automatic TX Power
Control
Turns the feature ON or OFF 0 1.2900
Target RMAC Address The RMAC address of the device used as reference 1 1.2901
Target RSSI Floor The lowest allowed RSSI value 1 1.2902
Allowed RSSI Range How much above the RSSI oor is the measured RSSI allowed to rise 1 1.2903
Update Period How oen is the power level checked 1 1.2904
Table 7.6 Modem Settings, ATPC
Example how to use ATPC can be found from manufacturer’s web site (Technical Bulletins):
https://www.satel.com/support-and-services/downloads/
7.1.9 NMS Modbus
This category allows the user to congure the NMS Modbus service, so that NMS values can be queried
with Modbus protocols (see section 5.8 for more information about NMS).
The SATELLAR works as a Modbus device that can be queried. The slave id can be changed, as well as the
used serial port (with Modbus RTU) and the binding IP address and port (with TCP). The NMS values are
stored in holding registers, and the only function that Modbus NMS supports is “Read holding Registers”.
The response will be a standard Modbus reply, or an exception code if the query is invalid.
The available register space are addresses 40001-49999. By default, registers 1-12 and 4097-8191 are
allocated to information that needs to be typically queried:
45
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
In the WWW UI, any other NMSID from either the Central Unit or Radio unit can be allocated to a register
that can then be queried. A list of Central Unit NMSIDs can be found in chapter 12, and a list of Radio Unit
NMSIDs can be found in chapter 12 of the Radio Unit user guide. You can also get a full list with NMS Import
(see section 8.5.1).
To add a new mapping, select “Add Mapping Row”. Type the Modbus register and NMSID pair. Add as many
mappings as you want and nally select “Apply Changes”. The information in the table will be lled auto-
matically. To remove a mapping, select the checkbox on the right of the mapping row and select “Delete
Selected”.
NMSIDs are divided into 4 categories based on their type, and it aect how they are mapped into the
registers:
• 8- and 16-bit NMSIDS are stored as they are into the register
• 32-bit NMSIDs are stored into two consecutive registers. If a 32-bit NMSID is mapped into register N,
no NMSIDs can be mapped into register N+1. If the value needs to be read, both Modbus registers N
and N+1 must be read, and the data combined in the application
• RMAC-specic RSSI values (NMSID 1.3087 and 1.55) are a special, hard coded case. Registers 4097-
8191 are reserved for queries about the RSSI-levels of RMACs 1-4095. So if for example the RSSI of
device 17 is required, register 4113 should be read. The register contains the RSSI value.
All other NMSIDs; 64-bit, String, IP Address and all NMSIDs that take more than 32 bits to store will be trun-
cated and stored into two consecutive registers. For example if the name of the device is SATELLAR, and
the name is mapped into a register, the two registers would contain SATE. If the name of the device would
be S1, the rst register would contain S1 and the second register would be empty.
When sending Modbus queries some thought is required for timeouts and latency. The time it takes to
generate a reply message depends quite naturally on how many NMSIDs are queried. When connected
locally, the average time it takes to generate a reply is about 10 ms + 70 ms times the number of NMSIDs to
be fetched. So if two NMSIDs are queried, the average response time is 150 milliseconds. This delay natu-
rally increases if the queries are sent over a radio network. Also if the CU is experiencing lots of traic the
latency might be higher. This should be taken into account when dening timeouts for queries, all queries
will not get responses if they are sent with a too high frequency.
46
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Setting Explanation Sub unit NMSID
NMS Modbus Service Turns the service ON or OFF 1 1.2800
Slave ID The Modbus Slave ID of the device, 0-247 1 1.2801
Protocol Used Modbus protocol: Modbus RTU, Modbus TCP or Modbus RTU
over TCP
1 1.2802
TCP Port Used TCP port (eective when protocol is TCP or RTU over TCP) 1 1.2803
Binding IP Address Eective when Modbus is TCP or RTU over TCP 1 1.2804
Serial Port Used serial port, RS or USB (eective when Modbus RTU is used) 1 1.2805
Register Mapping Array containing Modbus register/NMSID mapping 1 1.2815
Table 7.7 Modem Settings, NMS Modbus
Example of Custom Modbus NMS mapping can be found from manufacturer’s web site(Technical
Bulletins): https://www.satel.com/support-and-services/downloads/
7.1.10 Testing and Calibration
This category contains settings that help testing and calibrating the network.
Setting Explanation Sub unit NMSID
Carrier Test Activates the carrier test in the radio unit. When the test is on, the
RU will transmit a carrier signal continuously with no actual data
included. It can be used to measure how well other devices can
receive the transmissions. All devices in range operating on the same
frequency will be able to measure the RSSI. When the test is on, the
radio interface is reserved, because of the constant transmission.
0 1.3074
Carrier Test
Timeout
Species the duration for the carrier test on seconds. This value can
be modied either before starting the carrier test or during the test. If
the value is zero, the carrier test will stay on until turned o.
1 1.3094
Fast RSSI
scan
When this parameter is set to TRUE, RSSI value in the GUI will update
about once per second. (If set to FALSE, the update frequency of
RSSI value in the GUI is once per 30 seconds by default). Fast RSSI
scan increases CPU usage. Also, other statistics like Voltage and
Temperature will not be collected, if Fast RSSI scan is enabled. It is
recommended to enable Fast RSSI scan only when a fast update is
required for example for antenna alignment or troubleshooting.
1 1.330
47
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Setting Explanation Sub unit NMSID
RSSI RMAC
Address
By default the RSSI displayed in the GUI and the Diagnostics
application will show the RSSI measured from the last signal received.
If the device is receiving signals from multiple devices, it may be
diicult to match the measured RSSI to the corrcet transmitting
neighbor. This parameter can be used to force the RSSI measurement
to be done only for the messages received from the specic modem
only. Value expected for this parameter is the remote device RMAC.
If the value is 4096, the RSSI will be measured from any device. Note
that RMAC specic RSSI monitoring does not work with Carrier Test,
because the RMAC information is not included to test signal by the
transmitting modem.
1 1.331
Table 7.8 Modem Settings, Testing and Calibration
7.1.10.1 Example: Using carrier timeout and fast RSSI
In this example there is one master device with several neighbors. The user wants to know how well each
of the neighbors can hear the master, and adjust the antennas of the devices that have poor reception.
The carrier test is used.
The carrier test is activated in the master device. Also, because the device cannot be accessed remotely,
the timeout is set to two hours. Carrier test will automatically stop and normal operation can continue
aer 7200 seconds.
The following values are set from the GUI:
• Carrier test: ON
• Carrier test timeout: 7200
When the test is on, the user accessess all the remote modems to verify measured RSSI from the GUI. If
a poor RSSI value is found from any of the remote devices, the user proceeds to adjust the antenna. By
default, the RSSI on the screen updates about once per each 30 seconds. This may not be suicient for
antenna adjustment purposes. Therefore the user makes the RSSI measurement faster by changing the
following setting:
• Fast RSSI scan: ON
Now the RSSI measurement updates about once per second, and the user can see the results of the
antenna djustment in almost real time. Aer the antenna has been adjusted, the fast RSSI mode should be
turned o:
• Fast RSSI scan: OFF
48
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
7.2 Modem Info
This application contains information about the radio station. These values cannot be changed.
Figure 7.6 Modem Info by CU: Graphical user interface (GUI/LCD)
7.2.1 Status
Information about the current general state of the radio station. The values on this page may be refreshed
by pressing the F5 Key, or selecting Refresh from a menu, when viewed via the WWW interface on a stand-
ard web browser.
Item Explanation Sub unit NMSID
Temperature Measured inside the RU radio module. See RU user
manual for details.
0 1.32
Voltage Measured by the RU from the voltage input
terminals. Precision of the reading is 0.1 Volts, but
actual measurement accuracy may vary, see RU user
manual for details.
0 1.33
Bytes From Radio How much data (including NMS messages) has been
received by the RU from radio.
0 1.38
Bytes to Radio How much data (including NMS messages) has been
transmitted by the RU to radio.
0 1.39
Watchdog Error Count CU Number of reboots the CU’s Watchdog has
performed.
1 1.45
Last RSSI Signal strength of the last received radio message. 0 1.111
Alive Timer Time in seconds the RU has been running since the
last reset.
0 1.113
Transmitted Packet Count Number of Packet Routing packets transmitted by
Radio Unit to the radio since last reset of the RU.
0 1.120
Received Packet Count Number of Packet Routing packets received by
Radio Unit from the radio since last reset of the RU.
0 1.121
Detector Signal To Noise Ratio Signal to Noise Ratio (SNR) measured by the RU from
last received data packet, in decibels (dB).
0 1.122
49
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
View of Ethernet counters having multiple interfaces
Item Explanation Sub unit NMSID
Ethernet Status As a result of settings or auto MDI-X negotiation the
Ethernet status may change. This item shows the
current status. Connected/Not connected, 10 or
100Mb/s, Full or Half duplex.
1 1.3257
Last Boot Reason RU Reason for the last restart. User command,
Watchdog error, Power up etc.
0 9.795
Last Boot Reason CU Reason for the last restart. User command,
Watchdog error, Power up etc.
1 9.795
Temperature Ceiling Maximum measured temperature since the last reset 0 1.83
Transmitted Ethernet Packet
Count
Count of all packets transmitted to Ethernet. 1 1.141
Received Ethernet Packet
Count
Count of all packets received from Ethernet. 1 1.142
Ethernet Counters Count of Ethernet packets per interface. Interface
is dened with number i.e. 0 is trunk eth0 and each
VLAN is dened by VLAN ID. See picture below.
1 1.143
Transmitted Ethernet Byte
Count
Count of all bytes transmitted to Ethernet. 1 1.144
Received Ethernet Byte Count Count of all bytes received from Ethernet. 1 1.145
Ethernet Byte Counters Count of Ethernet bytes per interface. Interface is
dened with number i.e. 0 is trunk eth0 and each
VLAN is dened by VLAN ID. See picture below.
1 1.146
Transmitted Serial Byte Count Count of all bytes transmitted to serial port. 1 1.147
Received Serial Byte Count Count of all bytes received from serial port. 1 1.148
Table 7.9 Modem info, Status
50
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Figure 7.7 Modem info, Status by CU: Graphical user interface (GUI/LCD)
7.2.2 Services
This page shows information on dierent services running in the CU (see more about the services in chap-
ter 7.1.3). In addition to seeing which services are running, it can also be seen which services have been
restarted or have caused the device to reboot recently.
7.2.3 Radio Unit
This page shows information about the RU. See the Radio Unit User Guide for details.
Figure 7.8 Modem info, Radio unit by CU: Graphical user interface (GUI/LCD)
7.2.4 Central Unit
Next page shows information about the CU.
Item Explanation Sub unit NMSID
FPGA Watchdog Restarts Count of restarts the hardware watchdog has performed. 1 1.123
FPGA Total Restarts Total count of restarts the hardware has performed. 1 1.124
* Exact numbers and names of these items depend on the current HW conguration of the device
Table 7.10 Modem info, Central unit
51
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Item Explanation Sub unit NMSID
Firmware version The version of the le system of the CU. This information
is needed when updating the rmware using Firmware
Updater (see chapter 8.3)
1 1.650
Model Product model name. Normally this is “Satellar CU” 1 1.772
Ethernet MAC Address The Media Access Control (MAC) address of the built-in
Ethernet interface.
1 1.3210
Kernel version The version of the Linux kernel of the CU. This information
is needed when updating the rmware using Firmware
Updater (see chapter 8.3). This is the version of SATELLAR
kernel build, not the Linux kernel version it is based on.
1 1.3215
Serial Nbr RW The serial number of the CU, equal to the one printed on
the sticker on the device.
1 9.652
Board 1 * Hardware information about the PCB. 1 various
Interface board * Hardware information about the interface board (Ethernet
and USB connectors).
1 various
* Exact numbers and names of these items depend on the current HW conguration of the device
Table 7.10 Modem info, Central unit
Figure 7.9 Modem info, Central unit by CU: Graphical user interface (GUI/LCD)
52
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
7.3 Routing
The routing application allows changing the Packet routing tables, IP settings and routes. This is similar
to Modem Settings.
Figure 7.10 Routing by CU: Graphical user interface (GUI/LCD)
7.3.1 Packet Routing Tables
This category controls the packet routing tables of the RU. The interface is a little dierent on the GUI/
LCD and WWW. In both cases you can:
– Add new packet routes - Delete selected routes - Delete remote stations
– View current routes - Add remote stations to a route from a route
Important terms related to Packet Routing are:
- Neighbor, the RMAC address of a modem behind one radio link
- Remotes, RMAC address of modems behind the specic neighbor
In LCD GUI route management has 4 options: Edit Target, Add Remote RMAC, Delete Target and Add New
Neighbor.
Figure 7.11 Packet routing tables by CU: Graphical user interface (GUI/LCD)
1.
53
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Figure 7.12 Add new route
It is possible to cancel the procedure at any point and discard the route by selecting Cancel.
Editing of a route is done by highlighting the route that needs to be modied and then selecting Menu ->
Edit Target. See the gure “1. Add neighbor”.
To add a new remote RMAC address to existing route, highlight the neighbor to which the route is added to
and then select Menu -> Add Remote RMAC (see gure “1. Add neighbor”). Next, ll in the RMAC address to
be added to the route.
Figure 7.13 Edit route
Figure 7.14 Set remote RMAC
4. Enter remote RMAC
1. Add neighbor 2. Enter number of remotes 3. Enter neighbor RMAC
54
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Figure 7.15 Packet routing tables by CU: WWW user interface
With WWW interface, adding new routes is done by entering value for the neighbor RMAC address to
Neighbor eld and lling in the RMAC addresses of remotes behind this neighbor to the Remotes eld.
Separate remote RMAC address with whitespace. Apply the dened Packet Route by selecting Add
Routing Data. For example, to add a route to neighbor device with RMAC address 2, insert number 2 to
Neighbor eld and select Add Routing Data button to appl the new packet route.
In case of neighboring modem with RMAC address 3 having modems with RMAC addresses 5 and 6 behind
it, add the corresponding route as follows:
• Insert “3” to Neighbor eld
• Fill in “6 5” to Remotes eld
• Select Add Routing Data to apply changes.
To delete a route, highlight the neighbor or remote which needs to be deleted and then select Menu ->
Delete Target (see Figure “1. Add neighbor”).
Inserted values are pre-validated so in case of invalid input, SATELLAR will show the numbers in red color
and proceeding is not allowed until the value is corrected.
Once all needed modications are done, select Back twice to return to the main menu and you will be
prompted to save or discard settings.
55
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Figure 7.16 Adding multiple routes to neighbors
Multiple remotes can also be added similarly with one step. This is done by setting values to the First
Address and Last Address elds. The neighbor that has these addresses behind is dened by setting
the correct address to the Neighbor eld. The changes are applied by selecting Create a set of routes to
remotes. For example, Packet Routes to remotes 6,7,8,9 and 10 via the neighbor 5, is congured by setting
address 5 to Neighbor eld, number 6 to First Address and number 10 to Last Address eld. Selecting
Create a set of routes creates routes to remotes from 6 to 10 via the Neighbor 5.
Figure 7.17 Adding multiple routes to be reachable via one neighbor
Each neighbor packet route link can be specied with a dierent link specic modulation. If some of the
links have better link quality than others, it is possible to dene the best possible modulation for those
particular links - instead of using one common modulation dened by the weakest link. It is also pos-
sible to dene a handshake and a retransmission state for each link separately in the same way.
To use link specic values, link specic setting must be set on from either Modem Settings->Radio cat-
egory (Link specic modulation must be set to Manual) or from Modem Settings->Packet Mode Radio
Access Control (Link Specic Handshake and/or Retransmission must be on).
At GUI the same functionality is achieved by:
• Select Add Neighbor
• Setting number of remote RMACs to 2
• Dene the neighbor address to 3
• When asked for remote RMAC value, set the remote RMAC number 5
• When asked for next remote RMAC value, set the remote RMAC number 6
• To delete a route, mark the checkbox next to the route entry and select Delete Selected.
• To modify a route, change any of the values on a row and select on the Apply Changes.
In the WWW interface, Packet Routes can also be created automatically. Multiple routes can be cong-
ured with one step by dening a range of addresses. For example, setting the First Address to 5 and the
Last Address to 10 creates routes to the following neighbors: 5, 6, 7, 8, 9 and 10. The changes are applied
by selecting Create a set of routes to neighbors.
56
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
If link specic modulation has been set on but link specic modulation value at packet route is at o-
state, then modulation that is used is the common general modulation dened at Modem Settings ->
Radio category. Similar to that, the common general handshake and retransmission state are linked
to link specic handshake and retransmission state. It should be noticed that the value of link specic
modulation should be used so that it is either the same or higher than common general modulation.
See RU user manual for more information about link specic modulation.
NOTE:
- It is possible to show link specic options in add section with check box “Show Link Specic Options”
- It is possible to hide link specic options in Current routing tables section with check box “Hide Link
Specic Options”
- Link specic options are valid and visible only with QAM-products
Figure 7.18 Link specic settings
If you have entered an invalid route, SATELLAR will print a red error text and the invalid route is not
added.
All applied changes are committed and taken into use by selecting Commit Changes button. Applied
congurations can be reversed by Cancel applied changes.
See RU user manual for more information about packet routing.
In LCD GUI route management has 4 options: Edit Target, Add Remote RMAC, Delete Target and Add New
Neighbor. To add new route:
1. Select Menu -> Add Neighbor
2. Provide the number of remote RMAC addresses for this neighbor. In case adding only neighbor, and
no remotes, leave this to zero.
3. Fill in the RMAC address of the neighbor.
4. If number of remotes > 0, then RMAC for each remote is set.
57
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
7.3.2 IP
This category contains the Internet Protocol settings.
Setting Explanation Sub unit NMSID
IP Address
0 and 1
One of these is the Tun0 address. This cannot be directly modied. The
Eth0 address can be modied.
1 1.3208
Secondary IP
Address
List of additional IP addresses 1 1.3328
Ethernet Speed Auto, 10 Mbps or 100 Mbps. Some Ethernet devices will not work correctly if
speed is set to Auto. In this case select the correct speed using this setting.
1 1.3255
Automatic
IP State
OFF or ON. Default is OFF. If set to ON, the eth0 address is set to
172.20.X.1/14, where X equals the RMAC address. In this case, the eth0 IP
address cannot be modied until Automatic IP State is set to OFF.
1 1.3263
Ethernet Current
IP Address
Show the current eth0 address. If the address has been overridden by the
function button as detailed in chapter 5.5, this value is 192.168.1.1, even if
the setting on this same page has been set to another value.
1 1.3270
Ethernet Current
Ethernet mask
As above, shows the actual netmask in use at this time. 1 1.3271
Ethernet Duplex Settable to FULL or HALF. Some Ethernet devices require this to be set to
Half.
1 1.3276
IP Queue Max
Time Length
The IP router of the CU buers the IP packets going to the radio interface.
This setting controls how long individual packets are kept in the buer
before being deleted. See below for more information.*
1 1.3280
IP Queue Max
Packets
This setting controls the maximum number of packets in the outgoing IP
packet buer.*
1 1.3281
IP MTU Size MTU=Maximum Transmission Unit. MTU of a communications protocol of a
layer is the size (in bytes) of the largest protocol data unit that the layer can
pass onwards. The largest number is 1500-byte packet.
A larger MTU brings greater eiciency. Large packets increase lag and
minimum latency. Corruption of a single bit in a packet requires that the
entire packet is retransmitted. Retransmissions of larger packets take
longer.
1 1.3317
Proxy ARP When this option is enabled, SATELLAR responses with its own MAC
address to all ARP requests (Address Resolution Protocol) addressed to IP
address that actually locates in a remote network. This causes the other
hosts in the same local network to send their packets to the SATELLAR,
which then routes those packets according to its congured IP Route.
Eectively, the Proxy ARP connects to separate physical LAN segments on
each side of the radio network to the same IP network. (Default value: OFF).
1 1.3318
58
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Setting Explanation Sub unit NMSID
IP Header
Compression
IP Header Compression reduces the size of headers in IP connections. It
will reduce latency since the transmitted packets will be smaller. Possible
options are o, Van Jacobson and ROHC.
Van Jacobson compression algorithm is used to improve TCP/IP
performance over slow serial links. It packs the header of 40 bytes to about
3-4 bytes. It must be noticed that Van Jacobson assumes that there is
very little packet loss, so the feature should be used only in good-quality
point-to-point connections. Lost packets will make the receiver unable
to decompress the received packets, causing extra retransmissions. If
there are repeaters in the network, or there is noticeable packet loss, Van
Jacobson should not be used.
ROHC i.e. Robust Header Compression is a method for compressing IP, UDP,
TCP and RTP headers in IP packets. ROHC packs 40 bytes or 60 bytes of
header typically into only one or three bytes. As ROHC uses a functionality
called context which handle compressions per connection. This uses bit
more memory than Van Jacobson but can tolerate packet loss much better
than Van J. SATELLAR uses O-mode of ROHC.
1 1.3703
USB Ethernet IP
Address
IP address of possibly attached USB Ethernet dongle. The address dened
here will be set to Ethernet interface (eth1) that is created when dongle is
attached.
Default is 192.168.10.1/24
1 1.3714
USB Ethernet
Secondary IP
Address
Possible secondary address(es) of USB Ethernet dongle interface. 1 1.3715
IP Interface BindingThis feature enables bonding or binding of physical Ethernet interfaces.
Feature requires USB Ethernet dongle being attached.
Feature acts as a redundancy mechanism which uses other interface
if another goes somehow out of order or down. Both interfaces are
connected to IP interface bond0 which gets the IP interface of eth0 and
system acts basically similar to bridge i.e. physical interfaces are not
working as IP interfaces but instead as Ethernet ports which of one or the
other is being used depending on the case.
Default state is OFF. The default master port is native Ethernet port.
1 1.3716
* IP Queue handling: When the radio channel is experiencing heavy traic, IP packets cannot always be
sent immediately. They are placed in a queue waiting for the radio channel to become free. (See RU user
manual for more information). Note that the radio queue should not be set to too large values, because
the TCP/IP protocol will resend IP packets if it has not received a response in time. Too long IP queue
will in this case just cause more duplicate packets to be sent, to no useful eect. Also some real-time or
near-real-time applications, typically those using the UDP protocol, require packets to be at most a few
seconds old, therefore buering them for tens of seconds is not useful.
Table 7.11 Routing, Internet protocol settings
59
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Figure 7.19 Routing, IP by CU: Graphical user interface (GUI/LCD)
In the WWW UI, the user can add additional IP addresses to the device by selecting the plus symbol next to
the IP address:
New rows will appear on the page. The addresses will consist of two elds: the IP address with mask and
the interface:
The interface can be the Ethernet interface (eth0), radio interface (tun0), a virtual interface not connected
to any physical connector (local0) or a VLAN interface (eth0.*). VLAN interfaces need to be committed to
the device before they appear in the drop-down menu, see more about VLANs in section 7.5.
Aer the addresses have been set, select Apply changes to store them. To remove an address, check the
checkbox next to the address and select Delete Selected.
Addresses cannot be added or removed from the GUI, but existing ones can be viewed and modied.
60
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
7.3.3 IP Routes
This category allows adding, modifying and removing IP routes. For examples of typical routes, see chap-
ter 6.1.
Figure 7.20 Routing, IP Routes by CU: Graphical user interface (GUI/LCD)
A short introduction to IP routing
The SATELLAR IP radio network consists of Local Area Networks (LANs) and routers (the SATELLAR CUs).
One of the LANs is the radio network, reached through the tun0 interface of each SATELLAR. This LAN is
common to all SATELLARs. The other LANs are the Ethernet LANs (reached through the eth0 interface).
A router’s dened task is to route IP packets between LANs. To do this, the router needs routing tables which
tell it how to reach any other network. Therefore each router must have dened routes to all the LANs.
The task of dening routes is made easier by the concept of default route, also known as default gateway.
All IP packets are sent to the default gateway, unless there is a specic route telling otherwise.
All IP routes consist of two pieces of information.
– The target network address (including netmask)
– The target gateway address.
Together these two tell the router that an IP packet belonging to a certain network (i.e. LAN or subnet) must
be sent to a certain gateway. For example a route dened as 192.168.2.0/24 10.10.32.2, tells that all IP pack-
ets which have a destination address that falls under the 192.168.2.0/24 network address (for example
192.168.2.7) must be sent to the gateway 10.10.32.2.
Note that there must also be a return route dened in the other end router back to the original LAN.
(Sometimes a default route is enough for this). Typically SATELLARs at remote sites will act as the default
gateway for the Ethernet LAN they are connected to.
It is also possible to dene multiple routes to one network with redundant routing. For more information
see chapter 7.6. The rest of this chapter will focus on single routes to a single destination.
Consider the network in the Figure 7.20. There are four Ethernet LANs (1 through 4), connected by
SATELLAR radios (R1 through R4). The radios are connected by a h LAN, the radio LAN. LAN 1 is also
connected to the internet via a gateway (router, ADSL etc.).
61
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Internet
router
R1 R2
R3 R4
Radio LAN
SA00021
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
TD
RD
PWR
STAT
RX
TX
CTS
RTS
USB
ETH
PWR
STAT
OK
LAN 1 LAN 2
LAN 3 LAN 4
Figure 7.21 IP routing
Before designing the IP routes, we must dene the desired connectivity. To keep the amount of routes
smaller, we decide that LANs 2, 3 and 4 do not need to have access to each other, because our central sta-
tion is in LAN 1 and it will receive status messages from sensors connected to the other LANs. The sensors
do not need to communicate with each other. LAN 1 must however have access to the internet, so it can
be reached from o-site for remote monitoring.
Router Default gateway Other
routes
router WAN/internet LAN 2 via R1
LAN 3 via R1
LAN 4 via R1
R1 router LAN 2 via R2
LAN 3 via R3
LAN 4 via R4
R2 R1 none
R3 R1 none
R4 R1 none
Table 7.12 Interface routes, see Figure 7.20
(Note that interface routes are omitted for
simplicity, as they are automatically added)
62
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
The next step is to decide the actual IP address and netmask for each LAN. You also decide which device
will be the default gateway of each LAN.
LAN name network IP address Netmask Default gate-
way
LAN 1 192.168.1.0 24 router
LAN 2 192.168.2.0 24 R2
LAN 3 192.168.3.0 24 R3
LAN 4 192.168.4.0 24 R4
Radio LAN (Automatic) 10.10.32.0 19 R1
Table 7.13 IP address and net mask, see Figure 7.20
Please remember that the Radio LAN (tun0) addresses of each modem are automatically set based on the
RMAC addresses (see chapter 6.1.2). If we assume that each RMAC of radios R1…R4 is the same as their
number, we get the following IP addresses for the modems:
Device RMAC address tun0 IP address eth0 IP address (sugges-
tion)
router - - 192.168.1.1
R1 1 10.10.32.1 192.168.1.2
R2 2 10.10.32.2 192.168.2.1
R3 3 10.10.32.3 192.168.3.1
R4 4 10.10.32.4 192.168.4.1
Table 7.14 IP address, see Figure 7.20
Now we can dene the routing tables with actual addresses:
Device Target network gateway notes
router 0.0.0.0/0 <WAN IP address or interface> Default route is to internet
192.168.2.0/24 192.168.1.2 LAN 2 via R1
192.168.3.0/24 192.168.1.2 LAN 3 via R1
192.168.4.0/24 192.168.1.2 LAN 4 via R1
R1 0.0.0.0/0 192.168.1.1 Default route is via the router to internet
192.168.2.0/24 10.10.32.2 LAN 2
192.168.3.0/24 10.10.32.3 LAN 3
192.168.4.0/24 10.10.32.4 LAN 4
R2 0.0.0.0/0 10.10.32.1 Default route is via the radio network to R1
R3 0.0.0.0/0 10.10.32.1 Default route is via the radio network to R1
R4 0.0.0.0/0 10.10.32.1 Default route is via the radio network to R1
<other
devices in
the LANs>
0.0.0.0/0 <default gateway of the LAN as
dened above>
We omit the details, but in principle each
device in LANs 2, 3 and 4 will set the SATELLAR
as their default gateway. Devices in LAN 1 use
router as their default gateway.
Table 7.15 Routing tables with actual address, see Figure 7.20
63
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
To insert these routing tables to the SATELLAR CUs, use the Routing Application, IP Routes category. Note
that you also need to change the routing in your other routers to gain full connectivity. In case of demon-
strating and testing, the “router” is usually your PC.
Adding routing tables to SATELLAR
To add a new route with the WWW interface, insert the route in the text area and select Add New Route.
For example, to add a route to LAN 192.168.2.0/24 via the radio address 10.10.32.2, insert this:
You can also dene a Metric for each route for redundant routing. If the checkbox ”Show Route Monitoring
Options” is selected, a metric and monitor target can be specied for each route. These are only used
if there are multiple routes to one destination, otherwise they can be ignored. See chapter 7.7 for more
information.
In case “Show Route Monitoring Options” is selected, view looks like this:
To add a new route in LCD GUI, select Menu -> Add. Then modify destination Network (upper value) and
Gateway (lower value). Changing the editing between upper and lower values, or Network and Gateway, is
done with selection in Menu: select either Menu -> Network or Menu -> Gateway. When the route is ready,
select Save. Alternatively select Cancel to abandon the route.
Figure 7.22 Add and Save new route
To edit existing routes with WWW interface, use the Edit routes functionality. Select apply to apply
64
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
changes.
To edit IP routes with GUI: In the IP Routes view, highlight the route to edit and select Menu -> Edit.
Figure 7.23 Edit IP routes
With WWW interface, set of IP Routes can also be created automatically, based on the provided
parameters. The parameters are used as follows: the parameter Base address, together with Mask,
denes the destination network for the rst route. The next hop to this network will be the radio
network IP address of the neighboring modem provided to the eld First Address. For the next
automatically created route, the destination network will be the next available network according to
the Mask value.
Figure 7.24 Create a set of IP routes
For eaxmple, with the Mask 27, the network size will be 32 addresses. So if the rst automatically
created route is to network 192.168.0.0/27, the next one will be to 192.168.0.32/27. The next hop for
the next route will be the next radio network IP address in sequency. Automatic route creation will be
applied further on for the next network and next radio IP address, until the radio network IP address
specied in the eld Last Address is reached.
Eaxmple 1. Setting “Base Address: 192.168.0.0 Mask: 27 First Address: 4 Last Address: 7” creates
routes as presented in the following picture.
Figure 7.25 Example 1
65
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Example 2: Setting the following “Base Address: 192.168.2.0 Mask: 24 First Address: 2 Last Address: 3”
creates routes as presented in the following picture:
Figure 7.26 Example 2
To delete a route with WWW interface, mark the checkbox and select the Delete Selected button.
It is also possible to mark checkbox Chek All to select all routes. Deleting all routes at once is not
recomended if you have more than 500 routes.
To detele a route with GUI, highlight the correct route and select Menu -> Delete Target.
With the WWW interface, Delete to defaults button deletes all routes from device. This is useful espe-
cially with large amount of routes. Note that this action does not ask for conrmation, but the routes
are removed immediately.
If you have entered an invalid route, SATELLAR will print a red error text and the invalid route is not
added. Finally, remember to click on the Commit Changes button, or Cancel applied changes if you
made a mistake.
66
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
7.4 Serial IP
Serial IP is a feature where data coming from serial port is converted to IP packets and set to designated IP
address. Correspondingly the received IP packets are converted and forwarded to serial interface. Serial
IP conguration handling is divided into two sections for two interfaces:
– RS-232 connection in the radio unit (RU) and
– USB-Serial dongle attached to USB-A port of the central unit (CU).
Central Unit handles all the IP related data traic and the air interface is IP based. Central Unit
is needed for stations using the serial IP (CU, router). Central Unit is not required if the station
is acting only as a repeater (no terminal connection).
NOTE! IP routing to the destination is not required if the IP data traic is not entered to the
SATELLAR radio modem via RJ45 connector and the sender target address is dened to be
TUN0 address (radio address).
– The IP ports are selectable from port 1 to 65535. There are several ports already
in use for various applications (NOTE! Application layer), e.g. http 80, https 443,
SSH 21 and 22. Typically ports 1024 - 65535 are reserved for general purpose.
EXCEPTIONS: Ports 54441, 54442 and 55555 are reserved for SATELLAR use.
– Due to the IP based data transfer, the transmission delays variate. The SCADA
system shall be adjusted according to the SATELLAR Serial IP delays.
7.4.1 Serial IP RS-232 / USB-A
This section includes congurations related to both RS-232 and USB-A interface connection / serial IP
functionality.
Attribute Explanation Sub unit NMSID
Serial IP Mode Server – Used in cases where the data transfer is initiated by
some remote host. Server cannot open a connection, it can
only answer to the request for opening the connection by
Client.
1 3287
Client – Used typically in cases where most of data transfer is
initiated by this device. Client sends the request to the Server
for the connection to be opened.
Send Only - In this mode device is able only to send data to
from serial port to dened IP address and port i.e. not able to
receive any sending.
Receive Only – In this mode device is able to only receive data
to dened IP listening port and forward it to serial port .
67
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Attribute Explanation Sub unit NMSID
Twoway mode - This mode is meant to be used with TCP. In
the other modes TCP can either only originate the connection
(Client and Send Only) or listen to incoming connections
(Server and Receive Only). In Twoway mode either side can
either initiate or listen to connections.
Port Rate Rate of serial port – from 1200 to 460800 bps.
Default is 19200.
1 3288
Port Data Bits Serial Port Data Bits - 7 or 8. 1 3289
Port Parity Serial Port Parity - No Parity, Odd, Even. 1 3290
Port Stop Bits Serial Port Stop Bits – 1 bit or 2 bits. 1 3291
Protocol TCP, UDP, Telnet or Bulk Mode.
Must be coherent in network.
1 3292
Listening Port IP Port for listening incoming messages. * 1 3293
Destination Port IP Port for sending outgoing messages. ** 1 3294
Destination IP Address IP address for sending outgoing messages. ** 1 3295
Sender Retry Count Count for how many times messages are attempted to resent
in TCP protocol if send does not succeed. ***
1 3296
Sender Retry Interval The gap time between resending attempts (in TCP mode) in
milliseconds. ***
1 3297
UDP Listener Port Timeout Timeout for releasing the listener of one connection in UDP
mode in seconds. This means that if there is no data received
in dened time, connection is closed. New connection can be
established at any time again. ****
1 3298
Remote Control Port Mode Denes whether the RFC 2217 conguration possibility set on
or o, default being o.
1 3299
Remote Control Port Rate Port rate of remote control connection. Default is 115200. 1 3300
Remote Control Port IP port of conguration. 1 3301
Minimum Packet Characters** Minimum size of sent IP packets 1 3319
Packet Creation Timeout** How long to wait for new serial data before creating IP packet 1 3320
Serial Output Where is the serial output written to: serial port or radio. See
section 7.4.3 for more information
1 3327
Local IP Address This is the address that remote clients will connect to when
connecting to this device. It is also the sending address in case
of outgoing traic.
1 3404
* Parameter is eective when message listening is on (Server, Client, Receive Only).
** Parameter is eective when message sending is on (Server, Client, Send Only).
*** Parameter is eective when message sending is on (Server, Client, Send Only) with TCP protocol.
**** Parameter is eective when message listening is on (Server, Client, Receive Only) with UDP protocol.
Table 7.16 The congurations related to both RS-232 and USB-A interface connection / serial IP functionality
68
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
NOTE: The connection will be established only by the Client and only to the device acting in Server
mode. Once the connection has been established, the data traic can be both ways. The connection
will be kept open as long as the SATELLAR central units are running. The connection is closed by the
Client or the connection is opened to another destination by the Client.
Page has also link to check serial connector conguration status e.g. to verify that the serial port is not reserved for
NMS usage. Typically Radio Unit Port Assignment should be at state MCU UARTS TO SATBUS WITH CAN.
Figure 7.27 Conguration of Serial IP RS-232 via WWW-interface
69
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
7.4.2 UDP and TCP protocols
Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) are both based on Internet
Protocol (IP) suite. They are used for relaying datagrams - also known as network packets – from the
source host to the destination host solely based on the addresses. Packets are structured by Open
Systems Interconnection (OSI) model layer principles. OSI model structures packets to dierent layers and
TCP and UDP packets can quite simply be presented with these layers:
– Data link layer: Physical addresses i.e. source and destination MAC addresses
– Internet layer: IPv4 / IPv6 addresses and related header
– Transport Layer: TCP, UDP or similar protocol data (ports etc.) and related header
– Application Layer: Actual user data
Following tables present the structure of data. Data link layer data comes rst and in the end there is
frame footer. Between the frame data and footer is IP packet data. In IP packet internet layer data is rst,
then the transport layer i.e. protocol related data and nally actual user data.
Data Link layer
Frame header (8 bytes) Frame data (14 bytes) IP + UDP packet (below) Frame footer i.e. CRC (4 bytes)
IP Packet
bits 0-3 4-7 8-13 14-15 16-18 19-31
0 Version Internet Header
Length
Dierentiated
Services Code
Point
Explicit
Congestion
Notication
Total Length
32 Identication Flags Fragment Oset
64 Time To Live Protocol Header Checksum
96 Source Address
128 Destination Address
160+ Data (UDP Packet)
UDP Packet
bits 0-7 8 – 15 16 – 23 24 – 31
0 Source Port Destination Port
32 Length Checksum
64+ Data (actual user data)
70
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
Thus IP + UDP Packet headers are altogether 28 bytes. TCP packet is alike the UDP with some more infor-
mation in TCP section such as sequence number. TCP header is thus larger (20 bytes) than UDP (8 bytes).
The dierence between the protocols is the administration of packets and how the received packets are
supposed to be handled. UDP is a not connection based simple transmission model without implicit
handshaking dialogues for providing reliability, ordering, or data integrity. Thus, datagrams may arrive
out of order, appear duplicated, or go missing without notice. UDP assumes that error checking and cor-
rection is either not necessary or performed in the application, avoiding the overhead of such processing
at the network interface level. TCP on the other hand is connection based protocol which provides error
checking, ordering and general reliability.
Time-sensitive applications oen use UDP because dropping packets is preferable to waiting for delayed
packets. Also as described above, the size of headers - i.e. packet overhead - is smaller with UDP which
may make dierence when the size of actual data is always small. Examples of applications using UDP are
DHCP, DNS and voice and video applications. On the other hand, if error correction facilities, ordering and
general reliability is needed, an application may use the TCP. Examples of using TCP are HTTP, FTP, SMTP
and SSH.
7.4.3 Ethernet to serial converter
It is also possible to use Serial IP as an Ethernet/Serial converter with the Radio Unit in either Basic or
Source Routing mode. In that conguration, all data received by the TCP/UDP server congured with
Serial IP will be sent over the radio, and all data received from the radio will be sent as TCP/UDP packets.
To get the converter working, settings in several menus have to be modied:
• Serial IP settings need to be set correctly. NMSID 1.3327 must be set to “Radio”
• Protocol Mode in Modem Settings -> Network Protocol Mode must be something other than Packet
Routing
• Radio Unit Port Assignment in Modem Settings -> Serial Connector Conguration must be MCU
UARTS TO SATBUS WITH CAN
• The serial port settings in Modem Settings -> Data Port Settings must match the ones set for Serial IP
• Linklayer state must be OFF in Modem Settings -> Services
• CRC shall be set to OFF state in all radio modems (Modem Settings -> Serial Data Flow Control ->
CRC)
71
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
The WWW UI will display warning messages if some of these settings do not match:
7.4.4 Notes
There are some noticeable issues, which are related to serial IP functionality.
7.4.4.1 USB Serial dongle connection
Availability of USB serial connection is informed with dierent notes. When USB serial dongle is con-
nected, the following text is shown in the screen: USB serial dongle connected.
Figure 7.28 USB serial dingle connected
If not connected, then note about interface being not available is shown.
Figure 7.29 USB serial dongle not connected
Please make sure that Serial IP Mode is OFF when USB serial dongle is not connected.
7.4.4.2 RS-232 port availability
In some occasions RS-232 is reserved and cannot be used for Serial IP functionality. Following text is
displayed in such occasions.
72
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
7.4.4.3 Disconnecting USB Serial dongle
When disconnecting the USB Serial dongle the Serial IP Mode must to be set OFF. Detaching the dongle
when the mode is not OFF sets the device in to a fault state and may even reboot the device.
If the Serial IP Mode is ON, but the dongle is not connected, following warning text is displayed at web UI:
USB serial IP mode is on but dongle is not connected!! Pelase set the mode o.
7.4.4.4 Incompatible parameter combinations
There are some parameter combination cases that can make the connection ends incompatible:
– Dierent protocols: It must be veried that both connection ends have the
same protocol. When one connection end uses TCP and other UDP, connection
cannot work.
– Compatible modes: If both ends have either send only or receive only mode on,
connection does not work as assumed. On the other hand, when using send
only on one end and receive only on other end, it must be veried that send only
is in the end intended to send data.
– Ports and addresses: Ports and addresses must match in the setup. I.e. the
sending target address and port must match with IP address of listener and the
port that is opened for listening.
– CRC shall be set to OFF state in all radio modems (Modem Settings -> Serial Data
Flow Control -> CRC)
73
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
7.5 Virtual Local Area Network (VLAN)
Virtual LAN (VLAN) is a feature that allows a physical LAN network to be devided into separate
networks. All devices connected to same VLAN can communicate with each other as if they were con-
nected to the same physical LAN.
The Vlan operation and functionality is described in the IEEE (Institute of Electrical and Electronics
Engineers) standards 802.1q
The SATELLAR supports VLAN in its Ethernet port (eth0). The ethernet interface accepts those eth-
ernet frames that have a VLAN tag matching any of the VLAN IDs congured to SATELLAR. SATELLAR
removes any VLAN tag from the accepted frames aer receiving them and correspondingly adds VLAN
tag with a correct ID to the frames sent out from the VLAN interface. The VLAN information is not car-
ried over the radio and cannot be congured to the radio interface.
7.5.1 VLAN settings
The VLAN settings are available under the Routing menu, at the VLAN page. This applies for both, the
GUI on the modem display and the WWW user interface. In the VLAN conguration page, VLAN inter-
faces can be added, modied or removed.
7.5.1.1 WWW user interface
74
SATEL OY // SATELLAR MANUAL // CENTRAL UNIT // USER GUIDE // V. 1.9
7. Settings
2
The WWW UI is divided into two sections: add new VLAN interface and modify existing VLAN interfaces. To
add a new VLAN interface, ll the empty elds with correct values and then select Add new VLAN. The elds
have the following denitions:
To add a new VLAN interface, ll the empty elds with correct values and then select Add new VLAN. The
elds have the following denitions:
Name Explanation
IP address The IP address and the net mask of the VLAN interface. The IP address should be unique. The address is
given in the same format as the eth0 IP address, for example: 192.168.51.1/24
Interface Master interface for this VLAN, either eth0 or eth1
VLAN name A descriptive name for VLAN. Must be 1-31 characters long and can contain only alphanumeric symbols. All
specied VLANs must have unique names.
VLAN ID A number from the range 1-4094, identifying the VLAN. Each device connected to the same VLAN network
must have the same ID.
Proxy ARP Enable or Disable Proxy ARP operation for this VLAN interface.
Tag g ing The state of tagging related to particular VLAN. NOTE: valid only if bridge mode has been set to some other
state than OFF.
Full tagged: Messages in both directions (Ethernet and radio interface) are going out as tagged.
Untagged radio: Packets from Ethernet are untagged and packets to Ethernet are tagged. Packets from and
to radio IP interface are handled as untagged.
Untagged Ethernet: Same as previous but vice versa i.e. messages through Ethernet are untagged and radio
interface sets VLAN tag to them.
It must be noticed that some combinations do not work logically together. E.g. setting one side to Full
Tagged and other to Untagged radio does not work. As the tagged message would go over the radio to
device having only untagged radio interface, it does not handle tagged VLAN message.
Table 7.17 The concurations related to creating and modifying VLANs
You can add multiple VLANs. When all desired VLANs have been added, select Apply Changes and Commit
Changes as when modifying any other parameter. To delete a VLAN, select the checkbox next to it and
choose Delete Selected and Commit Changes.
You have the option to disable a VLAN instead of deleting it completely. The last eld in every VLAN is
Enabled, that can be set to NO. Remember to Apply and Commit changes. Every VLAN will be enabled by
default.