Please note, the Antenna-Tracking device is no longer maintained and should not be used for new M&C installations.
The Antenna-Tracking logical device is a 'high level' driver for motor driven antennas. It is used together with a driver for the type of antenna controller used. To operate the device in step track modes, also a beacon receiver is required. The Antenna-Tracking device provides three mayor tracking modes:
Device window pages
The following table shows which device window pages are available with this individual device type. Tool-bar functions not mentioned here are described at the general description of device windows .
--- Basic tracking parametersThe primary page contains the basic tracking parameters like the nominal antenna position or the mayor tracking mode. This page also gives access to the logging and analysis tools built into the tracking device. The most important parameters are explained below:satellite name: This ist the name of the satellite as it appears in the list of stored targets. When you read in ephemeris data which contains a satellite name, the latter gets copied into this field. You may however enter any other name.nominal orbit: With this parameter the satellite's nominal orbit position is specified. There are two applications for the nominal orbit value in the software: The tracking device is capable to evaluate the antenna pointing angles for the orbit position, you may move the antenna to the resulting position in order to find a new satellite quickly. Also the orbit value is used to identify and sort satellites in the target list.The nominal orbit position has to be entered as 'deg. east' To specify a satellite at 10° West, either enter -10.0 or 350.0, the software accepts both notations.tracking mode: With this parameter you select the major tracking mode. Available modes are:
--- Satellite listThe satellite list page permits to store tracking settings in a target memory pool which is unique to this instance of the Antenna-Tracking device. This is unlike the standard device preset function if the sat-nms software which stores device settings for all instances of one device type at a central place. The following functions are provided by this page:Save actual satellite: Clicking to this button stores the actual tracking parameters together with the nominal antenna pointing into a data file named after the actual satellite name followed by the nominal orbit position. If a file of this name already exists, it gets replaced.Delete seleted entry Deletes the selected (yellow colored) target memory file.Load selected parameters Loads all tracking parameters except the nominal antenna pointing from the selected target memory. This is intended to be used to copy the tracking settings from an already known satellite to a new one, which actually is being set up.Track selected satellite Loads all settings including the nominal antenna pointing and the tracking mode. Moves the antenna to the nominal pointing position and starts the selected tracking mode there.
--- Orbital modelAt this page you may define an orbital model for the satellite which is used with the PROGRAM tracking mode. The orbital model also may be used to find a satellite more precisely than by it's nominal orbital position.The tracking engine accepts either Keplerian elements in NASA 2-line format or Intelsat ephemeris data. The software automatically recognized the data format and chooses the appropriate orbital model. A common source for actual Keplerian ephemeris data is www.celetrak.com , weekly updated Intelsat orbital data may be found on the Intelsat web site.The easiest way to enter the orbital data to the tracking system is by copy & paste from the source web site. Clear the orbital data field, mark the desired orbital data in the web browser window and copy it into the orbital data entry field (use CTRL-C/CTRL-V on Windows based PC, the middle mouse button on Linux boxes like the sat-nms ACU indoor unit. For Intelsat data, copy the whole web page which shows the ephemeris data set. For Keplerian data copying the two lines containing the element data is required. When using data from Celestrak, you optionally may copy also the comment line above the element data, the satellite name will be adapted automatically in this case.Once you entered / copied the orbital data and change the input focus to another field, the software analyzed the data and updates the fields at the top of the page. The 'recognized orbital model' shows the type and age of the interpreted ephemeris data. The 'satellite name' and 'nominal orbit' are updated accordingly, if this information is present in the entered data. If you select the PROGRAM tracking mode on the primary parameter page, the antenna follows the position of the satellite as computed from the ephemeris data.Using the buttons below the orbital data entry field you may compute the actual antenna pointing either from the entered ephememeris data or from the satellite's nominal orbit position. Clicking to the large button at the bottom move the antenna to the computed position. This function is intended to be used to find a new satellite quickly. If there is no orbital data available for the satellite you search, you may enter it's nominal orbit position directly and compute the antenna pointing from this.The accuracy of the calculated antenna positions heavily depends on the antenna pointing calibration and on the accuracy of the antenna's geodetic location as defined with the configuration parameters.
--- Advanced step track parametersThis page contains a number of parameter which are used to tune the tracking algorithm. Most of these parameters affect the STEP and ADAPTIVE tracking modes as well.step size: This parameter controls the sizes of the search steps the tracking engine performs in the STEP and ADAPTIVE modes. With the step size set to 100%, the elevation test step is one half of the antenna's 1dB bandwidth. The azimuth step size is computed the same way, but divided by cos(elevation) to deskew look angle to the satellite. The antenna's beamwidth (approximately) is computed from the beacon frequency and the antenna diameter. A good initial value for the step size is 60%.settling time: The settling time is the time the tracking engine waits after it issued an antenna pointing command until it takes the first sample of the beacon level. Specially with small steps of the antenna position, the tracking engine has no real feedback when the antenna has reached it's final position. This delay time is used to ensure that the antenna pointing command has been executes and the beacon level has settled.step mode: In STEP mode, this parameter controls how the tracking engine selects the direction of a search step. With the SLOW step mode, search steps alternately are made in the one or the other direction. This step mode gives good results with satellites that move only a small amount. With the FAST step mode, each search step is made in the same direction of the last successful optimization step. With any unsuccessful step the direction changes. This mode is recommended to track inclined orbit satellites, because the tracking does not perform search steps against the satellite movement in the majority of cases. In the ADAPTIVE tracking mode, the tracking engine observes the step mode selection only as long as it cannot compute a usable model from the records steptrack data. Later it uses the the modeled antenna pointing to decide where to go for a search step.max optimization: The step track algorithm uses the measured beacon levels before a search step and after it together with some knowledge about the shape of the antenna beam to compute the peak location. Unexpected variations of the beacon level may disturb the measurement and may result to a wrong peak evaluation. To minimize the impact of this to the antenna pointing, the tracking algorithm limits the amount of an optimization step to this value. Setting this parameter to 0% forces the tracking engine to limit the peak position to a window between the antenna positions before and after the search step. Increasing the 'max optimization' parameter widens this window at both edges with the actual search step size multiplied by the 'max optimization' value.With the ADAPTIVE tracking mode this parameter is used, too. Here however it acts as a fault threshold: If a peak is outside, is is marked as invalid and not included to the tracking model computation.az/el search step: These fields show the actual search step sizes as absolute angles for you orientation. The fields get updated each time you change the 'step size' parameter.az/el window: These parameters define a rectangular window around the nominal antenna position. The tracking engine limits the optimization movements to this window.beacon averaging time: This parameter defines the time, while samples read from the beacon receiver get averaged to achieve one beacon level value. Recommended values are between 15 and 30 seconds, if the beacon receiver itself performs an effective averaging/smoothing of the level reading, shorter values may be possible.max standard deviation: While the program averages the beacon level readings, it also computes the standard deviation of the reading as a measure of the (short term) stability of readings. If the standard deviation exceeds this limit, the measurement is discarded.max signal drift: Before performing a search step, the tracking algorithm requires two beacon measurement series to differ not more than the value defined here. Otherwise the beacon level is assumed to drift, the search step is postponed or canceled.max drop in search step: If with a search step the beacon level drops more than the value set here, the antenna moves back to the previous or predicted position, no peak evaluation is done.min beacon level: If the measured beacon level falls below this value, a beacon level fault is risen and the measurement is marked as invalid. With the STEP tracking mode no tracking is performed until the beacon level is above the threshold again. In ADAPTIVE mode, the tracking engine tracks the satellite following the mathematical model made from the step track peaks.
--- Faults and fault maskBeacon receiver: The beacon receiver device states a fault. This may be a hardware fault or a loss of signal. It is recommended to switch of any level threshold monitoring at the beacon receiver and let the tracking device monitor the beacon level. The tracking device applies threshold monitoring only during the measurement phases, signal dropouts during the antenna movement phases are ignored.Beacon level: The measured beacon level is below the threshold set at the advanced step track parameters page.AZ/EL window limit: The recent step track peak found is outside the window limits set at the advanced step track parameters page. The antenna has been moved to the window limit rather than to the peak position. The fault stays active until the next tracking step.Antenna: The antenna positioning controller states a fault. This may be a motor failure, limit switch or another specific antenna fault.Search step size: The tracking engine is not capable to compute a valid tracking step size from the given data. This happen if either the antenna diameter (a setup parameter) or the beacon frequency is not set properly. The fault stays active until the missing value is set.AZ/EL Model match: In ADAPTIVE tracking mode, a tracking step found a peak which considered to be invalid at it is too far away from the position computed by the model. The fault stays active until the next tracking step.
--- The device info page.
--- The maintenance page. The configuration parameters described below are set at this page.
Configuration parameters
At the maintenance page of the device window there are a couple of configuration parameters which must be set to make the Antenna-Tracking device work properly.
| parameter | description |
|---|---|
| config.azimuthId | Enter here the parameter ID of the azimuth target value the tracking unit shall use. Example: 'ODU.azimuth' |
| config.stateAzId | Enter here the parameter ID of the azimuth read out value the tracking unit shall use. Example: 'ODU.state.az' |
| config.elevationId | Enter here the parameter ID of the elevation target value the tracking unit shall use. Example: 'ODU.elevation' |
| config.stateElId | Enter here the parameter ID of the elevation read out value the tracking unit shall use. Example: 'ODU.state.el' |
| config.polarizationId | Enter here the parameter ID of the polarization offset target value the tracking unit shall use. The tracking unit does no polarization, however a fixed polarization offset value is stored together with each target. Example: 'ODU.polarization' |
| config.antennaFaultId | Enter here the parameter ID of the antenna fault, the tracking unit shall monitor. |
| config.bcrxFreqId | Enter here the parameter ID of the beacon receiver frequency setting. The tracking unit sends the receive frequency stored with a target to this parameter (RF frequency, not L-band). Leave this field empty, if the beacon receiver frequency cannot be controlled through the sat-nms software. Please note, that in the tracking unit the beacon frequency must be set to the correct value even if it is not passed to the beacon receiver. This is because the tracing unit computes the step track search sizes from the beacon frequency. |
| config.bcrxLevelId | Enter here the parameter ID of the beacon receiver level reading. The value is expected to be a receive level in dBm or a C/N value [dB]. To read the analog output value of a tracking receiver, you need an external device which reads this voltage and converts the readint to dBm. The sat-nms Antenna Control Unit ODM is capable to do this. |
| config.bcrxFTrackId | If you are using a sat-nms L-band beacon receiver together with this tracking device, enter 'BCRX.ftrack.fast' here, replace BCRX by the device name of the beacon receiver. This tells the tracking engine to perform a synchronous frequency tracking step on the beacon receiver before each antenna tracking step. |
| config.bcrxFaultId | Enter here the parameter ID of the beacon receiver fault, the tracking unit shall monitor. |
| config.xDiameter | This parameter tells the tracking device the width of the antenna dish. The tracking device computes the azimuth tracking step size from this parameter and the beacon frequency value. |
| config.yDiameter | This parameter tells the tracking device the height of the antenna dish. The tracking device computes the elevation tracking step size from this parameter and the beacon frequency value. |
| longitude | The antenna's longitude (degree east). Provide this value with an accuracy of 0.01° to ensure a precise orbit to pointing calculation |
| latitude | The antenna's latitude (degree north). Provide this value with an accuracy of 0.01° to ensure a precise orbit to pointing calculation |
| altitude | The antenna's altitude over sea. Provide this value with an accuracy of 10 meters to ensure a precise orbit to pointing calculation |
Built in analysis tools
The Antenna-Tracking device is capable to show two different types of diagrams which support you to monitor and optimize the tracking behaviour.
The first diagram tool is the X/Y display of the antenna movements. This display works completely autoscaled, it shows one green dot for each antenna position the tracking memorizes (usually the recent 48 hours). The actual antenna pointing is marked with a slightly larger yellow dot. After at least 24 hours of continuous operation, the antenna position dots give the curve of the daily movement of the satellite, from the antenna's angle of look. With a mouse click to the diagram area, the display cas be switched into a Y/T diagram showing the recent 48 hours. This condensed display of the azimuth, elevation and beacon level variations over 48 hours is meant as an overview display. A second mouse click switches back to the previous view.
The separate Y/T display window gives more detailed information about what the tracking engine did during the recorded 48 hours. It provides variable scales, and permits to display additional information. The display shows either the azimuth or the elevation pointing found at the beginning of each each tracking step together with the beacon level measured at this time. The following additional information may be included to the diagram:
--- If this toolbar button is pressed, the diagram shows the search step and the beacon level change resulting from this as a dimmed peak at the left edge of each data point. You can easily monitor the signal degradation which is caused temporarily by the tracking search steps with this function enabled.
--- If this toolbar button is pressed, the diagram includes the evaluated peak positions. In STEP track mode, this actually is the location where the antenna gets moved to. In ADAPTIVE tracking mode, the antenna moves to the location resulting from the mathematical model which is computed from the step track peaks. In the latter case, the peak positions may be interpreted as the actual difference between the modeled pointing and the peak position.Recommended beacon receiver settings
Below some recommended settings for the sat-nms L-band beacon receiver for the use with the tracking device are listed. These settings have proved to work satisfactory in most cases. If you are using a third party beacon receiver, use analogous values a starting point.
Variables defined by this device driver
| name | type | flags | range |
|---|---|---|---|
| info.driver | TEXT | R/O | StringRange R/O |
| info.type | TEXT | R/O | StringRange R/O |
| info.port | TEXT | R/O | StringRange R/O |
| info.frame | TEXT | R/O | StringRange R/O |
| config.azimuthId | TEXT | SAVE SETUP | StringRange |
| config.stateAzId | TEXT | SAVE SETUP | StringRange |
| config.elevationId | TEXT | SAVE SETUP | StringRange |
| config.stateElId | TEXT | SAVE SETUP | StringRange |
| config.polarizationId | TEXT | SAVE SETUP | StringRange |
| config.antennaFaultId | TEXT | SAVE SETUP | StringRange |
| config.bcrxFreqId | TEXT | SAVE SETUP | StringRange |
| config.bcrxLevelId | TEXT | SAVE SETUP | StringRange |
| config.bcrxPolId | TEXT | SAVE SETUP | StringRange |
| config.bcrxInhibitId | TEXT | SAVE SETUP | StringRange |
| config.bcrxFaultId | TEXT | SAVE SETUP | StringRange |
| config.xDiameter | FLOAT | SAVE SETUP | DoubleRange (0.0 .. 0.0) |
| config.yDiameter | FLOAT | SAVE SETUP | DoubleRange (0.0 .. 0.0) |
| config.longitude | FLOAT | SAVE SETUP | DoubleRange (0.000 .. 0.000) |
| config.latitude | FLOAT | SAVE SETUP | DoubleRange (0.000 .. 0.000) |
| config.altitude | FLOAT | SAVE SETUP | DoubleRange (0 .. 0) |
| azimuth | FLOAT | SAVE | DoubleRange (0.00 .. 0.00) |
| elevation | FLOAT | SAVE | DoubleRange (0.00 .. 0.00) |
| polarization | FLOAT | SAVE | DoubleRange (0.0 .. 0.0) |
| trackMode | CHOICE | SAVE | EnumRange (OFF STEP ADAPTIVE PROGRAM) |
| polPlane | CHOICE | EnumRange DIS (H V) | |
| frequency | FLOAT | DoubleRange (0.000 .. 0.000) | |
| interval | INTEGER | SAVE | IntegerRange (0 .. 60) |
| name | TEXT | SAVE | StringRange |
| elements | TEXT | SAVE | StringRange |
| orbit | FLOAT | SAVE | DoubleRange (0.0 .. 0.0) |
| stepSize | INTEGER | SAVE | IntegerRange (0 .. 200) |
| stepMode | CHOICE | SAVE | EnumRange (FAST SLOW) |
| optimizeSize | INTEGER | SAVE | IntegerRange (0 .. 200) |
| averagingTime | INTEGER | SAVE | IntegerRange (1 .. 120) |
| settlingTime | INTEGER | SAVE | IntegerRange (1 .. 120) |
| dazMax | FLOAT | SAVE | DoubleRange (0.0 .. 10.0) |
| delMax | FLOAT | SAVE | DoubleRange (0.0 .. 10.0) |
| driftMax | FLOAT | SAVE | DoubleRange (0.00 .. 10.00) |
| dropMax | FLOAT | SAVE | DoubleRange (0.00 .. 10.00) |
| sdevMax | FLOAT | SAVE | DoubleRange (0.00 .. 10.00) |
| beaconThreshold | FLOAT | SAVE | DoubleRange (-100.0 .. 0.0) |
| state.saz | FLOAT | R/O | DoubleRange R/O (0.000 .. 0.000) |
| state.sel | FLOAT | R/O | DoubleRange R/O (0.000 .. 0.000) |
| state.daz | FLOAT | R/O | DoubleRange R/O (0.000 .. 0.000) |
| state.del | FLOAT | R/O | DoubleRange R/O (0.000 .. 0.000) |
| eval.az | FLOAT | R/O | DoubleRange R/O (0.000 .. 0.000) |
| eval.el | FLOAT | R/O | DoubleRange R/O (0.000 .. 0.000) |
| eval.pl | FLOAT | R/O | DoubleRange R/O (0.000 .. 0.000) |
| state.mode1 | TEXT | R/O | StringRange R/O |
| state.mode2 | TEXT | R/O | StringRange R/O |
| state.mode3 | TEXT | R/O | StringRange R/O |
| state.mode4 | TEXT | R/O | StringRange R/O |
| state.beacon | FLOAT | R/O | DoubleRange R/O (0.00 .. 0.00) |
| state.elements | TEXT | R/O | StringRange R/O |
| reset | TEXT | NOPRESET | StringRange |
| evalByOrbit | TEXT | NOPRESET | StringRange |
| evalByElements | TEXT | NOPRESET | StringRange |
| moveEvaluated | TEXT | NOPRESET | StringRange |
| slist.select | CHOICE | NOPRESET | EnumRange () |
| slist.action | TEXT | NOPRESET | StringRange |
| faults.01 | ALARM | R/O | AlarmFlagRange R/O (Beacon receiver) |
| faults.02 | ALARM | R/O | AlarmFlagRange R/O (Beacon level) |
| faults.03 | ALARM | R/O | AlarmFlagRange R/O (AZ window limit) |
| faults.04 | ALARM | R/O | AlarmFlagRange R/O (EL window limit) |
| faults.05 | ALARM | R/O | AlarmFlagRange R/O (Antenna) |
| faults.06 | ALARM | R/O | AlarmFlagRange R/O (Search step size) |
| faults.07 | ALARM | R/O | AlarmFlagRange R/O (AZ Model match) |
| faults.08 | ALARM | R/O | AlarmFlagRange R/O (EL Model match) |