SatLink VSAT User Guide
Publication no. 101557
Copyright © 2009 – STM Group, Inc.
Page 41 (160)
9. SatLink VSAT Configuration and Line-up Using Command
Line Interface
Follow all the procedures below when installing the SatLink VSAT and lining up the ODU using
command line interface of the SatLink VSAT.
9.1 Power On and Log On
1) To view the boot processes of the SatLink VSAT, connect a PC to the serial interface and launch a
Terminal Emulator as described in Appendix A. Otherwise go to step 2.
2) Turn on the power of the SatLink VSAT.
When turning on the SatLink VSAT first the Boot SW is loaded. A message such as the one below is
displayed on the CLI serial console when the boot SW starts. Telnet is not available until the application
has been started.
Boot-loader
- SW ID 120044, Revision 14.0.0 File system initialised
Press return to enter boot-loader
Under normal circumstances the user should not need to enter the boot-loader and should ignore the
“press return to enter boot-loader” message. The DVB RCS application will load automatically once the
boot SW load has completed. See Appendix J for further details concerning the boot SW. If access to the
boot-loader is required, press return within 10 seconds to display the login-prompt for entering the boot-
load. After the timer has expired, the DVB-RCS application will be loaded. The message
Loading
application
will be shown when the application starts to load.
3) Wait for the application software to be loaded and activated (typically takes 1-1.5 minutes).
The power LED on the front of the SatLink VSAT will blink when the SW is booting and will stay on
when the SW has successfully started. If watching the boot process on the RS-232 output, a printout
similar to this will be displayed when the SW has booted.
SatLink 2000
- Main board ID 120026, Revision R3.3
- SW ID 120208, Revision 14.0.0 Build 30
File system initialised Ethernet Interface MAC Address: 00:20:0e:10:35:34
DVB Interface MAC Address : 00:20:0e:10:35:34
Retrieving configuration....done
When the SatLink VSAT is configured for use with the SatLink 4033/4035 transceiver and the
TX cable is not connected to the ODU then the following error message will be shown when
the SW has booted:
ODU Initialisation failed. Unable to establish DiSEqC communication.
Please check connection to ODU and that the ODU supports
DiSEqC communication
This is normal and just indicates that the VSAT can not communicate with the transceiver
since the cable is not yet connected.
4) At this point the Telnet server in the SatLink VSAT is started and a Telnet session can be opened for
managing the VSAT. Local Echo must be enabled in the Telnet Client if the input from the keyboard
To Next Page
Loading...
