Page 3
Nera SatLink Terminal User Guide – Revision P Nera SatLink Terminal User Guide...
Page 4
Satellite AS makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties or merchantability and fitness for particular purposes. Moreover, Nera Broadband Satellite AS shall not be held liable for errors that may occur herein or for incidental or consequential damage in connection with the furnishing, performance, or use of this material.
Nera SatLink Terminal User Guide – Revision P Table of Contents INTRODUCTION ......................5 This User Guide......................6 Configuration tool overview ...................7 UNPACKING .........................8 INSTALLATION ......................8 Before installation ......................8 SatLink Terminal front and back panels ................9 IDU Installation ......................12 Antenna installation .....................13 Interface connections ....................13...
Page 6
Nera SatLink Terminal User Guide – Revision P DEFINITIONS, ACRONYMS AND ABBREVIATIONS..........56 REFERENCES ......................57 APPENDIX A. USING THE WEB INTERFACE ..............58 APPENDIX B. ACCESSING THE COMMAND LINE INTERFACE VIA RS-232 ....73 APPENDIX C. TFTP SERVER....................76 APPENDIX D. TELNET CLIENT .....................77 APPENDIX E.
Nera SatLink Terminal User Guide – Revision P 1. Introduction The Nera SatLink 1000, 1900, 1901 and 1910 are members of the Nera SatLink Terminal family of DVB- RCS Terminals. They act as IP routers to interface one or more PCs for bilateral communication via the satellite network.
The information given pertains to the following software (SW) and hardware (HW) versions and releases: SatLink IDU Software • Nera SatLink Boot loader, P/N 101225, SW build 1.8.0.2 and later • Nera SatLink Boot loader, P/N 106267, version 9.0.0 and later •...
Channel Master Type 243 – 2.4m Right Hand Circular Polarisation, P/N 105282 Configuration tool overview The Nera SatLink Terminal must be configured before it can communicate via the satellite to and from the network operator Gateway. The parameters to be configured are explained in section 6.2.
If possible, send another person to get medical aid. Otherwise, assess the condition of the victim and then call for help. • Determine if the victim needs artificial respiration or external cardiac compressions; then take appropriate action. 3.1.2 Site requirements The Nera SatLink Terminal shall be connected to the mains 110/230 VAC, 50-60Hz.
Nera SatLink Terminal User Guide – Revision P SatLink Terminal front and back panels 3.2.1 SatLink 1000 front and back panel Figure 4: SatLink 1000 Front panel Colour, indicates Blue, lights steadily when power switch is on and unit is powered. Flashes when loading Power software.
Page 12
Nera SatLink Terminal User Guide – Revision P 3.2.2 SatLink 1910 front and back panel Figure 6: SatLink 1910 Front panel Colour, indicates Blue, lights steadily when power switch is on and unit is powered. Flashes when loading Power software.
Page 13
Nera SatLink Terminal User Guide – Revision P 3.2.3 SatLink 1900 and 1901 front and back panels Figure 8: SatLink 1900 and 1901 front panel. Colour, indicates Blue, lights steadily when power switch is on and unit is powered. Flashes when the software Power is loading.
The Nera SatLink 1900/1901/1910 can be mounted in any EIA-standard 19-inch telecommunications rack or cabinet. The Nera SatLink 1000 needs to be placed on a shelf if it is to be placed in a rack. Use a Torx screwdriver and attach the mounting brackets to the router with the screws supplied. Hold the unit securely, brackets attached, and move it vertically until rack holes line up with the bracket notches, then insert and tighten the four screws holding the brackets to the rack.
Toggle to NODE when connecting to an Ethernet switch or an Ethernet hub and toggle to HUB when connecting to a single PC. For the Nera SatLink 1000 and 1910 there is no push button on the back panel as Ethernet HUB or NODE mode will be auto-detected and the correct mode chosen automatically.
Nera SatLink Terminal User Guide – Revision P 4. PC configuration After installation as described in Chapter 3 is carried out, the Nera SatLink Terminal is ready to be powered on. Windows TCP/IP configuration Verify that the TCP/IP configuration for PCs connected to the Terminal LAN is correct. Push the start- button in Windows, select the Control panel and then open Network Connections.
Page 17
4.1.1 Dynamic IP configuration of PCs connected to the Nera SatLink Terminal LAN By default the DHCP server in the Nera SatLink Terminal is enabled. When the Nera SatLink Terminal is powered on, all PCs connected to the Nera SatLink LAN can automatically retrieve their IP configuration from the DHCP server.
Page 18
4.1.2 Static IP configuration of PCs connected to the Nera SatLink Terminal LAN When the DHCP server in the SatLink Terminal is disabled, all PCs attached to the Nera SatLink Terminal LAN must be configured with static IP addresses that are within range of the Nera SatLink Terminal subnet (see section 6.2.1).
Nera SatLink Terminal as well as for showing status and reports. Start-up sequence When turning on the Nera SatLink Terminal first the Boot SW is loaded. A message such as the one below is displayed on the CLI/RS-232 when the boot SW starts. Note that Telnet is not available before the application has been started.
: IP configuration misc : Miscellaneous commands : ODU configuration : Software upgrade configuration user : User configuration : Event log Nera SatLink Terminals that have Boot SW release 8.x.x or earlier, will have factory default password satlink for the install user.
Logging of events The Nera SatLink Terminal logs certain events to a log stored in RAM. See Appendix J.4 for a list of the different events and what action that need to be taken for the different events. Use the CLI command to show the log from memory.
Nera SatLink Terminal User Guide – Revision P CLI command summary The available CLI commands are listed below. CLI commands Available in Available in User Boot Application Privilege Level ping <ipaddr> del <filename> ren <filename1> <filename2> dir [ext] type <filename>...
Page 23
Nera SatLink Terminal User Guide – Revision P CLI commands Available in Available in User Boot Application Privilege Level ip dhcp <enable|disable> ip dhcp show ip dhcp leasetime <time> [unit] ip dhcp dns <primary> <secondary> ip dhcp exclude <no> ip gre add <destaddr> <netmask>...
If the Nera SatLink Terminal does not seem to be reachable from the LAN after power-on, this may be due to slow update of the ARP cache on the PC. Then verify that the Nera SatLink Terminal is registered in the PC’s ARP cache by using the MS-DOS command arp –a.
- SW ID 101224, Revision 9.1.3 Build 56 Note that one must press Enter once to get the login-prompt to display if using the CLI via RS-232. The Nera SatLink Terminal should now be ready to be configured as described in the following sub- sections.
Page 26
DVB interface IP address. Please, always make sure that the next hop IP address for the default route is neither located on the Nera SatLink Terminal’s own LAN nor is identical to the DVB interface of the SatLink Terminal. Otherwise it will break the IP connectivity from the Nera SatLink Terminal to the DVB-RCS gateway.
Page 27
Nera SatLink Terminal User Guide – Revision P 6.2.2 Antenna and ODU parameter configuration The Nera SatLink Terminal is normally pre-configured to be used together with the Nera SatLink 403x Transceiver. The CLI command will show the ODU configuration with the two parameters, odu show ODU transmitter type and ODU receiver type, both set to Nera SatLink 403x.
Page 28
When using the Nera SatLink 3000 ODU transmitter or the SatLink 4033/4035/4036 Transceiver, the Nera SatLink Terminal must be configured with the antenna type in use in order to calculate the transmitted EIRP correctly. The following antennas are supported: Antenna #...
Page 29
LNB. Note: When ODU BUC is chosen to be the Nera SatLink 403x transceiver, the LNB will automatically be set to Nera SatLink 403x. The Nera SatLink IDU will detect the Nera SatLink transceiver model being used (i.e.
Page 30
SatLink Terminal must be restarted for the new configuration to take effect. 6.2.3 Terminal position In order to calculate the delay to the satellite correctly for the logon burst the Nera SatLink Terminal must be configured with its own position.
Page 31
Symbol rate : 30.000000 Msps Satellite (DVB) RX Status -------------------------------- State : Off The above example shows how to configure the Nera SatLink Terminal to use the following forward link: • Rx symbol rate: 30.0 Msps • Rx frequency: 12.591 GHz...
Nera SatLink Terminal is ready to acquire the forward link: 1. If not already logged on, start the Nera SatLink Terminal and login as installer (user = install, factory default password = dvbrcs) after having seen the message Starting DVB interface.
Page 33
CLI command dvb rx autostart off. Verify that the autostart is disabled using the CLI command dvb rx show. Later, when the Nera SatLink terminal is correctly aligned, the autostart functionality can be enabled in order to automatically attempt Forward Link acquisition in case of Forward Link loss.
Page 34
Ask the control centre if they can detect the transmitted CW. If they are not able to see the CW at the specified frequency and expected output power level, please power off the Nera SatLink Terminal immediately. Example: # dvb tx calibrate Using preconfigured CW frequency 14.123000 GHz...
Page 35
Nera SatLink Terminal User Guide – Revision P 10. Verify the calibrated power levels using the CLI command dvb tx show Example: # dvb tx show Satellite (DVB) TX Configuration -------------------------------- Auto start : Disabled Population ID IDU output power...
Nera SatLink Terminal is ready to logon to the DVB-RCS network. The Nera SatLink Terminal is only allowed to log on to the DVB-RCS network if its DVB MAC address is registered at the gateway. Registration of the terminal’s MAC address at the gateway is a network operator responsibility.
Nera SatLink Terminal User Guide – Revision P 4. To test the IP connection to the gateway open an MS-DOS window on the PC connected to the Nera SatLink Terminal LAN (Ethernet). Type the MS-DOS command ‘ping 10.10.10.1’ to test the connection to the gateway router If the router gives a positive reply to the ping message then the DVB-RCS satellite link is successfully up and running.
DHCP server, then the DHCP server will have the IP address range 10.10.10.1 to 10.10.10.252 available for DHCP clients. • Primary DNS server: IP address for the primary DNS server to be used by the hosts on the Nera SatLink Terminal LAN. •...
Nera SatLink Terminal User Guide – Revision P Example: # ip dhcp show DHCP Server Status ------------------------------------------- Server Status : Enabled Server IP address : 192.168.0.1 Server IP address range Starting IP address : 192.168.0.1 Ending IP address : 192.168.0.254...
Web browsing and FTP. The Nera SatLink Terminal can be configured to support two different QoS groups on the return link. QoS on the forward link is handled by the DVB-RCS Gateway and not discussed further in this manual.
Nera SatLink Terminal User Guide – Revision P Configuring QoS for the return link In order to determine the QoS group an IP packet belongs to, the SatLink terminal uses a multi-field classifier. This multi-field classifier is used to perform a look-up in a QoS classification table. This table can store up to 15 different masks that the IP packets will be matched against.
Page 42
Nera SatLink Terminal User Guide – Revision P The CLI command to be used to configure the QoS Classification table is ip qos mask <index> . This command has a variable length where one ore more tags with < group> <list of tags>...
Agreement parameters (CRA, maxRBDC, and max VBDC per QoS class) during the log-on sequence and, thus, override the default settings. The capacity requested by the terminal and the capacity granted by the NCC to the Nera SatLink Terminal on the return link can be viewed using the CLI command...
Page 44
The maxRBDC is set from the DVB-RCS Gateway and is a network/service provider decision. The Nera SatLink Terminal is pre-configured with a default value of maxRBDC for the Best Effort QoS class. This default value will be overwritten by the operator-defined value at log-on time.
(by avoiding use of dedicated SYNC slots when the terminal has no traffic to send). The power saving mode requires the use of the Nera SatLink 403x transceiver or the Nera SatLink 3000 transmitter. The power consumption will then be reduced from typically 27W to approximately 12W...
Page 46
Nera SatLink Terminal User Guide – Revision P To view the defined multicast routes use the CLI command ip show -mcast Example: # ip show -mcast IP Multicast Routing Table RouteAddress AddressMask IfIndex 224.0.0.2 255.255.255.255 224.0.2.2 255.255.255.255 Please note that subnetwork internal multicast groups on the LAN will show up in the multicast route table.
Nera SatLink Terminal User Guide – Revision P 12. Updating the Nera SatLink Terminal SW The flash in the Nera SatLink Terminal can store two SW images, both the currently used SW and a backup version in case download of a new SW version fails.
Below is described in detail how to upgrade the Nera SatLink Terminal software: 1. Verify the default settings for the manual software upgrade with the CLI command sw show 2.
Nera SatLink Terminal User Guide – Revision P 12.3 Restoring the backup software If one for some reason must restore the old software, then the following steps have to be executed. Please note that the current SW will be deleted when restoring the backup SW.
Network Address Translation (NAPT, Global NAT, and Static NAT) • GRE Tunnelling • TCP/IP Performance Enhancing Proxy (PEP) To show the list the SW options that are authorised for use on the Nera SatLink Terminal, use the CLI command sw show Example: # sw show...
To enable Network Address Translation (NAPT or static NAT) in the Nera SatLink Terminal, use the CLI command ip nat enable Example: # ip nat enable To show the status of the Network Address Port Translation in the Nera SatLink Terminal, use the CLI command ip nat show: Example # ip nat show...
Page 52
Nera SatLink Terminal User Guide – Revision P Please note that translation of outbound TCP/UDP fragmented datagrams will fail with NAT enabled. The reason is that only the first fragment contains the TCP/UDP header that would be necessary to associate the packet to a session for translation purposes.
Page 53
Nera SatLink Terminal User Guide – Revision P Example: # ip nat napt add 10.10.2.2 5000 192.168.0.12 3000 # ip nat show NAT Configuration ----------------- Network Address Port Translation (NAPT): Enabled Global Address Table IP Address dvb0 10.10.1.10 Static NAPT Map...
Page 54
Nera SatLink Terminal User Guide – Revision P 13.1.3 Configuration of Static NAT Static NAT provides two-way access to servers behind NAT. The destination IP address of the incoming packet is replaced by the corresponding local address that is configured in the Static NAT Map Table.
13.2 Generic Routing Encapsulation (GRE) and IP Tunnelling The Nera SatLink Terminal supports configuration of one IP tunnel from its DVB interface with Generic Routing Encapsulation (GRE) as specified in RFC 2784. Only the tunnel termination interface IP address, tunnel logical destination IP address and subnet mask need to be specified since the tunnel will always be set up from the DVB interface.
TCP PEP implementation in the SatLink System makes use of a TCP Performance Enhancing Server installed in the Nera SatLink Gateway and a PEP software client embedded in the Nera SatLink Terminal. The Nera SatLink Terminal embedded PEP client is an optional feature, which is enabled by entering a license key.
Page 57
Nera SatLink Terminal User Guide – Revision P Example: # sw license pep mykeyforenablingpep # ip pep server 10.0.0.10 # ip pep enable redirect (to verify that the functionality is enabled) # ip pep show PEP Status : enabled PEP Mode...
Nera SatLink Terminal User Guide – Revision P 14. Definitions, Acronyms and Abbreviations Bit Error Rate Block Up-Converter Command Line Interface Continuous Rate Assignment Common Signalling Channel Continuous Wave DiSEqC Digital Satellite Equipment Control Domain Name Service Digital Video Broadcasting...
User’s Assembly Manual and Operating Instructions for Visiosat 90 Dual Reflector Transmit / Receive Antenna, Nera document No. 103174. Nera SatLink Terminal. Management via SNMP, Nera document No. 103951. Digital Video Broadcasting, The International Standard for Digital Television, by Ulrich Reimers et.al., Berlin, Springer Verlag, 2001, 295 pages hardcover, ISBN 3-540-60946-6.
Terminal, please use the CLI via Telnet or RS-232 as a work-around for the problem. Please note that the Web-server in the Nera SatLink Terminal is given less priority than the processes that take care of the data transfer to and from the Satellite interface. This may occasionally result is slow response times for the Web pages.
Page 61
Nera SatLink Terminal User Guide – Revision P Assignment), Max RBDC (Rate Based Dynamic Capacity), and Max VBDC (Volume Based Dynamic Capacity), all being configured from the Gateway. CRA (Continuous Rate Assignment) is fixed capacity allocated to the terminal. The parameters Max RBDC (Rate Based Dynamic Capacity) and Max VBDC (Volume Based Dynamic Capacity) set limitations on the amount of capacity the terminal is permitted to request.
Page 62
Nera SatLink Terminal User Guide – Revision P A.1.2 Traffic statistics Traffic statistics can be seen by choosing the "Status" page, and then selecting the "Statistics" button. The page consists of three tables: IP packet statistics, satellite forward link statistics (receive), and satellite return link statistics (transmit).
Page 63
Nera SatLink Terminal User Guide – Revision P Figure 17: Statistics page...
Page 64
Nera SatLink Terminal User Guide – Revision P A.1.3 Device information Device information can be viewed by choosing the "Status" page, and then selecting the "Device" button. Information displayed is: • Model: Terminal hardware model. • Software version: Version number (build number) of the application software currently running.
Page 65
Nera SatLink Terminal User Guide – Revision P A.1.4 DHCP information The status of the DHCP server can be seen by choosing the "Status" page, and then clicking the DHCP button. General information about the status of the DHCP server and the DHCP client table is shown: •...
Page 66
Nera SatLink Terminal User Guide – Revision P Figure 19: Information concerning the current DHCP configuration...
Page 67
Nera SatLink Terminal User Guide – Revision P A.1.5 NAT information Please note that the NAT button is only visible on the web page if the NAT SW license is installed. Figure 20: Status information concerning the current Network Address Translation configuration...
Page 68
Autostart on/off for the transmitter • Population ID • EIRP. Only needed when using the Nera SatLink 4033/4035/4036 or 3000 transmitter (BUC). • IDU output power. Only needed when using other transmitters (BUCs) than Nera SatLink 4033/4035/4036 or 3000. •...
Page 69
Nera SatLink Terminal User Guide – Revision P 21: Nera SatLink Terminal configuration (Receiver, Transmitter and geographical position)
Page 70
Nera SatLink Terminal User Guide – Revision P A.2.2 IP address configuration IP address configuration can be done by choosing the “Configuration” page, and then selecting the “IP” button. The IP addresses and netmasks of the RCST's LAN and DVB interfaces and the LAN DHCP server can be configured here.
Page 71
Nera SatLink Terminal User Guide – Revision P Note: Please note that after saving the new IP address the Nera SatLink Terminal needs to be restarted for the changes to take place. The browser window may look incomplete during this save and may need to be...
Page 72
Nera SatLink Terminal User Guide – Revision P A.2.3 NAT configuration For terminals with the NAT option enabled, NAT can be disabled/enabled, and global IP addresses and address mapping can be configured here. If no static address mappings are defined for NAT, then dynamic port allocation (NAPT) will be used.
Page 73
After the correct IDU output power level has been found, (automatically when using the Nera SatLink 4033/4035/4036 and Nera SatLink 3000, manually when using other transmitters (BUCs)), the pointing and polarisation of the antenna should be fine adjusted based on measurements performed by the system operator on the transmitted CW.
Page 74
Nera SatLink Terminal User Guide – Revision P Figure 24: Terminal line-up web page...
• Detailed debugging The Command Line Interface may then be accessed from a local PC connected to the Nera SatLink Terminal’s RS-232 interface via a serial cable. HyperTerminal or any compatible terminal emulation program is used to access the CLI interface via RS-232.
Page 76
Figure 26: Hyper Terminal Connect To dialogue box Select the COM port where the serial cable attached to the Nera SatLink Terminal is connected, and click OK. The COM port Properties property sheet will appear, as shown in Figure 27.
Page 77
Nera SatLink Terminal User Guide – Revision P Use the pull-down lists to enter: • Bits per second: 38400 • Data bits: • Parity: None • Stop bits: • Flow control: none Click Apply to accept the properties. The property sheet will close and communication with the SatLink Terminal may begin.
TFTP upload from and download to the Nera SatLink Terminal has been tested with version 2.51 of this TFTP server, but any TFTP server should work. It is however essential that the TFTP server has support for negotiation of block lengths up to 8 Kbytes in order to obtain satisfactory performance over the satellite link, in terms of acceptable download time.
Nera SatLink Terminal User Guide – Revision P Appendix D. Telnet Client A good freeware Telnet client is Tera Term Pro Web 3.1.3. The software can be download from Ayera home page: http://www.ayera.com/teraterm. Especially when running Telnet from Windows XP it is recommended to use Tera Term instead of the built in Telnet Client in Windows XP, since setting Local Echo in the Windows XP client does not seem to work.
Nera SatLink Terminal User Guide – Revision P Appendix E. Management via SNMP Management of the Nera SatLink Terminal is supported via SNMP. For further information of SNMP management and the MIBs available, please refer to [6] and/or contact the system operator.
The transmission of a pure tone (CW) is supported for aiding the antenna fine adjustment as well as for use during power calibration. A default frequency for CW transmission is stored in the Nera SatLink Terminal configuration. This default frequency may be changed with the CLI command where is the return link frequency [kHz].
Nera SatLink Terminal User Guide – Revision P Appendix G. ODU installation The ODU comprises the antenna with feed-horn and mounting structure, a LNB unit with OMT and Tx- reject filter and a transmitter (BUC). Two cables with F-connectors, one for Tx and one for Rx are connecting the ODU to the IDU.
Page 83
Nera SatLink Terminal User Guide – Revision P If the Nera SatLink 4033/4035/4036 transceiver is used, the OMT, LNB and BUC are integrated in one mechanical housing. The SatLink 403x is mounted directly on to the antenna feed as shown in the figure above.
Page 84
Nera SatLink Terminal User Guide – Revision P Insert the remaining screws and tighten firmly with an Allen key.
Page 85
Nera SatLink Terminal User Guide – Revision P connector connector The IF connectors are placed in the chassis of the SatLink 403x. A protrusion on the case indicates ‘Rx’ and ‘Tx’ so that they are easily distinguishable. Cable connectors should be tightened firmly, but use of...
Page 86
Nera SatLink Terminal User Guide – Revision P Assembly of LNB unit, transmitter and feed-horn This section is not applicable for the Nera SatLink 403x transceiver. The main components are shown below: Antenna reflector mounting and feed-horn with supporting structure and screws.
Page 87
F-connector. Hence, a waterproof adapter from male N-connector to female F- connector must be used between the Tx-cable and the BUC connector. Transition connector The Nera SatLink 3000 transmitter has a female F-connector as input connector, therefore no transition is needed with the Tx-cable. No transition required...
Page 88
Nera SatLink Terminal User Guide – Revision P An assembly drawing with a Norsat 1020XRT transmitter is shown below:...
Page 89
Nera SatLink Terminal User Guide – Revision P An assembly drawing with a Nera SatLink 3000 transmitter is shown below:...
Page 90
Nera SatLink Terminal User Guide – Revision P The different assembly steps are shown below: Connect the feed-horn with the LNB unit using the correct screws. Remember the o-ring. Insert an o-ring at the WR-75 wave-guide interface on the transmitter.
Page 91
Nera SatLink Terminal User Guide – Revision P Assembly and installation of the antenna Different mounting structures for antennas are shown below. From the left-hand side, we have an L- shaped wall-mount, a three-leg mount and a standard straight mount. The tube diameter is 76 mm. For a correct mounting the surface must be vertical or horizontal, respectively.
Page 92
Nera SatLink Terminal User Guide – Revision P Bolts and equipment. Compass Check the visibility towards the satellite.
Page 93
Nera SatLink Terminal User Guide – Revision P Installation of an L-shaped wall-mount on a pipe: The mount must be fixed to the wall and levelled so the upper part of the tube is vertical. The antenna az/el mount is fastened to the vertical tube:...
Page 94
Nera SatLink Terminal User Guide – Revision P Continue the installation process: Fasten the feed-horn, LNB and transmitter to the feed-mount. Fasten the parabolic reflector to the az/el mount. Fasten the U-shaped profile to the reflector and connect the feed-mount.
Page 95
Nera SatLink Terminal User Guide – Revision P Connect the long support rods to the feed-horn mount. Adjust the position of the transmitter (coarse adjustment) to horizontal or vertical polarisation depending on the satellite transponder you are going to use.
Page 96
Nera SatLink Terminal User Guide – Revision P The peaking of the antenna by adjustment of azimuth and elevation: Coarse adjustment of azimuth. Loosen the bolts and adjust. Alternatively, rotate the complete antenna on the vertical rod. Fine adjustment of azimuth.
Page 97
Nera SatLink Terminal User Guide – Revision P satellite (the carriers are those you expect). If the polarisation is not well aligned, you will also see the carriers on the orthogonal polarisation. Then, continue with the fine adjustment in elevation and azimuth. It is recommended that the span on the spectrum analyser cover a single transponder.
Page 98
Nera SatLink Terminal User Guide – Revision P G.3.2 Polarisation alignment Rotate the complete feed-system (horn, LNB and transmitter) very slowly and carefully in one direction away from the coarse polarisation alignment. Monitor the spectrum-analyser and observe the carriers on the opposite polarisation.
Page 99
Nera SatLink Terminal User Guide – Revision P After polarisation adjustment. The carriers have disappeared. Tighten all the bolts and screws properly and have a final check on signal level and polarisation. G.3.3 Additional work The Rx- and Tx-cables should be strapped to the feed-mount.
Page 100
Nera SatLink Terminal User Guide – Revision P...
Page 101
G.3.4 Cables Nera recommends cables from Times Fiber (see Appendix L). For cable lengths up to 62 m, Times Fiber series 6 (diameter 6.93 mm) can be used. For lengths up to 82 m, use series 11 (diameter 10.2 mm) and for longer lengths, use series 500 (diameter 14.2 mm).
• And all C-band BUCs Please refer to section 6.3.2 for the description of the calibration procedure for the Nera SatLink 3000 (revision 5.0 and newer) and SatLink 403x. Ensure that the Nera SatLink Terminal configuration procedure in section 6.2 has been performed.
Page 103
Nera SatLink Terminal User Guide – Revision P Example: dvb tx cw on -30 14100000 will transmit a CW from the ODU output at 14.1 GHz with an IDU output power of –30 dBm from the Nera SatLink Terminal. Please check immediately with the control centre if they can detect the transmitted CW. If they are not able to see the CW at the specified frequency and expected output power level, please power off the Nera SatLink Terminal immediately.
Page 104
Nera SatLink Terminal User Guide – Revision P and type the CLI command: dvb tx outpow –27 Verify the setting by issuing the CLI command dvb tx show and save the setting by issuing the CLI command save config...
The Boot SW is stored outside the file system and can be compared with the BIOS and MS-DOS on a PC. It is used to have access to file system and the LAN when there is no application loaded on the Nera SatLink Terminal.
Debugging network connections Ping is a useful tool to debug network connections. A ping test can be done from a PC connected to the Ethernet port of the Nera SatLink Terminal (e.g. from Microsoft command prompt). Use the following commands: 1.
Page 107
Nera SatLink Terminal User Guide – Revision P Example: # dir Volume Label :NERADVB-RCST10 Directory Name : DVB-RCST FileName Size Date Time oldLog.txt 9816 00/00/0000 00:34:20 activeLog.txt 3192 00/00/0000 00:00:25 xxx.bak 1691265 00/00/0000 00:04:21 dvb-rcst.tgz 1690755 00/00/0000 00:24:28 config.txt 5188...
Page 108
Nera SatLink Terminal User Guide – Revision P List of events that may be logged The following are the most common events that may be shown in the log from the Nera SatLink Terminal. Use the CLI command to display the list of events stored in memory and the log show to display the list of events stored on the flash file system.
Page 109
The Nera SatLink Terminal was not able to enter the fine synchronisation state when trying to log on. After a timer has expired the Nera SatLink Terminal will retry to log on to the DVB-RCS gateway. ODU power on failure...
Page 110
Nera SatLink Terminal User Guide – Revision P Event Severity User action Comment required Missing Table Major None The Nera SatLink Terminal is not receiving a mandatory DVB-S/DVB-RCS table on the forward link. If the problem does not disappear within 10-60 minutes please contact the DVB-RCS gateway operator.
Page 111
Nera SatLink Terminal User Guide – Revision P Event Severity User action Comment required SW checksum error Major Check validity of A checksum error is reported on the *.tgz file. application *.tgz file downloaded during the software upgrade. The file will be deleted and the software upgrade will be aborted.
Nera SatLink Terminal User Guide – Revision P Appendix K. TCP enhancement and tuning General introduction to Performance Enhancing techniques The Transmission Control Protocol – TCP now is used by most applications on the Internet (e.g. HTTP, POP3 and FTP). The protocol is designed for controlling the end-to-end flow of data over an IP network, by imposing error control and congestion control.
Page 113
Nera SatLink Terminal User Guide – Revision P • Selective Acknowledgement: Basic TCP uses the goback-N acknowledgement scheme. This means that an acknowledgement applies to all transmissions up to the ack number. This means that when multiple packets are lost, all packets transmitted after the erroneous transmission must be retransmitted.
Page 114
Nera SatLink Terminal User Guide – Revision P Figure 30: Dr. TCP utility...
Appendix L. Cable Specification This appendix provides the cable specification for the cables to be used between the ODU and the Nera SatLink IDU. Two separate cables are require; one cable for the transmit (Tx) signal and one cable for the receive (Rx) signal.
Page 116
Nera SatLink Terminal User Guide – Revision P Maximum cable lengths: The maximum cable lengths for the Times Fiber cables are given in Table 12 and Table 13. The cable loss at 1450 MHz or the DC- resistance decides the range at Tx. At Rx, the range is decided by the cable loss at 2150 MHz together with the minimum symbol-rate.
Nera SatLink Terminal User Guide – Revision P Appendix M. Compliance The Nera SatLink 1000, 1900, 1901 and 1910 comply with the essential requirements of Article 3 of the R&TTE 1999/5/EC Directive, if used for its intended use. Safety (Article 3.1.a of the R&TTE Directive) This equipment has been designed and tested to meet the requirements of the following standards: •...
6.5. When rx autostart and tx autostart are set to off (disabled), the Nera SatLink Terminal will make one attempt to acquire the forward link when issuing the CLI command .
A rough outline of the procedure is as follows: The Nera SatLink Terminal tunes to the transport stream of the forward link that it has pre-configured as ”start-up” forward link. There it reads the NIT. The NIT PID value is hard-coded in the SatLink terminal.
Page 120
Nera SatLink Terminal User Guide – Revision P The Nera SatLink Terminal can report the following Receiver State status: Tuning transponder one Tuning transponder two Tuning transponder three Waiting for NIT (transponder one) Waiting for PAT (transponder two) Waiting for PMT (transponder two)
Need help?
Do you have a question about the SatLink 1000 and is the answer not in the manual?
Questions and answers