Comtech EF Data ROSS User Manual
S
Comtech EF Data is an
AS91 any
00 Rev B / ISO9001:2000 Registered Comp
ROS
Roaming Oceanic Satellite Server
Installation and Users Guide
IMPORTANT NOTE: The infor mation containe d in this document supersedes all previously published information
regarding this product. Product specifications are subject to change without prior notice.
Part Number MN/13070 Revision 4
ROSS MN/13070
PREFACE
Customer Support
Contact the Comtech EF Data Customer Support Department for:
• Product support or training
• Reporting comments or suggestions concerning manuals
• Information on upgrading or returning a product
A Customer Support representative may be reached at:
Comtech EF Data
Attention: Customer Support Department
2114 West 7th Street
Tempe, Arizona 85281 USA
480.333.2200 (Main Comtech EF Data Number)
480.333.4357 (Customer Support Desk)
To return a Comtech EF Data product (in-warranty and out-of-warranty) for repair or
replacement:
For Online Customer Support:
An RMA number request can be requested electronically by contacting the Customer Support
Department through the online support page at
For information regarding this product’s warranty policy, refer to the Warranty Policy, p. 5.
480.333.2161 FAX
• Contact the Comtech EF Data Customer Support Department. Be prepared to supply the
Customer Support representative with the model number, serial number, and a description
of the problem.
• Request a Return Material Authorization (RMA) number from the Comtech EF Data
Customer Support representative.
• Pack the product in its original shipping carton/packaging to ensure that the product is not
damaged during shipping.
• Ship the product back to Comtech EF Data. (Shipping charges should be prepaid.)
www.comtechefdata.com/support.asp:
• Click “Return Material Authorization Instructions” from the Service page for detailed
information on our return procedures.
• Click the “RMA Request form” hyperlink, and then fill out the form completely before
sending.
• Send e-mail to the Customer Support Department at service@comtechefdata.com.
Comtech EF Data, Vipersat Products Page 2 of 87
ROSS MN/13070
About this Manual
This manual describes the installation and operation for the Comtech EF Data Roaming Oceanic
Satellite Server (ROSS). This is a technical document intended for earth station engineers,
technicians, and operators responsible for the operation and maintenance of the ROSS.
Reporting Comments or Suggestions Concerning this Manual
Comments and suggestions regarding the content and design of this manual are appreciated. To
submit comments, please contact the Comtech EF Data Technical Publications department:
TechnicalPublications@comtechefdata.com
Conventions and References
Related Documents
The following documents are referenced in this manual:
• CDM-570
• SLM-5650A
Cautions and Warnings
IMPORTANT or NOTE indicates a statement associated with the task
IMPORTANT
being performed or information critical for proper equipment function.
CAUTION indicates a hazardous situation that, if not avoided, may
result in minor or moderate injury. CAUTION may also be used to
CAUTION
indicate other unsafe practices or risks of property damage.
WARNING indicates a potentially hazardous situation that, if not
WARNING
avoided, could result in death or serious injury.
Trademarks
Product names mentioned in this manual may be trademarks or registered trademarks of their
respective companies and are hereby acknowledged.
Comtech EF Data, Vipersat Products Page 3 of 87
ROSS MN/13070
Warranty Policy
Comtech EF Data products are warranted against defects in material and workmanship for a
period of two years from the date of shipment. During the warranty period, Comtech EF Data
will, at its option, repair or replace products that prove to be defective.
For equipment under warranty, the owner is responsible for freight to Comtech EF Data and all
related customs, taxes, tariffs, insurance, etc. Comtech EF Data is responsible for the freight
charges only for return of the equipment from the factory to the owner. Comtech EF Data will
return the equipment by the same method (i.e., Air, Express, Surface) as the equipment was sent to
Comtech EF Data.
All equipment returned for warranty repair must have a valid RMA number issued prior to return
and be marked clearly on the return packaging. Comtech EF Data strongly recommends all
equipment be returned in its original packaging.
Comtech EF Data Corporation’s obligations under this warranty are limited to repair or
replacement of failed parts, and the return shipment to the buyer of the repaired or replaced parts.
Limitations of Warranty
The warranty does not apply to any part of a product that has been installed, altered, repaired, or
misused in any way that, in the opinion of Comtech EF Data Corporation, would affect the
reliability or detracts from the performance of any part of the product, or is damaged as the result
of use in a way or with equipment that had not been previously approved by Comtech EF Data
Corporation.
The warranty does not apply t o an y produc t or parts there of where the serial num ber or the se rial
number of any of its parts has been a ltered, defaced, or rem oved.
The warranty does not cover damage or loss incurred in transporta tion of the pr oduct.
The warranty does not cover replacement or repair necessitated by loss or damage from any cause
beyond the control of Comtech EF Data Corporation, such as lightning or other natural and
weather related events or wartime environments.
The warranty does not cover any labor involved in the removal and or reinstallation of warranted
equipment or parts on site, or any labor required to diagnose the necessity for repair or
replacement.
The warranty excludes any responsibility by Comtech EF Data Corporation for incidental or
consequential damages arising from the use of the equipment or products, or for any inability to
use them either separate from or in combination with any other equipment or products.
A fixed charge established for each product will be imposed for all equipment returned for warranty
repair where Comtech EF Data Corporation cannot identify the cause of the reported failure.
Comtech EF Data, Vipersat Products Page 4 of 87
ROSS MN/13070
Exclusive Remedies
Comtech EF Data Corporation’s warranty, as stated is in lieu of all other warranties, expressed,
implied, or statutory, including those of merchantability and fitness for a particular purpose. The
buyer shall pass on to any purchaser, lessee, or other user of Comtech EF Da ta Corporation’s
products, the aforementioned warranty, and shal l indemnify and hold harm less Comtech EF Data
Corporation from any claims or liability of such purchaser, lessee, or user based upon allegations that
the buyer, its agents, or employees have made additional warranties or representations as to product
preference or use.
The remedies provided herein are the buyer’s sole and exclusive remedies. Comtech EF Data
shall not be liable for any direct, indirect, special, incidental, or consequential damages, whether
based on contract, tort, or any other legal theory.
Software Versions
Software Application version: 1.3.0.921
Software Part Number: SW13069C.app
Software ROSS Configuration Editor version: 1.3.0.921
Comtech EF Data, Vipersat Products Page 5 of 87
ROSS MN/13070
Document Revision History
Revision Description of Change EffectiveDate
1 Software Release 1.0.0.562
First Publication Release
2 Software Release 1.1.0.730
Moved vendor specific ACU reference to appendices, documented
Orbit ACU configuration, added section LCD front panel interface.
3 Software Release 1.2.0.812
Documented ROSS 1.2 features, service bound and multiband LNB
support.
4 Software Release 1.3.0.921
SLM-5650A Support, and ROAM Protocol Emplemented
11-5-2007
08-30-2008
11-30-2009
10-25-2010
Comtech EF Data, Vipersat Products Page 6 of 87
ROSS MN/13070
Table of Contents
1.1 Introduction ................................................................................................................................................ 9
1.2 Overview .................................................................................................................................................... 9
1.3 ROSS Control Function ............................................................................................................................ 10
1.4 Configuration Files ................................................................................................................................... 11
1.5 Database Files ........................................................................................................................................... 11
1.6 Features .................................................................................................................................................... 12
1.7 ROSS Client Interface .............................................................................................................................. 12
1.8 Storage Capacity ....................................................................................................................................... 12
1.9 Processing Power ..................................................................................................................................... 12
1.10 Flexible Interface Platform ....................................................................................................................... 13
1.11 Event Log ................................................................................................................................................. 13
1.12 Tracking Log ............................................................................................................................................ 13
1.13 ROSS Specifications ................................................................................................................................ 13
2 Installation Overview ............................................................................................................................... 15
2.1 Installation Requirements ......................................................................................................................... 15
2.2 Unpacking and Inspection ........................................................................................................................ 15
2.3 Installing the ROSS Unit .......................................................................................................................... 16
2.4 ROSS, Modem, and ACU Connectivity ................................................................................................... 16
2.5 Quick Start Configuration Checklist ........................................................................................................ 17
2.6 ROSS System Overview ........................................................................................................................... 18
3.1 ROSS Messages & Data .......................................................................................................................... 20
3.1.1 Transmit Enable Keep-alive (TEK) Message .......................................................................................... 20
3.1.2 ACU Commands ...................................................................................................................................... 20
3.2 Service Area Description ......................................................................................................................... 22
3.3 Modem Interaction with ROSS ................................................................................................................ 23
4.1 ROSS Client Interface .............................................................................................................................. 27
4.2 Connecting To ROSS via Serial Interface ................................................................................................ 28
4.3 Connecting to ROSS via LAN (Telnet) Connection ................................................................................ 29
4.4 Main Menu ............................................................................................................................................... 31
4.5 Configuration Menu ................................................................................................................................. 31
4.6 ACU Configuration .................................................................................................................................. 31
4.7 Modem Configuration .............................................................................................................................. 32
4.8 Network Configuration ............................................................................................................................. 33
4.9 Network ID ............................................................................................................................................... 33
4.10 VMS Multicast Address ........................................................................................................................... 33
4.11 Shoreline Default (Threshold) .................................................................................................................. 34
4.12 Change Console Password ....................................................................................................................... 34
4.13 General Setup: Date & Time .................................................................................................................... 34
4.14 Unit Status Page ....................................................................................................................................... 35
4.15 Transmit Status ......................................................................................................................................... 35
4.16 Last Position ............................................................................................................................................. 35
4.17 Heading Position ...................................................................................................................................... 36
4.18 Handoff Mode .......................................................................................................................................... 36
4.19 Stealth Mode ............................................................................................................................................. 36
4.20 Last Poll .................................................................................................................................................... 36
4.21 ACU Status ............................................................................................................................................... 36
4.22 Modem Status ........................................................................................................................................... 36
4.23 System Up Time ....................................................................................................................................... 36
4.24 Managing VMS ........................................................................................................................................ 37
4.25 Operations Menu ...................................................................................................................................... 37
4.26 ROSS Front Panel Interface (Keypad/LCD) ............................................................................................ 42
4.27 Configuration Menu ................................................................................................................................. 44
4.28 Status Menu .............................................................................................................................................. 45
Comtech EF Data, Vipersat Products Page 7 of 87
ROSS MN/13070
4.29 Operation Menu ........................................................................................................................................ 46
4.29.1 About Menu (command) .......................................................................................................................... 47
5 ROSS Configuration Editor ...................................................................................................................... 48
5.1 Creating Service Areas ............................................................................................................................. 48
5.2 ROSS Configuration Items ....................................................................................................................... 49
5.3 Edit Properties (IP Address) ..................................................................................................................... 50
5.4 Edit Insert (Service Area) ......................................................................................................................... 51
5.5 Enter Antenna Pointing Information ........................................................................................................ 52
5.6 Import Modem Configuration File ........................................................................................................... 54
5.7 Edit Modem Configuration File ............................................................................................................... 55
5.8 Edit Service Bounds ................................................................................................................................. 56
5.9 Service Bounds Configuration .................................................................................................................. 57
5.10 Service Bounds Configuration .................................................................................................................. 58
5.11 Service Bound Advanced Switching ........................................................................................................ 60
5.12 Edit Coordinated Areas ............................................................................................................................ 60
5.13 Coordinated Area Configuration .............................................................................................................. 61
5.14 Importing Polygon Coordinates from KML Files .................................................................................... 61
5.15 Coordinated Area ID ................................................................................................................................ 61
5.16 Shoreline Override ................................................................................................................................... 62
5.17 Nested Coordinated Areas ........................................................................................................................ 62
5.18 Edit RF Converter Profile ......................................................................................................................... 63
5.19 Tools Download ....................................................................................................................................... 67
5.20 Tools Upload ............................................................................................................................................ 67
5.21 Tools Download Event Log ...................................................................................................................... 68
5.22 Tools Clear Event Log .............................................................................................................................. 69
5.23 Tools Download Tracking Log ................................................................................................................. 69
5.24 Clear Tracking Log................................................................................................................................... 70
5.25 Import & Export of Coordinated Area Maps ............................................................................................ 71
5.26 Uploading Application Code .................................................................................................................... 72
6 Retrieving Event and Tracking Logs ........................................................................................................ 73
Appendix A: Documents and Glossary ....................................................................................................................... 75
Appendix B: Sea Tel DAC-2202 ................................................................................................................................. 76
Appendix C: Orbit Technologies OrSat AL-7200 Controller ...................................................................................... 82
Appendix D: ROAM Protocol ..................................................................................................................................... 84
Appendix E: LAN Configuration SetIP ....................................................................................................................... 85
Comtech EF Data, Vipersat Products Page 8 of 87
ROSS MN/13070
1.1 Introduction
Comtech EF Data has developed Satellite On The Move (SOTM) technology that provides a
global coverage method of satellite hopping dynamically to maintain communications and
extend the advantages of switched Single Channel Per Carrier (dSCPC) within a Vipersat
network. This method allows a mobile remote satellite station on-board a roaming oceanic vessel
to transition between satellite or hub coverage connections with minimal service interruption.
The key components to this technology are hub and remote satellite modems, a stabilized mobile
antenna system for tracking GEO satellites, a central management system maintaining the
alliance of the remote satellite network communication links, and a mobility controller with
multiple location codes of satellite service areas.
The Vipersat Roaming Oceanic Satellite Server (ROSS) fills the role of the satellite mobility
controller. In conjunction with an Antenna Control Unit (ACU), the ROSS performs satellite
antenna re-point and information gathering. When a transition requirement is identified, the
ROSS will push new pointing information to the ACU and provide the new transmission
parameters to the CDM-IP modem that are required for service area handoff.
1.2 Overview
The ROSS is one of the key components in the Comtech EF Data mobile satellite solution
system that provides the capability to automatically transfer remote sites from one satellite
connection to another as the mobile vessel moves between multiple satellite coverage areas. In
addition, the ROSS provides alternate configuration files for the modem that can be mapped to
specific regions of a satellite’s coverage area or ground station equipment. This allows
communication link parameters, such as data rate and modulation, to be optimized for the
satellite reception in that region.
A typical interconnect diagram for the ROSS as deployed aboard ship in a mobile remote
satellite application is shown in figure 1. Please note that the example in figure 1 uses a generic
device name antenna control unit (ACU). All references to antenna controller unit (ACU) are
refer to vendor neutral ACU. See appendices for supported ACU types.
Comtech EF Data, Vipersat Products Page 9 of 87
ROSS MN/13070
CISCO IP PHONE
7960
messages directories
12
ABC3DEF
i
settingsservices
45
JKL6MNOGHI
78
TUV9WXYZPQRS
0
#
OPER
*
Figure 1: Typical Interconnect Diagram
1.3 ROSS Control Function
The ROSS hosts a set of configuration, database, and map files that are used for controlling
satellite communications for the local remote terminal. This data provides the required reference
points for managing satellite handoff operations and for enabling/disabling the remote modem
transmitter. Shoreline boundaries provide a demarcation point for muting the modem transmitter
to prevent potential interference with fixed terrestrial or satellite systems.
Comtech EF Data, Vipersat Products Page 10 of 87
ROSS MN/13070
1.4 Configuration Files
There are two system configuration files used by ROSS:
ROSS Configuration Files – A factory default
file holds the parameter values of the ROSS unit, which include parameters such as unit IP
address, ACU address, Modem address, VMS Multicast address and Network Identifier.
The default configure file only sets the factory unit IP address (192.168.254.3/24) leaving
all other parameters un-initialized, zero. Upon initial configuration the active configuration
file is generated and used during normal operations. If the restore factory defaults is
executed the active file is removed and regenerated with default configuration.
Note the password is stored directly to the system account utility (default “C
is only configurable through the console Telnet/Serial interface. If the password is lost or
unknown, the password can be restored through the local serial console interface which
does not require a login user name or password. Also factory resetting will restore the
password to default.
configuration file and an active configuration
omtech”) and
1.5 Database Files
There are four database files used by the ROSS:
Service Areas (SA) File – This is the primary database that provides critical information
about each satellite with which the local remote will communicate, such as the satellite
orbital position, TX polarization, frequency, bandwidth and identifiable description. These
set of parameters are sent to the ACU upon detected handoff points. The service area is
directly associated to service boundary and modem configuration files, which in
combination construct the communication area.
Shoreline Database File – This file contains the coordinates that comprise the shoreline map.
The SOTM system ensures that satellite transmission is strictly coordinated within a
configurable shoreline threshold expressed in Kilometers. When it is necessary to override
the global shoreline threshold, an override value can be specified in a Coordinated Area.
Coordinated Areas Map (CAM) File – This global database file defines those areas that call
for special transmission requirements. These areas serve as overrides, either negative or
positive, for enabling/disabling the modem transmit function. See section describing the
Ross Configuration Editor for more information on editing coordinated areas.
Service Boundary (SB) File – This file defines the geometry of a service coverage area
within the satellite footprint for the remote. Typically, multiple service boundary files are
stored on the ROSS, each corresponding to either a specific satellite or central hub with a
common satellite coverage area. Handoffs occur between service areas when the boundary
of the current service area is crossed.
Modem Configuration File – This file contains all configuration parame ters for the CDM-
570/570L & SLM-5650A base modem and IP Network Processor card. Typically, multiple
modem configuration files are stored on the ROSS, each corresponding to only one service
area location.
Comtech EF Data, Vipersat Products Page 11 of 87
ROSS MN/13070
1.6 Features
The ROSS integrates storage capacity, location processing control with flexible interfaces in a
small hardware unit that is co-located with the mobile remote satellite station equipment (below
decks) with connections to the Comtech Vipersat modem (e.g., CDM-570L or SLM-5650A) and
the ACU.
1.7 ROSS Client Interface
The ROSS client interface is accessed using either remotely (Telnet) or locally using Serial
connections. The RS-232 serial connection is always running the ROSS client application and
requires no login account. This is the maintenance and operations console interface.
1.8 Storage Capacity
The ROSS offers generous non-volatile storage capacity that typically is not available in the
satellite modems. This capacity is used to store the large satellite foot print maps (approximately
1500), shoreline contour vector maps, exclusion areas, RF data, multiple modem configurations,
and other administrative information.
1.9 Processing Power
The ROSS provides its own CPU and software to implement the satellite roaming features,
constantly monitoring vessel position data, satellite signal, and management status in order to
determine if a satellite handoff is required. The ROSS CPU relieves the satellite modem from
having to perform the complex handoff task, thus eliminating any performance impact on the
modem.
Comtech EF Data, Vipersat Products Page 12 of 87
ROSS MN/13070
1.10 Flexible Interface Platform
The ROSS offers a flexible hardware platform with standard interfaces, such as
10/100/1000BaseT, RS-232, and USB. These interfaces facilitate integration with multiple
vendor equipment, such as antenna controllers, for mobility services.
1.11 Event Log
The ROSS provides a system event log. The event log is a circular file capable of storing up to
511 events that may occur in the normal course of operation. Each event is identified with an
event type/category and time stamp, which is viewable and retrievable through the client or
ROSS Configuration Editor application. This file can be downloaded either locally or over the
air at any desirable intervals. The client user interface also provides a clear button to delete all
events refreshing the log file to known state.
1.12 Tracking Log
The ROSS provides a tracking log file to comply with FCC part 25.221(c), as the ROSS unit
must keep a log of vessel position and transmission parameters. The Tracking log is also a
circular file capable of storing up to 32766 entries or 455 days before overwrites take place. Each
entry is timed at 20 minute interval taking a timed/date snapshot of the vessels current location,
frequency, transmit status, data rates and modulations… It is expected that network administrator
will bulk download the tracking log file on scheduled intervals as not to lose any recorded
history. The ROSS Configuration Editor application provides a user interface to download the
reformatted tracking log as a coma delimited text file. Additionally a small simple command line
utility is available to automatically schedule file downloads assuming the vessel is in
communications with the central management hub facility.
1.13 ROSS Specifications
The ROSS is a network appliance server designed for rack mounting as a headless device (no
monitor, keyboard, or mouse). Utilizing a flash drive rather than a hard drive provides inherent
reliability. The following provides a list of system specifications that makeup the ROSS
hardware unit.
Server Components:
• CPU – Intel Celeron, 2.6 GHz, 1x 100mm blower fan
• Operating System – Linux 2.6.16.2 (Light Weight Kernel)
• RAM – 512 MB
• Flash Drive – 1 GB Disk-On-Module (DOM)
Front Chassis View
Comtech EF Data, Vipersat Products Page 13 of 87
ROSS MN/13070
Front Panel:
Buttons
• Power On/Off button
• System Reset button
LED Indicator Lamps:
• Power LED
• Hard drive activity LED
• 2x Network activity LEDs
• System Overheat LED
LCD Keypad Interface:
• 16x2 illuminated LCD display
• Four navigation keys (up, down, left, right)
• Cancel Key
• Select/Enter Key
Rear Chassis View
Rear Panel Ports:
• 2x Network Interface – Ethernet 10/100/1000 BaseT, NIC 1, left port only used
• 1x RS-232 – Local Console, User Interface
• 2x USB – Re-Imaging or Upgrades
Operating Environment (ROSS System):
• Operating Temperature, 32° to 104°F, (0 to 40°C)
• Non-Operating Temperature, -40° to 158°F, (-40 to +70°C)
• Operating Humidity Range, 8 to 90% non-condensing
Power Supply:
• AC Voltage, 100 – 240V, 60 - 50Hz, 5Amp
Dimensions:
• 1U Rack Mount
• Height 1.7” (43mm), Width 16.8” (427mm), Depth 14.0” (356mm)
• Gross Weight 14lbs (6.4kg)
Comtech EF Data, Vipersat Products Page 14 of 87
ROSS MN/13070
2 Installation Overview
This section provides the steps necessary to install the ROSS unit as part of the remote terminal
equipment in a Vipersat SOTM network. Any additional noncompliant third party equipment is
not described in this document for clarity.
2.1 Installation Requirements
The document assumes that the ACU and all its supporting equipment have been installed and
configured.
Hardware:
• ROSS Unit
• CDM-570L or SLM-5650A Satellite Modem & Router
• Installed ACU (including all below & above deck equipment)
Software:
• ROSS Configuration Editor, v1.3.0.921
• SetIP LAN Configuration Utility, v1.0
• VLoad 3.5.39 or later
• Putty v0.60
• ACU configuration application (depends on ACU vendor)
Documentation:
• ROSS User Guide, MN/13070, r4
• CDM-570/570L Installation and Operation Manual, MN/22125
• SLM-5650A User Guide, MN-0000035
• ACU Installation and Operation Manual, see vendor’s for part numbers
2.2 Unpacking and Inspection
Inspect the shipping container for any evidence of damage. If any damage is found, notify the
carrier in case a claim may have to be filed. This will only be necessary should the contents also
be found to be damaged.
Unpack the equipment from the container. Retain all shipping materials for future use, such as
for reshipment or RMA service. Visually inspect the equipment for any possible damage
incurred during shipment.
Check the equipment against the packing list to ensure that the shipment is complete. Should any
items be found to be either missing or damaged, contact customer support to report and record
before proceeding forward.
Comtech EF Data, Vipersat Products Page 15 of 87
ROSS MN/13070
2.3 Installing the ROSS Unit
The ROSS is below-deck electronic equipment designed to mount flush in a standard 19-inch
equipment rack. Ensure that there is adequate clearance for ventilation, particularly on the top of
the unit. In rack systems where there is high heat dissipation, forced air-cooling must be
provided by top or bottom mounted fans or blowers. Under no circumstance should the highest
internal rack temperature be allowed to exceed 34ºC (95ºF).
Using a medium Phillips screwdriver, mount the ROSS in the designated rack space with four
rack screws. Always hand-tighten or use a low torque power driver to secure the front panel to
the rack rails. Note this is commercial grade manufactured equipment and it is recommended
that input AC power conditioning (online UPS) is provided.
2.4 ROSS, Modem, and ACU Connectivity
As shown in figure 1, the ROSS unit, MODEM (CDM-570L is shown in this example), and
ACU require several connections for data and signals. The installation and configuration of
the ACU hardware is beyond the scope of this document. Refer to the ACU vendor’s
documentation for more detailed information regarding ACU installation.
2.4.1 Ethernet LAN Connections
ROSS and the MODEM (CDM-570L shown in figure 1) communicate via IP over Ethernet LAN.
This is illustrated in figure 1, where the ROSS and MODEM are connected to an Ethernet switch.
The ACU must supports IP over Ethernet and ROSS supports IP for selected ACU, the ACU
should also be connected to the LAN. Any host equipment, such as PCs, IP phones, should also
be connected to the LAN.
2.4.2 Modem to ACU/Antenna
The Tx input and Rx output IF signals from the modem need to be wired to above-deck antenna
equipment such as LNB and BUC. In some cases, the Tx and Rx IF lines require connection to
the ACU sub-panel interface. The ACU installation manual should be referenced for specific
vendor information.
2.4.3 Modem Tx Mute and Rx Lock Signal
A majority of commercial ACUs use the Rx Carrier Lock as part of the closed feedback system
in the satellite acquisition mechanism. In other words, the ACU will aim its antenna until the
modem locks onto its configured carrier. It is also extremely important to correctly connect the
modem Transmit carrier muting signal from the modem to the ACU. This hardware control line
provides the overriding control to mute the transmit carrier over any other software logic. Tx and
Rx controls are shown in Figure 1 and identified “Antenna HW CNTL”. Consult the CDM
modem manual and ACU installation instructions provided by the ACU vendor for detailed
instructions.
Comtech EF Data, Vipersat Products Page 16 of 87
ROSS MN/13070
2.5 Quick Start Configuration Checklist
In order to provision and configure ROSS, the check list is provided. The checklist assumes that
all the ACU hardware and wiring has been properly installed and configured.
Step Description
1 Build Service Area Information
2 Orbital Position,
Tx Frequency
Tx Polarization
Bandwidth
3 Create Service Bounds (polygonal areas). A geo-mapping application may be used
to layout the polygon and its coordinate points saved to a KML (Keyhole Markup
Language) file.
4 Create Coordinated Areas (polygonal areas). Coordinated Areas are optional.
5 Configure the CDM-570L or SLM-5650A modems for satellite service connectivity.
Once connectivity is established, take a snapshot of the modem configuration file
(.txt) using VLOAD. This .txt file will later be imported into each Service Area
entry. Create a .txt file for every satellite the modem will be switched to.
6 Follow the instructions section 6.1. Open a new ROSS configuration file and create
the Service Areas with the information previously collected.
7 Save the configuration file. This will be uploaded to ROSS.
8 Upload configuration file using ROSS default IP address.
9 Using Putty to access console interface or front panel LCD keypad, configure the
appropriate IP address, subnet, and gateway for the ROSS unit. Test ROSS IP
connectivity by pinging it from another host on the LAN, or logging into the ROSS
client interface.
10 If not done yet, use the RCE to upload the configuration file containing the Service
Areas. Verify that the Services Area was uploaded successfully by browsing the
Service Areas from the client interface or keypad interface.
11 Configure the ACU type and configuration fields.
12 Test ACU status by inspect the ACU poll status from Operations menu.
13 Verify ACU connectivity by examining the vessel position returned by ACU
14 Configure the IP address of the CDM-570L modem that ROSS is controlling.
15 Verify Modem connectivity by examining the modem poll status in operations
menu.
16 Configure Default Shoreline value in Operations menu.
17 Test Manual Satellite Handoffs by using Manual Handoff command from ROSS
client interface or front panel LCD interface.
18 Save the current ROSS configuration into the Active flash memory.
19 Reset ROSS and verify correct functionality.
Comtech EF Data, Vipersat Products Page 17 of 87
ROSS MN/13070
2.6 ROSS System Overview
The ROSS server operates as a mediation device between the Comtech Satellite Modems and
Antenna Control Units (ACU) subsystem. Its primary role is to poll Global Positioning Satellite
coordinates (GPS) information from the ACU, determine the current location and push the
appropriate command/configuration files updating communication parameters. The ROSS unit
communicates to the modem and ACU on a network LAN interface connection using proprietary
IP protocols. Each unit’s IP address is programmed into ROSS starting a poll process which
gathers location, status and current configurations. As each units respond to the queried
messages the ROSS compares the received information to set database files making decisions to
mute carrier, change service area or continue to operate without interruption within the current
service area.
Service Areas are fundamental to the overall operation of ROSS as they contain control
information which is associated to three separate database/configuration files. Each service area
is configured with ACU set controls and linked to a Modem Parameter file, which are Service
Bound together through geographical operational fencing. The third element is the Coordination
Area Maps which are shared by all service areas. The overall fencing (binding) is geographical
longitude/latitude coordinates combined to create a closed polygon forming an operational area
or handoff boundary.
Through the polling of GPS coordinates from the ACU, ROSS processes hundreds of checks per
minute against the Service Area, Shoreline database, and Coordinated Areas. If anyone or all
represent a HIT, the ROSS initiates the proper action.
The ROSS server has four states that are processed during the course of initialization and
operation:
• Startup – Loading configuration and acquiring modem, ACU communications
• Normal – Normal operation mode assumes VMS connectivity in a service area
• Handoff – Detected transition to next service area
• Parked – No service area coverage configured
Startup
Startup is the first state the ROSS enters when the unit is powered or rebooted. During the startup
phase, the unit boots up the base OS, after system initialization the ROSS server is automatically
started by a watchdog script. This script is called from the OS and continually monitors the
ROSS running process. If the watchdog script fails process check, the ROSS process will be kick
started within 10 seconds. Boot time for ROSS server is approximately ~5 seconds, as a
complete cold start of the unit is ~25 seconds.
As the ROSS application is started the process loads configuration files, initializes internal
modules, and establishes communication with the modem and ACU. ROSS stays in this mode
until all devices are put into a known state by checking current location. If the current location
matches set service ID in the modem, no change is made dropping into normal operations.
Comtech EF Data, Vipersat Products Page 18 of 87
ROSS MN/13070
If the check returns a difference and new service area is available the ROSS will initiate a
handoff sending configuration files to modem and ACU for processing of the next operational
location.
Note both modem and ACU must have valid status polls or ROSS will not initiate any service
area configurations.
Normal
This state is the “all systems are go” operating mode where connectivity to the hub is expected
because the vessel location matches a service area in the service boundary. Satellite Location
Identification Protocol (SLIP) messages and other management data is exchanged with hub
VMS, such as ROSS registration commands, modem status, and command messages. Tracking
Log entries are recorded in normal mode, and all other modes.
The transmission can be inhibited in Normal mode by:
a. ACU block signal is sent to the modem due to hazardous threshold (blockage limits).
b. Coordinated Area designates as no transmit zone
c. Vessel is inside a uncoordinated baseline (200km or set value, 0 = none, shoreline hit)
d. Carrier Inhibit, loss of hub carrier transmission, (receive data lock)
e. Modem or ACU no poll response timeout failure (~15sec) – TEK message initiated
f. Additionally the modem will mute transmit in the absences of TEK messages
Comtech EF Data, Vipersat Products Page 19 of 87
ROSS MN/13070
Satellite Handoff Process
If the handoff state detects a transition point (new service area), the handoff function initiates the
following processes:
1. Disable Transmit – TEK message disabling modulator output power
2. Retrieve the new Service Area information
3. Pushes a new Modem Configuration Parameter file into modem
4. Send the command to ACU to point antenna to new satellite (Orbital Position,
Frequency & Bandwidth)
5. The modem will actively update all new parameters issuing a firm reset (quick
update)
6. Enable Transmit – TEK message enabling modulator output power
7. Enter Normal operating state waiting for modem to receive transmit grant message
from the hub
Note during this process the ROSS may send a TEK message enabling carrier before the antenna
has completed its tracking. In this state the ROSS relies on the hardwired transmit mute control
line from the antenna controller to the modem.
3.1 ROSS Messages & Data
3.1.1 Transmit Enable Keep-alive (TEK) Message
This TEK message is implemented as a watchdog process in the modem and is monitored for
transmit control change or absence status. If the modem detects the (absence) loss of 3 messages
(~15sec), the modem will fail poll reception timing out disabling modulator transmit. The ROSS
continuously sends TEK messages on 5 second intervals to the modem to reset the transmit
enable watchdog countdown timer. If the watchdog is not reset with a TEK message within the
specified interval, the modem will mute its transmitter until a TEK is received again.
3.1.2 ACU Commands
ACU commands typically use a proprietary message format. These commands are sent to the
ACU to reposition the antenna to new coordinates. ROSS sends Orbital Position, Frequency and
bandwidth to antenna control commanding it to resume tracking to new satellite location. The
ACU processes the orbital position into Azimuth and Elevation units calculated through the
current GPS coordinates. The frequency and bandwidth focuses the signal track algorithms on a
specific carrier typically the new service areas hub TDM carrier allowing the antenna signal
processor to peak on identified carrier. The modem demodulator lock signal is offered up to the
ACU through hardwire or soft-decision for final peak signal track and confirmation of satellite.
Comtech EF Data, Vipersat Products Page 20 of 87
ROSS MN/13070
3.1.3 Modem Configuration File
This is a standard modem parameter file that is currently used by all Vipersat enabled Comtech
modems, such as the CDM-570L or SLM-5650A. It is a proprietary formatted text file. This file
contains configuration parameters that allow the modem to establish communications with a
specific satellite. In other words, each modem configuration file is created for a specific satellite
and hub ground station and contains all possible parameters values for the base modem and IP
router interface card. The Service Area database associates this modem configuration file with a
specific satellite and hub network. The file transfer uses the Comtech proprietary Streamload
protocol for ROSS to push a new configuration updates. Upon complete reception the modem
stores and processes the new changes issuing a firm reset to initialize the new changes. The new
updates are accomplished without a reboot minimizing the transitioning time.
Critical parameter categories include:
• RF properties such Tx and Rx home state frequencies, FEC rate, modulation, data rates,
and baseline transmit power.
• STDMA burst map configuration
• Route table configured for specific network topology if required
• QoS rules for setting unique priorities and bandwidth
Modem Parameters Excluded by ROSS:
• IP Address – Modem IP communication address remains static
• Network Node ID – Defines unique flow ID assigned by controlling VMS
Modem Parameters Replaced by ROSS:
• Satellite ID – derived by ROSS per service area
Exclusions and Replacements are necessary in providing seamless association between user
unknown values and possible unwanted overwrites. All the configurations for the modem are
stored in a single directory and are associated to its service area by sequential numbered file
naming convention.
Comtech EF Data, Vipersat Products Page 21 of 87
ROSS MN/13070
3.2 Service Area Description
The Service Area (SA) is a container including all of the critical elements necessary to calculate
coordinated areas, determine operational or non-operational areas pushing updates and controls
to associated transmission equipment. The perimeter control within the SA is the Service Bounds
(SB) which is a multipoint polygon fence setting the satellite transmission beam area borders.
There are also Coordinated Area Maps (CAM) that if required can set transmit carrier zones
whereby the vessels transmit carrier is controlled to either enable or disable within these
boundaries. ROSS can store hundreds of these Service Areas that define the operating parameters
for each satellite and/or ground based equipment that the vessel requires for normal operation
within any given geographical location.
Each unique SA is created or maintained locally/remotely using the ROSS Configuration Editor
(RCE). The editor consolidates database elements into a single structure which is downloaded or
uploaded to the ROSS. The ROSS incorporates a file manger that labels each file element
through logical renaming appending each file with a sequential number grouping them all into a
SA. Example SA, the ACU command information sets the base reference with modem
configuration file(s), SB(s) which are then grouped together with a unique number. The SA
number is irrelevant to the user as it is assigned at the time of reception during uploads to ROSS.
The number assignment is only relevant to ROSS as container grouped database information.
The SA example figure 2 depicts the structure of two separate SA binding list elements together
into a distinct area. This grouping is shown with only one SB per SA and two shared CAM’s,
however multiple SB’s can be linked into a single SA. Configuring SA’s is described in much
more detail in the Configuration section of this manual.
Figure 2: Service Area Example
Comtech EF Data, Vipersat Products Page 22 of 87
ROSS MN/13070
3.3 Modem Interaction with ROSS
The Vessel equipment must bond together blending a mix of independent processes forming a
partnership of exchanged information and controls. This unique partnership builds a cohesive
system even though all run independent process. Each component has startup, normal and idle
modes of operation but still mesh together in timed acknowledged sequences.
The follow functional lists only describe the two Comtech units omitting the antenna control
system for lack of function detail. Each list is a step-by-step description on the basic processes
and how they interact forming the system functionality. This section describes what different
type of sequencing happens between cold and hot initializations.
3.3.1 Modem Initialization
The modem plays a key role in the communications chain as it must perform quickly through the
active transformation of pushed configurations file from ROSS. The modem has two different
modes of processing configurations files, one at boot time the other at run time. Each process
deferrers in sequence based on the initialization execution point.
Previously described the ROSS unit also has two types of execution points requiring long and
short initializations, however during the operational mode the ROSS unit pushes configuration
files to the modem which must be timed correctly for proper execution. During cold boot
(applied input power) all system components will typically complete initialization at different
times presenting a possible problem if the mediator (ROSS) pushed information too soon. ROSS
must wait for valid responses before sending controls or configurations prematurely resulting in
lost information. This validation before send eliminates repetitive processing streamlining the
initialization sequence.
Modem Cold Boot:
1. The Comtech modem stores two boot images, one is for the base modem processes and
the other is the IP Interface module (router). On power up both are loaded simultaneously
with base modem monitoring the boot state of the IP interface. The IP Interface module
boots the OS reading the FLASH parameter configuration file while the base modem
reads its last state values from NVRAM.
2. The Base modem first loads last state (stored) parameters which could have TX enabled,
however the transmit enable is held muted through a hardware control line from the IP
interface module until it completes its boot check before releasing. This prevents
premature transmission until the IP Interface has booted and finished rendering
configured states.
3. Once the IP Interface has finished booting it reads a stored parameter file from FLASH
sending two base modem configuration index scripts, Modem Group Configuration
(MGC) and Outdoor Group Configuration (OGC). These two loads contain the complete
IDU/ODU configuration sets.
4. Next the IP Interface loads Home State (subset of transmission values) parameters from
FLASH releasing the hardware mute signal.
Comtech EF Data, Vipersat Products Page 23 of 87
ROSS MN/13070
5. Last the modem looks for demodulator lock following TEK enable and grant to burst
transmit from hub STDMA controller.
6. During the modem boot cycle ROSS is in the background trying to query the modem for
last set Satellite ID (service area). Once ROSS receives a valid response containing the
SAT_ID_NUMBER, a compare is applied to current location determining if a
configuration update is required.
7. If polled SAT_ID_NUMBER matches current location no change is necessary. If
different a new configuration file is push updating all communications parameters.
8. The TEK message now commences setting the transmit flag to enable mode.
9. The modem is now at home state waiting for TEK enable and hub grant to transmit
message.
10. During this time ROSS will send commands to the ACU updating the new pointing
location.
11. Special power controls can be applied to assure connectivity to the hub station during the
burst entry cycle. See STDMA Power Hunt.
12. After TX enable and burst grant the remote modem sends a request for registration to the
managing VMS. It must receive acknowledgment before transitioning through IP routing
table changes and dynamic switching to dSCPC mode. During this process all customer
data traffic is blocked and only allowing management traffic to pass. This prevents
possible customer switching requests from being lost during registration processing.
Note during the modem query the ROSS server is also polling the ACU for location status.
If the ACU has failed to respond during this initial sequence, ROSS will enter Parked
mode waiting for valid responses before changing states. Also during this process the
antennas tracking maybe inhibiting transmit until signal lock is established.
3.3.2 Modem Hot Initialization
All the same valid polling rules apply during hot initialization processing and are assumed to be
valid in the next sequencing.
1. During normal mode the modem operates under standard Vipersat control with only one
difference, the ROSS governs the transmit state. All standard dynamic switching, power
controls and communication recoveries apply.
2. If the vessel transitions into a new SA the ROSS server process the handoff sequence as
describe previously. However the modem is now in an operational state with all current
set value enabled.
3. As the ROSS unit processes handoff mode it pushes the new configuration file to the
modem via a UDP Steamload protocol.
4. The modem receives the file and checks the integrity before copying to FLASH and
processing.
5. The processing of the parameter file is accomplished on the fly inhibiting transmit before
execution. As the file parameters are processed through the internal menu engine each
value is modified/copied over. Once complete the Streamload process performs a firm
boot (execution time is in the ms) initializing all new values.
Comtech EF Data, Vipersat Products Page 24 of 87
ROSS MN/13070
6. The modem is now at home state waiting for TEK enable and hub grant to transmit
message.
7. Special power controls can be applied to assure connectivity to the hub station during the
burst entry cycle. See STDMA Power Hunt.
8. After TX enable and hub grant to transmit the modem sends a request for registration to
the managing VMS. It must receive acknowledgment before transitioning through IP
routing table changes and dynamic switching to dSCPC mode. During this process all
customer data traffic is blocked and only allowing management traffic to pass. This
prevents possible customer switching requests from being dropped during registration
processing.
Note during the modem query the ROSS server is also polling the ACU for location and
status. If the ACU has failed to respond during this initial sequence, ROSS will enter
Parked mode waiting for valid responses before changing states. Also during this process
the ACU maybe inhibiting transmit until signal lock is established.
3.3.3 Transmit Power Controls
STDMA Power Hunt
Summary
The STDMA default power value is a possible problem as remotes with incorrect or impaired
transmissions cannot close their return links during service area entry mode. By adding a power
hunt algorithm with limits will provide burst link closure reliability.
The STDMA Power Hunt (SPH) function has a maximum power limit of up to 9dB in 3dB
increments greater than initial default, base value. This modulator power value cycles during
burst transmission increasing or decreasing power until it receives a reply from its managing
STDMA controller. This is accomplished through burst map acquisition acknowledgement flag.
Throughout the process the remote will remain at base or modified set power value until
commanded otherwise or manual operator intervention. Once in SCPC mode and DPC enabled,
the value is over written by DPC and servos to targeted set Eb/No value. Any revert from SCPC
to STDMA will reuse last set DPC value as power delta offset over default set-point. Reboot or
forced revert will cause the unit to clear all temporary set power values.
Implementation
The hub and remote units both provide a role in SPH which allows the remote modulator to
increase its base configuration (Home State) power setting to a maximum of 9dB from initial setpoint if link reception is incorrect or impaired. The hub STDMA burst map contains a flag which
is used separately by each remote in the group. This flag indicates if either their burst ACK
message was missed or received at the hub. When the hub STDMA controller receives a valid
burst ACK from the remote it sets the flag for the corresponding remote in the next burst map
indicating completed transmission.
There are two counters initialized in the remote, one that reads missed ACK’s and the other is
received ACK’s.
Comtech EF Data, Vipersat Products Page 25 of 87
ROSS MN/13070
During burst map reception the remote reads the ACK flag and either increments or resets
missed ACK counter. The missed counter is initialized and invoked when the first or next
message received has the flag set to zero ‘0’. It then starts a 10 missed count before incrementing
the power value by 3dB step. The second counter is received ACK’s which has a flag set to
‘1’and the count must receive 5 consecutive good ACK’s before resetting missed ACK counter.
Once reset the power hunt stops and the value is retained and put into a variable called DPC
Delta.
There are three separate stored power components, Baseline Power, DPC Delta, and SOTM
Offset. Note SOTM Offset is a reserved variable for future use.
Baseline Power is either Home State default power value which is applied at initialization, CLI
force home state or VMS force reverts or the last value received from VMS. The baseline power
value is based on link budget calculations which may be subject to error in SOTM environments.
DPC Delta is a shared value between SPH and DPC. SPH applies its offsets during STDMA
mode only, while DPC adjustments are made in SCPC only due to environmental conditions,
unknown budget calculations (ocean coverage errors) and also traveling through power variances
within a satellite beam. These two power offsets share this variable with only one exception DPC
can overwrite the SPH value.
Operational Conditions
When enabling SPH it is only available in STDMA. Switching to SCPC disables this
function allowing DPC to modify independently. However, the SPH value remains stored in
DPC delta variable unless over written.
Once set the delta value remains effective throughout switching states, SCPC or STDMA
unless overwritten by DPC.
The current SPH gets stored in the DPC delta variable for use in SCPC mode and STDMA
during reverts (Home State). It is cleared during a force revert, either from VMS or CLI.
There are two counters, missed ACK and other is received ACK’s.
SPH power is an incremental 3dB step value (added or subtracted) up to 9dB after 10 cycles
(burst maps) of missed ACK’s.
The missed ACK counter is cleared after receipt of 5 consecutive received ACK’s.
Boot & Initialization: (burst transmission succeed)
1. The default Home State power value is applied to the base modem modulator on boot-up.
2. After transmission grant, remote bursts to corresponding STDMA controller with ACK +
Registration request message.
3. If hub reception is NOT impaired and transmission acquisition is completed the burst
controller sets the missed ACK flag to ‘1’ indicating to corresponding remote good burst.
4. No power adjustment is required. “SPH value remains at zero value”
5. VMS responds to registration request sending registration configuration to remote.
Comtech EF Data, Vipersat Products Page 26 of 87
ROSS MN/13070
Boot & Initialization: (burst transmission failure)
1. The default Home State power value is applied to the base modem modulator on boot-up.
2. After transmission grant, remote bursts to corresponding STDMA controller with ACK +
Registration request message.
3. If hub reception was impaired and transmission acquisition failed the burst controller sets
the missed ACK flag to ‘0’ indicating to corresponding remote failed burst acquisition.
4. Power adjustment is required.
5. Remote missed ACK counter is initialized waiting next burst map and flag set value.
6. If count reaches 10 (burst maps) missed ACK’s the default power is increased by 3dB.
7. If next burst map indicates received ACK, the missed ACK counter holds count until 5
consecutive receive counts.
8. After 5 consecutive receive counts the missed counter is reset and the power value is
stored in DPC Delta variable.
9. VMS responds to registration request sending registration configuration.
10. Remote may now switch to SCPC mode.
Note all stated power process assumes receive transmission from the hub TDM is good.
4.1 ROSS Client Interface
The ROSS client interface is accessed using either Telnet or Serial connections through an open
source application, Putty. The RS-232 serial connection is always running the ROSS client
application and requires no login account. This serial interface is used for local maintenance
configuration management such as resetting login passwords or unit IP address.
The ROSS client interface is accessed by Putty, an open source Windows application. Putty is a
Win32 Telnet client configurable for either serial or LAN IP communications.
Comtech EF Data, Vipersat Products Page 27 of 87
Loading...