RevB NGC IDU - Ad Tech Manual - RevB - 11
RevB NGC IDU - Ad Tech Manual - RevB - 11
RevB NGC IDU - Ad Tech Manual - RevB - 11
Antenna Controller
Unit
Advanced Technical Manual
Manual# 7581691 – Revision B
ASC Signal Corporation reserves the right to change details in this publication without notice.
Trademark Notices
Any and all products and companies named herein are the trademarks of their respective creators and/or
owners.
Some of this software is licensed by the GNU General Public License (GPL), which requires that all
modifications or additions to the source code be kept public, and that the licensee continues to make the
source code covered public. None of this source code has been modified for use in this product. If you are a
user of this product who desires a copy of any source code covered by the GPL, contact our technical support
and we will provide this free of charge through an agreeable medium. We expect all source code archives will
be posted to public FTP servers. At the time of this writing the exact address is not known. Be advised that this
is a large archive. We may recommend you obtain it from the source we obtained it from, as the source may be
using more recent versions. We will always supply it ourselves if you prefer.
Some of this software is licensed by the GNU Lesser General Public License (LGPL), which requires that
modifications be kept public but does not require proprietary source code linked to LGPL'ed libraries be made
public. None of this code has been modified for use in this product. All of the required source code will be
conveyed along with the code covered by the GPL above.
Some of this software is licensed by variations of the Berkeley Software Distribution (BSD) license, which do
not require us to pass on source code. Some of this software has been modified for use in this product.
However, in the spirit of open source, the original code will be supplied in the same manner as the code
covered by the GPL on request.
Please be advised that you will incur the same responsibilities we have incurred if you choose to redistribute
any or all of the source codes obtained through this method. Please read the included license documents
carefully.
If you have any questions about our interpretation of our obligations under OSS licenses, do not hesitate to
contact us. Our intent is to comply fully with all licensing obligations.
LIST OF TABLES
Table 1.1: NGC-ODUs compatible with NGC-IDU 13
Table 1.2: NGC-IDU Optional Hardware Elements 14
Table 1.3: NGC-IDU Optional Software Elements 14
Table 1.4: Software Elements 14
Table 1.5: System Performance Specs 14
Table 1.6: Front Panel LEDs 16
Table 1.7: NGC Back Panel Connectors 18
Table 1.8: SCP LEDs 21
Table 1.9: SCP Main Board Jacks & Plugs 21
Table 1.10: SCP Modem Jacks & Plugs 21
Table 1.11: SCP Main Board Jumpers 21
Table 1.12: SCP Modem Jumpers 21
Table 1.13: TPU LEDs 22
Table 1.14: TPU Jacks & Plugs 22
Table 1.15: TPU Jumpers 22
Table 1.16: RPI-6 LEDs 24
Table 1.17: RPI-6 Jacks & Plugs 24
Table 1.18: RPI-6 Switches 25
Table 1.19: RPI-6 Jumpers 25
Table 1.20: RPI-6 Test Points 25
Table 1.21: KBCPU-1 LEDs 26
Table 1.22: KBCPU-1 Jacks & Plugs 27
Table 1.23: KBCPU-1 Switches 27
Table 1.24: KBCPU-1 Jumpers 27
Table 1.25: KBCPU-1 Test Points 27
Table 1.26: Keyboard functions 28
Table 1.27: KB-3 LEDs 28
Table 1.28: Spectrum Analyzer Jacks and Plugs 29
Table 1.29: J11 Pin-Out (analog beacon receiver interface) 33
Table 1.30: J12 Pin-out (receiver serial interface) 34
Table 1.31: Supported beacon receiver Models 34
Table 1.32: J3 RJ-45 Pin-Out 35
NOTICE
THE INSTALLATION, MAINTENANCE OR REMOVAL OF AN ANTENNA REQUIRES QUALIFIED,
EXPERIENCED PERSONNEL.
ASC SIGNAL CORP. INSTALLATION INSTRUCTIONS HAVE BEEN WRITTEN AND ILLUSTRATED FOR SUCH
PERSONNEL. ANTENNA SYSTEMS SHOULD BE INSPECTED AT LEAST ONCE A YEAR BY QUALIFIED
PERSONNEL TO VERIFY PROPER INSTALLATION, MAINTENANCE AND CONDITION OF THE EQUIPMENT.
ASC SIGNAL CORP DISCLAIMS ANY LIABILITY OR RESPONSIBILITY FOR THE RESULT OF IMPROPER OR
UNSAFE INSTALLATION OR MAINTENANCE PRACTICES.
I.III Miscellaneous Notices
Proprietary Information
The technical data contained herein is proprietary to ASC Signal Corporation. It is intended for use in the installation,
operation, and maintenance of ASC Signal equipment. This data shall not be disclosed or duplicated, in whole or in part,
without the expressed written consent of ASC Signal Corporation.
Installation Notice
Installation, maintenance, or removal of the hardware described in this manual requires qualified and experienced
personnel. ASC Signal installation instructions are written for such personnel. Qualified personnel MUST perform
proper installation and maintenance of the equipment, and MUST verify the condition of the equipment at initial
installation and periodically thereafter.
NOTE: ASC Signal is NOT liable or responsible for results of improper or unsafe installation and maintenance practices.
All designs, specifications, and availability of products are subject to change without notice.
IMPORTANT: What to Know When You See OPTION:
Any time you see “OPTION:” this means that the information following it is related to an optional element (in either
hardware or software) that may or may not apply to the arrangement of your particular NGC Unit. Please note that if you
see an option that you do not have but would like to purchase, you should contact ASC Signal.
I.IV Warning Symbols
Various components of this System may display safety symbols. Be sure to use extreme caution when operating
components with any of the following safety symbols:
Certains éléments du système montreront peut-être des symboles de sécurité. Faites très attention à faire marcher tous
les éléments qui tiennent les symboles de sécurité suivants:
OR WARNING! HAZARDOUS MOVING PARTS! KEEP FINGERS AND OTHER BODY PARTS AWAY!
AVERTISSEMENT! PIÈCES MOBILES DANGEREUSES! GARDEZ LES DOIGTS ET LES AUTRES PARTIES DU
CORPS HORS D’ATTEINTE!
WARNING! Statements identify conditions & practices that could result in injury or loss of life.
AVERTISSEMENT! Les rapports d’avertissement identifient les conditions ou les pratiques qui pourraient avoir comme
conséquence les dommages ou la perte de la vie.
KEEP AWAY FROM LIVE CIRCUITS: Personnel must observe all applicable safety regulations at all times. Ensure
power is disconnected or removed from the unit BEFORE replacing any components. Potential hazards may exist even
though the power control switch is in OFF position. Capacitors retain electrical charges. Always REMOVE POWER & use
test equipment to confirm a circuit is at ground potential BEFORE touching it. NEVER reach into or enter an enclosure to
service or adjust the equipment until the absence of power has been confirmed.
DO NOT SERVICE OR ADJUST ALONE: Under NO circumstances should ANY person reach into or enter the
enclosure for the purpose of servicing or adjusting the equipment except in the presence of someone who is capable
of rendering aid in case of an accident/emergency.
RESUSCITATION: Personnel working with or near high voltage should be familiar with resuscitation methods (CPR
and/or AED). CPR info may be obtained from medical personnel. For AED (Automated External Defibrillator) information,
contact supervisor or hosting administration for details on the availability and/or location of an AED unit at your worksite.
Figure 1-1: NGC-IDU FRONT VIEW Figure 1-2: NGC-IDU REAR VIEW
NOTE: normally, the chassis should NOT be opened as shown in the above figures.
1.1.1 Standard Features
All NGC-IDUs come with the following set of standard features:
• 800x480 WVGA-format 32,768-color touch screen
• Auxiliary keypad
• Optical (100baseFX) interface to the NGC-ODU
• Analog and serial beacon receiver interfaces
• TCP/IP over Ethernet (100BaseT) networking including SNMP, FTP, and NTP protocols
• USB jump drive support
• APC100 serial protocol emulation
• Status monitoring and logging
• External PC keyboard supported (not supplied)
When combined with certain NGC-ODUs, it adds the following standard features:
• Automatic stow and deploy of TriFold® antennas.
1.1.2 Options and Variations
The NGC-IDU is designed to create a complete system when combined with a wide variety of
configurations. It automatically configures itself to match ODU capabilities, including all installed options
[heaters, Pol drive kits, SRTs, etc.]. At the time of writing, the IDU supports the following ODUs.
Table 1.1: NGC-ODUs compatible with NGC-IDU
Part Number Description
NGC-ODU-208-3 208VAC, 3HP, Fixed
NGC-ODU-208-3D 208VAC, 3HP, Fixed, Dual Az (High Accuracy Encoders)
NGC-ODU-208-3-HA 208VAC, 3HP, Fixed, High Accuracy Encoders
NGC-ODU-208-5 208VAC, 5HP, Fixed
NGC-ODU-208-5-HA 208VAC, 5HP, Fixed, High Accuracy Encoders
NGC-ODU-208-LPP 208VAC, Low Profile Positioner, Dual Az
NGC-ODU-208-SPP 208VAC, Standard Profile Positioner
NGC-ODU-380-3 380VAC, 3HP, Fixed
NGC-ODU-380-3-HA 380VAC, 3HP, Fixed, High Accuracy Encoders
NGC-ODU-380-5 380VAC, 5HP, Fixed
NGC-ODU-380-5-HA 380VAC, 5HP, Fixed, High Accuracy Encoders
NGC-ODU-SRT 120/240VAC, SRT-only system, fixed
7581691_Rev B Page 13 of 179
The following optional hardware elements can be installed in or with the NGC-IDU. Optional software
associated with some of these elements is automatically activated by the NGC-IDU hardware.
The following software elements can be field activated by software license key as shown in the following
table:
Table 1.3: NGC-IDU Optional Software Elements
Option Code Feature Name Notes
NGC-101 Step Tracking (Standard)
NGC-102 SmarTrack® Orbital prediction algorithm
NGC-103 Predictive Track NORAD and Intelsat ephemeris
NGC-104 Full Track NGC-101 + NGC-102 + NGC-103
NGC-107 Enhanced Spec An Requires NGC-001 to be effective.
The software elements shown in the following table are automatically activated by the presence of specific
NGC-ODU hardware:
Table 1.4: Software Elements
Option Code/Part # Feature Name Notes
NGC-105 Acquisition Assist Activated by presence of AS-1 unit, mobile operational
configuration
7579403 Three-axis SRT carriage Motorized subreflector tracking carriage for 8.1m
antennas
7581065 Dual-axis SRT carriage Motorized subreflector tracking carriage for 3.5m
antennas
The NGC-IDU software system is common to all deliveries. Unlike some other antenna control systems,
customized software is not used. Therefore, the current release can always be updated on the NGC-IDU
and any optional feature will continue to work.
1.1.3 Overall NGC-IDU System Performance
11
3
4
5 10
2
6
7
8 9 12
1
Figure 1-3: NGC-IDU Front Panel
# Item Description
1 USB Jack Allows a limited number of peripheral devices to be connected to system. These include USB
keyboards and Windows-formatted USB drives (jump drives) which can be used for data
entry tasks without networking. There is also a USB jack on the back of the unit.
CAUTION: Some jump drives or other peripherals can interfere with the bootstrap of Linux
operating system. Do not leave jump drives or other peripheral devices attached when you are not
using them.
2 Touch-screen Allows interactive data entry and display of all controls to and information from the system.
Panel Unit (TPU) This TPU is the central user interface of the NGC-IDU.
3 Fault LED indicates current faults. If you touch it, screen jumps to Current Fault Summary
4 Standby Used to halt program movement quickly. It is a program halt (only program movement is
inhibited). LED is lit if system is halted
5 Signal Used to jump to Spectrum Analyzer function (if installed). LED lit if low signal fault present
6 Tracking Used to jump to tracking screen. LED indicates system is actively moving, seeking a new
peak by flashing, and indicates the system is actively tracking if constantly lit
7 GoTo Used to jump to satellite selection screen. LED flashes if antenna is in motion
8 LCL/Remote Used to toggle between Local (LCL) and Remote (REM) modes.
9 Jog Mode As the button text suggests, this button toggles the Jog mode
10 Jog Keys Allows jogging (if system is in correct mode), jump to Movement screen, and provides
backup to the touch-screen in the event that it becomes unresponsive
11 Keypad Allows alphanumeric entries as well as sign (+/-) and decimal (.) values
12 Power Button NGC-IDU Power ON/OFF
OPTION: one option is an EMERGENCY STOP button on left of front panel just above USB port. Emergency stop is an
inhibiter. Antenna will not move until it is cleared.
Figure 1-5: NGC Back Panel Connectors, Left Half, Expanded View
Figure 1-6: NGC Back Panel Connectors, Right Half, Expanded View
WARNING: The following sections show the internal components of the NGC-IDU. This information is provided for
use under guidance from ASC Signal service personnel only. Do not open IDU chassis unless instructed to do so by ASC
Signal service personnel. Opening the IDU chassis without proper authorization may result in a voided warranty. Also,
charges may apply to any subsequent repairs that are needed as a result of unauthorized opening of the IDU chassis.
With the chassis lid removed, the internal components of the NGC-IDU can be seen.
2
3
4 1
Figure 1-10: TS-7395 TPU CPU Card (picture may not be representative)
# Part Name
1 CN2 +12VDC power for TPU
2 n/a Backlight power to LCD display
3 J5 100BaseT Ethernet LAN connector (RJ-45)
4 J6 Dual USB header
5 CN34 XY touch-screen interface cable
6 DIO Diagnostic header, factory use only
7 CN4 LCD parallel display interface
Table 1.13: TPU LEDs
LED Color Name
D4 Red Power on fault LED 2, fades off with power up. Will turn back on
later
D5 Green Power on fault LED 1, turns on with power up, turns off
Table 1.14: TPU Jacks & Plugs
Part Function
CN2 5-28V Power In
CN34 XY touch-screen controller
CN4 LCD digital interface
J5 100BaseT Ethernet LAN connector (RJ-45)
J6 Dual USB connector
Table 1.15: TPU Jumpers
Part Function
JP1 Boot from SD card, not used in the NGC-IDU. Do not install
7581691_Rev B Page 22 of 179
1.7 NGC-IDU Real Panel Interface (RPI-6)
Rear Panel Interface (RPI-6) board provides all most external connections from NGC-IDU. RPI-6 contains
beacon receiver interface, internal network switch, power distribution circuits, & support functions for chassis
1.8.1 KBCPU-1
The keyboard CPU, when combined with the KB-3 module, makes up a USB keyboard assembly. To the
rest of the system, the USB keyboard is indistinguishable from an ordinary USB keyboard. Unlike the rest
of the system, however, this board is always powered on while the chassis is plugged in. This allows the
board to implement the soft power function.
The KBCPU-1 contains a microprocessor that implements the USB HID protocol, necessary circuits to
implement the capacitive touch sensors for up to 30 keys on the keyboard, and a piezoelectric speaker to
make sounds to signal key presses.
The KBCPU can also be started in a mode where it emulates a USB flash drive. This mode can be used to
change the firmware in the KBCPU by drag-and-drop using an ordinary PC.
Figure 1-12: Keyboard CPU (KBCPU-1)
# Part Name
1 J5 Electrode interface to the Keyboard
2 J2 Serial port
3 J1 USB port used to connect to TPU
4 J4 Power/Standby
5 J6 LED interface to the Keyboard
Figure 1-14: Built-in Spectrum Analyzer
# Part Name
1 N/A SMA jack for L-band input
2 N/A Network RJ-45
3 N/A Power jack
Table 1.28: Spectrum Analyzer Jacks and Plugs
Part Function
SMA jack L-band input from a cable connected to rear panel J15
USB jack USB interface, no used
DB9 Serial port, not used
RJ-45 Internal LAN connection to the RPI-6.
Power jack Accepts +14.6V power from the RPI-6 module
NOTE: The only LED on this part is the power indicator LED. There are no jumpers, test points, or other switches.
In the IDU, receiver is turned off unless current satellite in Working Satellite Table has a defined DVB carrier.
The DVB-S receiver electronics consists of two modules, a tuner module and a main (demodulator) module.
They are connected to each other using a Molex 98268-0155 Premo-Flex cable (ensure when ribbon cable is
installed that the contacts are on the correct side).
The following illustrations (Figures 1-15 & 1-16) show the components of the DVB-S receiver.
1.11.1 Rack Slides
Rack slides can be installed on the side of the unit for ease of mounting. Consult installation instructions.
1.11.2 ESTOP switch
The NGC-IDU with option NGC-006 has a front panel ESTOP switch. When this switch is depressed, the
NGC-IDU will stop the NGC-ODU from moving and refuse to accept any command that would move the
antenna.
Please note that this ESTOP is not a substitute for the outdoor ESTOP switches, which are electrically
interlocked. An NGC-IDU ESTOP will not prevent the handheld terminal from moving the antenna if it is
connected to the NGC-ODU.
1.11.3 External Keyboard (Customer-Supplied)
A standard PC keyboard can be plugged into the front panel to use for data entry. The NGC-IDU supports
most standard business USB keyboards with US layout. Support for non-US keyboards has not been
evaluated. ASC Signal cannot guarantee that any specific keyboard will work.
If this option is chosen, the Function Keys [F1 through F9] may be used to perform the following respective
functions:
F1 F2 F3 F4 F5 F6 F7 F8 F9
BLUE JOG FAULT STAND SIGNAL TRACKING GOTO LCL / SOFT
(jog) MODE BY (spec an) SAT REM POWER
SCREEN
1.11.4 External USB Jump Drive (Customer-Supplied)
External USB flash (jump) drives can be used for software update, configuration storage, data set update,
and other functions. The drive should be formatted as a conventional FAT32 volume. The NGC-IDU has
been tested with many name-brand USB flash drives from SanDisk, Lexar, and other manufacturers.
The IDU cannot format these drives. You must use a Windows PC or similar computer to perform any
necessary formatting.
NOTE: many times these drives are formatted at the factory and this format will normally work just fine.
Compatibility Note: Some USB jump drives use non-standard methods to implement proprietary security or other
features. These drives rely on the installation of specialized software device drivers so that Windows PCs can access
them. The IDU will not recognize or support these drives.
Security Note: IDU software is not based on Windows, MacOS, or other common desktop operating system. For that
reason, it should not be normally susceptible to viruses, such as Trojan horse programs, root kits, or other common
security threats. While it is theoretically possible to target any system with malware, the odds of a compatible threat being
developed and deployed for this system are unlikely.
The NGC-IDU may be connected to the receiver using either one for both of these jacks. If only analog jack is
connected, the IDU can use the analog voltage as a tracking source. If only serial port is connected, the IDU
can often control the beacon receiver and also use the serial port for the tracking signal level. If both are
connected, it can use both analog voltage and/or serial port based on user-selected option.
Supported beacon receivers include those listed in the following table:
Any other beacon receiver with an analog output ranging from 0-10VDC can be used as well.
NOTE: The NGC-IDU supports an internal beacon receiver kit. If this kit is installed, it will preclude the use of the two
external beacon receiver connectors. Connecting a beacon receiver to any of the pins on J11 or J12 except the alarm
contacts will compromise the operation of both beacon receivers and could cause damage.
See Section 2.6 in this manual for instructions regarding NGC-IDU software.
HOME Main Menu
Status Configuration
Administration
Operations
Controller
Configuration Menu
Operations Menu
Satellite Working Tracking General
Global Beacon
Track
Detailed Status Administration System SNMP SRT
Status Setup
Baseline Spec An
Config
Diagnostics Shutdown Smar‐
Adv. Track
VF Drives Movement
Update SW Config Step
Go To Mgmt Track
Sat
Faults Settings Install‐
Go To ation Motorization
Long.
History
User Mgmt Move/ Platform Location SRT
Flush Jog
Archives
Spec An
Figure 2-1: NGC-IDU Menu tree
2.1 Powering On & Off the NGC-IDU
WARNING! PROVIDE ADEQUATE SURROUNDING SPACE FOR VENTILATION! Take care not to cover vent or
cooling hole/slot in side covers
The IDU is intended for indoor, controlled environment use only. Before you start-up the IDU, you MUST
properly install and connect the system. For detailed instructions on installing the IDU, please refer to manual
7581695. For detailed instructions on installing the antennas motors, please refer to the appropriate Motor Kit
Electrical Installation Instructions document for your equipment, 7580540 (208VAC) or 7580541 (380VAC).
To power ON the IDU:
• Press the Power Button (on bottom right of the NGC front panel).
• System should power on
NOTE: LEDs of IDU Front Panel will flash sequentially as the system boots up. This is nothing to worry about. Do not
forget that you will need to WAIT 90 SECONDS for startup process to complete
Forced Shutdown (allowed, but not recommended for shutdowns under normal conditions):
• Press & hold Power Button (See Figure 1-3) for 6 seconds until system powers down
• The IDU will make a continuous beeping sound. This is nothing to be concerned about
2.2.2 Home Screen Breakdown
(There is one additional security level, Administrator, which is not covered by this document. This is the ASC
Signal proprietary mode. It cannot be accessed by customers because it may be used to change the system
serial number. Otherwise, it is identical to Installer.)
Path: HOME Æ Administration Æ User Mgmt.
The Installer password cannot be changed, and is locked as JFQB23.
The user changes the security level from the following path:
Path: HOME Æ Administration Æ press “Log On” button
Security levels are persistent and survive power cycling.
The choice of what security level to leave the system in is left to the customer. ASC Signal recommends
choosing a level that best fits the specific circumstances and preferences of the Earth Station.
2.4.1 Screen Saver
Path: HOME (Main Menu) Æ Administration Æ Settings
The above path will take you to the TPU Settings screen, where you can select between the Screen Saver
settings “ON” or “OFF.”
NOTE: the IDU touch screen does not develop “screen burn,” as one experiences with a CRT screen saver. LCDs do not
“burn in.” The IDU can develop temporary “memory” at times, which may resemble screen burn. However, this is not
permanent and will wear off in a short time.
Keep the following points in mind regarding the NGC-IDU Screen Saver:
• The default setting for the Screen Saver is “OFF”
• The Screen Saver will activate after 15 minutes of not using the TPU (touch screen)
• Screen Saver may be deactivated by simply touching the TPU or pressing any key/button on the front
panel
• The Screen Saver actually alternates between two screens: Status (Figure 2-5) and Current Fault
Summary (Figure 2-6) screens
Figure 2-6: NGC-IDU Keyboard
# Item Description
1 Fault Pressing this will take you to the Current Faults/Conditions screen
2 Standby Takes you to the Movement screen
3 Signal Takes you to the Spec An screen (if installed)
4 Tracking Takes you to the Tracking screen
5 GOTO Takes you to the GoTo Satellite screen
6 LCL/REM Toggle between Local and Remote modes
7 Jog Mode Activate Jog Mode (Blue=OFF, Green=ON)
8 Back Arrow Return to previous screen
9 HOME Go to the HOME (Main Menu) screen
10 CW (+) Jog Pol Clockwise (increase Pol value)
11 CCW (-) Jog Pol Counterclockwise (decrease Pol value)
12 Jog Screen Go to Jog screen
13 El Up Jog Elevation UP
14 El Down Jog Elevation DOWN
15 Az CCW Jog Azimuth Counterclockwise
16 Az CW Jog Azimuth Clockwise
17 Number Pad Used to input numeric values. In Jog Mode, use these to input Jog Speed: from 1=10%
(0-9) (slowest) to 9 = 90% (fastest). Note that choosing 0 = 0% Jog Speed, meaning the antenna
will not jog
18 Delete Delete selected field or value
19 Enter Accept input of selected field or value
20 Power Button Used to power ON/OFF the NGC-IDU
2.5.1 Detailed Status
Path: HOME Æ Status
There are three main detailed status screens. These give status information that helps the user understand
the state of the system.
Figure 2-7a: Detailed Status 1
# Item Description
1 Azimuth Current Az angle. Same as status at top of screen & displayed in global coordinates
2 Elevation Current El angle. Same as status at top of screen & displayed in global coordinates
3 Polarization Current Pol angle. Same as status at top of screen & displayed in global coordinates
4 Latitude Latitude of station on Earth. May/may not be editable depending on configuration. If system is
“fixed” station, they usually can be edited. If “mobile” they cannot be edited, as they are
supplied by the GPS. If GPS is provisioned on fixed system, fields will appear as editable, but
editing them will not accomplish anything as the GPS reading will override any entered value.
NOTE: Unless program tracking, it is not necessary to enter site’s exact latitude & longitude. However, NGC
automatically calculates many satellite look angles if you enter site’s exact latitude & longitude.
5 Longitude Longitude of the station on the surface of the Earth
NOTE: If you change latitude & longitude, look angles & Pol will be recalculated!
6 Altitude Altitude of the station on the surface of the Earth
7 Track Mode Displays currently selected track mode. Pressing it brings up a screen which allows selection of
various Track Mode functionalities
8 Track State Indicates the compass reading.
9 Heading This displays the True Heading, which corresponds to 0 degrees for platform Azimuth
10 GPS Status AS-1 fault status is reported here (not used in fixed antennas, and status will display as “fixed”)
Possible values: No data from dev, no satellite fix, or fixed
11 GPS Quality AS-1 quality is reported here (not used in fixed antennas). Possible values: good, marginal, or
none
12 GPS Sat Count GPS satellite count is reported here (not used in fixed antennas). Range: 0 to 12
13 Back Arrow Return to previous screen
14 Home Return to HOME screen
15 Diagnostics Go to Diagnostics screen
16 Faults Go to Current Faults/Conditions screen
17 Tracking Go to Track Status screen
Figure 2-7e: Detailed Status 5 (SRT Systems)
# Item Description
1 SRT Status The current status of the SRT (for SRT Only systems)
2 SRT X Limit X axis limit engaged, and what type (Hard or Soft, Off = limit not engaged)
3 SRT Y Limit Y axis limit engaged, and what type (Hard or Soft, Off = limit not engaged)
4 SRT Z limit Z axis limit engaged, and what type (Hard or Soft, Off = limit not engaged)
NOTE: See APPENDIX C, Table C.3 for Axis Limit Conditions
The Diagnostics screens, reached from Detailed Status and then Diagnostics, are useful for isolating the
root causes of any problems and parameters that are not reasonably grouped as other items.
The main screen shows some general information and provides several action and navigation buttons.
Figure 2-11: Administration Screen
# Item Description
1 User Access Level The current access level, as already described in this manual. The displayed access level is
dependent upon which password has been used to access the system.
2 SCP Version The current used version of SCP software
3 TPU Version The current used version of TPU software
4 Goto View ID Many screens have a View Code, which may be entered in this field in order to Shortcut to that
screen. The View Code for any screen can be found in the SCREEN INFO box, which may be
reached by holding down the HOME button for more than 5 seconds.
5 Log On Pressing this button will bring up the virtual keyboard, allowing you to enter the appropriate
password (unique to access level). Any incorrect passwords entered will be ignored and the
most current access level will remain unchanged.
6 Log Off Pressing this will reduce the Access Level down to “monitor,” which will restrict the user to basic
status information. Also, the menu structure will be limited to general user operations.
7 Back Arrow Return to Previous screen
8 Home Go to HOME screen
9 Shutdown Commence shutdown [“Confirm Shutdown” icon will appear]
10 Update SW Go to Update Software screen
11 Settings Go to TPU Settings screen
12 User Mgmt Go to User Management screen
Figure 2-12: Update Software Screen
# Item Description
1 SW Update Source This field allows you to choose between either the Internet or a File as a
source, from which you will retrieve software updates for installation. The
content and appearance of the “File Path” fields (below) and the “Update”
action buttons (to the left) will change in order to match what you select in
this field.
2 SCP SW File/URL Path Configurable path (File or URL, depending on what source is chosen) to
SCP .deb file
3 TPU SW File/URL Path Configurable path (File or URL, depending on what source is chosen) to
TPU .deb file
Figure 2-13: Operations Menu Screen
# Item Description
1 Track button Brings up Track Configuration Screen (see Section 2.8)
2 Movement button Brings up Movement Menu Screen (see Section 2.7.2)
3 Spec An Button Brings up Spectrum Analyzer Screen (see Section 2.7.3)
4 Pattern Button Brings up Pattern Screen
1
6 9
2
10
7 11
3
8
4 5
Figure 2-14: Tracking Screen
# Item Description
1 Scan button Initiates a spiral scan to attempt to find the satellite automatically.
2 Resume track Tells the system to attempt to resume the selected tracking mode.
3 Pre-charge For adaptive predictive track modes like SmarTrack®, tells the system to attempt to
resume selected tracking mode and use historical data to pre-charge the tracking model.
4 Status Goes to a lower level tracking status menu
5 Config Goes to a tracking configuration menu, see Section 2.8.3
6 Beacon plot Time strip-chart of beacon signal over the last ten minutes. Touch this to zoom in.
7 Az plot Time strip-chart of Az over the last ten minutes. Touch this to zoom in.
8 El Plot Time strip-chart of El over the last ten minutes. Touch this to zoom in.
9 Track State Summary of the current tracking state.
10 Track Mode Current selected tracking mode. Editable, but only when Track is paused.
11 Az vs El Plot XY plot of Az and El for current satellite over the history of position log. Touch this to
zoom in.
The beacon display screen gives some statistics about the analog beacon signal.
NOTE: if the tracking source is the spectrum analyzer, the serial data from a beacon receiver, or any other
receiver, this data will not necessarily be useful.
Figure 2-16: Beacon Display Screen
# Item Description
1 RainBuf Sigma Standard deviation of rain sample buffer. Used to mark likely rain events in event history log.
2 RainBuf Depth Number of one-minute sample intervals in the rain buffer
3 RainBuf Mean Average signal strength in rain buffer
4 Bcn Lvl Sigma Standard deviation of rain sample buffer. Used to mark likely rain events in event history log.
5 Filter Depth Number of samples in the beacon averaging filter
6 Scintillation System’s evaluation of the level of scintillation in the atmosphere
7 Beacon Plot Time strip-chart of beacon signal over the last ten minutes. Touch this element to zoom in.
Figure 2-17: Movement Screen
# Item Description
1 Track Brings up a menu of tracking commands (see Figure 2-18a)
2 Scan Initiates a spiral acquisition scan
3 Motor Brings up a menu of low-level diagnostic commands (see Figure 2-18b)
4 Track State Shows the current state of the tracking state machine.
5 Track Mode Shows current tracking mode
6 Goto Sat Brings up Goto Satellite screen
7 Goto Long. Brings up Goto Longitude screen
8 Move Ant. Brings up Movement Menu screen
Figure 2-18a: Movement Commands 1
Command Action
Clear SmarTrack® Model Erases the current SmarTrack® model. Cannot be undone.
Recalc. SmarTrack® Forces system to recompute model. Usually has little or no effect, for
backward compatibility only
Clear rain buffer Erases the rain analyzer buffer
Flush logs Forces the system to write log files. Not used much in operational systems.
Pause track Another way to stop track.
Resume track Another way to resume track.
Precharge track Another way to resume track through precharge.
Figure 2-19: Goto Satellite Screen
# Item Description
1 Goto Sets up the receiver parameters for the indicated satellite and then moves to its stored
location.
2 Retune Sets up receiver parameters for indicated satellite but does not move to stored location
3 Recompute Force angle recomputations
4 Warning column Has warning symbol if entry not filled out enough to support 3PP tracking. Sortable.
5 Working # column Index into this table. Sortable.
6 Band column See Section 3.9.2.
7 Name column Name of the satellite. Sortable.
8 Longitude column Orbital longitude of the satellite. Sortable.
9 Az column Projected Azimuth of the satellite. Sortable.
10 El column Projected Elevation of the satellite. Sortable.
11 Polarization column Projected Pol angle of the satellite. Sortable.
12 Pol type column See below.
7581691_Rev B Page 54 of 179
13 NORAD ID column NORAD ID.
14 Scroll bar Used to move around the list window.
15 Stow button (TriFold® only) Starts the stow command, see Section 5.1.9
16 Acquire button (TriFold® only) Starts the acquisition assist command, see Section 5.1
17 Working table shortcut Jumps to the editing screens.
2.7.2.1 Goto Longitude Screen
The Goto Longitude screen can be used to point the antenna at the predicted location of a
geostationary satellite at a specific longitude without going to the degree of creating a satellite entry.
This is generally recommended only for installation.
Figure 2-20: Goto Longitude Screen
# Item Description
1 Satellite Long. Longitude of satellite. Used with site latitude & longitude to compute nominal look
angle
2 Satellite Pol Orbital skew of satellite. 0 is usually horizontal, 90 vertical. Used to estimate Pol
angle for drive
3 Stop Stop current movement, if any.
4 Move Execute changes to computed Az, El, and/or Pol from orbital parameters that have
been entered.
Figure 2-21: Typical Jog Screen (Pol Installed)
# Item Description
1 Store Peak button Saves the current position into the working satellite table as the Peak Az, El,
and Pol. This only works if Status Bar shows a current satellite.
2 Resume (Pause) Resumes tracking if not tracking, pauses tracking if currently tracking. This is
Track button a convenience button to reduce the need for menu navigation.
3 CW Pol jog Turns Pol rotator clockwise (if equipped). Blank if no Pol drive is configured.
4 CCW Pol jog Turns Pol rotator counterclockwise (if equipped). Blank if no Pol drive is
configured.
5 El up jog Jogs Elevation up
6 El Down jog Jogs Elevation down
7 Az CCW jog < Jogs Azimuth counterclockwise
8 Az CW jog > Jogs Azimuth clockwise
9 Dish jog selector Selects main dish motorization for movement. Blank unless the system has
both kinds of motorization. If the system has only an SRT, SRT selection is
implied.
10 SRT jog selector Selects SRT motorization for movement. Blank unless system has both kinds
of motorization
11 Jog Speed selection Jog speed as a % of max speed. Jog speed of 0 effectively disables the jog
function.
12 Jog Speed selector Picks a jog speed as a percentage of the maximum speed.
13 Target Az Designated commanded position for Az. Note the SRT and main dish cannot
be positioned independently except through jogging.
14 Target El Designated commanded position for El. Note the SRT and main dish cannot
be positioned independently except through jogging.
15 Target Pol Target Pol, if equipped. Field is blank if no Pol drive is configured.
16 Stop button Stop current movement, if any.
17 Move button Execute changes to Az, El, and/or Pol that have been entered.
18 Right panel selector Scrolls the right-hand panel between several options, see following screens.
TOGGLE BUTTON
Figure 2-22a: Jog Screen (No Pol Installed)
# Item Description
1 Store Peak Allows you to store the current target coordinates as the signal peak
2 Resume Track Allows you to return to the Tracking State
3 Jog Arrows Use these arrows to jog Az & El. If Pol drive is installed, you will see the CW & CCW
Pol arrows (not shown)
4 Jog Speed This column allows you to choose your Jog Speed, in %, from 0% to 90%
5 Target Az This field allows you to numerically input a Target Azimuth
6 Target El This field allows you to numerically input a Target Elevation
Target Pol (not shown) This field allows you to numerically input a Target Polarization
7 STOP Pressing this button will immediately STOP antenna movement
8 Move Pressing this will accept the input Target Az & El (& Pol if installed), and move the
antenna to the Target coordinates
9 Toggle Button This will allow you to toggle between certain views. For example, pressing up will
show the Spec An Beacon and pressing down will show the Beacon vs. Time Plot.
Toggling up or down will also allow you to see other view options on the toggle button.
Figure 2-22b: Jog Screen with SRT Selected for Movement
Figure 2-22c: Jog Screen with Beacon vs. Time Displayed
If the spectrum analyzer is installed, a beacon spectral display can be shown along with the jog panel to
facilitate manual peaking.
Figure 2-22d: Jog Screen with Spec An Beacon Displayed
If the spectrum analyzer is installed, an L-band spectral display can be shown along with the jog panel
to facilitate manual peaking.
Figure 2-22e: Jog Screen with Spec An Displayed
Figure 2-22f: Jog Screen with SRT Position Displayed
2.7.3 Spectrum Analyzer (Option)
Path: HOME Æ Operations Æ Spec An (tap the touch screen to open General Mode screen)
Figure 2-23: Spec An Tab Bar
# Item Description
1 General Activate General page (see Section 2.7.3.1)
2 Frequency Activate Frequency page (see Section 2.7.3.2)
3 Span Activate Span page (see Section 2.7.3.3)
4 Amplitude Activate Amplitude page (see Section 2.7.3.4)
5 Marker Activate Marker page (see Section 2.7.3.5)
6 RBW/Trace Activate RBW/Trace page (see Section 2.7.3.6)
When at any page of the Spectrum Analyzer, all configurable parameters populate the right edge of the screen in the
form of green radio buttons. The select parameter has absolute focus of all configuration techniques.
Configurable parameters may be edited using some or all of the following elements:
1. The description and value on the 3-Way rocker.
2. The virtual keyboard or selection box for invoked by pressing the 3-Way rocker in the center.
3. Incrementing and decrementing using the ‘+’ or ‘-‘ sign on the 3-Way rocker.
4. The left/Right or down/up arrow keys on the key pad.
5. The number pad, including enter and delete, on the keypad (not used for enumerated lists).
6. The arrows and numbers keys on a keyboard plugged into the USB jack or as part of a PC running the PC
version of the UI.
2.7.3.2 Frequency Page
This page allows alterations to the X axis and contains parameters to alter range of frequency observed
in plot.
2.7.3.4 Amplitude Page
Figure 2-29: Spec An Marker Mode
# Item Description
1 Next Peak Places marker in focus to next peak LOWER than marker is presently
2 Peak Right Places marker in focus to next peak right of its current position. May be higher or lower than
marker’s current position
3 Peak Left Places marker in focus to next peak left of its current position. May be higher or lower than
marker’s current position
4 Hide Markers Hides any User Interface (UI) Markers currently in use. Press again to show UI Markers.
5 Normal Allows you to move the Normal marker using 3-Way rocker, keypad, etc. (you can always “grab”
and move the marker from any visible screen). The delta marker will not be visible if in Normal
configuration. When in Normal configuration, normal marker is in focus for all action buttons
6 Delta Allows movement of Delta marker with 3-Way rocker, keypad etc. Normal marker remains visible
when in Delta configuration but can only be moved by “grabbing” it with finger. Frequency setting
on 3-Way rocker is actual, while value displayed in delta marker box is difference between the
actual delta marker position and normal marker position. When in Delta configuration, delta
marker is in focus for all action buttons
7 3-Way Rocker Used to edit values
8 UI Normal This action can be invoked by switching to Marker tab or just by touching plot in any other tab.
Marker Actual marker is gray diamond that rides on plot, while gray info button/box above contains
marker’s coordinates. You can move location of the marker by “grabbing” marker line with your
finger and moving it left or right. The user marker is represented with a gray marker and gray info
box, while the delta marker has a blue diamond and box. The delta info box doesn’t show the
marker coordinates, but difference of delta marker & normal marker coordinates
Figure 2-31: Controller Configuration Manu Screen
# Item Description
1 Satellite Go to Satellite Menu screen
2 Tracking Config Go to Tracking Configuration menu screen
3 Motorization Go to Motorization screen
4 System Setup Go to System Setup screen
5 Platform Go to Platform Configuration screen
6 SRT Go to SRT Configuration screen
Figure 2-32: System Setup Screen
# Item Description
1 Restart GUI button Restarts the GUI program. Not normally needed.
2 Operational Basic setup parameters used to tell NGC-ODU what kind of pedestal and equipment it is
Configuration running on. Be very careful to get this right. See table C.19 for meaning of values.
3 J9 Emulation Configures which protocol to emulate on J9 on rear panel. Typical value is “APC100”
4 Time Current UTC time from GPS or NGC-IDU. DO NOT use local time. The IDU does not
adjust for daylight savings time or any other local conventions, and only uses UTC (also
known as GMT or Zulu time).
5 Sys Name Name of the system within the site
6 IP Addr Network address of external ethernet port. See Section 3.8
7 IP Mask Network mask of external Ethernet port. See Section 3.8
8 SNMP Opens the SNMP Configuration Page
9 Baseline Opens the Baseline Page
10 Advanced For certain advanced functions. DO NOT USE.
11 Config Mgmt Opens the Configuration Management Page
12 Installation Opens the Installation Interview
Page 3 (on screen) of the System Setup screens does NOT contain information that is of common interest
to the general user.
2.8.1.1 SNMP Configuration
The following screens will allow you to configure various elements of the NGC-IDU’s SNMP agent.
Path: HOME Æ Configuration Æ System Setup Æ SNMP
Figure 2-34: SNMP Configuration Screen
# Item Description
1 SNMP Off Enable or disable the SNMP agent globally. Changing this requires a power cycle
2 Read Community Read community string used by SNMPv1 and SNMPv2 for GET and GET-NEXT
access
3 Write Community Write community string used by SNMPv1 and SNMPv2 for GET, SET, and GET-
NEXT access
4 Trap Community Trap community string used by SNMPv1 and SNMPv2 traps.
2.8.2 Configuring Satellites
The NGC-IDU supports storage of up to 64 working satellites and up to 1000 global satellites in the system.
The NGC-IDU can store a variety of satellite information, including pre-programmed, fixed Az, El, and Pol
values. Additionally, the NGC-IDU can store more sophisticated information, such as a full set of orbital
tracking parameters used with the tracking option.
The working satellite table contains the satellites that can be used by the system immediately. These
satellites can be edited, and the system can be pointed at them.
The global satellite table contains all satellites that the NGC-IDU knows about. In order to edit them, the
user must put them in the working satellite table. Note that while only a limited amount of information is
displayed for the global table entries, all information is retained when a satellite in demoted to the global
table by the user.
Path: HOMEÆ Configuration ÆSatellites
This screen allows the user to select between working table editing and global table actions.
Figure 2-36: Satellite Menu Screen
# Item Description
1 Working Satellite Table This button will take you to the Working Satellite Table
2 Global Satellite Table This button will take you to the Global Satellite Table
Figure 2-37: Working Satellite Table
# Item Description
1 New button Pressing this button will start the process of creating a new satellite entry from scratch
Edit button (Not shown) Selecting a satellite and pressing Edit brings up the Edit Screens
2 Remove button Selecting a satellite and pressing Remove will erase a satellite after confirmation.
Note unless it is also removed from the Global Table it will still be available to be
recalled. Note a recalled satellite may not necessarily be put in the same column.
3 Recalc Angs button Recompute look angles.
4 Warning column Has warning symbol ( ) if entry not filled out enough to support 3PP tracking.
Sortable.
5 Working # column Index into this table. Sortable.
6 Band column See below.
7 Name column Name of the satellite. Sortable.
8 Longitude column Orbital longitude of the satellite. Sortable.
9 Az column Projected Az of the satellite. Sortable.
10 El column Projected El of the satellite. Sortable.
11 Polarization column Projected Pol angle of the satellite. Sortable.
12 Pol type column See below.
13 NORAD ID column NORAD ID.
14 Purge Visible button Erases any entries below the horizon.
15 Refresh Table button Reloads this table.
X band feed
Ku band feed
User defined 1
User defined 2
User defined 3
User defined 4
Figure 2-38: Working Satellite Entry Screen
# Item Description
1 Commit Saves the current entry into the satellite tables. Updates to working tables are also made to
global tables.
2 Cancel Drops the current edits and restores the previous data. This is used when the user has made a
serious mistake and wishes to start over.
3 Recompute Re-project the look angle based on current data. The system does not always do this
automatically, so this is a way to force it to do so.
4 Clear DVB Erases the (optional) DVB descriptor (see Section 2.8.2.1.2)
5 Working Sat # Index into the working satellite table
6 Azimuth Calculated Az of the satellite from the current location. This entry can be edited if desired but the
Recompute button will cause it to be overwritten.
7 Elevation Calculated El of the satellite from the current location. This entry can be edited if desired but the
Recompute button will cause it to be overwritten.
8 Polarization Calculated Pol of satellite from current location, taking into account orbital Pol & local skew
angle. This entry can be edited if desired but Recompute button will cause it to be overwritten.
9 Longitude Orbital longitude slot of the satellite. This is essential data, see Section 4.7
10 Name Name of the satellite. This is essential data, see Section 4.7
11 Peak Az Saved peak Az of satellite. It may not match calculated Az. Note the recompute button will erase
this angle. Peak Az of 0.000 is ignored.
12 Peak El Saved peak Az of the El. It may not match calculated El. Note the recompute button will erase
this angle. Peak Az of 0.000 is ignored.
13 Peak Pol Saved peak Pol of the El. It may not match the calculated Pol. Note the recompute button will
erase this angle. Peak Pol of 0.000 is ignored.
14 Orbital Pol Orbital Pol angle plus offset, used to calculate Pol angles. This is essential data, see Section 4.7
15 Clear Spectra Used to erase any associated L-band spectra in the system taken with Spectrum Analyzer.
Figure 2-40: Working Satellite Entry Page 3
# Item Description
1 Norad ID 5-digit ID assigned by NORAD. This is essential data, see Section 4.7
2 NORAD Az Offset Per-satellite Az offset for NORAD fine tuning. See Section 4.1.2
predictive tracking offsets
3 NORAD El Offset Per-satellite El offset for NORAD fine tuning. See Section 4.1.2 predictive
tracking offsets
4 Norad Data Validity Indication Red or Green tells if data has expired
5 Norad Line 1 69-character TLE line 1
6 Norad Line 2 69-character TLE line 2
Figure 2-42: Working Satellite Entry Page 5
# Item Description
1 Track Signal source to use for peaking, 3PP step-track, and so forth. Users who are unsure should
Source leave this set to auto.
2 Pol Type Type of Pol associated with the satellite. See Section 3.10 for more information. This is useful
for TriFold ® systems with interchangeable feeds. Users who are unsure should leave this set
to auto.
3 Band Type of band associated with the satellite. See Section 3.10 for more information. This is
useful for TriFold® systems with interchangeable feeds. If unsure, you should leave this set to
auto.
None Acq (Not shown above) Signal source to use for acquisition assist. If unsure, you should leave
Source this set to auto.
Figure 2-43: Intelsat Data Screen
# Item Description
1 Commit button Save the current edits into the satellite table entry
2 Cancel button Drop the current edits from the satellite table entry
3 Sat Name Name of the IESS 422 data set. Not critical
4 Epoch Date/Time Epoch time on which ephemeris is based. Also start of timeframe for expiration.
5 Predicted Long. Estimated longitude 170 hours after epoch time, used as a check on the rest of the data
6 Predicted Lat. Estimated latitude 170 hours after epoch time, used as a check on the rest of the data
Figure 2-44: Intelsat Data Page 2
# Item Description
1 LM0 Mean longitude, in degrees East
2 LM2 Longitude drift acceleration
3 LonC Amplitude of longitude oscillation, cosine term
4 LonS Amplitude of longitude oscillation, sine term
5 LatC Latitude oscillation, cosine term
6 LatS Latitude oscillation, sine term
7 LM1 Longitude drift, in degrees/day
8 LonC1 Rate of change of longitude oscillation, cosine term
9 LonS1 Rate of change of longitude oscillation, sine term
10 LatC1 Rate of change of latitude oscillation, cosine term
11 LatS1 Rate of change of latitude oscillation, sine term
Figure 2-45: DVB Element Configuration Screen
# Item Description
1 Commit button Save this DVB element into the table entry.
2 Cancel button Drop these edits.
3 Satellite Name Name of the satellite, not used by DVB subsystem.
4 Carrier Frequency Downlink carrier frequency, see Table 5.1
5 LNB Frequency LNB local oscillator, see Table 5.1
6 Search Range AFC capture range, see Table 5.1
7 Sym Frequency Symbol rate, see Table 5.1
8 Roll Off Roll off of filter, see Table 5.1
Figure 2-46: DVB Element Configuration Page 2
# Item Description
1 Sym Rate Code See Table 5.1
2 Modulation See Table 5.1
3 Modulation2 See Table 5.1
4 FEC Forward error correction, see Table 5.1
5 LPF See Table 5.1
6 IQ Swapped See Table 5.1
7 22kHz Tone, not normally used. See Table 5.1
8 Horizontal See Table 5.1
9 Options See Table 5.1
7581691_Rev B Page 74 of 179
2.8.2.2 Working with the Global Sat Table
Figure 2-47: Global Satellite Table Screen
# Item Description
1 Set Working button If a satellite is highlighted and it is not in the working table, pressing this button
moves it into the working table.
2 Delete button If a satellite is highlighted that is not in the working table, pressing this button will
permanently delete it. All information will be lost. If the satellite is restored from
the NORAD geo.txt file, all frequency and other configuration data not in the TLE
is lost.
3 Recalc Angs Recompute look angles for all satellites based on current geolocation.
4 Name column The common name of the satellite, taken from the geo.txt file.
5 Band icon column An indication that the satellite entry has been associated with a specific
frequency band. See Section 3.10 for more information.
6 Longitude column Orbital longitude slot. For inclined orbit satellites this is the mean longitude.
7 Pol column Orbital Pol. Usually 0 degrees for horizontal, 90 for vertical. Note some
satellites have slightly twisted orientation.
8 Pol type icon Indicates if the satellite is associated with linear, circular, or neither (automatic)
column Pol. See working table page 5 (on screen) for more information.
9 Norad ID Five-digit number assigned by NORAD.
10 Working set number Number of the satellite in the working table, or none
11 Scroll slider Slider allows paging or scrolling through entries. Note user can also drag the
screen.
12 Update Table See Section 2.8.2.2.1
13 Purge Table See Section 2.8.2.2.2
14 Refresh table Refreshes the table (similar to refresh on a web browser)
Figure 2-48: Update Satellite Table Screen
# Item Description
1 Install URL button Using the file named in item 5, the system updates the NORAD TLE in each
element in the global satellite table. If the satellite is also in the working
satellite table, it is updated too. If the satellite does not exist, a new entry in
the global satellite table is created for it.
2 Install File button Using the file named in item 6, the system updates the NORAD TLE in each
element in the global satellite table. If the satellite is also in the working
satellite table, it is updated too. If the satellite does not exist, a new entry in
the global satellite table is created for it.
3 Archive button When pressed, copies all satellite tables to the archive file path (item 7) on
the jump drive.
4 Install Archive button Copies the archive named in item 7 into the system replacing the working and
global satellite tables.
5 URL Path File name of the NORAD file on an FTP site
6 File Path File name of the NORAD file geo.txt
7 Archive File Path File name of the archive file, always globalsatdump.tgz
8 Update URL button Using the file named in item 5, the system updates the NORAD TLE in each
element in the global satellite table. If the satellite is also in the working
satellite table, it is updated too. No new entries are created.
9 Update File button Using the file named in item 6, the system updates the NORAD TLE in each
element in the global satellite table. If the satellite is also in the working
satellite table, it is updated too. No new entries are created.
Satellites in the working table are never removed from the global table no matter what other
categories they fit into.
Figure 2-49: Update Satellite Table Screen
# Item Description
1 Purge All but Visible Remove all entries from global table that are not in working table
as well as not visible. Visible is defined as below the horizon
from current site location. This action cannot be undone.
2 Purge All but Working Remove all entries from global table that are not in working
table. This action cannot be undone.
3 Purge Non- Remove all entries from the global table that are not in the
Geostationary working table with inclinations greater than as determined by
their NORAD TLEs (If an entry doesn’t have a TLE, it is
assumed to be geostationary). This action cannot be undone.
1
2
3
4
Figure 2-50: Step-Track Configuration Screen
# Item Description
1 Step Multi Factor % of a 3dB beamwidth to move during peaking. Parameter is typically set at 0.120 (12%),
but you may have a slightly different idea for the value. Values <0.120 will tend to flatten
the beacon response and weaken resolving power of tracking algorithm. Values >0.120
may produce more accurate peaks but may cause significant signal loss during the
peaking process. ASC Signal does not normally recommend changing this value. There
may be valid reasons, however, for overriding this parameter. Nominal value is 0.120
2 Step Cycle time Max time between unconditional peaking intervals, in minutes. Nominal value is 15 min
3 Step Cycle Signal loss from previous peaking result, at which system automatically re-peaks antenna.
Thresh Smaller values will result in more movement. Nominal value is 0.40dB
4 Step Distance Distance for each step-track move, automatically calculated from antenna size, downlink
frequency, & step multiplier factor. Not user changeable
2.8.4 SmarTrack® Configuration
Path: HOME Æ Configuration ÆTracking Config ÆSmarTrack®
IDU SmarTrack® algorithm is based on building a mathematical model of observed satellite orbit from the
history of Az & El readings during tracking. Once sufficient data is collected to build a reliable model, the
system switches automatically to a predictive mode and uses occasional peaking to update the model.
Quality of model is given in dB by computing RMS error between the model’s predictions and actual
peaking points on the tracking status screen.
NOTE: many step track parameters also apply to SmarTrack® during the “model building” phase.
See following page for Figure 2-51 of the SmarTrack® Configuration screen and descriptive table.
2
3
Figure 2-51: SmarTrack® Configuration Screen
# Item Description
1 Minimum Used in predictive tracking modes to determine allowable computed tracking error in degrees.
Move When predicted Az/El vector differs from current Az/El vector by more than minimum move
value, system orders a move. Value may need adjustment for your system requirements.
Making value too small will cause extra movement, and making it too large will cause signal
loss between jumps.
NOTE: If the value is less than the deadband parameters in the Az and El axes this will be ineffective.
2 Cycle The time between model updates once system is running in predictive mode. Should not be
Time confused with Step Track cycle time
3 RePeak Level at which model is updated because signal has fallen too far from last peak. This should
Trigger not be confused with the Step Track Repeak Level
2.8.5 Configuring the Platform
To access the Platform Configuration screen, allowing you to view, edit, & configure values related to your
platform (Site ID, Antenna Size, fixed parameters, etc.), use the following path:
• Path: HOME Æ Configuration Æ Platform
• You will now be at the Platform Configuration screen
2.8.6 Configuring Motorization
Path: HOME Æ Configuration Æ Motorization
These pages are used to configure all parameters related to the position and rate loops for each of the two
or three axes for the main dish. There are up to five screens. The exact contents will vary based on the
configuration of the NGC-ODU.
Figure 2-52a: Motorization Screen
# Item Description
1 Az Ratio Az encoder turns ratio, related to resolver speed and any gearing. Note this does not refer
to the transformation ratio, which is electrical.
2 Az Kp Az axis PID controller proportional gain coefficient. This is similar in effect to the “ramp
down” or “deceleration” parameter in other controllers, although entered as the reciprocal. A
setting of 0125/0100 means that the controller will start slowing the axis at about (1/1.25) or
0.800 degrees. A higher gain means a steeper ramp-down.
3 Az Kd Az axis PID controller derivative gain coefficient. This is almost always set with a numerator
of 0. This can be used to dampen acceleration.
4 Az Ki Az axis PID controller integration gain coefficient. This provides a slight boost to help drive
out very small errors. It has a similar effect to the “hunting” coefficients of some other
controllers. Note that if parameter is raised it may be necessary to lower the same axis’ Kp.
5 Az Drv Time Distance between samples in Integration buffer in Az axis PID to use as derivative
difference signal.
6 Az Int Depth Az Axis PID integrator depth in samples. Not generally changed from 100.
7 Az Invert Indicates whether Az resolver/encoder is mounted so it counts backward from true angle
8 Az Max Rate Az max rate. Ranges 100 to 1000, where 1000 corresponds to max permissible output of
VFD
9 Az Min Rate Az min rate. Ranges from 0 to 1000, where 1000 corresponds to the minimum permissible
drive signal to the VFD. Not usually set below 100.
10 Az Rsp T/O # of seconds with no discernable movement tolerated by Az axis control loop when position
loop is enabled. May affect jogging in some NGC-ODUs as well.
11 Az Int Time Number of seconds of samples to integrate in the Az PID control block.
12 Az Az drive error tolerance. When the difference between target platform Az and the current
Deadband platform Az as is less than this value, the Az command is completed. Note that the system
will allow a slightly larger error without declaring a timeout in order to prevent resolver jitter
from causing spurious errors.
2.8.6.3 Polarization Main Dish Axis Configuration Screens
This screen is always available.
Figure 2-52e: Motorization Page 5
# Item Description
1 Pol Present Indicates whether or not a Pol drive is present, selected from a list of predefined
options
2 Pol Invert Indicates whether Pol resolver/encoder is mounted so it counts backward from true
angle
3 Pol Ratio Pol encoder turns ratio. The number of times the resolver or encoder turns per turn of
the main axis
4 CW Coast Distance from target platform Pol that NGC cuts power to Pol motor in CW direction
5 CCW Coast Distance from target platform Pol that NGC cuts power to Pol motor in CCW direction
6 Pol Rsp T/O # of seconds with no discernable movement tolerated by Pol axis control loop when
position loop is enabled
7 Pol Brake Time delay between actuating Pol brake release and turning on drive signal to Pol
Delay motor. When set to 0.0 the brake release function is disabled.
Figure 2-52f: Motorization Page 6
Figure 2-53: SRT Axes
If an XY SRT is present, this screen looks like that shown in the below example (Figure 2-54a):
Figure 2-54a: SRT Configuration Screen 1
# Item Description
1 SRT Status Overall summary of SRT’s current state
2 SRT Num SRT master configuration field, selected from a list of predefined options (none, XY present,
Axes XYZ present).
3 SRT Axis TO Timeout value for all SRT axes. Minimum time to drive motors without seeing any feedback
change. Individual axes on the SRT cannot be separately configured for timeouts.
4 Soft Lmt Used in calibration of X and Y to ascertain position for soft limits versus detected hard limits
Margin
5 SRT 3dB BW Estimate of number of degrees offset before SRT degrades signal by 3dB
7581691_Rev B Page 85 of 179
If no SRT is present, the screen looks like that shown in the below example (Figure 2-54b):
Figure 2-54b: SRT Configuration Screen 2
2.8.7.1 SRT X Axis Configuration
The screen shown in the below example (Figure 2-54c) is used to configure the SRT X axis (also
known as the Azimuth/Az or cross-Elevation).
Figure 2-54c: SRT Configuration (X Axis) Screen 3
# Item Description
1 SRT X Calibrated side-to-side range of SRT
Range
2 SRT X Scale Relationship between X offset and cross-el beam displacement
3 SRT X Axis Motor type for attached stepper motor to the X SRT axis, selected from a list of predefined
Motor Type motors. This controls the amount of current delivered to the motor and the holding torque.
Figure 2-54d: SRT Configuration (Y Axis) Screen 4
# Item Description
1 SRT Y Range Calibrated up-and-down range of SRT
2 SRT Y Scale Relationship between Y offset and El beam displacement
3 SRT Y Axis Motor type for attached stepper motor to the Y SRT axis, selected from a list of predefined
Motor Type motors. This controls the amount of current delivered to the motor and the holding torque.
2.8.7.3 SRT Z Axis Configuration
The screen shown in the below example (Figure 2-54e) is used to configure the SRT Z axis (also
known as the focus).
To complete the minimum setup & configuration of the IDU, you will need to have already collected the
following information/data:
1. Site ID or Name
2. Site Latitude and Longitude. OPTION: with GPS option, you do not need this info
3. Current Coordinated Universal Time (UTC), in either Zulu (Z) or Greenwich (GMT) time. OPTION: Again, if
you have GPS option you do not need this info
4. The center frequency of your local oscillator that down-converts the beacon to L-band
5. Whether the beacon is inverted (lower side band) or not (upper side band) by the down converter. C-band
frequency is usually inverted, while Ku is not
6. The kind of beacon receiver to which you are interfacing
7. Your LAN address, mask, and gateway. Only needed if plan to use the Ethernet option
8. The satellite at which you intend to point the antenna, its NORAD ID, and its beacon frequency
INFO/DATA #1-#7 above will be needed during the INSTALLATION INTERVIEW and #8 will be needed
during SATELLITE CONFIGURATION
Figure 3-1: Installation GUI Conventions
# Item Description
1 Status Bar Limited version of Status Bar (see Figure #-#)
2 Reset Button Un-checks all steps and resets progress bar
3 Step List Used to skip around to desired steps or to view which steps have been completed
(completed steps will have checkmarks). Can be scrolled through by firmly dragging your
finger up and down over list as if pushing it.
4 Sub-step Back Arrow Move back to a previous sub-step (arrow not shown in example)
5 Exit Leave Installation interview and return to System Setup screen
6 Progress Bar Shows % of steps “completed.” “Completed” simply means user has progressed through
the elements (sub-steps) of the current step
7 Current Step Description of current step. Will be checked if the step is completed
8 Sub-step/Question Sub-steps are most often questions, requesting yes/no choice or configuration
9 Next Step Pressing this button will take you to the next step.
10 Sub-step Forward Arrow Move forward to next sub-step (arrow not shown in example)
STEP 1, QUESTION 1: OPERATIONAL CONFIGURATION
If this is the initial setup of your NGC Unit, this should be the
first screen you see.
Question 1 will ask you to choose from one of two possible
answers regarding Operational Configuration:
• FIXED, which means your antenna is in a specific,
permanent location
• MOBILE, meaning that your antenna is designed to be
moved from location to location (such as a TriFold®
antenna)
STEP 1, QUESTION 2: ANTENNA SIZE
Question 2 will ask about the ANTENNA SIZE, meaning
the size of your antenna’s aperture measured in meters
(4.6m, 8.1m, etc.)
STEP 3: AZ CHARACTERISTICS
STEP 9: ELEVATION LOW LIMIT
Software Limits (SW Lmt) are input by the HANDHELD/ODU; DO NOT CHANGE THEM.
The screen may ask “Would you like to move to the down limit manually?” Pressing NO allows you to review/edit the
input values to make sure they are correct. YES will redirect to the JOG SCREEN.
The screen will now ask “Would you like to configure miscellaneous parameters?” NO will move you to STEP 11.
YES will allow you to review/edit data for:
• El Overcurrent Trip
• El Overcurrent Time
• El Brake Delay
STEP 11: Pol CHARACTERISTICS If your antenna does NOT have a Pol Drive, screen
will read “Pol drive not present.” If Pol drive is
present, system will ask “Would you like to review
the polarity setup?” NO will move you to STEP 12.
YES will allow you to review and edit the input data
for:
• Pol Encoder Offset
• Pol ratio
• Pol Rsp T/O
• CW Coast
• CCW Coast
• Pol Invert
DO NOT CHANGE VALUES UNLESS NEEDED
STEP 12: Pol HIGH LIMIT
Software Limits (SW Lmt) are input by the HANDHELD/ODU; DO NOT CHANGE THEM.
The screen may ask “Would you like to move to the CW limit manually?” Pressing NO allows you to review/edit the
input values to make sure they are correct. YES will redirect to the Jog screen.
STEP 13: Pol LOW LIMIT
Software Limits (SW Lmt) are input by the HANDHELD/ODU; DO NOT CHANGE THEM.
The screen may ask “Would you like to move to the CCW limit manually?” Pressing NO allows you to review/edit the
input values to make sure they are correct. YES will redirect to the Jog screen.
STEP 15: INDOOR PARAMETERS
The screen may read “Would you like to review the
general indoor parameters?” or you will see the Configure
Value screen shown in the photo to the left. NO will move
you to STEP 16. YES will allow you to review and edit the
data already input as needed for (you might want to record
this data for future reference in the areas below):
• Site ID:
• Product Key:
DO NOT CHANGE Product Key
STEP 16: GPS SYSTEM If you have GPS option, the NGC should detect it and
configure location values. Screen will ask “Would you like
to review the site location parameters?” Press YES to
review data (you might want to record this information for
future use).
OPTION: If you DO NOT have GPS (or if for some reason it
is not being detected), screen will ask “No GPS detected.
Should there be?” If you have a GPS but it isn’t being
detected, push the YES button, connect your device to the
system, and follow the on-screen instructions.
OPTION: If you DO NOT have a GPS option, simply press NO and manually input the following values (unless already
input, in which case simply review values and move on to STEP 17):
• Latitude
• Longitude
• Altitude
• Time
The screen will then ask “Does the system control the beacon receiver?” Answer YES or NO (SEE INSTRUCTIONS
BELOW FOR YOUR ANSWER)
“YES” ANSWER—review and/or input your specific Device Type. System will search for a default template and, if one is
found, will say “Default setups exist. Apply?” Answer YES to apply defaults, or NO to manually input values for Serial
Baud rate, Serial Control, Serial Multi-address (addr), Bcn Offset, Bcn Slope, and Low Signal Lvl
“NO” ANSWER—review and/or manually input values for Bcn Offset, Bcn Slope, and Low Signal Lvl
STEP 19: LAN SETTINGS
Screen may ask “Would you like to review the network settings?”
(press YES to review). Next it will ask “Would you like to review the
ethernet settings?” NO will move you to next (SNMP) question. YES will
allow you to review/edit data for:
• IP Address (Addr)
• IP Mask
• Gateway
OPTION: this data only applies if you have the ethernet option
Interview will ask “Would you like to review the SNMP settings?” NO will move you to STEP 20. YES will allow you to
review/edit values for the following:
• SNMP Off (True = it is OFF, and False = it is ON)
• Read Community (public, private, etc.)
• Write Community (public, private, etc.)
• Trap Community (public, private, etc.)
STEP 21: TRACKING PARAMETERS
TRACKING PARAMETERS ARE NOT NORMALLY CHANGED
The screen may ask “Would you like to review the tracking settings?”
or will present you with screen shown on the left.
NO will END INSTALLATION INTERVIEW
YES will allow you to review & edit values for:
• Step Multi Factor
• Step Cycle Time (Minutes)
• Step Cycle Thresh
• Cycle Time (Minutes)
• Minimum Move (Degrees)
• NORAD Life (Days)
• Intelsat Life (Days)
OPTION: please note that ONLY APPLICABLE PARAMETERS WILL BE PRESENT out of the above list of options.
Your specific software license will determine what parameters are authorized for your unit.
The step size should be equal to one half of the half-power beamwidth. The NGC-IDU will calculate this for
you.
The above procedure is intended to peak the antenna on the satellite. To complete the antenna peaking on
the satellite, align the antenna feed Polarization with the satellite by peaking the co-polarized feed port with
a satellite signal or null the cross-polarized feed port with a satellite signal by rotating the feed.
Figure 3-3: Analog Beacon Receiver Example
7581691_Rev B Page 98 of 179
3.5 Platform Configuration
The platform configuration elements tell the NGC-IDU and NGC-ODU the antenna’s size, how the pedestal is
mounted, and the information needed to determine where the antenna is pointed. Most of the settings here are
stored in and used by the ODU. The following sections describe how they are used for background.
3.5.1 Antenna Size
The IDU needs to know the antenna size as part of the process of estimating 3dB beamwidth. The antenna
size is always in meters.
To view or change the antenna size, use the following path:
• Path: HOME Æ Configuration Æ Platform
3.5.2 Antenna Encoder Offsets, Types, and Limits
The NGC-ODU has two built-in coordinate systems, the Local coordinate system and the Global coordinate
system. The ODU takes the raw resolver/encoder readings and adds the programmed center offsets to
create the platform angles that, when combined with the SRT offsets (if present), make up the local
coordinate system.
Soft movement limits are always specified along real axes in the NGC-ODU and IDU. Therefore, for
example, the Azimuth limits are “CCW platform SW Limit” and “CW Platform SW Limit”. The IDU does not
calculate or enforce travel limits based on the global coordinate system (Note, however, that the box limits
are calculated and enforced as global coordinates).
Use the following path and procedure to view or change the encoder offsets, encoder type, and soft limits:
• Path: HOME Æ Configuration Æ Platform.
• Go to the page associated with the axis (Az, El, Pol)
NOTE: if the encoder center offsets are changed, it may be necessary to change the software limits as these are not
automatically connected to each other in the software.
Figure 3-4: ODU Coordinate Transform Flow
The heading value can be used to allow for the antenna not being mounted with the center of travel facing
due South. See Appendix A for an example of what to do for an antenna that is installed in the Southern
Hemisphere.
The roll and pitch values can be used to correct for what is called “kingpost tilt.” Kingpost tilt is basically a
deviation of the Az axis of rotation from perpendicular. For a fixed antenna, the following diagram shows
the relevant terms.
18
0°
Figure 3-5: Roll & Pitch in NGC-ODU & How They Are Used
For example, if an antenna is installed so the pedestal is leaning back by 1.2° from perpendicular in the
North direction, the resulting effects on the coordinate system can be largely corrected by setting the pitch
setting to -1.200°.
If the NGC-IDU is connected to a GPS service, either through the AS-1 module as in a TriFold® controller,
or through the 10MHz reference option, it may not be necessary to enter this information directly.
Use the following path and procedure if no GPS service is available, in order to enter the latitude,
longitude, and altitude:
• Path: HOME Æ Configuration Æ Platform
• Press the Location button.
NOTE: latitude and longitude are entered in fractional degrees, not in degrees and minutes.
If the NGC-IDU is connected to a GPS service, either through the AS-1 module as in a TriFold® controller, or
through the 10MHz reference option, it may not be necessary to enter this information directly.
Use the following path and procedure if no GPS service is available, in order to enter the latitude, longitude,
and altitude:
• Path: HOME Æ Configuration Æ Platform
• Press the Location navigation button.
NOTE: latitude and longitude are entered in fractional degrees, not in degrees and minutes.
“Pre-Charge” is appropriate for SmarTrack® when the user has been Step-tracking for some period of time.
Pre-Charge will use the position log information from previous peaking intervals to retrospectively build the
model. See Section 4.3 in this manual for more information on SmarTrack®.
Once the network is configured, it is best to test it using PING. The use of this utility is outside the scope of
this document.
The IDU can obtain time from the external GPS in the optional ASC Signal AS-1 module. For mobile TriFold®
systems where no connection to the Internet is available, this is mandatory. An AS-1 can also be installed in
fixed applications to serve as both a system time and location source. In this case, date and time will be
automatically set and maintained.
Generally it is safe to use all three as long as the NTP server is properly synchronized to the GPS time system.
If no GPS or NTP time is available, the user may directly enter the current date and time from the Current Time
field on any page that displays it, e.g., the System Config page. Note that if the user enters time into a system
with an NTP connection, it may be overridden within 15 minutes, as soon as the NTP client runs again.
Unlike some other systems, the IDU allows the system date and time to be changed at any time. Intervals
between tracking steps and other periodic tasks are performed by elapsed time, which is unaffected by setting
the clock forward or backward. Note, however, that changing the time may make time-sensitive plots and data
look confused or awkward, as previous data samples are not adjusted by the system.
Some NGC Antenna Control Systems may have other time sources, such as built-in GPS references, as well.
This is out of scope for this manual.
4.1.1 Predictive Tracking
When the system is in NORAD or Intelsat tracking mode, the NGC-IDU regenerates a new angle from the
model periodically. The rate at which this happens depends on how much the model indicates satellite
appears to be moving. When the new pointing angle exceeds the minimum move constraint from the
previous angle, the command angle is updated. No feedback or other considerations alter the generation
of these angles.
The angle is of course the ideal look angle from the current location. To make this accurate, the system
time must be closely synchronized and the latitude and longitude of the earth station must be accurately
7581691_Rev B Page 109 of 179
known. The predictive track user should either install an AS-1 to get the time, connect the NTP client in
the NGC-IDU to an accurate time server, or monitor and correct the time of the NGC-IDU at least monthly.
Refer to section 3.10 System Time in this manual.
The data set must be entered before this approach can be used. See below for details.
Predictive track works best if antenna is very precisely installed and aligned. The antenna mount should be
as orthogonal as possible (El axis perpendicular to Az, and the kingpost dead plumb). The resolver offsets
should be carefully set to minimize pointing error.
4.1.2 Predictive Tracking Offsets
Even if all of these offsets are well done, there still may be small errors due to nonlinearities in the mount.
The NGC-IDU includes the ability to use satellite-by-satellite offsets for Az and El for each algorithm which
can be used to correct these last few hundredths of a degree.
To edit these offsets, use the following path and procedure:
• Path: HOME Æ Configuration Æ Satellite Æ Working Sat Tbl
• Select and edit the satellite of interest
• NORAD Az and El offsets are found on page 3 (on screen)
• Intelsat Az and El offsets are found on page 4 (on screen)
• Commit the changes to save them.
These parameters may be edited while the system is running. The offset will take effect on the next
prediction cycle, which may take a few moments.
Predictive track cannot account for true atmospheric refraction distortion (although some is modeled in at
low Elevations) of the antenna due to physical effects such as temperature, wind pressure, and mechanical
droop, and so forth. It will not normally perform as well as an equivalent system with closed-loop tracking.
Aligning and adjusting look angles is a tedious process that is beyond the scope of this manual.
4.1.3 NORAD Data Set
NORAD two-line elements sets (TLEs) actually consist of three lines. The first line is the name of the
satellite. The second and third lines contain fixed-length 69-character strings.
The NORAD SGP/SDP algorithm is a sophisticated astrophysical model suitable for all kinds of different
orbits – geostationary, geosynchronous, even MEO and LEO satellites. NORAD TLEs are available for the
ISS, for example.
The following figure shows a representative two-line element set with some example elements identified.
The exact meaning of each field is well-documented elsewhere and understanding them is not essential to
operating the NGC-IDU.
Epoch date/time
Element data
Predicted Lat/Lon
SmarTrack® is subject to very stiff quality metrics. The algorithm will use the model to reverse-project the
peaking data collected and determine RMS error, which is computed first in degrees and then in estimated loss
in dB using the 3dB beamwidth. If that error is greater than 1/3 of the repeak trigger, the model is not
considered valid and the system will attempt to update it.
4.3.1 SmarTrack® Configuration
The following SmarTrack® parameters are configurable:
• Minimum Move
• SmarTrack® Cycle Time
• Repeak Trigger
NOTE: many of the step-track parameters also apply to SmarTrack® during the “model building” phase.
4.3.2 Functionality of SmarTrack®
SmarTrack® collects points using three-point peaking (3PP) step-track. It must have at least five points
collected over at least a six hour period, and these points must pass the quality check. SmarTrack® collects
these points using the same frequency and re-peak criteria configured for step track.
Once the model is valid, the NGC-IDU switches into a predictive mode. It will then update the model
periodically, whenever the SmarTrack® repeak trigger is exceeded, or whenever the SmarTrack® cycle
time has been exceeded.
Model sample data older than 48 hours is discarded, and points closer than 15 minutes to each other are
also condensed.
4.3.3 Optimization of SmarTrack®
Very little adjustment is required for SmarTrack® once the 3PP subsystem is configured to work well.
Note, however, that there are some basic tips:
• Don’t set the repeak trigger too small. This can keep the system from using the models it develops
• Don’t select a SmarTrack® cycle time longer than 240.0 minutes
4.3.4 Pre-charge feature
The SmarTrack® algorithm can use information collected while step-tracking to pre-charge a model.
To do this, use the following path and procedure:
• Path: HOME Æ Operations Æ Track
• Pause tracking
• Change the tracking type to SmarTrack®
• Select Pre-Charge
Figure 4-3: SmarTrack® model
The most interesting elements are the Model data and Quality metric lines.
The model data contains the estimated parameters of the satellite at the Epoch time listed (which is the
same as the file generated time for all practical purposes).
SmarTrack® tends to slightly overestimate inclination for tightly-station-kept geostationary satellites. This is
because any error at all is assigned by the algorithm to the inclination.
The totalLoss is the RMS error of the collected points in the position log compared to the predicted angle
from the model calculating backward. This is converted to dB using the 3dB beamwidth and a parabolic
approximation of the antenna pattern.
• An analog beacon receiver may be interfaced using the analog, serial, or both interfaces. The choice of
whether to use analog or serial (digital) data from the beacon receiver is configurable.
• The optional built-in spectrum analyzer may be used for some satellites.
• The optional DVB receiver may be used for some satellites.
4.4.1 Analog Beacon Receiver Interface
Many commercial beacon receivers (not supplied with the IDU) can be connected to ports J11 and J12 on
the rear panel of the IDU. The IDU can accept an analog voltage (0-10VDC, see A on the figure) as long as
the analog voltage is linearly proportional to the tracking signal’s received signal strength in dB.
This configuration is recommended for maximum performance because the IDU will over-sample and
process analog signal to detect scintillation and other effects and take measures to minimize their effect.
The IDU has sensitivity to roughly 10mV of signal change. The measured statistics are available through
the tracking status screen.
Path: HOME Æ Configuration Æ Tracking Config Æ Beacon Rcvr, select a Bcn Data Type of “analog”
3. If satellite is NOT listed in Global Satellite Table, you will need to enter it from scratch by using the
following path: HOME (Main Menu) Æ Configuration Æ TRACKING CONFIG Æ BEACON RCVR and
moving on to Step 4.
4. Make sure the beacon frequency is correct (in L-band, not in C or Ku etc.). Typically, beacon frequency
will be between 950 and 2050 MHz. If you are using an analog beacon receiver, you want this to be
roughly 7.5 to 8 volts. Peak Up the antenna, as you may need to adjust the signal strength and/or add
Beacon Attenuation or Offset
7581691_Rev B Page 120 of 179
4.7 Box Limits
The box limit feature can be used to limit the range of travel for the NGC-IDU when it is tracking a satellite.
Actions taken on hitting a box limit depend on the tracking algorithm. Here are some examples of what is
meant by this:
• Step-track-like algorithms including SmarTrack®’s pause track and must be manually restarted. Hitting
a box limit here is considered a serious fault condition.
• Program track algorithms limit movement to the box limits but continue to track as best as they can.
Hitting a box limit here is not considered a serious condition since the angle is generated
mathematically.
• Position designate and jog commands are not affected by box limits.
To enable box limits, feature must be globally enabled, and individual satellite must have defined box limit set.
To enable box limits globally, use the following path and procedure:
• Path: HOME Æ Configuration ÆTracking Config Æ General
• Navigate to screen 2, select Box Limits, and change the setting to “enabled”
To enable and define box limits for the current satellite, use the following path and procedure:
• Path: HOME Æ Configuration Æ Satellite Æ Working Sat Tbl
• Select the satellite of interest and edit it
• Navigate to screen 2
• Set the Box Limits field to “enforced.” If no limits were defined, the IDU will fill in some limits allowing ±2
degrees El and ±1 degree of Az. Alter these to match the desired limits
At this time, the NGC-IDU does not attempt to calculate box limits using spacecraft data. It is often a good
idea to let the NGC-IDU track the satellite for a day and set the limits using the data collected.
Figure 4-5: Box Limits
Box limits are not recommended for TriFold® mobile antenna systems due to the complexity of maintaining
them, as these systems are designed to be moved from location to location on a regular basis.
7581691_Rev B Page 121 of 179
4.8 SNMP Parameters and Configuration
The NGC-IDU includes an implementation of the Simple Network Management Protocol (SNMP), versions 1
and 2c. It does not currently support SNMP version 3.
Prior to setting up SNMP parameters, you must have the following information:
• SNMP Manager Address
• SNMP Trap Address
• SNMP System Location
• SNMP System Contact
ASC Signal recommends you obtain the information listed above from your network administrator before
attempting to set up SNMP.
The ASC Signal specific enterprise management information base (MIB) is available to qualified customers.
Contact ASC Signal customer support for information.
SNMP v1 and v2c has limited security based on “community strings”. A community string is basically a per-
message password that the SNMP Agent in the NGC-IDU validates against a programmed value.
There are three community strings used:
Table 4.3: Community String Functions
Function Default
Read-only “public”
Read-write “private”
Trap “public”
Figure 5-1: Raster scan
There are two programmable parameters for the raster scan.
• Scan slew distance is the total width of the sector (default is 26 degrees). Set this higher if the
compass uncertainty is causing problems.
• Scan slew speed is the jog speed used for the Az scan. A value of 2 should work for all systems, but it
may be necessary to adjust it.
To edit these parameters, use the following path and procedure:
• Path: HOME Æ Configuration Æ Tracking Config Æ General
• Navigate to page 4 (on screen)
If the signal the system is configured to recognize is not sufficiently unique, the acquisition assist function
may acquire the wrong satellite. This is why it is called “acquisition assist.” Operator should confirm the
satellite acquired is correct.
If the ODU will not change the compass mode to the desired state, the stow or deploy sequence will display
a fault.
Example: At one point, the carrier information below was unique to Horizontal downlink from Astra-1 at 19.2° east:
• Frequency: 12515
• Symbol rate: 22000
• FEC: 5/6
• IQ Swap Off
So, if the user at the adjacent satellites from 45° east to 45° west with this selection, the user would only find a lock at
19.2° east as this combination is unique to that satellite.
Ideally there should be as many unique values as possible and the most useful is the Symbol rate. It is
quite common to find symbol rates of 22000, 27500 and 30000 as these are the rates that most
commercial satellite broadcasters use. More unusual symbol rates are most likely to be unique carriers.
There are other useful tools, such as the following: unusual FEC’s like 7/8 or 1/2, for example, as well as
where IQ Swap is found, can also be helpful in creating unique selections.
Where possible it is essential to find permanent commercial services rather than temporary feeds as it will
most likely be a carrier that is continually broadcast 24 hours and can be relied upon in the future.
One way, used on the ASC Signal APC300, and continued in this product, is to follow the formula:
A+t
P = P0 + I cos( )
D
Where P is the Polarization, P0 the default polarization angle from the satellite table, I the maximum inclination
angle, A the time of max inclination, and t the current time. D is the constant that maps time into the circle for a
sidereal day. Note that any value in the satellite table for this parameter will override the current setting when
the satellite is changed.
To enter this for a satellite, use the following path and procedure:
1. Path: HOME Æ Configuration Æ Satellite Æ Working Tbl
2. Select satellite and edit. Go to screen 4
3. Enter Pol Inc field (I in formula) and Pol Inc Peak Time (A)
When a satellite is selected (ReTune or Goto), these values are copied into the current operation.
To enter this for tracking directly, use the following path and procedure:
1. Path: HOME Æ Configuration Æ Tracking Config Æ General
2. Go to page 4 (on screen)
3. Enter Pol Inc field (I in formula) and Pol Inc Peak Time (A).
Future versions of the NGC-IDU will include the ability to calculate Pol skew offset from Ephemeris data.
Figure 6-3: General Troubleshooting Flowchart #3
NGC-IDU screen is displaying “SRT”
If an SRT SHOULD be
If an SRT should NOT be
present, then the problem will
present, check to ensure that
need to be fixed out at the
no SRT is configured.
NGC-ODU.
Figure 6-5: Communications Troubleshooting Flowchart #2
Front Panel of NGC -IDU does NOT
appear to be connected to the SCP
Operator maintenance consists of cleaning the surface of the unit including the LCD module and performing
key test to check the functionality of the IDU Front Panel Keypad to the right of the TPU or to a keyboard
plugged into the unit.
WARNING: if liquid crystal material leaks from the TPU screen DO NOT allow it to come into contact with your eyes
or mouth. In case of contact with hands, skin, or clothing, wash thoroughly with soap and water.
STOP! This section applies only to FIXED EARTH STATION ANTENNAS that are located in the
SOUTHERN HEMISPHERE. This DOES NOT APPLY TO MOBILE ANTENNAS, which make such
adjustments automatically, or to antennas in the NORTHERN HEMISPHERE.
If you are using a Fixed Antenna and are located in the Southern Hemisphere, you will need to make a setup
adjustment in order to avoid having the NGC read your Az values as “Impossible Angle.”
The NGC antenna control system moves in reference to a set of directional defaults (which are set for the
Northern Hemisphere, with Due North at 0 degrees). Due to this, the IDU will read these defaults in the
Southern Hemisphere as pointing the antenna into the ground, causing an “Impossible” Angle alert to come up.
The process for adjusting values for a FIXED ANTENNA in the SOUTHERN HEMISPHERE is as follows:
1. For location in the SOUTHERN HEMISPHERE, setup the system so that DUE NORTH is 180
DEGREES (the opposite of the usual 0 DEGREES, as is normal for locations in the NORTHERN
HEMISPHERE)
3. Once Az LIMITS have been set, change the HEADING ANGLE to 180 DEGREES by doing one of
the following:
Or
SCP
System Control Processor
Serial I/F Serial I/F to DVB Receiver
Optional DVB
J13
Receiver
Power Power
serial
RJ12 Beacon Serial Interface RPI-6
Rear Panel Interface
Power/Standby KBCPU-1 KB-3
USB
J15
Analyzer
Power
Power
USB
RJ2 +15VDC
Figure B-2: NGC Antenna Control System Block Diagram
B.2 Basic Structure of the NGC-IDU Control Electronics
The IDU control electronics consists of:
• The Touch Panel Unit (TPU), which provides the user interface.
• The System Control Processor (SCP), which provides control and storage.
• The Rear Panel Interface-6 (RPI-6) PWA, which includes an internal network switch for interconnecting
the components, the beacon receiver analog interface, power circuitry, and other functions
• The Keyboard CPU PWA and an attached Keyboard PWA
• Optional spectrum analyzer
Together with the ODU’s MC-7 board, the TPU, SCP, RPI-6, and (optional) Spectrum Analyzer modules are
interconnected using an internal TCP/IP network over 100BaseT. The network addresses are fixed for these
functions and require no configuration.
B.2.1 Touch Panel Interface PWA
The TPU PWA is an ARM9-based embedded Linux system running an open-source GUI program based
on the Nokia Qt/Embedded development environment. Source code to the TPU GUI program will be
supplied to all customers free of charge on request, as per the license for this environment, but this
software is provided as-in with no warranty. The TPU has an integral 800x480 pixel WVGA color graphics
display with 15-bit color (32787 colors) and an integral touch screen interface. It connects via 100BaseT
Ethernet to the network switch on the RPI-6 PWA, which allows it to communicate with the SCP PWA.
The TPU is to be a Technologic Systems TS-7395 single board computer with WVGA display. This is a
200MHZ ARM9 CPU (Cirrus EP9301) running Debian Linux 2.6. This board 128 MB of RAM and 512MB
of NAND-Flash memory, which is used to host the OS and application.
Very little information is stored on the TPU PWA persistently, just some user interface functions. Most
information is stored on the SCP and supplied to the TPU in real time.
B.2.2 System Control Processor PWA
The System Control Processor (SCP) is the central controlling entity. It implements data storage and
tracking functions.
The SCP is a Technologic Systems TS-7300 single board computer. This is a 200MHZ ARM9 CPU (Cirrus
EP9301) running Linux (a specialized distribution from the board vendor) 2.4. This board has 32MB of
7581691_Rev B Page 143 of 179
RAM, a real-time clock module, USB support, two network adapters (one internal and one external), and
two SD card slots.
This system will use the following peripherals from the TS-7300, as described below:
• SD card slot 0 is used to host the operating system. The SD card is formatted in Linux format and
cannot be read with a standard PC.
• Ethernet 0 is connected through the RPI-6 to the outside world
• Ethernet 1 is connected through the RPI-6 to the internal network switch
• UART 0 is the Linux console
• UART 2 (COM3) is used to implement the legacy serial interfaces
• UART 3 (COM4) is used to interface to the DVB receiver
• UART 4 (COM5) is used to control the LEDs on the front panel
The following peripherals are not used: USB interface, remaining serial ports, I/O ports.
The SCP PWA includes an installed analog telephone modem for remote diagnostics. The use of this is
reserved to ASC Signal Corporation.
B.2.3 Real Panel Interface PWA
The RPI-6 PWA is the central glue that connects the other modules in IDU. Functionally, it provides an
internal network switch, optical interface, beacon receiver interface with signal processing functions, power
supplies and management, and other glue functions. It also provides connectorization for the real panel,
which is the basis of the name of the board.
RPI-6 is connected by 100BaseT Ethernet jumpers to the TPU, SCP, and Spec Analyzer.
Electric power in IDU is all at or below +15VDC. The AC-to-DC adapter is an external “brick” device. This
makes the IDU itself a Safety Extra Low Voltage (SELV) device.
RPI-6 is based on a 32-bit NXP LPC2388 microcontroller. This ARM7TDMI embedded processor includes
networking, serial, Ethernet, flash memory, & RAM on a single chip with a 64 MDhrystone CPU core.
The RPI-6 software program uses a multitasking real-time kernel to balance a local network interface,
managing the serial beacon receiver, managing the analog interface, and other functions. RPI-6 also
programs the on-board internal network switch on power up and monitors the switch for failure conditions.
The RPI-6 also can run in a mode where it implements the USB mass storage device class. This
functionality is used to provide a quick software update facility in the field by connecting the USB port to a
host PC, which sees it as a “jump drive”.
The RPI-6 and the SCP exchange data continuously about every 100ms. The SCP sends down
configuration information, and the RPI-6 sends up status information and measured samples from the
beacon interface. All communication between the RPI-6 and SCP is carried over the internal network.
B.2.4 Keyboard CPU and Keyboard PWAs
The KBCPU-2 implements a basic USB Human Interface Device (HID) which looks exactly like an ordinary
keyboard to the TPU, which it is connected to. The KBCPU’s LED functions are interfaced through a
dedicated serial link to the SCP, because USB does not provide an extensible LED interface for keyboard
devices. The KBCPU also implements the soft power switch for the NGC-IDU. The keyboard itself is a
separate PWA which uses capacitive touch technology to implement a keyboard without moving parts. The
keyboard PWA is overlaid with a legend sheet to finish the front panel.
If a standard personal computer external keyboard is plugged into the front panel, it should be recognized,
and can be used for data entry or other tasks. ASC Signal does not recommend leaving a keyboard
connected to the NGC-IDU. Note that no mouse support is provided due to restrictions in the graphics
package.
The KBCPU-2 is based on a 32-bit NXP LPC2388 microcontroller. This ARM7TDMI embedded processor
includes networking, serial, Ethernet, flash memory, and RAM on a single chip with a 64 MDhrystone CPU
core. The Ethernet networking function is not used.
7581691_Rev B Page 144 of 179
The KBCPU-2 software program implements the USB keyboard function and interfaces via serial port to
the SCP to allow for controlling the front panel LEDs color and intensity. Because the USB HID protocol
supports too few LEDs, a serial link is used.
The KBCPU-2 also can run in a mode where it implements the USB mass storage device class; this
functionality is used to provide a quick software update facility in the field by connecting the USB port to a
host PC, which sees it as a “jump drive”.
The KBCPU-2 and the SCP only exchange data as needed. The SCP sends down information to control
the LEDs on the front panel. The KBCPU-2 sends all information to the TPU through the USB channel in
the form of keyboard scan codes.
B.2.5 (Option) Spectrum Analyzer Module
When ordered, an embedded spectrum analyzer module is installed in the chassis at the factory.
This analyzer can be used for several purposes:
• First, it can be used as a general tool for looking at received signals.
• Second, it can be used as a tracking receiver in some configurations.
• Third, it can be used as an acquisition receiver in TriFold® mobile systems in some configurations.
The "in some configurations" caveat has to do with the RF system engineering of the system. If the
broadband IF power on the L-band is much higher than the beacon power, it is possible that the spectrum
analyzer's RF front end will not have enough dynamic range to find a setting that can successfully measure
the beacon. There may be inter-modulation products in the signal as a result. This can be corrected in
many cases by notch filters or other system engineering techniques beyond the scope of this note.
When configured as a tracking or acquisition source, the spectrum analyzer measures the total power of
the beacon on a narrowband sweep. The center frequency used is the frequency programmed for the
current satellite in the Working Satellite Table. The span is 100kHz, the resolution bandwidth is 10kHz (this
resolution bandwidth is wide for the typical beacon and makes the trace look squashed on the screen, but it
gives the best mathematical results). The system integrates the total power for 50kHz around the peak,
adds an arbitrary offset to get this in the clear-sky range (0.0 dB), adds another offset.
Please note that the system is not necessarily designed to support tracking by Spectrum Analyzer and
tracking by Beacon Receiver for the same satellite with all beacon receivers. Because the per-satellite
attenuation field is re-used, it may be difficult to select parameters that work for all situations.
The Spectrum Analyzer software program is supplied by the vendor. The Spectrum Analyzer uses a built-
in LANtronix serial-to-Ethernet converter. The SCP program established a TCP/IP connection with the
Spectrum Analyzer to control and monitor it. The Spectrum Analyzer has a fixed internal network address
assigned at the factory.
B.2.6 Internal Networking
The internal network is implemented as a peer-to-peer mesh of TCP/IP hosts using the 100baseT switch
on the RPI-6 as a central element. Except for the Spectrum Analyzer interface, to simplify protocol design,
all data is sent from processor to processor in one-way isochronous streams called “umbilical data”. Each
stream consists of self-timed messages sent 5 to 10 times per second with lists of data items. Any
processor, restarted, will have a complete set of every data item in a matter of seconds. When data items
change, the sender simply sends out the updated value, and receiver is responsible for noticing changes.
All data exchanged between processors in the system is tagged with universal data indentifiers, and
expressed in “big-endian” byte order. The “endianism” is a slight handicap given than all processors in the
NGC are actually little-endian, but following network byte order is safest given the big-endian application
ancestry and the large base of existing code to handle this orientation. The tagging assures consistent
handling of data throughout the system.
B.5 Tracking
Tracking can be necessary for one or more of several reasons:
• Satellites whose orbit is not nearly perfectly circular and equatorial will move in the sky. Tracking allows the
antenna to follow even satellites with large movements.
• Large antennas, and antennas receiving high frequencies, can have narrow 3dB beamwidth, which means
that they must be positioned accurately even if the satellite motion is small.
• Satellite operators can require active tracking as a condition of permitting the earth station to transmit. They
do this in order to assure that the antenna is correctly 'peaked' on the satellite.
• In some cases, temperature and solar energy effects can slightly distort the antenna's shape, affecting the
"optics", and causing the antenna to slightly mis-point.
An active tracking system can alleviate some or all of these issues.
The IDU is designed to track geosynchronous satellites, including geostationary satellites and satellites with
inclined orbits up to 10 degrees, using a variety of algorithms.
B.5.1 Three-Point Peaking (Step-track)
The IDU uses an algorithm called Three Point Peaking to step-track a satellite. It uses the same algorithm
for all configurations, main dish motors or SRTs. This algorithm is covered by a US Patent.
The algorithm is quite simple. The antenna is deliberately de-pointed by a fraction of the beamwidth and
the signal strength is measured. If the signal strength improves, the antenna is de-pointed again by the
same distance. If the signal strength drops, the antenna is de-pointed in the opposite direction by twice that
value. The system collects data until it sees three points with a peak in the geometric center, at which point
it fits the measured values to a parabolic curve with the equation and calculates the mathematical
maximum point (where x=0). It then moves there and repeats the algorithm on the opposite axis.
If the SRT is provisioned with a Z axis, a third cycle is added to focus the antenna. In practice this achieves
excellent pointing accuracy with a minimum number of movements.
There are several programmable parameters that affect the algorithm. The antenna size, LNB local
oscillator, and the beacon frequency are used to compute the nominal 3dB beamwidth of the antenna using
a generic formula that tends to be reasonably accurate.
Where f is the downlink frequency is GHz and A is the antenna diameter in meters. This value is multiplied
by the step multi factor to get a step distance. The selection of the antenna size and LNB local oscillator
frequencies is obvious and comes from the system equipment design.
7581691_Rev B Page 147 of 179
Selecting the step multiplier factor requires decisions because a trade-off is involved. If the step multiplier
factor is large, the temporary loss during de-pointing may be larger than desired. However, because the
loss is more "defined" than a smaller jump relative to the noise present in the beacon level, the
mathematics will get a better solution. If there is a need to constrain maximum loss, the installer should
pick a smaller step size. However, this will mean slightly less overall accuracy since the noise power in the
signal is more significant, and will probably mean more steps to find the maximum. Also, if the step size is
smaller than the minimum pointing capability of the antenna, the tracking algorithm may be handicapper.
ASC Signal cannot advise as to what value is most appropriate for a situation and the user may have to
find it by analysis of results.
The algorithm, like all tracking algorithms, is only as good as the pointing performance of the antenna.
Because of the functional decomposition of the NGC system, this performance is completely controlled by
the ODU and its interface.
The performance factors of the antenna that can affect step-tracking performance include, but are not
limited to, the following:
• Repeatability and stability of resolver or encoder feedback, including hysteresis
• Suitable tuning of axis control variables for the ODU’s PID control loops
• Stiffness and repeatability of the antenna structure itself
Step-tracking is not particularly sensitive to antenna calibration beyond finding the satellite in the first place.
It is not particularly sensitive to physical distortion of the antenna due to heat, droop, or the notional ‘steady
state wind.’ It is not particularly sensitive to the absolute accuracy of the resolver or encoder.
This mode requires a beacon receiver or other receiving system to serve as a feedback mechanism. The
signal strength must be a reasonable proxy for the pointing accuracy of the system.
B.5.2 (Software option) Orbital Prediction Tracking (SmarTrack®)
SmarTrack® is a patented algorithm that uses step-track information to estimate the orbital parameters of
the vehicle (the satellite "model") and predict its trajectory through the sky. It is only designed to work with
geosynchronous satellites.
It takes roughly six hours for the algorithm to collect enough data to create a solution. During this interval
the operation of the system will be exactly the same as step track.
Once the model is created and the solution is reliable, the predictions are used as long as the signal
strength is maintained. If the signal drops unexpectedly, or whenever the cycle times out, the algorithm
collects a new data point and updates the model. If the signal drops below the low signal threshold, the
algorithm becomes purely predictive and attempts to follow the satellite's motion until it returns.
There are several parameters to tune this interface. The repeak trigger tells how much loss is acceptable
before the algorithm attempts to repeak. The cycle time is the maximum interval between model updates
for the sake of time. The minimum move is the amount of total movement between the projected angle and
the actual angle before the algorithm will actually move the antenna.
Path: HOME Æ Operations Æ Track Æ Status Æ SmarTrack® Mdls screen
The model is very technical, but at the end of the file there is some information that may be of general use:
• Inclination is the estimated inclination of the satellite. This tends to be slightly more than the true
inclination because of hysteresis (wind up) in the axes.
• Eccentricity is the estimated eccentricity. Again, this can be slightly exaggerated for the same reasons
as inclination.
• East longitude is the "east longitude of the mean anomaly".
• argPerigee is the argument of perigee
• phi0 should be roughly 0. If it is not, it indicates some small error in the setup.
• totalLoss is a metric of the accuracy of the model. It is the RMS error, in dB, of the difference between
retrospectively-predicted positions and actual peaks in the measurement cycles, converted to dB using
the beamwidth of the antenna.
This mode requires a beacon receiver or other receiving system, and a license key with the appropriate
feature enabled. The feature can be enabled in the field by entering a new license key.
The algorithm, like all tracking algorithms, is only as good as the pointing performance of the antenna.
Because of the functional decomposition of the NGC system, this performance is completely controlled by
the ODU and its interface. It also has other factors that affect it.
The performance factors of the antenna that can affect SmarTrack® performance include, but are not
limited to:
• Repeatability and stability of resolver or encoder feedback, including hysteresis
• Suitable tuning of axis control variables for the ODU’s PID control loops
• Stiffness and repeatability of the antenna structure itself
• When in predictive mode, the algorithm is dependent on physical distortion of the antenna due to heat,
droop, or the notional ‘steady state wind’. If these factors create losses within the step RePeak trigger,
the IDU will tolerate them and lose accuracy
SmarTrack® is not particularly sensitive to antenna calibration beyond finding the satellite in the first place.
It is not particularly sensitive to the absolute accuracy of the resolver or encoder.
This mode requires a beacon receiver or other receiving system to serve as a feedback mechanism. The
signal strength must be a reasonable proxy for the pointing accuracy of the system.
B.5.3 (Software option) Program Tracking (NORAD and Intelsat)
NORAD and Intelsat are predictive tracking modes that use different algorithms to predict the look angle of
a satellite using measured orbital parameters. They are different algorithms using different data sets but
they product similar results. They are very useful for tracking satellites where no beacon receiver
equipment is present.
Periodically, the algorithm computed the estimated position of the satellite and projects the look angle. The
NGC adapts to the predicted motion of the satellite in determining how often to re-compute the estimated
position. If the estimated position is more than the minimum move, the IDU will move the antenna to match
the new position.
This mode requires a license key with the appropriate feature enabled. A beacon receiver can be helpful
but is not required. The feature can be enabled in the field by entering a new license key.
The algorithm, like all tracking algorithms, is only as good as the pointing performance of the antenna.
Because of the functional decomposition of the NGC, this performance is completely controlled by the
NGC-ODU and its interface.
The performance factors of the antenna that can affect program tracking performance include, but are not
limited to:
• Repeatability and stability of resolver or encoder feedback, including hysteresis
• Suitable tuning of axis control variables for the NGC-ODU’s PID control loops
• Stiffness and repeatability of the antenna structure itself.
• The algorithm is dependent on physical distortion of the antenna due to heat, droop, or the notional
‘steady state wind’.
• The algorithm is highly sensitive to antenna calibration.
Once the appropriate offsets have been determined and configured, it is not particularly sensitive to the
absolute accuracy of the resolver or encoder over large distances, but it is highly sensitive to nonlinearity
over the range of travel for the current satellite.
Due to limitations in the off-the-shelf product used to implement SNMP, certain configurations may require
ASC Signal to make small modifications to the configuration of the SNMP Agent. Specifically, permanent
trap destinations that survive system power cycle cannot be altered from any supported interface.
When the system is in “Local” or “Local Handheld” mode, almost all “read-write” object IDs (OIDs) in the
MIB are presented as “read-only.” The management station can override this by forcing the item
acs4000LocalRemote.1 to “remote.”
B.6.2 Serial Interface
The NGC Antenna Control System includes a serial port interface to implement subsets of certain legacy
M&C protocols for APC100, APC300, and APC400.
This interface is highly limited. It is not recommended for new designs, and not recommended for control of
the system regardless of settings, although it can be used for minimum monitoring.
The basic problem is the legacy protocols are device-specific and emulation is somewhat limited. Another
problem is the IDU simply has more data than the earlier systems and the M&C protocol cannot express all
of the necessary items.
ASC Signal strongly recommends the use of SNMP to monitor and control the system. Alternately,
advanced users can use the open-source TPU software package as a basis for a control system, although
ASC Signal cannot support this effort as that code is supplied for that purpose without warranty.
NOTE: For APC100 mode, when the system is in “Local” or “Local Handheld” mode, almost all set commands are
rejected. The management station can override this through an NGC-specific extension to the APC100 protocol.
The analog interface is a 0 to 10V DC signal from the beacon receiver to the IDU. The voltage is
proportional to the measured signal strength, usually (but not always) at a ratio of 2.0 dB per volt. Ideally
the peak voltage of the beacon receiver should be about 7.5 to 8.0 volts; this provides adequate dynamic
range for rain fades and tracking but also avoids hitting the high limit.
The serial (aka "digital") interface is an RS-232, RS-422, or RS-485 interface to the beacon receiver which
can be used for configuration and control of the beacon receiver. The use of this interface is not required; it
is, however, mandatory if the IDU is required to be able to re-tune the beacon receiver when moving
between satellites.
Different beacon receivers have different configuration requirements due to different capabilities. For
example, an Atlantic Satellite ASC300-L requires only the frequency and attenuation level to be set; this
receiver can be completely controlled from the IDU. The Miteq BR-L has far more parameters and while the
NGC can control it to some extent, it is better to interface to this with an M&C system (not supplied).
The IDU can use signal strength readings reported serially from the beacon receiver if desired. ASC Signal
recommends the analog interface because the IDU can over-sample this signal and measure not just the
signal levels but the scintillation in the signal levels. Generally, the serial interface does not provide this
information. However, it may be desirable in some systems, especially if the installer is trying to re-use a
legacy beacon receiver that is not configured for 0-10VDC operation.
Heading True heading that corresponds to 0 degrees for Degrees, Yes, Status Æ or
platform Az 0 to 359.999 typicall Configuration Æ
y0 Platform
HW Address MAC Address of Ethernet MAC address Yes Configuration Æ
System Setup
Intelsat Life Expiration criterion for Intelsat data sets Days Yes Configuration Æ
Tracking Config Æ
General
IP Address Network address of external ethernet port IP address Yes Configuration Æ
System Setup
IP Mask Network mask of external Ethernet port IP address Yes Configuration Æ
System Setup
J9 Emulation Configures which protocol to emulate on J9 on APC100 Yes Configuration Æ
the rear panel System Setup
Jog Speed Jog speed for Az and El axes 0 to 9 No Operations Æ
MovementÆ Move
Ant.
Latched Faults Alarms reported by NGC since last time latch List (see No Status Æ Faults
was cleared including ones that have gone away Appendix D &
Table C.30)
Table C.3: Axis Limit Conditions, Azimuth, Polarization, and SRT X axes
These are the limit conditions commonly reported by the NGC-ODU for axes with clockwise and
counterclockwise directions.
Value Meaning Comment
---- No device present, option not selected
CCW limit Counterclockwise hardware limit Takes precedence over soft CCW limit
CW limit Clockwise hardware limit Takes precedence over soft CW limit
Limit fault Usually means both hardware limits are active at same Repair required
time
off No limit active
Soft CCW limit Clockwise software limit Configurable limit
Soft CCW limit Counterclockwise software limit Configurable limit
This is an emulation, as best as the NGC-IDU can implement it. The NGC-IDU, however, is not an APC100,
and does not derive software source code or other functionality directly from the APC100, so differences in
behavior and likely to exist. Differences are documented within this manual wherever possible.
ASC Signal Corporation has made every effort to make the NGC-IDU transparently emulate the APC100 as
much as possible, but M&C programs should still be retested to ensure compatibility.
• A general rule is that the NGC-IDU will report the actual value it is using rather than reporting an
emulation of the value that the APC100 would have used. This can mean small differences between
values uploaded from the values downloaded where units are different.
• Status information from the NGC-IDU to the M&C system is supported. The other direction except for
movement commands is implemented but may have unexpected results, because the APC100 had far
less information than the NGC-IDU does.
• The NGC-IDU is more liberal in accepting commands from the serial port than the APC100 was, and
many commands and data operations will work when the unit is in LOCAL mode. This is because the
data design of the NGC-IDU can more accurately deal with multiple command sources. It is
recommended, but not necessary, that the control system examine the LOCAL/REMOTE bit in the
status field and not issue commands if the unit is in LOCAL mode.
• The NGC-IDU has more configuration settings, in general, than the APC100, so the UP and DP
commands cannot and should not be used to attempt to restore the state of a system.
• Note also that this is a legacy protocol so improvements to it cannot be made without impacting existing
installations.
• The NGC-IDU does not allow for emulation of this protocol over the TCP/IP network in the current
software system.
• Do not attempt to export parameters from the NGC-IDU and upload to an APC100, this is not
supported.
• New working table satellites uploaded through the APC100 interface will be very incomplete. This is not
recommended or supported.
NOTE: configuration of the NGC-IDU over this interface should be attempted only with extreme caution.