• No results found

Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

N/A
N/A
Protected

Academic year: 2021

Share "Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series"

Copied!
14
0
0

Loading.... (view fulltext now)

Full text

(1)

SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

Device Upgrade Procedure

for

NTC/21xx, NTC/22xx, AZxxx

and ELxxx device series

(2)

Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

i

SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

© 2011 Newtec cy.

The material contained in this document is confidential and intended for use only by parties authorised by Newtec.

All Rights Reserved. No part of this document may be photocopied, reproduced, stored in a retrieval system, or transmitted, in any form or by any means whether, electronic, mechanical, or otherwise without the prior written permission of Newtec cy.

Newtec cy Laarstraat 5

9100 Sint-Niklaas, Belgium General: +32 (0)3 780 65 00 www.newtec.eu

Fax +32 (0)3 780 65 49 General: general@newtec.eu

(3)

About this Application Note Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

ii

SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

ABOUT THIS APPLICATION NOTE

This note provides all information on how to perform an upgrade of NTC/21xx, NTC/22xx, AZxxx and ELxxx (except EL8xx) equipment by using the Bucket Upgrade File mechanism.

Cautions and symbols

The following symbols appear in this note:

A caution message indicates a hazardous situation that, if not avoided, may result in minor or moderate injury. It may also refer to a procedure or practice that, if not correctly followed, could result in equipment damage or destruction.

A hint message indicates information for the proper operation of your equipment, including helpful hints, shortcuts or important reminders.

A reference message is used to direct to; an internal reference within the document, a related document or a web-link.

Version history and applicability

Document version Date Author Comment

Version 2.0 ADKE New Document

Version 2.1 ADKE Updated Version

Version 2.2 ADKE Updated Version

Version 3.0 19-01-2010 WDW Update and added AZ & EL Version 4.0 16-11-2010 WDW Added R8 GUI upgrade

(4)

About this Application Note Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

iii SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

Feedback

Newtec encourages your comments concerning this document. We are committed to providing documentation that meets your needs.

Please send any comments by contacting us at documentation@newtec.eu. Please include document and any comment, error found or suggestion for improvement you have regarding this document.

(5)

Table of Contents Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

iv SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

TABLE OF CONTENTS

About this Application Note ...ii

Cautions and symbols ... ii

Version history and applicability ... ii

Feedback ... iii

Table of Contents ...iv

1 Introduction ...1

1.1 About Bucket Upgrade Files ...1

2 Preparation Steps Before Upgrading...2

2.1 Setting IP address on the device ...2

2.2 Storing configuration ...3

2.2.1 Generating diagnostic report ...3

2.2.2 Generating output file ...3

3 Upgrade Procedure...4

3.1 Standard Upgrade procedure ...4

3.2 Upgrade procedure using GUI...6

4 After the Upgrade...8

(6)

Introduction Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

1 of 9 SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

1 INTRODUCTION

This bulletin describes how to perform an upgrade of NTC/21xx, NTC/22xx, AZxxx or ELxxx (except EL8xx) equipment by using the Bucket Upgrade File mechanism. This will upgrade following files to the latest version:

 M&C platform for the general device (if applicable, the Kernel will be upgraded too).

 M&C software for individual boards.

 FPGA bit files of individual boards.

 SNMP daemon.

 GUI (Graphical User Interface).

1.1

About Bucket Upgrade Files

The Bucket Upgrade Folder you received is a zip file that contains all necessary firmware and FPGA bit files for the boards in the device.

It is generated automatically from the Newtec equipment database and will contain the latest available versions of the software and FPGA bit files for all boards possible in a device. The Bucket Upgrade File also contains the application that will manage the upgrade.

A Bucket Upgrade File contains all FPGA bit files and M&C software for all possible boards and the M&C platform. Upon starting the upgrade, the upgrade application will first perform a board scan in order to determine the boards installed in that specific device and their current software version. If the version detected is lower, the board will be upgraded and if it is equal or higher, the board will not be downgraded. The results of the board scan can be viewed in:

(7)

Preparation Steps Before Upgrading

Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

2 of 9 SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

2 PREPARATION STEPS BEFORE UPGRADING

In order to successfully complete the upgrade some preparation steps need to be taken.

2.1

Setting IP address on the device

To be able to perform the upgrade, you need connection between your PC and the device. To set the device IP address, go to:

 NTC/2xxx >> Unit >> Setup >> Ethernet settings  Device IP address: <Device IP address>

Enter a valid IP address within the subnet mask of your PC. Make a connection between your PC and the port LAN on the device. This can be done in 2 ways:

 Connect directly to the device

 Connect a crossed UTP cablebetween your PC and the port LAN of the device.

 Connect via the Local Area Network connection (LAN).

 Connect a straight UTP cable between your PC and the Ethernet switch.

 Select a free IP address in the LAN’s IP range.

How to determine and change your PC’s IP address:

 On a Windows PC, go to start>Control Panel>Network Connections.

 Right-click on Local Area Connection.

 Select “Properties”.

 Scroll down and double-click “Internet Protocol (TCP/IP)”.

 If necessary (!) change your computer’s IP address and subnet mask.

You can also check your IP address by opening a DOS box and type “ipconfig”.

(8)

Preparation Steps Before Upgrading

Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

3 of 9 SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

2.2

Storing configuration

We strongly advice to store the device configuration on your PC. After upgrading, this action will easily help you to setup your device again.

During the bucket file procedure a factory reset will be performed automatically. This will result in restoring default values on your device for all control parameters.

There are 2 options to store the configuration. One of them is to generate a diagnostic report; the other is generating an output file. Both procedures are described in the next paragraphs.

2.2.1

Generating diagnostic report

 Open a web browser and type http://<Device_IP_address> in the address field.

 Click “Diagnostics report” in the quick navigation bar. This will generate a report with all the actual settings.

 Save this diagnostics report on your PC (leave as html format)

 Go to the Upgrade procedure on page4.

2.2.2

Generating output file

 Go to the Control menu and select Unit configuration.  NTC2xxx >> Unit >> Control >

 Generate output file: Unit Configuration

 Open a web browser and enter ftp://<device_IP_adress>/ftp/out/.

 Copy the *.cfg file to your PC.

 Go to the Upgrade Procedure on page 4.

Due to older software on the device, it could be that “Generating Output File” is not supported. In this case, use the diagnostic report procedure.

(9)

Upgrade Procedure Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

4 of 9 SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

3 UPGRADE PROCEDURE

3.1

Standard Upgrade procedure

Before starting the upgrade we recommend to restart the device. This can be done by simply unplugging and reconnecting the power cable.

Before starting the upgrade we recommend to turn off the firewall of your PC. The PC firewall could cause issues during ftp transfer of the files to the device.

1. Unzip Bucket Upgrade File to a local folder on your PC. 2. Make a ftp connection with your device in the following way:

 Open Windows explorer on your PC.

 Type ftp://ip_address_device in the address field. (If prompted for a username and password, use ftp, ftp).

3. Transfer the content of the upgrade file to the device:

 Open local folder with unzipped Bucket upgrade files.

(10)

Upgrade Procedure Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

5 of 9 SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

Do not copy the zipped Bucket Upgrade file itself to the root folder!

4. Start the upgrade on the device by going to the following menu:  NTC2xxx >> Unit >> Control

 Device reset: <=Upgrade=>

 Select “upgrade”

 Upgrade information is displayed on the front panel

 The device will scan its boards to detect the current firmware version and FPGA bit file version. Only boards with a lower version of the Bucket Upgrade File will be upgraded. Unless the Bucket Upgrade File is modified to force the upgrade.

 Wait until the Upgrade is finished. The front panel display will provide a percent complete status indication for each of the files being upgraded. During the upgrade, the Test LED will flash.

 Do not power-cycle the device during the upgrade, the device will reboot itself upon completion of the upgrade.

5. Store the upgrade_log by performing the next actions:

 Press F5 in your local Windows explorer to refresh the ftp site contents.

 Go to ftp://<Device_IP_address>/httpd/upgrade_log.html.

 Save this file to your desktop. Keep the html format.

 Send the file to techsupport@newtec.eu. The upgrade logfile contains:

 A list of upgrade files that were found on the ftp site.

 The boards present in the device with hardware and software identification.

 A check for all upgrade files if the related board are present. If present the software version is checked and if needed the result and versions (before and after the upgrade) are listed. In case you were provided with multiple Bucket Upgrade Files (e.g. when the device software must be upgrade but also the SNMP daemon from a separate Bucket Upgrade File), the above described procedures (1-5) will have to be repeated.

(11)

Upgrade Procedure Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

6 of 9 SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

 We strongly recommend you to clear the cache of your webbrowser after the GUI has been reloaded.

3.2

Upgrade procedure using GUI

From R8 onwards the firmware can be upgraded using the graphical user interface. This makes the upgrade simpler since no direct ftp access is required anymore.

The next steps explain how the firmware upgrade works using the graphical user interface. 1. Open a web browser and type http://<Device_IP_address> in the address

field.

2. The GUI will open and you will be asked to log in. Log in as root using following details:

a. Username: root b. Password: root

3. Logged in as root the following screen will appear (the ‘Overview’ will differ per device)

a. The upgrade can be started by pressing the ‘Firmware Upgrade’ button on the ‘Misc.’ tab in the right bottom corner.

(12)

Upgrade Procedure Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

7 of 9 SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

5. The upgrade will be started when you click ‘Upgrade’ in the pop up window.

6. During the upgrade the following window appears:

a. A detailed log can be viewed clicking the drop down arrow

7. When the upgrade is finished you will be asked to reload the GUI.

 We strongly recommend you to clear the cache of your webbrowser after the GUI has been reloaded.

In case you were provided with multiple Bucket Upgrade Files the above described procedures will have to be repeated.

(13)

After the Upgrade Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

8 of 9 SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

4 AFTER THE UPGRADE

 We strongly recommend you to clear the cache of your webbrowser after the GUI has been reloaded.

If the upgrade was successful and the settings were saved according to the steps explained in 2.2.1 or 2.2.2, the original settings can be restored in the following way:

Diagnostic report

Use the diagnostic report, generated before the upgrade, to manually reset all device parameters. Open the report, all control parameters are described under: NTC2(AZ)(EL)xxx/<device type>/Control.

Use the GUI or front panel to reset, one by one, the parameters retrieved from the diagnostics report.

In Appendix B you can find an example of a diagnostic report.

Activating system file

Use the cfg file to restore all parameters in the device. The cfg file must be copied from your local PC back onto your device.

 Paste the file in your windows explorer to the following directory on your device:.

ftp://<device _IP_address>/FTP/in/  Activate the system file:

 NTC2xxx >> Unit >> Control  Activate System File: All

(14)

APPENDIX A – Diagnostics Report example

Device Upgrade Procedure for NTC/21xx, NTC/22xx, AZxxx and ELxxx device series

version 4.0

9 of 9 SHAPING THE FUTURE OF SATELLITE COMMUNICATIONS

APPENDIX A – DIAGNOSTICS REPORT EXAMPLE

--“

NTC2280/Modulator/Control/Modulation/Main

FEC-rate and mod. QPSK-3/4

Interface bitrate 13.823530 Mbps

Symbol rate 10.000000 Mbaud

Output frequency 1250.000000 MHz

LBand output level -15.0 dBm

Gain control mode AGC

Carrier modulation on

L-band transmit disabled

NTC2280/Modulator/Control/Modulation/PHY

LBand spectrum inv. direct

Linear predistortion N.A. (029)

Slope equaliser 0 units

Roll-off factor 25%

Monitor output mode always on

Occupied bandwidth 12.500000 MHz

NTC2280/Modulator/Monitor/Interfaces

PRBS detector status N.A. (029)

Estim. error count N.A. (029)

PRBS sync seconds N.A. (029)

Estim. error rate N.A. (029)

Estim. error ratio N.A. (029)

PRBS monitor input N.A. (029)

References

Related documents

a) Debit Current account and credit interest on drawings b) Debit interest on drawings and credit current account c) Debit appropriation account and credit Current account d)

Description of the annotated items and discussion of the skill sets that are common between the annotated items and the etude, and ways in which the annotated item(s) prepare

Desejava-se, também, saber qual a relação entre a antiguidade e os níveis de burnout e ainda quais as diferenças entre os bombeiros voluntários e os bombeiros profissionais no que

Bending or twisting of cables or leads directly on the thermistor body is not permissible4. Avoid using chemical substances as

It must be ensured that no water enters the NTC thermistors (e.g. through plug terminals). Avoid dewing and condensation unless thermistor is specified for these conditions...

Bending or twisting of cables or leads directly on the thermistor body is not permissible.. Avoid using chemical substances as

Knjiga Sparidi otkriva tajne ribolova, od onih najatraktivnijih kao što su zubaci, pagari, komarèe, šargi i kantari pa do ništa manje u ribolovu uzbudljivih predstavnika sparida kao

In doing so, this study has traced the development of the Mexican assisted reproduction industry from esterilología to repro- ductive biology, from a clinical practice to a