Tektronix RFM220 User Manual

Download

RFM220

ISDB-Tb Measurem

ZZZ

User Manual

ent Demodulator

*P071289600*

071-2896-00

RFM220 ISDB-Tb Measurement Demodulator

ZZZ

User Manual

This document supports software version 1.0.

www.tektronix.com

071-2896-00

Copyright © Tektronix. All rights reserved. Licensed software products are owned by Tektronix or its subsidiaries or suppliers, and are protected by national copyright laws and international treaty provisions.

Tektronix products are covered by U.S. and foreign patents, issued and pending. Information in this publication supersedes that in all previously published material. Speciﬁcations and price change privileges reserved.

TEKTRONIX and TEK are registered trademarks of Tektronix, Inc.

Contacting Tektronix

Tektronix, Inc. 14150 SW Karl Braun Drive P.O . Bo x 50 0 Beaverton, OR 97077 USA

For product inf

In North America, call 1-800-833-9200. Worldwide , vis i t www.tektronix.com to ﬁnd contacts in your area.

ormation, sales, service, and technical support:

This warranty is for the hardware.

Warranty

Tektronix warrants that this product will be free from defects in materials and workmanship for a period of one (1) year from the date of shipment. If any such product proves defective during this warranty period, Tektronix, at its option, either will repair the defective product without charge for parts and labor, or will provide a replacement in exchange for the defective product. Parts, modules and replacement products used by Tektronix for warranty work may be new or reconditioned to like new performance. All replaced parts, modules and products become the property of Tektronix.

In order to obtain service under this warranty, Customer must notify Tektronix of the defect before the expiration of the warranty period and make suitable arrangements for the performance of service. Customer shall be responsible for packaging and shipping the defective product to the service center designated by Tektronix, with shipping charges prepaid. Tektronix shall pay for the return of the product to Customer if the shipment is to a location within the country in which the Tektronix service center is located. Customer shall be responsible for paying all shipping charges, duties, taxes, and any other charges for products returned to any other locations.

This warranty shall not apply to any defect, failure or damage caused by improper use or improper or inadequate maintenance and c resulting from attempts by personnel other than Tektronix representatives to install, repair or service the product; b) to repair damage resulting from improper use or connection to incompatible equipment; c) to repair any damage or malfunction caused by the use of non-Tektronix supplies; or d) to service a product that has been modiﬁed or integrated with other products when the effect of such modiﬁcation or integration increases the time or difﬁculty of servicing the product.

are. Tektronix shall not be obligated to furnish service under this warranty a) to repair damage

THIS WARRANTY IS GIVEN BY TEKTRONIX WITH RESPECT TO THE PRODUCT IN LIEU OF ANY OTHER WARRANTIES, EXPRESS OR IMPLIED. TEKTRONIX AND ITS VENDORS DISCLAIM ANY IMPLIED W TEKTRONIX' RESPONSIBILITY TO REPAIR OR REPLACE D EFECTIVE PRODUCTS IS THE SOLE AND EXCLUSIVE REMEDY PROVIDED TO THE CUSTOMER FOR BREAC H OF THIS WARRANTY. TEKTRONIX AND ITS VENDORS WILL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES IRRESPECTIVE OF WHETHER TEKTRON IX OR THE VENDOR HA S ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.

[W2–15AUG04]

ARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

This warranty is for the software media.

Warranty

Tektronix warrants that the m edia on which this software product is furnished and the encoding of the programs on the media will be free from defects in materials and workmanship for a period of three (3) months from the date of shipment. If any such medium or encoding proves defective during the warranty period, Tektronix will provide a replacement in exchange for the defective medium. Except as to the media on which this software product is furnished, this software product is provided “as is” without warranty of any kind, either express or implied. Tektronix does not warrant that the functions contained in this software product will meet Customer's requirements or that the operation of the programs will be uninterrupted or error-free.

In order to obtain service under this warranty, Customer must notify Tektronix of the defect before the expiration of the warranty period. If Tektronix is unable to provide a replacement that is free from defects in materials and workmanship within a reasonable time thereafter, Customer may terminate the license for this software product and return this software product and any associated materials for credit or refund.

THIS WARRANTY IS GIVEN BY TEKTRONIX WITH RESPECT TO THE PRODUCT IN LIEU OF ANY OTHER WARRANTIES, EXPRESS OR IMPLIED. TEKTRONIX AND ITS VENDORS DISCLAIM ANY IMPLIED WARRANTI TEKTRONIX' RESPONSIBILITY TO REPLACE DEFECTIVE MEDIA OR REFUND CUSTOMER'S PAYMENT IS THE SOLE AND EXCLUSIVE REMEDY PROVIDED TO THE CUSTOMER FOR BREACH OF THIS WARRANTY. TEKTRONIX AND ITS VENDORS WILL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES IRRESPECTIVE OF W HETHER TEKTRONIX OR THE VENDOR HAS ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.

ES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

[W9b – 15AUG04]

IMPORTANT

READ BEFORE OPERATING EQUIPMENT

This software is provided under license from Tektronix, Inc. Retention of this program for more than thirty (30) days or use of the program in any manner constitutes acceptance of the license terms.

CAREFULLY READ THE ENCLOSED SOFTWARE LICENSE AGREEMENT. If you cannot agree to the license terms, promptly contact the nearest Tektronix Field Ofﬁce for return assistance.

TEKTRONIX SOFTWARE LICENSE AGREEMENT

THE PROGRAM, OR PROGRAMS, ENCODED OR INCORPORATED WITHIN EQUIPMENT, IS FURNISHED SUBJECT TO OF THE PROGRAM FOR MORE THAN THIRTY DAYS OR USE OF THE PROGRAM IN ANY MANNER W ILL BE CONSIDERED ACCEPTANCE OF THE A GREEMENT TER MS. IF THESE TERMS ARE NOT ACCEPTABLE, THE UNUSED PROGRAM AND ANY ACCOMPANYING DOCUMENTATION SHOULD BE RETURNED PROMPTLY TO TEKTRONIX FOR A FULL REFUND OF THE LIC ENSE FEE PAID. (FOR INFORMATION REG ARDING THE RETURN OF PROGRAMS ENCODED OR INCORPORATED WITHIN EQUIPMENT, CONTACT THE NEAREST TEKTRONIX SALES OFFICE.)

DEFINITIONS. "Tektronix" means Tektronix, Inc., an Oregon corporation, or local Tektronix' legal entity that is supplying the equipment.

THE TERMS AND CONDITIONS OF THIS AGREEMENT. RETENTION

"Program" means the Tektronix software product (executable program and/or data) enclosed with this Agreement or included within the equipment with which this Agreement is packed.

"Customer" means the person or organization in whose name the Program was ordered.

LICENSE. Customer may:

1. Use the Program on any number of machines at any one time;

2. If the Program is provided in connection with a ﬂoating-user license, the Program may be used on multiple

machines provided that the user is authorized, and the total number of users at any one time does not exceed the total number of l icensed concurrent users;

3. Modify the Program or merge it with another for use on one or more machines by authorized users; and

4. Copy the Program for archival or backup purposes. The Program may be copied onto multiple machines for

use by authorized users.

Each copy of the Program made by Customer must include a reproduction of any copyright notice or restrictive rights legend appearing in or on the copy of the Program as received from Tektronix.

Customer may not:

1. Transfer the Program to any person or organization outside of Customer or the corporation of which Customer is a part without the prior written consent of Tektronix, except in connection with the transfer of the equipment within which the programs are encoded or incorporated;

2. Export or reexport, directly or indirectly, the program, any associated documentation, or the direct product thereof, to any country to which such export or reexport is restricted by law or regulation of the United States or any foreign government having jurisdiction without the prior authorization, if required, of the Ofﬁce of Export Administration, Department of Commerce, Washington, D.C. and the corresponding agency of such foreign government;

3. For object-code Programs only, reverse compile or disassemble the Program for any purpose; or

4. Copy the documentation accompanying the Program.

For Programs designed to reside on a single-machine and support one or more additional machines, either locally or remotely, without permitting the Program to be transferred to an additional machine for local execution, the additional machines shall be considered within the deﬁnition of "single machine".

Title to t he Program and all copies thereof, but not the media on which the Program or copies may reside, shall be and remain with Tektronix or others for whom Tektronix has obtained a respective licensing right.

Customer shall pay when due all property taxes that may now or hereafter be imposed, levied or assessed with respect to the possession or use of the Program or this license and shall ﬁle all reports required in connection with such taxes.

Any portion of the Program modiﬁed by Customer or merged with another program shall remain subject to these terms and conditions.

If the Program is acquired by or for an agency of the U.S. Government, the Program shall be considered computer software developed at private expense and the license granted herein shall be interpreted as granting Customer restricted rights in the Program and related documentation as deﬁned in the applicable acquisition regulation.

THE PROGRAM MAY NOT BE USED, COPIED, MODIFIED, MERGED, OR TRANSFERRED TO ANOTHER E

UPON TRANSFER OF ANY COPY, MODIFICATION, OR MERGED PORTION OF THE PROGRAM, THE LICENSE GRANTED HEREIN IS AUTOMATICALLY TERMINATED.

TERM. The license granted herein is effective upon acceptance by Customer, and shall remain in effect until terminated as provided herein. The license may be terminated by Customer at any time upon written notice to Tektronix. The license may be terminated by Tektronix or any third party from whom Tektronix may have obtained a respective licensing right if Customer fails to comply with any term or condition and such failure is not remedied

thin thirty (30) days after notice hereof from Tektronix or such third party. Upon termination by either party,

wi Customer shall return to Tektronix or destroy, the Program and all associated documentation, together with all copies in any form.

LIMITED WARRANTY. Tektronix warrants that the media on which the Program is furnished and the encoding of the Program on the media will be free from defects in materials and workmanship for a period of three ( 3) months from the date of shipment. If any such medium or encoding proves defective during the warranty period, Tektronix will provide a replacement in exchange for the defective medium. Except as to the media on which the Program is furnished, the Program is provided "as is" without warranty of any kind, either express or implied. Tektronix does not warrant that the functions contained in the Program will meet Customer's requirements or t hat the operation of the Program will be uninterrupted or error-free.

In order to obtain service under this warranty, Customer must notify Tektronix of the defect before the expiration of the warranty period. If Tektronix is unable to provide a replacement that is free from defects in materials and workmanship within a reasonable time thereafter, Customer may terminate the license for the Program and return the Program and any associated materials for credit or refund.

XCEPT AS EXPRESSLY PERMITTED BY THESE TER MS AND CONDITIONS.

THIS WARRANTY IS GIVEN BY TEKTRONIX WITH RESPECT TO THE PROGRAM IN LIEU O F ANY OTHER WARRANTIES, EXPRESS OR I MPLIED. TEKTRONIX AND ITS VEN DORS DISCLAIM ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULA R PURPOSE. TEKTRONIX' RESPONSIBILITY TO REPLACE DEFECTIVE MEDIA, OR REFUND CUSTOMER'S PAYMENT IS THE SOLE AND EXCLUSIVE REMEDY PROVIDED TO THE CUSTOMER FOR BREACH OF THIS WAR

LIMITATION OF LIABILITY, IN NO EVENT SHALL TEKTRONIX OR OTHERS FROM WHOM TEKTRONIX HAS OBTAINED A LICENSING RIGHT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR CONN ECTED WITH CUSTOMER'S POSSESSION OR USE OF THE PROGRAM, EVEN IF TEKTRONIX OR SUCH OTHERS HAS ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.

THIRD-PARTY DISCLAIMER. Except as expressly agreed otherwise, third parties from whom Tektronix may have obtained a licensin undertake to furnish any support or information relating thereto.

GENERAL. This Agreement contains the entire agreement between the parties with respect to the use, reproduction, and transfer of the Program.

Neither this Agreement nor the license granted herein is a ssignable or transferable by Customer without the prior written consent of Tektronix.

This Agreement and the license granted herein shall be governed by the laws of the state of Oregon.

g right do not warrant the program, do not assume any liability with respect to its use, and do not

RANTY.

All questions regarding this Agreement or the license granted herein should be directed to the nearest Tektronix Sales Ofﬁce.

ADDITIONAL LICENSE GRANT FOR VIDEO TEST SEQUENCES. The Software Product may include certain test

ns, video test sequences and video clips (together “Video Test Sequences”). If so, the following terms

patter describe Your rights to the Video Test Sequences:

You may use, copy and modify the Video Test Sequences and display or distribute copies of individual Video Test Sequences in connection with Your video testing activity.

are not licensed to do any of the following:

You

1. You may not distribute the collection of Video Test Sequences, except in connection with the sale of original equipment containing the Video Test Sequences, without prior written permission from Tektronix.

2. You may not permit third parties to distribute copies of the Video Test Sequences.

3. You may not sell, license or distribute copies of the Video Test Sequences on a standalone basis or as part of any

collection, product, or service where the primary value of the product or service is the Video Test Sequences.

You must indemnify, hold harmless, and defend Tektronix from and against any claims or lawsuits, including attorneys' fees, that arise from or result from the use or distribution of Video Test Sequences as modiﬁed by You.

You must include a valid copyright notice on Your products and services that include copies of the Video Test Sequences.

Table of Contents

General Safety Summary ........ ................................ ................................ .............. v

Compliance Information ............................. ................................ ........................ vii

EMC Compliance.................... ................................ .................................... vii

Safety Compliance............................... .................................... ..................... ix

Environmental Considerations ......... .................................... ............................. xi

Preface ..................... .................................... ................................ ............... xiii

Product Documentation ......................... ................................ ....................... xiii

Naming Conventions ........................ ................................ ........................... xiii

Related Products ............................. .................................... ....................... xiv

Firmware and Software Upgrades ............. ................................ ........................ xv

Conventions Used in This Manual. .................................... ................................ xv

Getting Started ................................ .................................... .............................. 1

Product Descri

Before Installation ........... .................................... ................................ .......... 6

Operating Considerations ....... ................................ .................................... ...... 7

Hardware Installation.................................... .................................... .............. 8

Powering the Instrument On and Off .......................... ................................ ........ 11

Software Installation..................... ................................ ................................ 12

Conﬁguration................................. .................................... ........................ 18

Starting the RFM220 Software......................... ................................ ................ 34

Operating Basics.................. ................................ ................................ ............ 41

RFM220 Instrument......... .................................... ................................ ........ 41

RFM220 Aggregator ............ .................................... ................................ .... 43

RFM220 Device Setup ...... .................................... ................................ ........ 47

220 Client... .................................... ................................ .................... 52

RFM

Alarm Thresholds.................................... ................................ .................... 63

Graphs..................... .................................... ................................ ............ 66

Event Logs........................ ................................ .................................... .... 70

Device Metrics ....................... ................................ ................................ .... 72

Reference.......... .................................... ................................ ........................ 75

Connecting to an MTM400A DTV Monitor . ................. .................................... .... 75

Frequency Shift Measurement.. .................................... ................................ .... 76

Recovering the IP Address.. .................................... ................................ ........ 77

Preventative Maintenance ...................... ................................ ........................ 83

Repacking for Shipment ........ ................................ .................................... .... 84

Troubleshooting.. ................................ ................................ ........................ 85

Index

ption.......................... .................................... .......................... 1

RFM220 User Manual i

Table of Contents

List of Figures

Figure 1: RFM220 ISDB-Tb Measurement Demodulator ............................. .................... 1

Figure 2: RFM220 system block diagram ....... ................................ ............................ 3

Figure 3: Chassis air ﬂow . ................................ ................................ .................... 8

Figure 4: Securing the instrument in an equipment rack........................................... ........ 8

Figure 5: RFM220 rear panel ..... ................................ .................................... ........ 9

Figure 6: Enabling the WCF HTTP and Non-HTTP activation features..................... .......... 14

Figure 7: Initial RFM220 InstallShield display ................. .................................... ...... 15

Figure 8: Selecting the applications to install ................... .................................... ...... 16

Figure 9: Installing the software .................. .................................... ...................... 17

Figure 10: Final InstallShield screen ..................... ................................ .................. 17

Figure 11: RFM220 shortcut icons ....................... ................................ .................. 18

Figure 12: RFM220 Device Setup dialog showing initial connection ................................ .. 20

Figure 13: Structure of the Conﬁguration.xml ﬁle.......................................... .............. 23

Figure 14: Partial Conﬁguration.xml ﬁle showing the ﬁle structure for monitoring two

RFM220 instruments .................. ................................ ................................ .. 30

Figure 15: Windows Fir

Figure 16: Adding the RFM220 Aggregator to the Windows ﬁrewall ............... .................. 32

Figure 17: Adding the Client Communications port to the Windows ﬁrewall............... .......... 32

Figure 18: Adding the Client Communications port to the Windows ﬁrewall............... .......... 33

Figure 19: Setting full access privileges ............. ................................ ...................... 35

Figure 20: RFM220 Aggregator window ................................ .................................. 37

Figure 21: Initial RFM220 Client login window........................ ................................ .. 38

Figure 22: RFM220 Client login window showing two monitored devices . .......................... 39

Figure 23: Initial RFM220 Client application window. ............................ ...................... 40

Figure 24: Front panel LED indicators............................................... ...................... 42

Figure 25: RFM220 rear panel.... .................................... ................................ ...... 42

Figure 26: RFM220 Aggregator application window ...... ................................ .............. 45

Figure 27: RFM220 Device Setup dialog................................ ................................ .. 47

Figure 28: RFM220 Device Setup dialog................................ ................................ .. 50

Figure 29: Setting the Windows 7 visual effects........ ................................ .................. 53

Figure 30: Setting the Windows XP display effects ................ ................................ ...... 53

Figure 31: RFM220 Client window elements .. ..................... ................................ ...... 56

Figure 32: RFM220 Client login window . . ................. .................................... .......... 57

Figure 33: Edit Settings dialog........................................ .................................... .. 58

Figure 34: Alarm Conﬁguration dialog .................. ................................ .................. 60

Figure 35: Change Password dialog...................................... ................................ .. 61

Figure 36: About window ............. ................................ ................................ ...... 61

Figure 37: Status bar ............................... ................................ .......................... 62

Figure 38: Alarm Conﬁguration dialog .................. ................................ .................. 63

Figure 39: Graphs pane .................... ................................ ................................ .. 66

Figure 40: Add Graph menu selections .................................. ................................ .. 67

Figure 41: RFM220 Client Logs pane ....... ................................ .............................. 71

ewall dialog ................. ................................ ...................... 31

ii RFM220 User Manual

Table of Contents

Figure 42: Metrics display....................................... ................................ ............ 72

Figure 43: Device Information metrics display ........................... ................................ 73

Figure 44: Combined RF and TS monitoring ................. ................................ ............ 75

Figure 45: Outputting the RF or ASI input signal to an MTM400A monitor . ........................ 75

Figure 46: Entering location information for HyperTerminal ....................... .................... 77

Figure 47: Entering the connection description for HyperTerminal .................... ................ 78

Figure 48: Selecting the COM port for HyperTerminal...................... ............................ 78

Figure 49: Entering the COM port properties for HyperTerminal .. ................................ .... 79

Figure 50: Setting the emulation mode for HyperTerminal.......................... .................... 80

Figure 51: Conﬁguring t

Figure 52: HyperTerminal window showing the ANSIW emulation mode........ .................... 81

Figure 53: HyperTerminal window showing the IP address in hex. ................................ .... 82

Figure 54: Enabling the WCF HTTP and Non-HTTP activation features ..... ........................ 88

he ASCII setup for HyperTerminal ........ .................................... 81

RFM220 User Manual iii

Table of Contents

List of Tables

Table i: Product documentation........................... ................................ ................. xiii

Table 1: Supported ISDB-Tb modes . .................................... ................................ .... 5

Table 2: Standard accessories......... ................................ .................................... .... 6

Table 3: Electrical operating requirements .................. ................................ ................ 7

Table 4: External connect

Table 5: RFM220 Aggregator platform requirements.......... .................................... ...... 13

Table 6: RFM220 Client platform requirements ............................ .............................. 13

Table 7: Error indicator color codes.................. ................................ ...................... 55

Table 8: Alarm measurement thresholds................................. ................................ .. 65

ors .......... ................................ ................................ ...... 10

iv RFM220 User Manual

General Safety Summary

Review the following safety precautions to avoid injury and prevent damage to this product or any products connected to it.

To avoid potential hazards, use this product only as speciﬁed.

Only qualiﬁed personnel should perform service procedures.

General Safety Summary

To Avoid Fire or

Personal Injury

Use proper power cord. Use only the power cord speciﬁed for this product

and certiﬁed for the country of use.

Ground the product. This product is grounded through the grounding conductor of the power cord. To avoid electric shock, the grounding conductor must be connected to earth ground. Before making connections to the input or output terminals of the product, ensure that the product is properly grounded.

Observe all terminal ratings. To avoid ﬁre or shock hazard, observe all ratings and markings on t information before making connections to the product.

Power disconnect. The power cord disconnects the product from the power source. Do not block the power cord; it must remain accessible to the user at all times.

Do not operate without covers. Do not operate this product with covers or panels removed.

Do not operate with suspected failures. If you suspect that there is damage to this product, have it inspected by qualiﬁed service personnel.

Avoid exposed circuitry. Do not touch exposed connections and components when power is present.

Use proper fuse. Use only the fuse type and rating speciﬁed for this product.

he product. Consult the product manual for further ratings

ot operate in wet/damp conditions.

Do n

Do not operate in an explosive atmosphere.

Keep product surfaces clean and dry.

Provide proper ventilation. Refer to the manual's installation instructions for

details on installing the product so it has proper ventilation.

RFM220 User Manual v

General Safety Summary

Terms in This Manual

Symbols and Terms on

the Product

These terms may appear in this manual:

WARNING. Warning statements identify conditions or practices that could

result in injury or loss of life.

CAUTION. Caution statements identify conditions or practices that could

result in damage to this product or other property.

These terms may appear on the product:

DANGER indicates an injury hazard immediately accessible as you read the marking.

WARNING indicates an injury hazard not immediately accessible as you read the marking.

CAUTION indicates a hazard to property including the product.

The following symbol(s) may appear on the product:

vi RFM220 User Manual

Compliance Information

This section lists the EMC (electromagnetic compliance), safety, and environmental standards with which the instrument complies.

EMC Compliance

EC Declaration of Conformity – EMC

Meets intent of Directive 2004/108/EC for Electromagnetic Compatibility. Compliance was demonstra

tedtothefollowingspeciﬁcations as listed in the

Ofﬁcial Journal of the European Communities:

EN 61326-1 2006. EMC requirements for electrical equipment for measurement, control, and laboratory use.

CISPR 11:2003. Radiated and conducted emissions, Group 1, Class A

IEC 61000-4-2:2001. Electrostatic discharge immunity

IEC 61000-4-3:2002. RF electromagnetic ﬁeld immunity

IEC 61000-4-4:

2004. Electrical fast transient / burst immunity

IEC 61000-4-5:2001. Power line surge immunity

IEC 61000-4-6:2003. Conducted RF immunity

IEC 61000-4-11:2004. Voltage dips and interruptions immunity

EN 61000-3-2:2006. AC power line harmonic emissions

EN 61000-3-3:1995. Voltage changes, ﬂuctuations, and ﬂicker

123

European contact.

Tektronix UK, Ltd. West e rn Pen i ns ula

tern Road

Wes Bracknell, RG12 1RF United Kingdom

This product is intended for use in nonresidential areas only. Use in residential areas may cause electromagnetic interference.

Emissions which exceed the levels required by this standard may occur when this equipment is connected to a test object.

For compliance with the EMC standards listed here, high quality shielded interface cables should be used.

RFM220 User Manual vii

Compliance Information

Australia / New Zealand

Declaration of

Conformity – EMC

Complies with the EMC provision of the Radiocommunications Act per the following standard, in accordance with ACMA:

CISPR 11:2003. Radiated and Conducted Emissions, Group 1, Class A, in accordance with EN 61326-1:2006.

Australia / New Zealand conta

Baker & McKenzie Level 27, AMP Centre 50 Bridge Street Sydney NSW 2000, Australia

ct.

viii RFM220 User Manual

Safety Compliance

Compliance Information

EC Declaration of Conformity – Low

Voltage

Additional

Compliances

Equipment Type

Safety Class

Pollution Degree

Description

Compliance was demonstrated to the following speciﬁcation as listed in the Ofﬁcial Journal of the European Communities:

Low Voltage Directive 2006/95/EC.

EN 61010-1: 2001. Safety req measurement control and laboratory use.

IEC 61010-1: 2001. Safety requirements for electrical equipment for measurement, control, and laboratory use.

Testandmeasuringequipment.

Class 1 – grounded product.

A measure of the con and within a product. Typically the internal environment inside a product is considered to be the same as the external. Products should be used only in the environment for which they are rated.

taminants that could occur in the environment around

uirements for electrical equipment for

Pollution Degree

Pollution Degree 1. No pollution or only dry, nonconductive pollution occurs. Products in this category are generally encapsulated, hermetically sealed, or located in clean rooms.

Pollution Degree 2. Normally only dry, nonconductive pollution occurs. Occasionally a temporary conductivity that is caused by condensation must be expected. This location is a typical ofﬁce/home environment. Temporary condensation occurs only when the product is out of service.

Pollution Degree 3. Conductive pollution, or dry, nonconductive pollution

ecomes conductive due to condensation. These are sheltered

that b locations where neither temperature nor humidity is controlled. The area is protected from direct sunshine, rain, or direct wind.

Pollution Degree 4. Pollution that generates persistent conductivity through conductive dust, rain, or snow. Typical outdoor locations.

ollution Degree 2 (as deﬁned in IEC 61010-1). Note: Rated for indoor use

P only.

RFM220 User Manual ix

Compliance Information

Installation

(Overvoltage) Category

Descriptions

Overvoltage Category

Terminals on this product may have different installation (overvoltage) category designations. The installation categories are:

Measurement Category IV. For measurements performed at the source of low-voltage installation.

Measurement Category III. For measurements performed in the building installation.

Measurement Category II. For measurements performed on circuits directly connected to the low-voltage installation.

Measurement Category I. For measurements performed on circuits not directly connected to MAINS.

Overvoltage Category II (as deﬁned in IEC 61010-1)

x RFM220 User Manual

Environmental Considerations

This section provides information about the environmental impact of the product.

Compliance Information

Product End-of-Life

Handling

Restriction of

Hazardous Substances

Observe the following guidel

Equipment recycling. Production of this equipment required the extraction and use of natural resources. The equipment may contain substances t hat could be harmful to the environment or human health if improperly handled at the product’s end of life. To avoid release of such substances into the environment and to reduce the use of natural resources, we encourage you to recycle this product in an appropriate system that will ensure that most of the materials are reused or recycled appropriately.

This symbol indicates that this product complies with the applicable European Union requirements according to Directives 2002/96/EC and 2006/66/EC on waste electrical and electronic equipment (WEEE) and batteries. For information about recycling options, check the Support/Servic

This product i the scope of the 2002/95/EC RoHS Directive.

sclassiﬁed as Monitoring and Control equipment, and is outside

ines when recycling an instrument or component:

e sec tion of the Tektronix Web site (www.tektronix.com).

RFM220 User Manual xi

Compliance Information

xii RFM220 User Manual

Preface

This manual describes how to install and operate the Tektronix RFM220 ISDB-Tb M easurement Demodulator.

Product Documentation

The following table lists the other documents supporting the RFM220 demodulator. These m anuals are available on the Tektronix Web site at www.tektronix.com/manuals.

Table i: Product documentation

Item (Tektronix part number) Purpose

RFM220 User Manual (071-2896-XX)

RFM220 Speciﬁcations and Performance Veriﬁcation Technical Reference (077-0565-XX)

RFM220 Declassiﬁcation and Security Instructions (077-0567-XX)

RFM220 Software License Notices Reference (001-1581-XX)

Provides installation and operational information (this document)

Provides complete product speciﬁcations and a procedure for verifying the operation of the instrument

Provides instructions for removing your proprietary information from the instrument

Provides the software licenses that cover the RFM220 software

Preface

Naming Conventions

This document uses the following naming conventions when referring to the different components of the RFM220 system:

RFM220 ISDB-Tb Measurement Demodulator. This is the hardware compon or just “instrument.”

RFM220 Aggregator application. This is the software application that collects data from monitored RFM220 instruments and is referred to as either “RFM220 Aggregator” or just “Aggregator.”

RFM220 Client application. This is the software application that displays the monitoring data collected by the Aggregator and is referred to as either “RFM220 Client” or just “Client.”

RFM220 Device Setup utility. This is the software application that allows the user to set the instrument network parameters, reset the instrument, or upgrade the instrument ﬁrmware and is referred to as the “Device Setup utility.”

ent of the system and is referred to as either “RFM220 instrument”

RFM220 User Manual xiii

Preface

Related Products

Tektronix also offers the following related products:

MTM400A DTV Monitor

IPM400A DTV Monitor

The MTM400A DTV Monitor provides a complete solution for multilayer, multichannel, remote monitoring to DVB, ATSC, DCII, and ISDB-T/Tb standards with content-checking support for MPEG-2 and H.264/AVC. Optional RF measurement interfaces provide a powerful and cost-effective solution for monitoring DVB-T transmitter sites or DVB-S/S2 uplinks and downlinks. An in-depth, real-time MPEG analysis option allows diagnostics to be performed on live broadcast signals without having to use deferred-time analysis of captured streams.

Refer to the MTM400A DTV Monitor Quick Start U ser Manual, Tektronix part number 071-2492-XX.

The IPM400A DTV Monitor is a powerful solution for remote monitoring of IP video national and regional headends. The IPM400A simultaneously veriﬁes both IP and TS integrity on all IP Video ﬂows (sessions) on a GbE link. It is ideal for monitoring networks which carry both Mul Transport Streams (MPTS) or Single-Program Transport Streams (SPTS), at either constant bit rate (CBR) or variable bit rate (VBR). An in-depth, real-time MPEG analysis option allows diagnostics to be performed on live payload without having to use deferred-time analysis of captured streams.

Refer to the IPM400A DTV Monitor Quick Start User Manual, Tektronix part number 071-2698-XX.

ti-Program

QAM400A DTV Monitor

RFM300 DTV Monitor

The QAM400A DTV Monitor provides a complete solution for remote real-time monitoring of cable broadcast signals. The comprehensive QAM RF and SI/PSI and PSIP conﬁdence-monitoring capabilities provide a powerful and cost-effective solution for monitoring HFC (hybrid ﬁbre-coaxial) cable headends. An in-depth, real-time MPEG analysis option allows diagnostics to be performed on live ATSC signals without having to use deferred-time analysis of captured streams.

Refer to the QAM400A DTV Monitor Quick Start User Manual, Tektronix part number 071-2784-XX.

The RFM300 DTV Monitor provides a complete solution for remote real-time DTV monitoring of ATSC signals. The comprehensive 8VSB RF and PSIP conﬁdence-monitoring capabilities provide a powerful and cost-effective solution for monitoring DTV transmitter sites, including contribution and distribution feeds at local and national operation centers for FCC compliance. An in-depth, real-time MPEG analysis option allows diagnostics to be performed on live ATSC signals without having to use deferred-time analysis of captured streams.

Refer to the RFM300 DTV Monitor Quick Start User Manual, Tektronix part number 071-2700-XX.

xiv RFM220 User Manual

Preface

VQS1000 Video Quality

Software

VQS1000 is a Video Quality Software application for single ended objective QoE analysis of video and audio content. It is designed for use with all current Tektronix IP Video and DTV Monitor probes using private backhaul video and audio and audio. It can also be used standalone for ﬁle analysis. Combined with physical transport alarms from the Tektronix probes, operators can determine if the source of a problem is in the content (for example, over-compression) or in network distribution layers.

Refer to the VQS1000 Video Quality Software Quick Start User Manual, Tektronix part number 077-0489-XX.

Firmware and Software Upgra des

Updates to the RFM220 system ﬁrmware and software are released to the Tektronix Web site when problems are ﬁxed or when new product features are introduced. (See page 51, Upgrading Instrument Firmware.) To check for ﬁrmwa (www.tektronix.com/products/video-test).

Conventions Used in This Manual

re or software upgrades, go to the Tektronix Web site

The following icons are used throughout this manual.

Sequence

Step

Front

panel

power

Connect

power

Network

PS2 SVGA USB

RFM220 User Manual xv

Preface

xvi RFM220 User Manual

Getting Started

Product Description

The Tektronix RFM220 ISDB-Tb Measurement Demodulator provides the means to measure and monitor signal performance for signals conforming to the Brazilian and Japanese ISDB-Tb terrestrial Digital TV standard.

The RFM 220 demodulator can measure MER in real time, commonly considered a key ﬁgure for qualifying a transmitting system. The input to the RFM220 demodulator can be an RF signal or an ASI stream. The software interface displays measurement traces, signal spectrum, and constellation and lets you conﬁgure and control the instrument using a local or remote Ethernet connection.

Installed at a tran monitor in real-time the essential signal performance ﬁgures such as input level, MER, shoulder levels, and error rate ratio. The ASI output on the RFM220 demodulator can output either the ASI input signal or the RF demodulated signal to feed an external video/audio decoder or a transport stream analyzer such as the Tektronix MTS400A MPEG Test System.

The RFM220 demodulator can be used as a standalone RF monitoring solution or used in conjunction with a Tektronix MTM400A DTV monitor to provide combined R DTV M onitor.)

Figure 1: RFM220 ISDB-Tb Measurement Demodulator

smission site, the RFM220 demodulator can continuously

F and TS monitoring. (See page 75, Connecting to an MTM400A

RFM220 User Manual 1

Getting Started

Key Features

Demodulator

Single RF input

Single ASI input

Automatic transmission mode recovery

Measurement probes

Full band input level

Channel input level

Left and right shoulder

Signal to Noise Ratio (SNR)

Carrier Frequency Offset (CFO)

Coarse MER

Fine MER per Layer

BER, PER

TS monitoring possible when the RFM220 output signal is fed to a TS

analyzer such

as the Tektronix MTM400A DTV Monitor

Measurement data

Recovery transmission mode (from TMCC)

SFN window (5 main echoes)

Measurement displays

Spectrum response

Coarse and overall Constellation pattern

Fine Constellation pattern per layer

Delay proﬁle

Clock and synchronization signal management

Internal 10 MHz but possibility to correct measures with external

reference

Control and management

Control via HTTP/Ethernet using the RFM220 software

Alarm management via SNMP

2 RFM220 User Manual

Getting Started

System Overview

The following illustration shows the block diagram of the RFM220 system, which consists of the following components: RFM220 instrument, RFM220 Aggregator application, and RFM220 Client application.

The RFM220 instrument(s) that will be monitored and the PCs running the RFM220 Client application must be connected to the same Ethernet network as the PC or server running the

The RFM220 system can be used as a standalone RF monitoring solution or used in conjunction with a Tektronix MTM400A DTV monitor to provide combined RF and TS monitoring.

RFM220 Aggregator application.

Figure 2: RFM220 system block diagram

RFM220 instrument. The RFM220 instrument is the hardware component

of the system. ASI and RF signals that are connected to the instrument are monitored remotely by the RFM220 Aggregator. SNMP traps are sent to the RFM220 Aggregator when signal measurements exceed the user-deﬁned limits, which are set using the RFM220 Client.

An individual RFM220 instrument can be monitored by only one RFM220 Aggregator at a time. Multiple RFM220 Clients can view the monitoring data for a single RFM220 instrument at a time by connecting to the RFM220 Aggregator that is monitoring the instrument.

RFM220 User Manual 3

Getting Started

RFM220 Aggregator applicaton. The RFM220 Aggregator application collects and stores data from RFM220 instruments and makes the data available to RFM220 Clients that connect to the Aggregator.

The RFM220 Aggregator can reside on a PC or on a network server. The typical RFM220 system installation will have the RFM220 Aggregator installedonanetworkserver RFM220 Client application installed.

The RFM220 Aggregator can be conﬁgured to collect data from up to ten RFM220 instruments at a time. Only one RFM220 Aggregator should connect to an individual RFM220 instrument at a time. M ultiple RFM220 Clients can connect to the RFM220 Aggregator at a time.

The RFM220 Aggregator conﬁguration can be changed using the Conﬁguration.xml ﬁle, which controls communications between the RFM220 system components (instrument, Aggregator, Client). The ﬁle can be updated dynamically, meaning that it can be updated while the RFM220 Aggregator is running.

RFM220 Client application. The RFM220 Client application allows the user to view the monitoring data collected by t he R FM220 Aggregator application.

,whereitcanbeaccessedbyremotePCswiththe

The data available for viewing includes event logs, metrics of signal parameters, device information such as the ﬁrmware version installed in the RFM220 instrument, and various graphs. You can view the data from any RFM220 instrument that the RFM220 Aggregator is m onitoring. Multiple RFM220 Clients can be connected at the same time to a single RFM220 Aggregator.

MTM400A DTV Monitor (TS monitoring). All RF-related monitoring of the input signal is performed by the RFM220 system. If you also want to perform TS-related monitoring of the input signal, you can route the output signal from

RFM220 instrument to a TS analyzer such as the Tektronix MTM400A

the DTV Monitor. (See page 75, Connecting to an MTM400A DTV Monitor.)

RFM220 Device Setup utility. The RFM220 Aggregator software includes the RFM220 Device Setup utility. This utility allows the administrator of the RFM220 system to connect to a RFM220 instrument to perform the following tasks:

View and change the network settings

View and change the secondary trap address and port number (for use with an NMS system)

Restart the instrument

Reset the instrument settings back to the default values

Upgrade the instrument ﬁrmware

View the type of instrument and the installed hardware and ﬁrmware versions

4 RFM220 User Manual

Getting Started

User Proﬁles and Roles

The RFM220 system uses two user proﬁles to control software access: Administrator and User. Each user proﬁle has different roles for supporting the RFM220 system.

Administrator. The Administrator proﬁle has the following roles:

NOTE. Although some of the administrative functions listed below can be

performed by any user, it is recommended that the person who i s assigned the role of RFM220 system administrator be the one responsible for these tasks.

Conﬁguring the RFM220 Aggregator and making sure t he correct RFM220 Client software is installed on all user PCs.

Conﬁguring the network settings for each RFM220 instrument and ensuring that each instrument is monitored by only one RFM220 Aggregator.

Assigning passwords to the Administrator and User proﬁles.

Ensuring that the correct set of RFM220 Clients are connecting to the correct RFM220 Aggregators

Conﬁguring the alarm thresholds and other measurement parameters.

Supported ISDB-Tb

Modes

Conﬁguring the channel plans and tuning the RFM220 instrument to a speciﬁc channel and frequency.

Upgrading the instrument ﬁrmware and the Aggergator and Client software as needed.

User. The User proﬁle has the following role:

Viewing the measurement status of the signal connected to the RFM220 instrument and generating error log reports.

NOTE. A person logged in under the User proﬁle is not be ab

le to change

the RFM220 system conﬁguration.

The RFM220 demodulator supports the ISDB-Tb modes listed below:

Table 1: Supported ISDB-Tb modes

Item Description

Transmission modes

Bandwidth 6 MHz

FFT (carrier spacing) Mode 1 (4 kHz), Mode 2 (2 kHz), Mode 3 (1 kHz)

Mapping

Time interleave From 0 to 32

Guard intervals 1/4, 1/8, 1/16, 1/32

FEC 1/2, 2/3, 3/4, 5/6, 7/8

Hierarchical mode

Multi-carrier (OFDM)

QPSK, 16QAM, 64QAM

Single layer, 1+12 layer, layered A+B, layered A+B+C

RFM220 User Manual 5

Getting Started

Before Installation

Unpacking the

Instrument

Installation Process

Unpack the instrument and check that you have received all of the standard accessories. (See Table 2.)

Table 2: Standard accessories

Accessory Tektronix part number

Certiﬁcate of Compliance

RFM220 Software and Documentation CD 063-4352-XX

RFM220 User Manual 071-2896-XX

Power cord – Brazil

The process for installing and starting the RFM220 system includes the following steps:

CAUTION. To prevent installation problems, the person assigned as the

RFM220 system administrator should perform these initial system-setup tasks. (See page 5, User Proﬁles and Roles.)

1. Install the RFM220 instrument and power the instrument on. (See page 8, Hardware Installation.)

001-1180-XX

N/A

2. Install the RFM 220 software. (See page 12, Software Installation.)

3. For each RFM220 instrument that you intend to monitor, reset the instrument settings back to the factory-default state and conﬁgure the network settings. (See page 18, Conﬁguring the Network Settings of a RFM220 Instrument.)

4. Edit the Conﬁguration.xml ﬁle for the RFM220 Aggregator. (See page 22, Conﬁguring the RFM220 Aggregator.)

5. Conﬁgure the Windows ﬁrewall settings. (See page 31, Conﬁguring the Windows Firewall.)

6. Start the RFM220 Aggregator application. (See page 35, Starting the RFM220 Aggregator.)

7. Start the RFM220 Client application. (See page 38, Starting the RFM220 Client.)

6 RFM220 User Manual

Operating Considerations

Getting Started

Electrical

The following table lists the electrical operating requirements for the RFM220 instrument. The complete electrical operating requirements are listed in the RFM220 Speciﬁcations and Performance Veriﬁcation Technical Reference.

Table 3: Electrical operating requirements

Requirement Speciﬁcation

Temperature, operating

Altitude, operating

Source voltage 100 to 240 VAC50/60 Hz, ﬂuctuations must not exceed

Power consumption

Peak inrush current 1 A peak at 240 VAC,50Hz

Fuse rating

Overvoltage category II (as deﬁned in IEC61010-1)

Pollution d

egree

+5 °C to +40 °C, 30 °C per ho temperature of the intake air at the front and sides of the instrument

0 to 3,000 m (9,800 ft.)

±10% of the nominal rate voltage

0.6 A, 100-240 V, 5

Mains fuse is 2 A, 250 V, delay fuse; internal (not operator repl service personnel.

2 (as deﬁned in IEC61010-1), rated for indoor use only

0/60 Hz, single phase

aceable). Refer servicing to qualiﬁed

ur maximum gradient,

Software

Ethernet Network

For the best operating performance, Tektronix strongly recommends that you install the RFM220 A ggregator and the RFM220 Client applications on separate computers. The Microsoft .NET Framework 3.5 software needs to be installed on the computer hosting t he RFM220 Client.

The RFM220 instruments that will be monitored and the PCs running the RFM220 Client application need to be connected to an Ethernet network which has access to the PC or server running the RFM220 Aggregator application.

RFM220 User Manual 7

Getting Started

Hardware Installation

Air Flow

Figure 3: Chassis air ﬂow

Rackmounting

The RFM220 demodulator chassis is cooled by drawing air in from the left side of the instrument and exhausting it out the right side of the instrument. (See Figure 3.)

CAUTION. To prevent damage to the instrument from overheating, do not

block the left or right side of the instrument. Leave at least two inches of clearance on each side.

The RFM220 demodulator chassis is designed to be a transportable platform. If you need to install the instrument into an equipment rack, use one of the following two methods:

Use appropriate hardware to secure the front face plate of the instrument to the rack, restraining the cantilevered mass of the instrument. (See Figure 7.)

Use a rack shelf to support the instrument.

Figure 4: Securing the instrument in an equipment rack

8 RFM220 User Manual

Getting Started

Connecting Signals to

the Instrument

Figure 5: RFM220 rear panel

The external connectors are all located on the rear panel of the instrument. (See Figure 43.) Refer to the RFM220 Speciﬁcations and Performance Ver iﬁcation Technical Reference for more detailed information about each connector and the associated signal requirements.

NOTE. The 1PPS In connector is not used. Do not connect a signal cable

to this connector.

After you install the RFM220 demodulator in the desired location, connect the power cord on the rear panel. Connect the power cord plug to a properly grounded electrical outlet.

CAUTION. To be sure of compliance with speciﬁed EMC standards and

directives, use only high quality shielded cables with this product. Equipment performance can be affected. Typically, the cables are braid and foil types that have a low impedance connection to shielded connectors at both ends.

that was provided with the instrument to the power connector

RFM220 User Manual 9

Getting Started

The following table describes the signal requirements for each connector.

Table 4: External connectors

Connector Description

RF input

Stream input (ASI) Connector: BNC, 75Ω

Stream output (ASI) Connector: BNC, 75Ω

10 MH z clock input

Gigabit (LAN/IP interface)

RS-232 port Connector: Sub-D9 female

1PPSIn

Connector: N type, 50Ω Standard: ISDB-Tb Input frequency range: 170-230 MHz / 470-862 MHz Bandwidth: 6 MHz Input amplitude range: –90 dBm to –30 dBm Maximum input level: 0 dBm

Transport stream rate: 50 Mbps maximum Data format: Accepts both Burst and Packet mode DVB-ASI format; 188/204 bytes

Transport stream rate: Same as ASI input Mode: Packet Format: 188/204 bytes

Connector: BNC, 50Ω Frequency: 10 MHz Level: -15 dBm to +15 dBm

Connector: 10/100/1000 Base-T; RJ-45 Use only good quality screened cable; Cat 6 Data rate: 100 Mbps maximum (2 streams) Packet type: IPv4 Mode: Half/full duplex Protocols:

Baud rate: 57600 bps Standard: RS-232 Other: No

This connector is not used.

IEEE802.3, RTP/UDP/IP, IPv4, ARP

parity, 8 bits data, 1 bit stop

CAUTION. Do not connect a signal cable to the 1 PPS In

connector.

10 RFM220 User Manual

Getting Started

Network Installation

The typical RFM220 system will have the RFM220 Aggregator installed on a network server where it can communicate with R FM220 instruments on the network and be accessed by network PCs that have the RFM220 Client application installed.

In this case, the network server that runs the RFM220 Aggregator must have two network ports that are ded

Control port. This port connects to the network to which the RFM220 instruments are connected. You will enter the IP address of the Control port in the “SNMPConﬁguration” section of Conﬁguration.xml ﬁle. (Seepage22,Conﬁguring the RFM220 Aggregator.)

Corporate port. This port connects to the network to which the PCs running the RFM220 Client application are connected. You will enter the IP address of the Corporate port in the “ClientCommunication” section of Conﬁguration.xml ﬁle. (Seepage22,Conﬁguring the RFM220 Aggregator.)

The RFM220 Aggregator software includes the RFM220 Device Setup utility that allows users to conﬁgure the network parameters of the RFM220 instrument. S you must assign the instrument a speciﬁc IP address. (See page 18, Conﬁguring the Network Settings of a RFM220 Instrument.)

ince the RFM220 instrument does not support DHCP service,

icated for RFM220 system communications:

NOTE. If necessary, contact your local network administrator for help in

entering the correct network parameters.

If you lose or cannot remember the IP address of a RFM220 instrument, you can recover the IP address using an RS-232 command. (See page 77, Recovering the IP Address.)

Powering the Instrument On and Off

The RFM220 demodulator has a rear-panel power switch located next to the

wer cord connector. (See Figure 5 on page 9.)

To power on the instrument, connect the power cord to your local power source, and then use the rear-panel switch to power on the instrument. The front-panel Power On LED will light up.

To power off the instrument, use the rear-panel switch to power off the instrument and then remove the power cord from the power source.

RFM220 User Manual 11

Getting Started

Software Inst allation

The RFM220 software consists of two applications and one utility:

CAUTION. For the best operating performance, Tektronix strongly

recommends that you install the RFM220 Aggregator and the RFM220 Client applications on separate computers. The RFM220 Aggregator and RFM220 Client computers must be connected to the same Ethernet network as the RFM220 instruments that w

RFM220 Aggregator. This application collects data from the RFM220 instrument and makes it available to the RFM220 Client application. The Aggregator can be conﬁguredtocollectdatafrom multiple RFM220 instruments at a time. The RFM220 Aggregator will typically be insta PCs running the RFM220 Client.

RFM220 Client application. This application allows the user to display the data that the RFM220 Aggregator has collected from any of the RFM220 instruments that it is monitoring. The RFM220 Client will typically be installed on PCs connected to the same network as the server running the RFM220 Aggregator.

ill be monitored.

lled on a network server where it can be accessed by

RFM220 Device Setup. This utility allows the user to set the IP address parameters for a RFM220 instrument. This utility is installed as part of the RFM220 Aggregator software.

12 RFM220 User Manual

Getting Started

Computer

Requirements

To communicate with the RFM220 instrument, you need to install the RFM220 software on a client PC or server. The following table lists the required platform requirements.

Table 5: RFM220 Aggregator platform requirements

Characteristic Description

Processor Minimum: Commonly available dual-core system;

for example, Intel Core 2 Duo CPU @ 2.66 GHz or similar Preferred: Commonly available quad-core system;

For example, Intel Xeon CPU E5420 @ 2.5 GHz or similar

Operating System Minimum: Microsoft Windows XP Pro or Windows 7

Preferred: Windows 7 with 64 bits

Disk Space Minimum: 120 MB free disk space

RAM

Ethernet

4GB

Dual 1 Gigabit interfaces

Table 6: RFM220 Client platform requirements

Characteristic Description

Processor

Operating System Microsoft Windows XP Pro or Windows 7

Disk Space 120 MB free disk space

RAM

Ethernet

Display 1024 x 768 pixel or higher resolution

Installed Software Microsoft .NET Framework 3.5 with Service Pack 1

Minimum: Commonly available dual-core system: For example, Intel Pentium D CPU @ 3.2 GHz or similar

4GB

1 Gigabit interface

RFM220 User Manual 13

Getting Started

Windows 7

Requirements

Installation privileges. To install the RFM220 software on Windows 7

systems, you must log on to the computer with administrative privileges.

Microsoft .NET Framework 3.5 feature requirements. If the RFM220 software is installed on a computer running Windows 7, the RFM220 software will not operate properly (for example, trend graphs will not be displayed) unless the WCF HTTP and Non-HTTP Activation features in the Microsoft .NET Framework 3.5 software are enabled.

Before you install the RFM Windows Features dialog and verify that the Microsoft .NET Framework 3.5 features are checked as shown below.

220 software on a Windows 7 computer, open the

Figure 6: Enabling the WCF H TTP and Non-HTTP activation features

14 RFM220 User Manual

Getting Started

Installing the RFM220

Software

Perform the following procedure to install the RFM220 software on your client PC:

1. Insert the RFM220 Software and Documentation CD into the CD drive of your client PC.

2. When the CD browser opens, click the Install Software button. Windows Explorer opens the directory containing the software installation ﬁles on the CD.

3. Copy the software installation ﬁles to a location on the hard drive of your computer.

4. Start the software installation process as follows for the operating system on your PC or server:

Windows 7 systems. Right-click the setup.exe ﬁle and select

Properties. If necessary, select Full Access andthenclosethe Properties dialog. Right-click the setup.exe ﬁle again and select Run as Administrator.

Windows XP systems. Double-click the setup.exe ﬁle.

5. When the RFM220 InstallShield Wizard welcome screen opens, click Next to continue.

Figure 7: Initial RFM220 InstallShield display

6. The next screen displays the software license agreement. Click Print to print out a copy of t he license agreement. After you read the license agreement, click I accept the terms of the license agreement,andthen click Next to continue.

RFM220 User Manual 15

Getting Started

7. The next screen lets you select which applications to install. Select which application(s) you want to install, and then click Next to continue.

CAUTION. For the best operating performance, Tektronix strongly

recommends that you install the RFM220 Aggregator and the RFM220 Client applications on separate computers.

To install the RFM220 software on a PC or server that will be

dedicated to running only only RFM220 Aggregator.

To install the RFM220 software on a PC that will be used as a client to

access the RFM220 Aggregator application located on another PC or server, select only RFM220 Client.

To install both the RFM220 Aggregator and the RFM220 Client

applications, select both RFM220 Aggregator and RFM220 Client.

the RFM220 Aggregator application, select

Figure 8: Selecting the applications to install

8. The next screen lets you select where to install the RFM220 software. If you want to install the software to a location other than the default location, click Browse and then navigate to your desired location. Click Next to continue. The default location of the software installation is here:

Windows 7 systems: C:\Program Files (x86)\Tektronix\RFM220

Windows XP systems: C:\Program Files\Tektronix\RFM220

9. The next screen gives you a chance to change your installation settings. Click Back to change your settings or click Install to proceed with the software installation.

16 RFM220 User Manual

Getting Started

10. As the software installs, a progress bar shows the progress of the installation.

Figure 9: Installing the software

11. When the software installation is complete, click Finish to exit the InstallShield Wizard.

Figure 10: Final InstallShield screen

RFM220 User Manual 17

Getting Started

12. After the software is installed, shortcut icons will appear on your desktop for the RFM220 Aggregator and/or RFM220 Client applications you installed. The RFM220 Aggregator, RFM220 Client, and RFM220 Device SetupapplicationsarealsolistedintheStartmenuunderAllPrograms > Tektronix.

Conﬁguration

Conﬁguring the

Network Settings of

a RFM220 Instrument

You can copy the RFM220 Device your desktop. The shortcut icons for all three RFM220 applications are shown below.

Figure 11: RFM220 shortcut icons

In order for the Aggregator to monitor a RFM220 instrument, the instrument must be on the same network as the computer hosting the Aggregator. In order for the RFM220 Client to communicate with an Aggregator, the Aggregator and Client computers must be on the same network. The RFM220 instrument and the Clie subnet, if present.

The RFM220 Aggregator software includes the RFM220 Device Setup utility that allows you to conﬁgure the network parameters of a RFM220 instrument. Since the RFM220 instrument does not support DHCP service, you must assign the instrument a speciﬁc IP address.

nt computers should also be connected to the same network

Setup shortcut from the Start menu to

NOTE. If necessary, contact your local network administrator for help in

entering the correct IP address parameters.

If you lose or cannot remember the existing IP address of a RFM220 instrument, you can recover the IP address using an RS-232 command. (See page 77, Recovering the IP Address.)

18 RFM220 User Manual

Getting Started

First time operation. If the network settings of the RFM220 instrument have not been changed from the factory-default settings, perform the following steps to prepare the instrument for use on your local network:

NOTE. This procedure is for ﬁrst-time operation only. If you have

already changed the network settings of the RFM220 instrument from the factory-default settings, perform the changing network settings procedure. (See page 49, Changing Network Settings.)

For this procedure, you will need a PC or laptop that is not connected to your local network.

1. Install t he RFM220 Aggregator software on a PC that is not connected to your local network.

2. Connect an Ethernet cable between the Gigabit port on the RFM220 instrument and the Ethernet port on the PC.

3. If necessary, power on the instrument.

4. Set the following network parameters on the PC:

IP address typ

IP address: 192.168.0.100

Subnet mask: 255.255.255.0

Gateway: Leave this ﬁeld empty

5. Open a command prompt on the PC, and then ping the default IP address of the RFM220 instrument: 192.168.0.209. If the ping fails, check your network settings, your connections to the network, and then try to ping the instrument again.

6. If the instrument responded to the ping, then locate the RFM220 Device Setup utility that was installed on your PC:

Windows 7 systems:

C:\Program Files (x86)\Tektronix\RFM220\RFM220

ggregator\RFM220DeviceSetup.exe

Windows XP systems:

C:\Program Files\Tektronix\RFM220\RFM220 Aggregator\RFM220DeviceSetup.exe

e: Static

NOTE. If you installed the RFM200 Aggregator software to a location other

than the default location, your path to the RFM220 Device Setup utility will be different than the path shown above.

RFM220 User Manual 19

Getting Started

7. Start the RFM220 Device Setup utility as follows for the operating system on your PC or server:

Windows 7 systems. Right-click the RFM220DeviceSetup.exe ﬁle

and select Run as Administrator.

Windows XP systems. Double-click the RFM220DeviceSetup.exe

ﬁle.

8. In the RFM220 Device Setup dialog, enter 192.168.0.209 in the Device IP Address box, and then click Connect.

9. After the RFM220 Device Setup utility connects to the instrument, the current network settings and device information ﬁelds are displayed.

Figure 12: RFM220 Device Setup dialog showing initial connection

NOTE. Always work with your local network administrator to properly set

these va

Make a note of the network settings you assign the instrument for later reference.

10. In the Change Network Settings ﬁelds, enter the network settings that are

lues.

appropriate for your network, and then click Save new network settings.

20 RFM220 User Manual

Getting Started

11. If you will be using an Network Management System (NMS) to monitor SNMP traps sent by the RFM220 system, perform the following steps. Otherwise, leave these ﬁelds blank and go to step 12.

a. Enter the IP address of the PC or server hosting the NMS system in

the New secondary trap box.

b. Enter the port number that will receive SN MP traps on the PC or

server hosting the NMS system in the New port number box.

c. Click Save new second trap settings.

CAUTION. If you enter a secondary trap destination, you need to ensure

that the secondary tr exceptions on the PC or server hosting the N MS system. This enables the NMS system to receive traps from the RFM220 system.

If you click Save new second trap settings, you must enter a valid IP address and port number for the secondary trap destination. You will receive an error message if a valid IP address is not entered.

ap port number is added to the Windows Firewall

12. Remove power from the instrument, connect the instrument to your network, and then reapply power.

13. On a PC that is connected to the same network as the instrument and has the RFM220 Aggregator software installed, use the RFM220 Device Setup utility to connect to the instrument using the new IP address.

14. In the RFM220 Device Setup dialog:

a. Click Reset to default settings.

b. Click Reset device.

15. Clos

e the RFM220 Device Setup dialog.

RFM220 User Manual 21

Getting Started

Conﬁguring the

RFM220 Aggregator

The R FM220 Aggregator is conﬁgured using the Conﬁguration.xml ﬁle, which contains various user-deﬁned parameters that control the communications between the three components of the RFM220 system: instrument, Aggregator, and Client. Consult with your local network administrator before setting these parameters.

Conﬁguration change requirements. The Conﬁguration.xml ﬁle can be updated dynamically. This means that after the ﬁle has been initially set up during the installation process, the ﬁle can be updated while the Aggregator is running. The Aggregato updated Conﬁguration.xml ﬁle when changes to the ﬁle are saved.

CAUTION. The RFM220 software will not work properly if you have more

than one RFM220 Aggregator monitoring an RFM220 i nstrument at a time. The Aggregator can communicate with multiple instruments at a time, but an individual instrument can only communicate with one Aggregator at a t ime.

In the case where more than one Aggregator has connected to an RFM220 instrument, only the last Aggregator to connect to the instrument will receive SNMP t

The RFM220 system requires the Conﬁguration.xml ﬁle in order to operate. It is recommended that you backup this ﬁle to a safe location. A copy of the default ﬁle is located on the RFM220 Software and Documentation CD that was shipped with the product.

rap messages from the instrument.

r will automatically load the parameters from the

After a conﬁguration change, the Aggregator requires approximately 2 minutes to reconﬁgure for each instrument listed in the Conﬁguration.xml ﬁle. To prevent software problems, you should wait at least 2 minutes after saving a change for each instrument listed in the ﬁle before you make additional changes to the Conﬁguration.xml ﬁle. For example, if 5 instruments are listed in the ﬁle, you should wait 10 minutes before making additional changes.

22 RFM220 User Manual

Getting Started

File structure. The Conﬁguration.xml ﬁle contains four sections of communication parameters. The default ﬁle contains comment sections, which describe the various parameters. The following illustration shows the structure of the ﬁle with the comment sections removed.

Client Communication contains the settings used by the RFM220 Aggregator for communicatio

SNMP Conﬁguration contains settings that are used by the RFM220 Aggregator to receive to alarm notiﬁcations (SNMP traps) from monitored RFM220 instruments.

ns with connected RFM220 Clients.

Diagnostic Log contains be logged into the Aggregator.Log ﬁle. This ﬁle contains log messages at the Aggregator level and is intended to be used only as a diagnostic aid.

NOTE. There is a separate DiagnosticLog setting in the Devices section of the

ﬁle for limiting which event messages appear in the RFM220 Client display and in the log ﬁle for each monitored RFM220 instrument.

Devices contains the communication settings for each of the RFM220 instruments that will be monitored by the RFM220 Aggregator.

settings that control which event messages will

Figure 13: Structure of the Conﬁguration.xml ﬁle

RFM220 User Manual 23

Getting Started

Procedure. Perform the following steps to edit the Conﬁguration.xml ﬁle (See Figure 13 on page 23.):

CAUTION. Read the requirements for making conﬁguration changes before

you edit the ﬁle. (See page 22, Conﬁguration change requirements.)

1. Before you edit the Conﬁguration.xml ﬁle, use the RFM220 Device Setup utility to conﬁgure the network settings of the RFM220 instrument(s) that will be monitored by the RFM220 Aggregator. (See page 18, Conﬁguring the Network Settings of a RFM220 Instrument.)

2. Use Wordpad, Notepad, or an XML editor to open the following ﬁle:

Windows 7:

C:\Program Files (x86)\Tektronix\RFM220\RFM220 Aggregator\Conﬁguration.xml

Windows XP systems:

C:\Program Files\Tektronix\RFM220\RFM220 Aggregator\Conﬁguration.xml

NOTE. If you installed the RFM220 software to a location other than the

default location, the path to your Conﬁguration.xml ﬁle will be different.

3. Edit the Client Communication parameters, which control the communications between the RFM220 Aggregator and connected RFM220 Clients.

a. Change the I PAddress parameter to match the IP address of the

network interface on the PC or server to which all RFM220 Clients will connect. This PC or server should be running the RFM220 Aggregator and be connected to the same network as all of the PCs running the R FM220 Client.

CAUTION. For the best operating performance, Tektronix strongly

recommends that you install the RFM 220 Aggregator and the RFM220 Client applications on separate computers. In the case where you need to run the Aggregator and Client applications on the same PC or server, you can enter "localhost" for this parameter instead of the IP address.

However, entering localhost limits access to the RFM220 Aggregator to only the RFM220 Clients that are installed on that PC or server. It is recommended that you use the IP address instead of localhost since that will allow RFM220 Clients to access the RFM220 Aggregator from PCs other than the one hosting the Aggregator.

24 RFM220 User Manual

Getting Started

b. Change the Port parameter to match the port number on the PC

or server running the RFM220 Aggregator that you will use to communicate with RFM220 Clients. You should change this value only if your PC or server is already using port 8000 for communication with other devices.

NOTE. You will need to add this port number to the Windows ﬁrewall

exceptions on the Aggregator PC or server to prevent communication problems between the Aggregator and any connected RFM220 Clients. (See page 31, Conﬁguring the Windows Firewall.)

The Aggregator will display the message “An attempt was m ade to access a socket in a way forbidden by its access permissions” if it detects communication conﬂicts with another device. In this case, change the value of this parameter to an unused port number.

c. Change the TimeoutInms parameter value as needed, based on

the performance of your network. This is the amount of time in milliseconds after which communications with an RFM220 Client will time out and a communication error message will be displayed.

4. Edit the SNMP Conﬁguration parameters, which are used by the RFM220 Aggregator to receive to alarm notiﬁcations (SNMP traps) from the RFM220 instruments. These settings are global in nature; they are applied to all RFM220 instruments that are monitored by the RFM220 Aggregator.

NOTE. The RFM220 Aggregator supports two trap destinations. The ﬁrst

destination is always set by the RFM220 Aggregator to itself so that it can record all alarms. The second destination is set for any other listener, such as an NMS (Network Management System), that needs to monitor alarms

aised by the RFM220 instruments.

a. Change the AggregatorTrapDestination IPAddress parameter to match

the IP address of the PC or server on which the RFM220 Aggregator is installed. This is the Control IP address.

CAUTION. To prevent communication problems, do not use “localhost” as

the Aggregator Trap Destination IP address. This address must be the IP address of the PC or server on which the RFM220 Aggregator is installed.

RFM220 User Manual 25

Getting Started

b. Change the AggregatorTrapDestination Port parameter to match

the port number on the Aggregator PC or server that will be used to receive SNMP traps from monitored RFM220 instruments. You should change this value only if your PC or server is already using port 162 for communication with other devices. The RFM 220 Aggregator will display an error message if it detects communication conﬂicts with other devices.

NOTE. You will need to add the Aggregator Trap Destination and

Get/Set UDP port numbers to the Windows ﬁrewall exceptions on the Aggregator PC or server t RFM220 Aggregator and any connected RFM220 Client. (See page 31, Conﬁguring the Windows Firewall.)

c. Change the GetSetUDPPort parameter to match the port number on the

Aggregator PC or server that will be used for UDP communications with the RFM220 Clients. You should change this value only of your PC or server is already using port 161 for communication with other devices. The RFM220 Aggregator will display an error message if it detects communication conﬂicts with other devices.

o prevent c ommunication problems between the

d. Change the GetCommunityString and SetCommunityString parameter

values as de required by your network.

e. Change the GetSetResponseTimeoutInms parameter value as

needed, based on the performance of your network. This is the amount of time in milliseconds after which Get and Set command communications with a monitored RFM220 instrument will time out and a communication error message will be displayed.

sired. These values should not need to be changed unless

26 RFM220 User Manual

Getting Started

5. Edit the Diagnostic Log parameters that control which event messages will be logged into the Aggregator.Log ﬁle. This ﬁle contains log messages at the Aggregator level and is intended to be used as a diagnostic aid.

NOTE. There is a separate DiagnosticLog setting in the Devices section of this

ﬁle for limiting which event messages appear in the log ﬁles for a speciﬁc device.

a. Change the DiagnosticLog Level parameter value to control which

events are logged into for this parameter are listed below. When this parameter is set to a value other than Off, the selected message level and the levels that are above the selected level will be logged. For example, if Info is set as the logging level, all messages for Info and Error will be logged. If Verbose is set as the logging level, all messages for Error, Info, Debug, and Verbose will be logged. Entering the value Off turns off the logging function. Entering the value All enables logging of all messages.

the Aggregator.Log ﬁle. The possible values

Off Error Info Debug Verbose All

b. Change the DiagnosticLog MaxFileSizeInMB parameter value as

needed to increase or decrease the maximum ﬁle size in megabytes for the Aggregator.Log ﬁle.

RFM220 User Manual 27

Getting Started

6. Edit the Devices parameters, which are used to govern the communications for each of the RFM220 instruments that will be monitored by t he RFM220 Aggregator.

a. Do not change the Device Type parameter value from RFM 220. This

parameter is for future use.

b. Change the IPAddress

of the RFM220 instrument that will be monitored by the RFM220 Aggregator.

CAUTION. The RFM220 software will not work properly if you

have more than one RFM220 Aggregator application monitoring an RFM220 instrument at a time. The Aggregator can communicate with multiple instruments at a time, but an individual instrument can communicate with only one Aggregator at a time.

c. Change the Name parameter to the device name, if any, that is

associated with the RFM220 instrument that will be monitored by the RFM220 Aggregator. The name you enter here will appear in the Client Login dialog to help you select a particular RFM220 instrument when the Aggregator is monitoring multiple RFM220 instruments.

d. Change the CommunicationMode parameter value from Normal to

Secure if you want communications between the RFM220 Aggregator and the RFM220 instrument CRC'd and veriﬁed at both ends.

e. Change the FTPCommunication ResponseTimeoutInms parameter

value as needed, based on the performance of your network. This is the

ount of time in milliseconds after which FTP communications with

am a monitored RFM220 instrument will time out and a communication error message will be displayed.

parameter to match the IP address

f. Change the HTTPCommunication ResponseTimeoutInms parameter

value as needed, based on the performance of your network. This is the amount of time in milliseconds after which HTTP communications with a monitored RFM220 instrument will time out and a communication error message will be displayed.

g. Change the MaxEventLogEntries RFEventLogs parameter value as

needed to increase or decrease the maximum number of entries in the RF Event log.

28 RFM220 User Manual

Getting Started

h. Change the MaxEventLogEntries DeviceEventLogs parameter value

as needed to increase or decrease the maximum number of entries in the Device Event log.

i. Change the DiagnosticLog Level parameter value to control the

amount of logging that occurs for the RFM220 instrument. The possible values for this para parameter is set to a value other than Off, the selected message level and the levels that are above the selected level will be logged.

For example, if Info is set as the logging level, all messages for Info and Error will be logged. If Verbose is set as the logging level, all messages for Error, Info, Debug, and Verbose will be logged. Entering the value Off turns off the logging function. Entering the value All enables logging of all messages.

Off Error Info Debug Verbose All

meter are listed below. When this

j. Change the DiagnosticLog MaxFileSizeInMB parameter value as

needed to i each event log.

ncrease or decrease the maximum ﬁle size in megabytes of

RFM220 User Manual 29

Getting Started

7. If you want the RFM220 Aggregator to monitor more than one RFM220 instrument at a time, edit the Conﬁguration.xml ﬁle as follows:

a. Duplicate the Device Type parameters in the Devices section of the

Conﬁguration.xml for each RFM220 instrument you want to monitor. The following ﬁgure shows a Conﬁguration.xml ﬁle with two Device sections, which allows the RF instruments.

b. For each Device Type section you duplicate, repeat step 5 to edit the

Devices parameters for the additional RFM220 instrument.

M220 Aggregator to monitor two

Figure 14: Partial Conﬁguration.xml ﬁle showing the ﬁle structure for monitoring two RFM220 i

nstruments

30 RFM220 User Manual

Getting Started

Conﬁguring the

Windows Firewall

Network communications between the RFM220 system components (instrument, Aggregator, and Client) may be inhibited unless the RFM220 Aggregator application and the communication ports that you conﬁgured in the Conﬁguration.xml ﬁle are set as exceptions in the Windows Firewall settings of the PC or server running the RFM220 software. Perform the following steps to set the Windows ﬁrewall exceptions:

1. Use the Start menu on your computer to open the Control Panel.

2. Double-click Windows Firewall to open the Windows Firewall dialog

shown below.

Figure 15: Windows Firewall dialog

RFM220 User Manual 31

Getting Started

3. Add the RFM220 Aggregator application to the ﬁrewall exceptions:

a. In the Windows Firewall dialog, click Add Program.

b. In the Add a Program dialog, select RFM220 Aggregator from the

Programs list, and then click OK to close the Add a Program dialog.

Figure 16: Adding the RFM220 Aggregator to the W indows ﬁrew all

4. Add the Client

a. In the Windows Firewall dialog, click Add Port.

b. In the Add a Port dialog, enter RFM220 Aggregator in the Name box.

c. In the Port number box, enter the port number you entered i n the

Client Communication section of the Conﬁguration.xml ﬁle. The default port number is 8000.

d. Select TCP, and then click OK to close the Add a Port dialog.

Communications port to the ﬁrewall exceptions:

Figure 17: Adding the Client Communications port to the Windows ﬁrewall

32 RFM220 User Manual

Getting Started

5. Add the SNMP Conﬁguration ports to the ﬁrewall exceptions:

a. In the Windows Firewall dialog, click Add Port.

b. In the Add a Port dialog, enter RFM220 Aggregator intheNamebox.

c. In the Port number box, enter the AggregatorTrapDestination Port

number you entered in the SNMP Conﬁguration section of the Conﬁguration.xml ﬁle. The default port number is 162.

d. Select UDP, and then click OK to close the Add a Port dialog.

e. Repeat steps a through d for the GetSetUDP Port number you entered

in the SNMP Conﬁguration section of the Conﬁguration.xml ﬁle. The default port number is 161.

f. If you used the RFM220 Device Setup utility to conﬁgure a secondary

SNMP trap address and port number to support an NMS system, repeat steps a through d using the network name of the PC or server hosting your NMS system and the port number you assigned to receive traps.

NOTE. You will also need to add the secondary trap destination port

number to the ﬁrewall exceptions on the computer hosting the NMS system.

Figure 18: Adding the Client Communications port to the Windows ﬁrewall

6. In the Windows Firewall dialog, click OK to accept t he changes and close the Windows Firewall dialog.

RFM220 User Manual 33

Getting Started

Starting the RFM220 Software

Starting the RFM220 software is a two step process. You must ﬁrst start the RFM220 Aggregator application and then start the RFM220 Client application.

CAUTION. The RFM220 instrument must be powered on and connected to the

same network as the PC/server on which the RFM220 Aggregator and Client applications are installed.

Windows 7 Privileges

Before you start the RFM220 software on a Window 7 system, ensure the following:

The user who is logged onto the computer has Full Access privileges for the RFM220 applications.

Start the RFM220 applications using the “Run as administrator” command.

Setting Full Access privileges. Perform the following steps to set access privileges for

1. Right click the RFM220 Aggregator or RFM220 Client icon on your desktop and select Properties.

2. Select the Security tab in the Properites dialog.

3. Select SYSTEM in the list of groups and user names, and then set the full

access permissions. (See Figure 19.)

4. Select Administrators in the list of groups and user names, and then set the full access permissions.

5. Select Users in the list of groups and user names, and then set the full access permissions.

6. Click OK to save the changes and close the Properties dialog.

the RFM220 software on a Windows 7 system:

34 RFM220 User Manual

Getting Started

Starting the RFM220

Aggregator

Figure 19: Setting full access privileges

Perform the following steps to start the RFM220 Aggregator application:

1. Before you sta tasks on the PC or server where you installed the RFM220 Aggregator application:

a. Use the RFM220 Device Setup utility to conﬁgure the network settings

of the RFM220 instrument(s) that the A ggregator will monitor. (See page 18, Conﬁguring the Network Settings of a RFM220 Instrument.)

b. Conﬁgure the Conﬁguration.xml ﬁle as necessary for your installation.

(See page 22, Conﬁguring the RFM220 Aggregator.)

c. Conﬁgure the Window Firewall to support network communications.

(See page 31, Conﬁguring the Windows Firewall.)

2. Start the RFM 220 Aggregator as follows for the operating system on your PC or server:

Windows 7 systems. Right-click the RFM220 Aggregator icon on

your desktop and select Run as Administrator.

Windows XP systems. Double-click the RFM220 Aggregator icon

on your desktop.

rt the Aggregator application, perform the following

RFM220 User Manual 35

Getting Started

3. The RFM220 Aggregator window displays messages as the application initializes. When the initialization is complete, you will see the message “Aggregator is ready.” (See Figure 20.)

CAUTION. To prevent communication problems with the RFM220 system, wait

until you see the message “Aggregator is ready” in the Aggregator window before you use the RFM220 Client to connect to the Aggregator.

During the initialization process, the Aggregator sets trap destinations, disables some alarms, and establishes communications with each RFM220 instrument that the Aggregator is conﬁgured to monitor. The initialization process must complete before monitoring data is valid.

The Aggregator initialization process takes approximately 70 seconds for each RFM220 instrument that the Aggregator will monitor. For example, if the Aggregator is conﬁgured to monitor 10 instruments, it will take approximately 11-12 minutes for

The Aggregator continously monitors the Conﬁguration.xml ﬁle. Whenever the ﬁle is edited and saved, any changes that were made to the ﬁle will immediately change the Aggregator conﬁguration.

the initialization process to complete.

After a conﬁgu minutes to reconﬁgure for each instrument listed in the Conﬁguration.xml ﬁle. To prevent software problems, you should wait at least 2 minutes after saving a change for each instrument listed in the ﬁle before you make additional changes to the Conﬁguration.xml ﬁle. For example, if 5 instruments are listed in the ﬁle, you should wait 10 minutes before making additional changes.

The Aggregator will display the message “An attempt was made to access a socket in a way forbidden by its access permissions” if it detects conﬂicts with

er device on a communication port. In this case, you will need to edit the

anoth Conﬁguration.xml ﬁle to change the conﬁgured port to an unused port number.

ration change, the Aggregator requires approximately 2

36 RFM220 User Manual

Getting Started

Figure 20: RFM220 Aggregator window

4. After the Aggregator initialization completes, you can deselect and minimize the RFM220 Aggregator window to ensure that the Aggregator application is not accidently closed.

CAUTION. When you close the RFM 220 Aggregator window, the

Aggregator w RFM220 instrument(s) and all existing trend data will be lost.

When the RFM220 Aggregator window is selected on the PC or server desktop, pressing Ctrl-C will close the RFM220 Aggregator application. To ensure that no trend data is lost, deselect or minimize the RFM220 Aggregator window after the application initializes.

5. Leave the PC or server on and t he RFM220 Aggregator application running for as long as you want the Aggregator to collect data from the RFM220 instruments it is monitoring.

ill no longer be able to collect data from the monitored

RFM220 User Manual 37

Getting Started

Starting the RFM220

Client

The RFM220 Aggregator must already be running before a RFM220 Client can connect to the Aggregator. Perform the following steps to start the RFM220 Client application:

1. On the PC where you installed the application, start the RFM220 Client as follows for the operating system on your PC or server:

Windows 7 systems. Right-click the RFM220 Client icon on your

desktop and select Run as Administrator.

Windows XP systems. Double-click the RFM220 Client icon on your

desktop.

Figure 21: Initial RFM220 Client login window

2. In the RFM220 Client Login window, enter the IP address or device name of the PC or server hosting the RFM220 Aggregator.

NOTE. For ﬁrst-time operation, the Aggregator box is blank. In future

logins, the last IP address or device name that you used to connect to a RFM220 Aggregator will be displayed.

If the Conﬁguration.xml ﬁle has been updated since the last time you logged on to the instrument to change the port number used by the Aggregator for

lient communications, you will need to add the new port number to the

C Aggregator IP address. For example, if the IP address of the Aggregator is

128.94.1.36 and the new port number is 8001, then enter 128.94.1.36:8001

in the Aggregator box.

38 RFM220 User Manual

Getting Started

CAUTION. When you use the RFM220 Client to connect to a

RFM220 instrument, the software does a version check to verify that the ﬁrmware version installed in the instrument and the software versions of the RFM220 Aggregator and RFM220 Client are all compatible.

If they are not compatible, an error message will be displayed and you will not be able to connect to the RFM220 instrument until the software or instrument ﬁrmware is upgraded to a com

3. After you enter the IP address or device name in the Aggregator box, click Find Devices.TheIPadd

RFM220 instruments being monitored by the selected Aggregator will be displayed in the Monitored Devices list.

NOTE. If a RFM220 instrument is added to the Aggregator after you click

Find Devices, you must click Find Devices again to see the additional instrument in the monitored devices list.

patible version.

resses, device names, and status for all of the

The following illustration shows a device name being used to connect to a RFM220 Aggregator, which is monitoring two RFM220 instruments.

Figure 22: RFM220 Client login window showing two monitored devices

RFM220 User Manual 39

Getting Started

4. Select the RFM220 instrument from the Monitored Devices list to which you want to connect. The selected device will be highlighted.

NOTE. The monitored devices list includes a status column, which lists the

status of the monitored device: Online or Ofﬂine. Ofﬂine devices are currently unavailable to the RFM220 Aggregator. (See page 55, Online and ofﬂine monitoring.)

5. Select a user name from the drop-down list: Administrator or User.

NOTE. Two user types are provided: Administrator and User. The

Administrator has full operating privileges. The User can view all data but cannot change alarm parameters or perform other administrative tasks. (See page 5, User Proﬁles and Roles.)

6. Enter the appropriate password. The default password is tek for the Administrator user type. There is no default password for the User.

7. Click the Connect button. For ﬁrst-time operation, the RFM220 Client appears as shown below with no log entries and the LED indicators in the Metrics pane grayed out. This indicates the default state of all tests being disabled.

The RFM220 enabled and alarms are conﬁgured. (See page 60, Alarm Conﬁguration.)

Client will show log events and metrics data after tests are

Figure 23: Initial RFM220 Client application window

40 RFM220 User Manual

Operating Basics

This section provides the basic operating information for each component of the RFM220 system:

RFM220 instrument

RFM220 Instrument

Installation

Considerations

Network Settings

RFM220 Aggregator applicat

RFM220 Client application

RFM220 Device Setup utility

Network installation. If you are operating the RFM220 system on a local Ethernet network, the RFM220 instrument(s) to be monitored must be connected to the same network as the PC or server hosting the RFM220 Aggregator application.

Non-network ins

Ethernet network, you must directly connect the Ethernet port on the RFM220 instrument to the Ethernet port on the PC or server hosting the RFM220 Aggregator and Client applications.

(See page 8, Hardware Installation.)

The RFM22 Use the RFM220 Device Setup utility to change the network settings of a RFM220 instrument so that it can operate on your network.

tallation. If you are operating the RFM220 system without an

0 instrument is shipped with a default IP address (192.168.0.209).

ion

(See page 18, Conﬁguring the Network Settings of a RFM220 Instrument.) (See page 47, RFM220 Device Setup.)

If you lose or cannot remember the IP address of a RFM220 instrument, you can recover the IP address using an RS-232 command. (See page 77, Recovering the IP Address.)

RFM220 User Manual 41

Operating Basics

Front Panel

The front panel has three LED indicators.

Figure 24: Front panel LED indicators

Alarm Status. This red LED has three states:

Off. Indicates there is no critical error.

Blinking. Indicates an input failure (no signal).

On. Indicates one of the following errors has occurred: temperature, internal failure, hardware failure, or software failure.

Ready Status. This green LED has three states:

Off. Indicates there is no input signal (AGC KO).

Blinking. Indicates that the input signal is OK, but that no measurements are possible (AGC KO, Carrier KO, or MPEG KO).

Rear Panel

On. Indicates that the i nput signal is OK, the measurements are OK, and the output stream is available.

Power On. This green LED has two states:

On. Indicates that the instrument is powered on.

Off. Indicates that the instrument is powered off.

Power switch. The power switch is located on the left side of the instrument rear panel. The power cord must be connected to a power source and this switch turned on before the instrument will operate. The front-panel Power On LED turns on to indicate when power is applied to the instrument.

Signal connectors. All of the signal connectors are located on the rear panel. (See page 9, Connecting Signals to the Instrument.)

CAUTION. To prevent operating problems, do not connect a signal cable to

the 1 PPS In connector.

Figure 25: RFM220 rear panel

42 RFM220 User Manual

RFM220 Aggregator

Operating Basics

The RFM220 Aggregator application collects data from monitored RFM220 instruments and makes it RFM220 Client applications. The RFM220 Aggregator can be conﬁgured to monitor up to 10 RFM220 instruments. (See page 18, Conﬁguration.)

available to be viewed by connected

Installation

Considerations

The typical RFM220 system installation will have the RFM220 Aggregator installed on a network server, where it can be accessed by network PCs with the RFM220 Client application installed. In this case, the network server that runs the RFM220 Aggregator must have two network ports that are dedicated for RFM220 system communications:

Control port. This port connects to the “Control” network of the RFM220 instruments, which is the network to which the RFM220 instruments are connected.

Corporate port. This port connects to the “Corporate” (public) network where users can use the RFM220 Client application to access the RFM220 Aggrega

With this installation scenario, you need to edit the “ClientCommunication” section of the Conﬁguration.xml ﬁle to enter the “Corporate” IP address of the server running the RFM220 Aggregator, and also edit the “SNMPConﬁguration” section of ﬁle to enter the “Control” IP address of the server.

If you do not have a local network, the RFM220 Aggregator and Client applications must be installed on the same PC or server, and the Ethernet port on the RFM220 instrument must be directly connected to the Ethernet port on the PC or server hosting the RFM220 applications.

tor.

Operating

Considerations

For the RFM220 system to operate properly, you need to observe the following operating conditions for the RFM220 Aggregator:

CAUTION. The RFM220 system will not operate as designed unless the

ollowing operating requirements for the RFM 220 Aggregator are observed.

For best system performance, install the RFM220 Aggregator and Client applications on separate computers. The computers must meet the minimum requirements. (See page 13, Computer Requirements.)

Although the RFM220 Aggregator can monitor up to 10 instruments and can have multiple RFM220 Clients connected at the same time, system performance diminishes as more instruments are monitored and as more RFM220 Clients connect to the Aggregator and display graphs.

For best system performance, the logging level should be set at Info in the Conﬁguration.xml ﬁle unless there is a speciﬁc signal problem or RFM220 system problem you are investigating.

RFM220 User Manual 43

Operating Basics

Only one Aggregator should monitor an RFM220 instrument at a time. The Aggregator can communicate with up to 10 instruments at a time, but an individual instrument can communicate with only one Aggregator at atime.

NOTE. In the case where more than one Aggregator has connected to an

RFM220 instrument, only the last Aggregator to connect to the instrument will receive SNMP trap messages from the instrument.

The Aggregator requires access to the Conﬁguration.xml ﬁle in order to operate. This ﬁle sets the parameters that control the communications between the different components of the RFM220 system. You must conﬁgure this ﬁle before you can operate the RFM220 system. (See page 22, Conﬁguring t

If the Conﬁguration.xml ﬁle is lost or deleted, the Aggregator will not be able to start or operate. The default location of the Conﬁguration.xml is as follows. The location will be different if you installed the Aggregator software to a location other than the default location.

he RFM220 Aggregator.)

Windows 7:

C:\Program Files (x86)\Tektronix\RFM220\RFM220 Aggregator\Conﬁguration.xml

Windows XP systems:

C:\Program Files\Tektronix\RFM220\RFM220 Aggregator\Conﬁguration.xml

A replacement copy of the default ﬁle is located on the RFM220 Software and D ocumentation CD that was shipped with the product. It is recommended that you save a backup copy of the Conﬁguration.xml ﬁle after you conﬁgure your system.

On Windows 7 systems, the user who has logged on as the Administrator

st have Full Access privileges.

44 RFM220 User Manual

Operating Basics

The RFM220 Aggregator must be started and fully initialized before a RFM220 Client can connect and view valid data from a monitored RFM220 instrument.

The Aggregator initialization process takes approximately 70 seconds for each instrument that the Aggregator will monitor. For example, if the Aggregator is conﬁgured t approximately 11-12 minutes for the initialization process to complete. When the Aggregator is fully initialized, the message “Aggregator is ready” is displayed, as shown near the bottom of the following illustration.

o monitor 10 instruments, it will take

Figure 26: RFM220 Aggregator application window

Once the Aggregator is started, the application should be left running for as long as you want to collect data from the RFM220 instruments.

The Aggregator collects and stores trend data from the instruments that it is monitoring. As long as the Aggregator stays running, the trend data remains available for all of the instruments that the Aggregator has monitored since it was started. However, all trend data will be lost when

Aggregator application is closed or shut down. Press Enter or Ctrl-C

the to close the RFM220 Aggregator.

The Aggregator will display the message “An attempt was made to access a socket in a way forbidden by its access permissions” if it detects conﬂicts with another device on a communication port. In this case, you will need to edit the Conﬁguration.xml ﬁle to change the conﬁgured port to an unused port number. (See page 86, Communication port conﬂicts.)

RFM220 User Manual 45

Operating Basics

The RFM220 Aggregator maintains all of the log and settings ﬁles in the following directories on the PC or server where the Aggregator is installed:

Windows 7:

C:\Users\<user ID>\AppData\Local\Tektronix\RFM220\RFM220 Aggregator\Logs

C:\Users\<user ID>\AppData\Local\Tektronix\RFM220\RFM220 Aggregator\Settings

Windows XP systems:

C:\Documents and Settings\<user ID>\Local Settings\Application Data\Tektronix\RFM220\RFM220 Aggregator\Logs

C:\Documents and Settings\<user ID>\Local Settings\Application Data\Tektronix\R

Since the trend data and log entries are lost when the Aggregator is shut down, it is recommended that the RFM220 system administrator backup the log and settings ﬁles before the Aggregator is stopped. The administrator should also ensure that no log ﬁles are present in the Logs folder when the Aggregator is restarted. (See page 70, Event Logs.)

FM220\RFM220 Aggregator\Settings

When you use the RFM220 Client to conﬁgure the alarm settings, you should leave enough range between the Active and Clear thresholds to account for minor signal ﬂuctuations. To prevent an SNMP alarm storm from overloading the Aggregator, If the error band is too narrow and the signal has a lot of ﬂuctuations, a large number of SNMP traps will be generated and can overload the Aggregator.

46 RFM220 User Manual

RFM220 Device Setup

Operating Basics

The RFM220 Device Setup utility dialog shown below is used by the RFM220 system administrator to perform the following tasks:

Conﬁguring the network settings of RFM220 instruments so they can operate on t he local network

Conﬁguring a secondary trap destination for use with an NMS system

Resetting a RFM220 instru default settings

Upgrading the instrument ﬁrmware

Viewing the hardware and ﬁrmware versions of the RFM220 instrument

ment or resetting the instrument back to the

Figure 27: RFM220 Device Setup dialog

RFM220 User Manual 47

Operating Basics

Performing RFM220

System Maintenance

The procedure for using the Device Setup utility to setup the RFM220 system is described in the Software Installation section of this manual. (See page 18, Conﬁguring the Network Settings of a RFM220 Instrument.)

If you need to perform maintenance on a RFM 220 instrument, such as changing the IP address, resetting the device, or upgrade the ﬁrmware, perform the following steps:

CAUTION. To prevent false errors from being reported in the event logs,

perform the following steps during system maintenance. If an instrument being monitored by a RFM220 Client is taken ofﬂine, the LED indicator for RF Lock in the Status bar will blink red and the Metrics pane will be grayed to indicate that the data is no longer valid.

All trend data and log entries for the RFM220 instrument is lost when the instrument is removed from the Conﬁguration.xml ﬁle. You should back up the following ﬁles be

Windows 7 systems: C:\Users\<user ID>\AppData\Local\Tektronix\RFM220\RFM220 Aggregator

Windows XP systems: C:\Documents Data\Tektronix\RFM220\RFM220 Aggregator

fore you perform instrument maintenance:

and Settings\<user ID>\Local Settings\Application

1. Notify us RFM220 instrument that will be removed from the system.

2. Delete the RFM220 instrument from the Conﬁguration.xml ﬁ le.

3. Use the Device Setup utility to perform maintenance on the instrument as

requi to the default settings and then reset the instrument.

4. Add the RFM220 instrument back into the Conﬁguration.xml ﬁle.

5. Use the RFM220 Client to set the alarm conﬁguration parameters for

e instrument.

6. Use the RFM220 C lient to select the correct channel plan and channel number, retune the channel input frequency, compensate for an external attenuation if one exists, and set the left and right shoulder distances.

7. Notify users that the instrument has been returned to the RFM220 system.

ers that they need to disconnect their RFM220 Client from the

red. After you perform the maintenance, be sure reset the instrument

48 RFM220 User Manual

Operating Basics

Changing Network

Settings

This procedure assumes that you have already installed the RFM220 instrument on your network and have powered the instrument on. For ﬁrst-time operation, perform the ﬁrst-time operation procedure. (See page 19, First time operation.)

Perform the following steps to conﬁgure the network settings of a RFM220 instrument. You should alway correctly set these values.

CAUTION. If you change the network settings of a RFM220 instrument, you

must reset the instrument before you use the Aggregator to start monitoring the instrument.

1. On the PC or server wh RFM220 Device Setup utility that was installed in the following directory:

Windows 7 systems:

C:\Program Files (x86)\Tektronix\RFM220\RFM220 Aggregator\RFM220DeviceSetup.exe

Windows XP systems:

C:\Program Files\Tektronix\RFM220\RFM220 Aggregator\RFM220DeviceSetup.exe

s work with your network administrator to

ere the RFM220 Aggregator is installed, locate the

NOTE. If you installed the RFM200 Aggregator software to a location other

than the default location, your path to the RFM220 Device Setup utility will be different than the path shown above.

2. Start the RFM220 Device Setup utility as follows for the operating system on your PC or server:

Windows 7 systems. Right-click the RFM220DeviceSetup.exe ﬁle

select Run as Administrator.

and

Windows XP systems. Double-click the RFM220DeviceSetup.exe

ﬁle.

3. In the RFM220 Device Setup dialog, enter the current IP address of the RFM220 instrument in the Device IP Address box, and then click Connect.

If you cannot locate the IP address of the instrument, you can recover the address using an RS-232 command. (See page 77, Recovering the IP Address.)

RFM220 User Manual 49

Operating Basics

4. After the RFM220 Device Setup utility connects to the RFM220 instrument, the current network settings and device information ﬁelds are displayed.

Figure 28: RFM220 Device Setup dialog

5. Enter any desired changes for the network settings and then click Save new network settings.

CAUTION. If you change the IP address of a RFM220 instrument, you must

reset the instrument as described in the following steps before you use the Aggregator to start monitoring the instrument.

After changing the network settings, the RFM220 Device Setup utility will not be able to access the instrument for a while if the instrument is on different subnet than the computer hosting the RFM220 Device Setup utility.

If you enter a secondary trap destination, you need to ensure that the secondary trap port number is added to the Windows Firewall exceptions on the PC or server hosting the NMS system. This enables the NMS system to receive traps from the RFM220 system.

6. If you want an NMS system to also monitor the SNM P traps sent by the RFM220 system, enter the secondary trap and associated port number in the appropriate boxes and then click Save new second trap settings.If you are not using an NMS system, leave the secondary trap ﬁelds blank.

7. Click Reset to default settings to reset the RFM220 instrument back to the default settings.

8. Click Reset device to reset the RFM220 instrument.

50 RFM220 User Manual

Operating Basics

9. Click Disconnect to disconnect the RFM220 Device Setup utility from the RFM220 instrument.

10. If you are conﬁguring multiple RFM220 instruments, repeat steps 3 to 9for each instrument.

11. Close the RFM220 Device Setup utility dialog.

Resetting Instruments

and Instrument

Settings

Upgrading Instrument

Firmware

The Device Setup utility provides the following selections for resetting RFM220 instruments:

Reset device. Use this selection to reset the RFM220 instrument to which you are connected. Measurement settings are not affected.

NOTE. You need to reset the instrument if you change the network settings

of a monitored instrument.

Reset to default settings. Use this selection to r eset the various instrument settings back to their default values.

Tektronix occasionally releases product ﬁrmware and software updates to introduce new features or to ﬁx product problems. If a instrument ﬁrmware update is available, perform these steps:

CAUTION. Before upgrading the instrument ﬁrmware, following the steps for

performing RFM220 system maintenance. (See page 48, Performing RFM220 System Maintenance.)

1. Download the upgrade ﬁrmware to the PC or server hosting the Aggregator.

2. Remove the instrument from the Conﬁguration.xml ﬁle.

3. Use the Device Setup utility to connect to the instrument.

4. Click Select ﬁrmware, and then browse to the location of the upgrade

ﬁles.

5. After you select the ﬁrmware ﬁles, click Upgrade to start the upgrade process.

CAUTION. While the instrument is being upgraded, do not power down

the instrument. If the instrument is powered down during an upgrade, the ﬁrmware will likely be corrupted, which will require the instrument to be returned to Tektronix for repair.

6. After the upgrade is complete, click Reset device to reset t he instrument.

7. Add the upgraded instrument back into the Conﬁguration.xml ﬁle.

RFM220 User Manual 51

Operating Basics

RFM220 Client

The RFM 220 Client application allows you to view the data that the RFM220 Aggregator application has collected from the RFM220 instrument(s) that the Aggregator is monitoring.

Installation

Considerations

The typical RFM220 system installation will have the RFM220 Aggregator installed on a network server, where it can be accessed by network PCs with the RFM220 Client application installed.

You can run the RFM220 Client application from any PC or server that is on the same Ethernet network as the PC or server on which the RFM220 Aggregator application is running. In situations where multiple Aggregators are installed, you can use the RFM220 Client to access any Aggregator runnin

The RFM220 Client can connect to only one Aggregator at a time and can view data from only one monitored RFM220 instrument at a time.

Multiple RFM220 Clients can establish network connections to the RFM220 Aggreg

NOTE. The performance of the RFM220 Aggregator diminishes as more

RFM220 Clients are connected and as more graphs are selected to be displayed by the RFM220 Clients.

For best system performance, install the Aggregator and Client applications on separate computers and limit the number of graphs that each RFM220 Client opens at a time to six.

g on the network.

ator and request for data for a particular device.

Improving Performance

Windows 7 systems. On Windows 7 systems, the RFM220 software is more

responsive when the Visual Effects settings are changed as follows:

1. Use Windows Explorer to navigate to the following ﬁle: \Windows\System32\SystemPropertiesPerformance.exe

2. Double-click SystemPropertiesPerformance.exe to open the

Performance Options dialog.

3. Select the Visual Effects tab, and then click Adjust for best performance

as shown below.

4. Verify that all of the boxes are unchecked in the Custom list, and then

click OK to save the changes and close the Performance Options dialog.

52 RFM220 User Manual

Operating Basics

Figure 29: Setting the Windows 7 visual effects

Windows XP systems. On Windows XP systems, the RFM220 software is

more responsive when the display effect settings are changed as follows:

1. Use the Start menu to open the Control Panel.

2. Double-clic

3. Select the Appearance tab, and then click Effects to open the Effect

dialog.

4. In the Effects dialog, select the settings as shown in the following illustra

k Display to open the Display Properties dialog.

tion, and then click OK to accept the changes.

Figure 30: Setting the Windows XP display effects

RFM220 User Manual 53

Operating Basics

General Operating

Information

User types. The RFM220 Client application allows you to log into an

RFM220 instrument using one of two user types:

Administrator. Log in as Administrator for unrestricted access to full operating privileges such as setting measurement thresholds.

User. Log in as User when you need to only view the measurement data or to generate log reports.

CAUTION. To operate the RFM220 software on Windows 7 systems, the user

who has logged on must have Full Access privileges.

Each user type has a different role for supporting and using the RFM220 system. Some functions of the Client application, such as using the Conﬁguration menu, are only available to a user logged in as the Administrator. (See page 5, User Proﬁles and Roles.)

Passwords. The default password for each user type are as follows:

Administrator: tek

User: none (blank)

A user must be logged in as the Administrator to change the passwords. Select Change Password in the Conﬁguration menu to open the Change Password dialog box. You can use the dialog box to change the password for both user types.

NOTE. The passwords are used for software access only. They do not provide

security for the monitoring data or for the instrument hardware.

54 RFM220 User Manual

Operating Basics

Error indicator color codes. The RFM220 Client uses colored LEDs to indicate the status of signal measurements and device events. Use the Alarm Conﬁguration dialog box to enable/disable tests, and to categorize error levels and set measurement limits for each test. (See page 60, Alarm Conﬁguration.)

Table 7: Error indicator color codes

Item Description

Red indicates that a test categorized as Critical has failed or that a threshold limit on a Critical test has been crossed.

Amber indicates that a test categorized as a Warning has failed or that a threshold limit on a Warning test has been crossed.

Blue indicates that a test categorized as Information has failed or that a threshold limit on a Information test has been crossed.

Green indicates that a test has not failed or that a threshold limit has not been crossed.

Gray indicates that a test is disabled.

Date and time displays. When the Aggregator is started, it pushes the UTC time into each instrument listed in the Conﬁguration.xml ﬁle. All of the times that are shown in the RFM220 Client displays (for example, in the e vent log entries and in the Status bar), are the times reported by the RFM220 instrument in terms of the time on the RFM220 Client computer, including taking into account the local time zone and daylight savings time settings.

Changes to the time zone or daylight savings time settings that occur on the RFM220 Client computer after the RFM220 Client has been started, will be automatically accounted for in the time displays on the RFM220 Client.

NOTE. There may be a small discrepency in the time displayed on the RFM220

Client computer and the time displayed in the RFM220 Client. This is caused by small time drifts in the RFM220 instrument that occur after the instrument receives the UTC time from the RFM220 Aggregator.

Online and ofﬂine monitoring. In the RFM220 Client Login dialog, the monitored devices list includes a status column, which lists one of the following as the status of the monitored device: (See Figure 22 on page 39.)

Online. Indicates that the device is an RFM220 instrument and that it is available to the Aggregator.

Ofﬂine. Indicates that the device is an RFM220 instrument and that it is turned off or otherwise unavailable to the Aggregator.

NOTE. Since trend data and log entries are stored by the RFM220 Aggregator

for as long as it remains running, you can still connect to an ofﬂine RFM220 instrument if that instrument was ever monitored by the Aggregator. In this case, you will be able to view trend data and event log entries for the ofﬂine device that was collected in the past while the device was online and being monitored by the Aggregator.

RFM220 User Manual 55

Operating Basics

Display Elements

The RFM220 Client window has the following primary display elements:

Title bar. Lists the name of the product: Tektronix RFM220.

Menu bar. Provides access to the various menu commands. Click on a menu name to access the commands under that menu. The menu commands are described on the following pages.

Status bar. Displays the status of various parameters. (See page 62, Status Bar.)

Graphs pane. Displays the graphs you select from the pull-down list. Controls allow you to change the graph layout, show error range indicators, and change the trend time scale of a graph. (See page 66, Graphs.)

Metrics pane. Displays the metrics of the measurement results and information about the selected device (RFM220 instrument).(See page 72, Device Metrics.)

Logs pane. Displays information about RF events (signal measurements) and device (RFM220 instrument) events. Control buttons allow you to pause, clear, or save the event log. (See page 70, Event Logs.)

Pane Controls. Allows you to completely collapse or expand the pane boundaries. You can adjust the pane sizes by dragging and dropping the pane boundaries.

Figure 31: RFM220 Client window elements

56 RFM220 User Manual

Operating Basics

Device Menu

The Device menu provides the following selections to enable you to connect or disconnect from an RFM220 instrument or to connect to another Aggregator.

Connect. Displays the RFM220 Client Login dialog. Use this dialog to connect to a different RFM220 instrument that is being monitored by the Aggregator to which you are connected or to connect to a different Aggegator that is running on the network. (See page 38, Starting the RFM220 Client.)

Figure 32: RF

Exit. Saves your settings and closes the RFM220 Client application.

M220 Client login window

RFM220 User Manual 57

Operating Basics

Conﬁguration Menu

The Conﬁguration menu provides the following selections to enable you to conﬁgure the channel plan, enable/disable tests and set alarm thresholds, or to change user passwords:

NOTE. A user must be logged in as the Administrator to select any of the items

in the Conﬁguration menu. (See page 5, User Proﬁles and Roles.)

Edit Settings. Displays the Edit Settings dialog shown below. Use this dialog to conﬁgure the channel plan for your input signal.

Figure 33: E dit Settings dialog

58 RFM220 User Manual

Operating Basics

The Edit Setting dialog allows you to perform the following tasks:

Conﬁgure the channel plan by setting the following parameters:

Channel Number. Select which channel will be monitored from either

the ISDB-Tb or ISDB-T channel plans. Select the appropriate plan and channel number for the input signal you intend to monitor.

Input Frequency. Enter the frequency for the selected channel. You

can set the channel frequency to any number between 170–862 MHz in Hertz. If you set the input frequency to a custom value that does not match the frequency of any of the channels in the selected Channel Plan, the Channel Plan se list is made empty.

Ext Attenuator. Enter the dB value of any external attenuator that is

connected to the input signal. This allows the RFM220 system to compensate for the attenuator and adjust the measurement thresholds for reporting signal errors.

Left and Right Shoulder Distance. Enter the distance (in kHz) for

the left and right shoulders. This allows the RFM220 system to compensate for the shoulder distance on the input signal. The default value is 3150 kHz.

lected is set as None and Channel Number

Conﬁgure which signal will be output from the ASI output connector of the RFM220 instrument. You can select either the ASI input signal or the RF dem

After you make any desired changes, click Apply to apply the changes. Click OK to apply the changes and close the dialog box.

odulated signal.

RFM220 User Manual 59

Operating Basics

Alarm Conﬁguration. Displays the Alarm Conﬁguration dialog shown below. Use this dialog to enable/disable tests and set alarm measurement parameters. After you make any desired changes, click Apply to apply the changes. Click OK to apply the changes and close the dialog window.

Information about how to set the measurement thresholds is provided later in this manual. (See page 63, Alarm

CAUTION. To prevent an SNMP alarm storm from overloading the Aggregator,

you should leave enough range between the Active and Clear threshold to account for minor signal ﬂuctuations. If the error band is too narrow and the signal has a lot of ﬂuctuations, a large number of SNMP traps will be sent to the Aggregator.

Thresholds.)

Figure 34: Alarm Conﬁguration dialog

60 RFM220 User Manual

Operating Basics

Change Password. Displays the Change Password dialog shown below.

About Menu

Figure 35: Change Password

Select the user type (Administrator or User) of the password you are changing, and then enter the old password and the new password. Click OK to save the new password and close the Change Password dialog.

Displays the About the RFM220 hardware and software versions.

window shown below, which contains information about

dialog

Figure 36: About window

RFM220 User Manual 61

Operating Basics

Status Bar

The Status bar appears at the bottom of the Client display and provides the following information:

Logged in as. Lists which user type (Administrator or User) was used to login to the RFM220 system. Each user type has different roles. (See page 5, User Proﬁles and Roles.)

Aggregator. Lists the IP address or network name that was used to connect to the Aggregator in the RFM220 Client Login dialog.

Device. The device section lists the following information:

IP. This is the IP address of the RFM220 instrument to which you

are connected.

Date & Time. This is the current date and time of the RFM220

instrument to which you are connected. The time displayed here and in the event logs may vary from the time displayed on your computer. (See page 55, Date an

Status. This colored LED indicates t he current status of the instrument.

Green indicates the instrument is online and red indicates the instrument is ofﬂine. When an instrument is ofﬂine, the Metrics display grays out to indicate that the displayed signal parameters are no longer valid.

d time displays.)

Figure 37: Status bar

RF lock. Displays a colored LED to indicate whether the RFM220 instrument is locked to the frequency of the input signal:

Green indicates that the instrument is locked to the input signal.

Red indicates that the instrument is not locked to the input signal.

ASI Output. Lists which signal is being output from the ASI ouput connector on the RFM 220 instrument (ASI Input Signal or RF Demodulated Signal). Use the Edit Settings dialog to change which signal is output. (See page 58, Edit Settings.)

62 RFM220 User Manual

Alarm Thresholds

Operating Basics

Select Alarm Conﬁguration from the ConﬁgurationmenuintheRFM220 Client, the Alarm Conﬁguration to enable/disable tests and set alarm measurement parameters.

NOTE. When you enable/disable tests or change measurement thresholds,

information messages are entered in the Device Event log. The messages are color-coded blue to indicate they are information-only messages. (See page 55, Error indicator color codes.) (See page 70, Event Logs.)

dialog opens as shown below. Use this dialog

Figure 38: Alarm Conﬁguration dialog

RFM220 User Manual 63

Operating Basics

The Alarm Conﬁguration dialog allows you to perform the tasks listed below. After you make any desired changes, click Apply to apply the changes and then click OK to save the changes and close the dialog window.

Enable/disable tests. Click the box next to the test names to enable or disable tests. Enabled tests are indicated by a check mark. Disabled tests are indicated by a gray LED in t

Set the Active threshold. Click in the Value ﬁeld and enter the measurement threshold for each test. When this threshold is exceeded, an error message will be generated. The Min/Max Value columns list the threshold ranges for each test. The Nominal column lists the recommended value for the test.

NOTE. When there is a change in the Alarm state, for example, when the

measurement value crosses the Active threshold or when it crosses the Clear threshold, SNMP t secondary trap destination intended for your NMS System (if you used the Device Setup utility to conﬁgure the secondary trap destination).

raps are generated and sent to the Aggregator and to the

he Metrics pane.

Set the Clear threshold. Click in the Value ﬁeld and enter the measurement threshold for each test. When this threshold is crossed by a test that is in an active error condition, an error-cleared message will be generated.

Set the Severity level. Set the error-reporting severity level for each test by picking from the drop-down list: Critical, Info, or Warning. Color codes are assigned to the status LEDs based on the severity levels that are conﬁgured here. (See page 55, Error indicator color codes.)

Conﬁgure the Delay proﬁle echo parameters. Enable or disable the Delay Proﬁle Echo measurement to set parameters such as amplitude level and distance for echo-related time distortions. If the echo distance is set to User Deﬁned, you can set the distance limits for modes 1 ,2 and 3. Alarms occur if the echo amplitude is higher than the Amplitude level you set and if it is outside of the set region. If the echo distance mode is set to Automatic, alarms are generated based on the Mode and Guard Interval.

NOTE. The Delay Proﬁle alarm is a software alarm, unlike the other alarms

which are SNMP alarms. Therefore, alarms generated by the Delay Proﬁle alarm will not be sent to the secondary t rap destination that is intended for your NMS System.

64 RFM220 User Manual

Operating Basics

Measurement

Thresholds

The following table shows the default active and clear thresholds for each test along with the maximum and minimum values for each test. The nominal value is the normally expected value for the test.

CAUTION. To prevent an SNMP alarm storm from overloading the Aggregator,

Table 8: Alarm measurement thresholds

Active

Test name

Channel (input) level upper threshold -30 dBm -32 dBm -90 dBm -30 dB m -30 dBm

Channel (input) level lower threshold

Full band level upper threshold -10 dBm -12 dBm -50 dBm -10 dBm -10 dBm

Full band level lower threshold -50 dBm -48 dBm -50 dBm -50 dBm -10 dBm

Layer A MER lower threshold 20 dB 22 db 15 dB 20 dB 37 dB

Layer B MER lower threshold 20 dB 22 db 15 dB 20 dB 37 dB

Layer C MER lower threshold

Left shoulder lower threshold

Right should lower threshold 35 dB 37 dB 15 dB 35 dB 44 dB

BER ( Bit Error Rate) upper threshold

PER (Packet Error Rate) upper threshold

Carrier frequency offset upper threshold 5,000 Hz 4,000 Hz -340,000 Hz 5,000 Hz 340,000 Hz

Mean SNR lower threshold

Delay proﬁle echo -25 dB NA -25 dB -25 dB 0 dB

threshold

-90 dBm -88 dBm -90 dBm -90 dBm -30 dBm

20 dB 22 dB 15 dB 20 dB 37 dB

35 dB 37 dB 15 dB 35 dB 44 dB

100,000 parts per billion

20 dB 22 dB 0 dB 20 dB 28 dB

Clear threshold

10,000 parts per billion

Minimum value

0 parts per billion

Nominal value

100,000 parts per billion

Maximum value

1,000,000,000 parts per billion

Compensating for an external attenuator. If your input signal has an external attenuator, you need to adjust the alarm thresholds to compensate for the attenuator.

RFM220 User Manual 65

Operating Basics

Graphs

The Graphs pane is where measurement graphs are displayed and controlled.

CAUTION. The graphs will not display properly if the resolution of your

computer monitor is less than 1024 x 768 pixels.

NOTE. The performance of the RFM220 Aggregator diminishes as more

RFM220 Clients are connected and as more graphs are selected to be displayed by the RFM220 Clients. For best system performance, install the Aggregator and Client applications on separate computers and limit to six, the number of graphs that each RFM220 Client opens at a time.

Figure 39: Graphs pane

66 RFM220 User Manual

Operating Basics

Selecting Graphs

Use the drop-down list of the Add Graph menu to select/deselect graphs to display. You can select multiple graphs to display. Selected graphs are indicatedbyacheckmark.

NOTE. As you select more graphs to display, the performance of the

RFM220 software will diminish.

Figure 40: Add Graph menu selections

Trend graphs. All of the graphs in the Add Graph list that appear above the

graph list separator are trend graphs.

The Aggregator collects and stores trend data from the instruments that it is monitoring. As long as the Aggregator stays running, the trend data remains availab it was started. However, all trend data will be lost when the Aggregator application is closed or shut down, or when the instrument is removed from the Conﬁguration.xml ﬁle.

le for all of the instruments that the Aggregator has monitored since

RFM220 User Manual 67

Operating Basics

Special graphs. Constellation and spectrum graphs enable you to identify modulation problems such as amplitude imbalance, quadrature error, coherent interference, phase noise, amplitude noise, phase error and MER problems. Left and right shoulder measurements are displayed in dB to help indicate if there are spectrum mask issues.

NOTE. Special graphs are shown properly only if the instrument is online.

Special graphs for Ofﬂine instruments will show a “Loading Data” message. If a special graph is already open and showing data when an instrument goes ofﬂine, the special graph will continue to show the old data or the last graph obtained.

If the RF input signal to the RFM220 instrument is not proper or if RF lock to the signal is lost, the Constellation graph will not show data and a “Loading Data” message will be continuously displayed. A possible cause of this problem in an inaccurately tuned channel frequency. Use the Conﬁguration menu to edit the channel plans and tune channel frequencies. (See page 58, Conﬁguration Menu.)

Changing the Graph

Layout

Change Layout menu. Use the Change Layout drop-down list to select one of

the following layouts:

Horizontal

Vertical

Tiled Horizontal

Tiled Vertical

Pane controls. Allows you to completely collapse or expand the pane boundaries. You can adjust the pane sizes by dragging and dropping the pane boundaries. (See Figure 31.)

Graph selection. Clickonagraphtoselectit. Theselectedgraphwillhave a red line around the graph.

Error range indicators. The Error Range Indicator check box is only available when a trend graph or the Delay Proﬁle graph is seleted. When the error range indicators are displayed, the error thresholds are indicated by red areas on the graph.

Trend timescales. The Trend Timescale drop-down list is only available when a trend graph is selected. The following t ime scales are available:

Previous minute

Previous ten minutes

Previous hour

Previous day

Previous week

68 RFM220 User Manual

Operating Basics

Trend Graph Updates

Trend graph displays are updated as follows:

The error range indicators are updated with every update cycle of the trend graphs.

The update rate of the trend graphs depends on the time scale that is selected:

When “Previous minute” or “Previous ten minutes” is selected, graphs

are updated every 5 seconds.

When “Previous hour” is selected, graphs are updated every 12

seconds.

When “Previous day” is selected, graphs are updated every 5 minutes.

When “Previous week” is selected, graphs are updated every hour.

NOTE. When “Previous day” or “Previous week” i s selected as the time

scale for a graph, changes that are made to the active alarm threshold are not immediately reﬂected on the error range band of the graph. You can force the graph to update by closing and reopening either the graph or the application itself.

Error Range Indicators

Plot Lines

The error-range indicators on the graph displays correspond (See Figure 39 on page 66.) t dialog. (See page 63, Alarm Thresholds.)

For trend graphs, the error range indicators behave as follows:

The error range indicators show the same value as the corresponding Activ

The presence of the upper and lower error bands depends on the presence of the upper and lower alarms for that metric. If a metric has only an upper limit, only the upper error-range band will be displayed. An error-range band will not be shown f or metrics that do not have either an upper or lower value alarm.

The error range indicators on the graphs are updated at every update cycle of the trend graphs.

Most of the graphs have a Settings button in the top right corner which allows you to add or remove plot lines on the graph. You can select the following plot lines to display. By default, all plot lines are shown.

Draw maximum. Draws a plot line for the maximum measurement.

Draw average. Draws a plot line for the average measurement.

o the active alarm thresholds set in the Alarm Conﬁguration

e alarm threshold value for that metric.

Draw minimum. Draws a plot line for the minimum measurement.

RFM220 User Manual 69

Operating Basics

Event Logs

The RFM220 Aggregator creates and stores events from monitored RFM220 instruments in log ﬁles.

Log File Location

Log File Types

Log File Management

The RFM220 Aggregator maintains all of the log ﬁles in the Application Data folder on the PC or server where the Aggregator is installed. The path to these ﬁles are as follows:

Windows 7 systems: C:\Users\<user ID>\App Aggregator\Logs

Windows XP systems: C:\Documents and Settings\<user ID>\Local Settings\Application Data\Tektronix\RFM220\RFM220 Aggregator\Logs

There are two t yp

Aggregator.log, which contains log entries that are related to the Aggregator. A user will not typically need to access this ﬁle.

<IP address>.log, w hich contains the device logs for the associated RFM220 inst RFM220 instrument that the Aggregator has monitored.

Backingupthelogﬁles. To prevent the loss of data, it is recommended that the RFM220 system administrator backup the log ﬁles whenever the Aggregator is stopped (for example, if the RFM220 system requires maintenance or if

is a reason to stop the Aggregator).

there

es of log ﬁles in the Logs directory:

rument being monitored. There will be a ﬁle for each

Data\Local\Tektronix\RFM220\RFM220

CAUTION. To prevent the loss of data after the Aggregator has been shut

down, the RFM220 system administrator needs to ensure that no log ﬁles are present in the Logs folder before the Aggregator is restarted.

Saving log ﬁles. To help solve a problem with your RFM220 system, Tektronix may request a copy of your log ﬁles. If your logging has been set to a low level such as Info in the Conﬁguration.xml ﬁle (See page 22, Conﬁguring the RFM220 Aggregator.), Tektronix may request that you change the logging to a higher level such as Debug or Verbose in order to get a better diagnosis of the problem. Except in such support request cases, users are advised to set the logging level to Info.

Log size control. The size of the event logs and the length of the log entries is controlled by the Conﬁguration.xml ﬁle used by the RFM220 Aggregator.

70 RFM220 User Manual

Operating Basics

Preexisting Errors

RFM220 Client Logs

Display

Aggregator startup. When the Aggregator is ﬁrst started, errors may already

exist in the monitored signal. Since the Aggregator cannot know when the preexisting error started, the error is reported in the event logs with the preﬁx “Synchronized” to indicate that the error started prior to the Aggregator starting to monitor the signal. This type of message is also displayed when a test is enabled after the Aggregator is started.

The timestamp for these Synchronized messages is the time the error was detected by the Aggregator, not the time the error occurred.

Instrument reset. When a RFM220 instrument is reset, the alarm state for the SNR test is set to true. This is because during the instrument reset, the SNR value is set to 0. If the Aggregator is started after the instrument is reset, it will be observed t hat the SNR value will go below the threshold with no alarm being reported (because the alarm state is already set to true). The work-around for this situation is to ﬁrst clear the SNR alarm by setting a lower value for the Clear threshold, and then later setting new Active and Clear thresholds.

The RFM220 Client displays t wo types of event logs:

RF events. All of the RF-related events are shown in the RF Event Log.

Device event the Device Event Log.

s. All of the other instrument-related events are shown in

You can view the desired event log by selecting the associated tab in the Logs pane: RF Event Log or Device Event Log.

You can p Clear, or Save buttons. Only a user logged in as the Administrator can clear the logs.

Figure 41: RFM220 Client Logs pane

ause, clear, or save the selected event log by clicking the Pause,

RFM220 User Manual 71

Operating Basics

Device Metrics

The Metrics pane provides two tabs to display various metrics for the signal and instrument being monitored

: Metrics and Device Information.

Metrics Tab

Select the Metrics tab to display metrics for the input signal.

Figure 42: Metrics display

72 RFM220 User Manual

Operating Basics

Device Information Tab

LED Indicators

Select the Metrics tab to display metrics for the RFM220 instrument that is being monitored.

Figure 43: Device Info

When SNMP alarms from a RFM220 instrument are sent to the RFM220 Aggregator, the LED indicators in the Metrics pane will change color to match the severity level of the detected error. (See page 55, Error indicator color codes.)

rmation metrics display

Synchronizing Alarms

If a RFM220 in by an Aggregator, you need to reapply the alarm conﬁguration settings to synchronize the alarm LED indicators on the Metrics pane with the actual state of the alarms. To reapply the alarm conﬁguration settings, open t he Alarm Conﬁguration dialog and click Apply.

CAUTION. If you do not reapply the alarm conﬁguration settings after a

RFM220 instrument is reset to the factory default settings, the LED indicators for some metrics will indicate an active error condition that cannot be cleared.

strument is reset to the default settings while being monitored

RFM220 User Manual 73

Operating Basics

74 RFM220 User Manual

Tektronix RFM220 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual