6866600D04 MMI Commands RevC

Dimetra IP
MTS Man Machine Interface Commands
6866600D04-C
December 2006
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs. Laws in the United States and other countries
preserve for Motorola certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola computer programs contained in
the Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the
copyrights, patents or patent applications of Motorola, except for the normal nonexclusive, royalty-free license to use that arises by operation of law in the sale
of a product.
Disclaimer
Please note that certain features, facilities and capabilities described in this document may not be applicable to or licensed for use on a particular system, or
may be dependent upon the characteristics of a particular mobile subscriber unit or configuration of certain parameters. Please refer to your Motorola contact
for further information.
Trademarks
Motorola, the Motorola logo, and all other trademarks identified as such herein are trademarks of Motorola, Inc. All other product or service names are the
property of their respective owners.
Copyrights
© 2006 Motorola, Inc. All rights reserved.
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into any language or computer language, in any form or by
any means, without the prior written permission of Motorola, Inc.
CMM labeling and disclosure table
The People’s Republic of China requires that Motorola’s products comply with
China Management Methods (CMM) environmental regulations. (China
Management Methods refers to the regulation Management Methods for
Controlling Pollution by Electronic Information Products.) Two items are used to
demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.
• Logo 1 means that the product contains no substances in excess of the
maximum concentration value for materials identified in the China
Management Methods regulation.
• Logo 2 means that the product may contain substances in excess of the
maximum concentration value for materials identified in the China
Management Methods regulation, and has an Environmental Friendly
Use Period (EFUP) in years, fifty years in the example shown.
Logo 1 Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during
which the Toxic and Hazardous Substances (T&HS) contained in the Electronic
Information Product (EIP) will not leak or mutate causing environmental pollution
or bodily injury from the use of the EIP. The EFUP indicated by the Logo 2 label
applies to a product and all its parts. Certain field-replaceable parts, such as
battery modules, can have a different EFUP and are marked separately.
The Disclosure Table is intended only to communicate compliance with China
requirements; it is not intended to communicate compliance with EU RoHS or any
other environmental requirements.
© 2007 Motorola, Inc.

Document
History
Document History
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Edition Description Date

6866600D04–A Initial Edition Jul. 2006
6866600D04–B Air_Tracer and Air_Tracer_Mode MMI commands added in Sept. 2006
Chapter 5.
6866600D04–C • "atten_default" and ".EGOP" MMI commands added Dec. 2006
• pm_config MMI command deleted
• -r option added to the "STATUS BSL" MMI command
• "rx_fru_config" MMI command moved to the Test
Application chapter and description updated
• The –Pn option for "STATUS EAS" on page 4-13 has been
updated.
6866600D04-C December 2006 i

Document History
ii 6866600D04-C December 2006

Dimetra IP System Release 6.0
System Documentation
Booklet 3-1: Managing Zone Infrastructure
Booklet 3-2: Managing Radio Users
Volume 1 Volume 2 Volume 3 Booklet 3-3: Administering Servers, Volume 4
Understanding Fault Configuration Controllers and Gateways Accounting
your Dimetra IP Management Management Booklet 3-4: Managing Network Transport Equipment Management
System Booklet 3-5: Administering Databases
Booklet 3-6: Feature Configuration
6802800U51 6802800U52 6802800U53 Booklet 3-7: Fleetmap Management 6802800U54
Volume 5 Volume 7 Volume 8

Booklet 5-1: Monitoring System Volume 6
Performance High Level Field Replace-
Performance Security
Management Diagnostics and able Units
Booklet 5-2: Managing Network Transport Management
Troubleshooting and Entities
Equipment Performance
6802800U55 6802800U56 6802800U57 6802800U58
Booklet 9-1: Master Site

Volume 9 Volume 10 Volume 11
Hardware Installation Booklet 10-1: Authentication, Encryption and
Installation and Authentication, End-to-End
Booklet 9-2: Master Site Provisioning - Installation and
Configuration Encryption and Secure
Software Installation Configuration
Provisioning Communications
Booklet 9-3: Network Transport Applications Booklet 10-2: Managing Authentication,
6802800U59 Installation and Configuration 6802800U60 Encryption and Provisioning 6802800U61
Security/Authentication Feature Manuals
PCI Short Form PCI Crypto KMF Crypto Alias Integrated MultiCADI UCS
Crypto Card Card Upgrade Card Instruction Solution (AIS) Feature Synchronisation
Service Manual Manual Manual Feature Manual Manual Tool Manual
6802700U92 6881132E24 6881003Y85 6802800U66 6802800U67 6802800U62
AUC Crypto End to End Air Interface Backup/Restore Network Telephone

Card Instruction Encryption Encryption Collector Security Interconnect
Manual KVL3000 Plus KVL3000 Plus Application Feature Manual Feature Manual
User Guide User Guide User Guide
6802800U71 6802800U14 6802800U15 6802800U22 6802800U70 6802800U65
KVL 3000 Plus Provisioning Data MCC 7500

key Variable Centre Users Feature Manual Feature Manual
Loader Service Manual
Manual
6802800U69 6802800U64
6802800U68 6802800U40
Online Help
Affiliation Application Authentication Performance FullVision RCM RCM

Display launcher Centre Reports Online Help Online Help Reports
Online Help Online Help Online Help Online Help Online Help
Software UCM ZCM ZoneWatch System and KMF TESS

Download Online Help Online Help Online Help Zone Profile Online Help Online Help
Online Help Online Help
Service Information
EMEA Systems Support Centre (ESSC)
The EMEA Systems Support Centre provides a Technical Consulting service. This service is accessed via the Call
Management Centre.
Jays Close, Viables Industrial State

Basingstoke, Hampshire RG22 4PD,
United Kingdom
Contact via Call Management Centre
Telephone: +44 (0) 1256 484448
Email: ESSC@motorola.com
European Systems Component Centre (ESCC)
The European System Component Centre provides a repair service for infrastructure equipment, including the
MBTS. Customers requiring repair service should contact the Call Management Centre to obtain a Return
Authorisation number. The equipment should then be shipped to the following address unless advised otherwise.
Motorola GmbH CGISS

European Systems Component Centre
Am Borsigturm 130
13507 Berlin
Germany
Telephone: +49 (0) 30 66861414
Telefax: +49 (0) 30 66861426
E-Mail: ESCC@motorola.com
Parts Identification and Ordering
Request for help in identification of non-referenced spare parts should be directed to the Customer Care
Organization of Motorola’s local area representation. Orders for replacement parts, kits and assemblies should be
placed directly on Motorola’s local distribution organization or via the Extranet site Motorola Online at
https://emeaonline.motorola.com.
EMEA Test Equipment Support
Information related to support and service of Motorola Test Equipment is available by calling the Motorola Test
Equipment Service Group in Germany at +49 (0) 6128 702179, Telefax +49 (0) 6128 951046, through the
Customer Care Organization of Motorola’s local area representation, or via the Internet at
http://www.gd-decisionsystems.com/cte/.
Your Input
...is much appreciated. If you have any comments, corrections, suggestions or ideas for this publication or any
other requiremens regarding Motorola publications, please send an e-mail to doc.emea@motorola.com.
Updated Versions of this Manual

......are available at our Extranet site Motorola Online. Contact us at doc.emea@motorola.com for access.
Table
of
Contents
Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■

Icon Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . -xi
Chapter 1: Introduction
MMI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Access Levels and Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Chapter 2: Test Application Commands

Test Application Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
canbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
adc_scaling_factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
analog_digital_converter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
alarm_force. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
alarm_log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
alarm_log_clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
alarm_log_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
atten_default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
battery_settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
backplane_slotid_long_text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
calibration_factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
comm_port_parms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
chipset_reg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
digital_analog_converter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
e1_external_loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
fru_configuration_parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
fault_management_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
fault_management_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
e1_frm_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
fru_self_diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
firmware_version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
gps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
igps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
kit_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
led_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
led . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
6866600D04-C December 2006 iii

Contents
login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
lrr - last_reset_reason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
memory_parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
pps_enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
platform_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
revision_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
reference_source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
real_time_clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
rx_fru_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
time_reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
temp_sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
watchdog_settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65
Chapter 3: BOOT1 Commands

BOOT1 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
ATTRIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
build_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
bview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
cd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
chmod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
cp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
ethstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
exit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
fdir. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
finstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
fusage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
go . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
ifattach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
ifconfig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
ifstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
inetcfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
ipaddr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
ls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
mkdir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
mload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
mv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
netstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
pwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
rm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
rmdir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
iv 6866600D04-C December 2006

MTS Man Machine Interface Commands Contents
shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
sleep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
stat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
testapp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
tftp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
traceroute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
ttcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
unmount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
vols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Chapter 4: Site Controller Commands

Site Controller Application Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
ATTRIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
BRLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
BTS_TYPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
CLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
DISPLAY CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
EAS_OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
.EGOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
EXIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
KILL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
KVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
LOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
LOGOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
LS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
MAX_WSVR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
MIRROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
NETSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
PASSWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
PING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
PORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
RGPS_DELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
SITE_LOCATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
STATUS BR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
STATUS BSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
STATUS BSLQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
STATUS BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
STATUS CRTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
STATUS EAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
STATUS FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
STATUS FRF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
STATUS KEYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
STATUS LMI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
STATUS PEER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
STATUS RIGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
STATUS SC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
STATUS SEC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
STATUS SRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
6866600D04-C December 2006 v

Contents
TFTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
TIMEZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
UNLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
VER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
WHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
atc # get device_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
atc # get kit_number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
atc # get vendor_serial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
atc # get track_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
atc # get status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
atc # get alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
atc # set cav_tune_timo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
atc # get cav_tune_timo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
atc # cav_park . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
atc # set cav_vswr_alm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
atc # get cav_vswr_alm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
atc # get cav_status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
dpm # get device_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
dpm # get kit_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
dpm # get vendor_serial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
dpm # get track_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
dpm # get status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
dpm # get alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
dpm # get fwd power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
dpm # get rev_power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
dpm # get vswr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
dpm # set vswr_alm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
dpm # get vswr_alm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
psu # get device_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
psu # get kit_number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
psu # get vendor_serial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
psu # get track_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
psu # get status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
psu # get alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
psu # get battery_voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
psu # get battery_current. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
psu # get battery_temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
psu # set force_dc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
psu # get force_dc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
psu # set dc_operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
psu # get dc_operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
psu # set ac_operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
psu # get ac_operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
psu # get 7v_voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
psu # get 28.5v_voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
psu # get 28.5v_current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
psu # get fan_voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
psu # get power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
psu # get psu_temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
psu # get ambient_temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
psu # set fan_speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
psu # get fan_speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
psu # set fan_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
psu # get fan_config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
psu # start_fan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
vi 6866600D04-C December 2006

MTS Man Machine Interface Commands Contents
can reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

can reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
can view_mapping_list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
can add_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
can remove_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
can change_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
can check_mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
Chapter 5: Base Radio Commands

Base Radio Test Application Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
cabinet_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
position_id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
fv -oplatform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
freq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Base Radio Application Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
AIEA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
AIR_TRACER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
AIR_TRACER_MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
CCIMMUN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
CHANSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
CLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
DEKEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
EXIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
GET ACTIVE_TRACES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
GET ABACUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
GET ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
GET BAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
GET BTS_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
GET CABINET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
GET CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
GET EX_AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
GET EXT_REF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
GET FWD_PWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
GET INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
GET JAVELIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
GET LOG_INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
GET MAX_VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
GET PA_AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
GET PA_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
GET POSITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
GET PLATFORM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
GET REF_PWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
GET RPTR_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
GET RX(n)_AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
GET RX_FREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
GET RX_FRU_CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
GET SYS_GAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
GET TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
GET TOMAHAWK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
GET TX_FREQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
GET VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
KEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
6866600D04-C December 2006 vii

Contents
KVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
LOGOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
lstalm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
lstalmtr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
VER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
SET CABINET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
SET LAPD_TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
SET LOG_ROUTING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
SET MAX_VSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
SET POSITION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
SET PD_TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
SET RX_FREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
SET RX_FRU_CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
SET SYS_GAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
SET TRACES_OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
SET TX_FREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
SET SCT_DISP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
SET SM_TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Appendix A: Glossary
viii 6866600D04-C December 2006

List
of
Tables
List of Tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Table 2-1: CAN Bus Related Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Table 2-2: Managing the CAN Bus Unit mapping List . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Table 2-3: Variables Readable from the CAN bus Units . . . . . . . . . . . . . . . . . . . . . . . 2-4
Table 2-4: Writing CAN Bus unit Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Table 2-5: Parking a Cavity in an Auto-Tune Cavity Combiner . . . . . . . . . . . . . . . . . . . . 2-7
Table 2-6: Sending Reset Frames to CAN Bus Units . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Table 2-7: Sending and Displaying Low-level Frames to/from CAN Bus Units . . . . . . . . . . . . 2-8
Table 2-8: Chipset_reg options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Table 2-9: Chipset_reg options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Table 2-10: lc MMI Objects, led_id and LED Color State Mapping . . . . . . . . . . . . . . . . . . 2-46
Table 2-11: Mapping between MMI Objects and MMI APIs . . . . . . . . . . . . . . . . . . . . . 2-51
Table 3-1: Common Options: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Table 4-1: Attribute Bit Values: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Table 4-2: Common Options: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Table 4-3: Other Options: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Table 4-4: Options available at any time and with any syntax: . . . . . . . . . . . . . . . . . . . . 4-3
Table 4-5: General Parameters: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Table 4-6: Roles of Switch Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
6866600D04-C December 2006 ix

List of Tables
This page intentionally left blank.
x 6866600D04-C December 2006

About
This
Manual

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
What is Covered In This Manual?

This manual describes the Man-Machine Interface Commands used to test and configure MTS Sites.
Helpful Background Information

“MTS 2 and MTS 4 Configuration, Installation and Basic Service Manual”
Related Information
Man Machine Interface Commands are used in the “MTS 2 and MTS 4 Configuration, Installation
and Basic Service Manual”, in the chapter “Configuration and Testing”.
Icon Conventions
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The document set is designed to give the reader more visual cues. The following graphic icons are used
throughout the documentation set. These icons and their associated meanings are described below.
6866600D04-C December 2006 xi

Icon Conventions
SUGGESTION
A suggestion implies a recommendation or tip from Motorola, that does not require to be
followed, but might be helpful. There is no warning level associated with a Suggestion.
Notes contain information more important than the surrounding text, such as exceptions or
preconditions. They also refer the reader elsewhere for additional information, remind the reader
how to complete an action (when it is not part of the current procedure, for instance), or tell the
reader where something is located on the screen. There is no warning level associated with a Note.
Information that is crucial to the discussion at hand, but that is not a Caution or Warning, receives
an Important icon. There is no warning level associated with the Important icon.
The caution icon implies information that must be carried out in a certain manner
to avoid problems, procedures that may or may not be necessary as determined
by the reader’s system configuration, and so on. Although no damage will occur if
the reader does not heed the caution, some steps may need repeating.
The warning icon implies potential system damage if the instructions or

procedures are not carried out exactly, or if the warning is not heeded.
The danger icon implies information that, if disregarded, may result in severe
injury or death of personnel. This is the highest level of warning.
xii 6866600D04-C December 2006

Chapter
1
Introduction
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MMI Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MMI commands are the input from a service computer to the system RS-232 serial port (19200 bps, 8 data
bits, 1 stop bit, no parity). Depending on the task, the RS-232 port is accessed from the Site Controller,
or from the front of each Base Radio Controller (BRC) in the Equipment Cabinet.
The service technician enters the MMI commands to communicate with the Site Controller at the
system level. The system response is returned to the service computer via RS-232.
Various test procedures use these commands to test and configure the system. The test procedures
for the Site Controller are described in “MTS 2 and MTS 4 Configuration, Installation and
Basic Service Manual”, in chapter “Configuration and Testing”.
Access Levels and Modes

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Site Controller and BR commands are available through the use of the password. This password allows
the service technician access to a subset of the MMI command set for field service operations.
There is a default password that is programmed during manufacturing. The pass-
word should be changed via the MMI.
Site Controller can be accessed in the following modes:
• BOOT1: used for loading the actual Site Controller Application or loading the Test Application
• Test Application: provides facilities for setup, diagnostic and testing
• Site Controller Application
6866600D04-C December 2006 1-1

Conventions Chapter 1: Introduction
Base Radio has similar modes, where MMI commands can be used:
• BOOT1: used for loading the actual Base Radio Application or loading the Test Application
• Test Application: provides facilities for setup, diagnostic and testing
• Base Radio Application
Conventions
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The syntax for each command is presented as follows:

• Plain text shows the actual text to be typed to invoke a command or action.
• Italic text shows where a parameter or value is to be substituted.
• [Text enclosed in square brackets] indicates an optional value that may be entered.
• Where items are separated by vertical bars |, the items are the applica-
ble choices that may be entered.
• {Text enclosed in braces} indicates a corresponding selection or a parameter
that must be entered for the command to execute.
• <Text enclosed in brackets> indicates a value to be entered and should
be replaced by the actual value.
• A series of dots ... indicates one or more occurrences of a preceding parameter.
• A pair of dots .. indicates a range of valid values.
• Proportional text is used to show the command line output in examples.
The syntax for the Site Controller and BR commands is case sensitive. Each example is
shown in the format that should be entered by the operator.
Some commands require the use of parameters. If input parameters are not entered, a response
is returned identifying the proper syntax for the command.
A definition describes in detail each command’s purpose and function. Where helpful, the definition is
followed by an example of the commands response. Typical values have been used whenever possible.
Some commands return varying responses (such as available, not available, unknown, o.k., and
alarm). Only one of the possible responses is listed in each example.
1-2 6866600D04-C December 2006

Chapter
2
Test Application Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Test Application: provides facilities for setup, diagnostic and testing.
Test Application Commands

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Test Application is a powerful mode, inappropriate use of Test Application MMI
can lead to a permanent hardware failure. Please proceed with extreme caution.
HELP
Syntax:
help –c<command>
Description:
The help command displays a short synopsis of the command, comprising an option list and a brief description.
canbus
Syntax:
Commands for manipulating power supplies, auto-tune cavity combiners and digital power meters
– devices that communicate via the CAN bus – all share a common syntax:
can | canbus –o<object> -c<command> <various parameters depending on command>
6866600D04-C December 2006 2-1

canbus Chapter 2: Test Application Commands
The following table provides a quick overview of all commands related to the CAN bus.
Table 2-1 CAN Bus Related Commands
Power Digital Auto-Tune CAN

Com- Supply Power Cavity bus in
Function
mand psu0 – Meter dpm0 Combiner general
psu3 – dpm3 atcc0 – atcc3 platform
map Displays list of registered units. X
add Adds a unit to the list. X
chg Changes a units position. X
del Deletes a unit from the list. X
delmap Deletes the entire mapping list. X
read Read the value of a variable in a unit X X X
write Writes a value to a variable in a unit X X X
reset Sends a reset frame. X X X X
status Displays the CAN bus status. X
mode Displays the CAN bus mode. X
open Enables display of received frames. X
close Disables display of received frames. X
send Sends a frame. X
park Parks a cavity. X
Managing the CAN bus unit mapping list:

The five commands for managing the mapping list are explained in the following table:
Table 2-2 Managing the CAN Bus Unit mapping List
Commands for adding, deleting and changing CAN bus units

Purpose Display the contents of the CAN bus unit mapping list
Syntax can –oplatform -cmap
Example > can -oplatform -cmap
TrackID Unit Registration State
------- ---- ------------------
OWK0640005 psu1 Registered
BNT0611001 dpm0 Registered
DPM0616002 dpm1 Registered
COM0632845 atcc1 Registered
COM0632853 atcc0 Registered
OWK0619001 psu0 Registered
COM0632854 Tried to register but not in Mapping List
COM0632855 Tried to register but not in Mapping List
Comment The exact format of the output of this command may change.
Purpose Add a CAN bus unit to the CAN bus unit mapping list.
Syntax can –oplatform –cadd –t<trackID> -u<unit name>
2-2 6866600D04-C December 2006

MTS Man Machine Interface Commands canbus
Table 2-2 Managing the CAN Bus Unit mapping List (Continued)
Commands for adding, deleting and changing CAN bus units
Example > can -oplatform -cadd -tOWK0640099 -upsu2
>
Comment trackID must be in the form AAA99BBBBB, where A denotes a letter, 9 denotes
a digit and B is either a digit or one of the letters B, C, D, F, G, H, J, K, L, M,
N, P, R, S, T, V, W, X, Y, Z. Unit name is one of psuX, dpmX, atccX, where X
denotes a digit between 0 and 3
Purpose Delete a CAN bus unit from the CAN bus unit mapping list.
Syntax can –oplatform –cdel -t<trackID>
Example > can -oplatform -cdel -tCOM0632855
>
a digit and B is either a digit or one of the letters B, C, D, F, G, H, J, K, L, M,
N, P, R, S, T, V, W, X, Y, Z.
Purpose Change the name (i.e. the position) of a CAN bus unit mapping list.
Syntax can –oplatform –cchg -t<trackID> -u<new unit name>
Example > can -oplatform -cchg -tOWK0640099 -upsu2
>
a digit and B is either a digit or one of the letters B, C, D, F, G, H, J, K, L, M, N,
P, R, S, T, V, W, X, Y, Z. new unit name is one of psuX, dpmX, atccX, where X
denotes a digit between 0 and 3
Purpose Delete the entire mapping list

Syntax can –oplatform –cdelmap
Example > can -oplatform -cdelmap
>
Comment This command will remove all units from the mapping list, but it will not send
any CAN bus frames to the units.
Reading CAN bus unit variables:

Commands for reading variables from the various CAN bus units share a common syntax:
can –o<object> -cread –v<variable name>
Some commands for reading variables from the ATCCs may require a cavity number:
can –o<object> -cread –v<variable name> -n<cavity number>
6866600D04-C December 2006 2-3

The following table lists the names of the variables that can be read from the different
CAN bus units together with examples of their use.
Table 2-3 Variables Readable from the CAN bus Units
Digital Auto-Tune
Power
Power Cavity Example
Supply
Meter Combiner
Device ID Device ID Device ID > can -opsu0 -cread -vdevice
psu0: device id = vendor: 30,
hw_revision: 80, sw_revision: 45
Kit Number Kit Number Kit Number > can -odpm1 -cread –vkit
dpm1: kit number = 0000000000
Vendor Serial Vendor Serial Vendor Serial > can -odpm0 -cread -vserial
Number Number Number dpm0: serial number = FC1061000588
Track Track Track > can -oatcc1 -cread -vtrackid
Number Number Number atcc1: track id = COM0632845
Status > can -oatcc0 -cread -vstatus

atcc0: status = (0x8):
Tuning Status: Not Tuned Master/Slave:
Slave
Alarm: No alarm generated
Alarm > can -oatcc1 -cread -valarm
atcc1: alarm = (0x0):
Software: Ok
Channel Spacing: Ok
VSWR: Ok
Master/Slave: Ok
Motor Alarm: Ok
Tuning Error: Ok
Cavity Tune > can -oatcc1 -cread -vtune_to
Timeout atcc1: cavity tune timeout = 480 minutes
VSWR Alarm > can -oatcc0 -cread -vvswr_alarm_th

Threshold atcc0: vswr alarm threshold = 3.20
Cavity Status > can -oatcc0 -cread -vcav_status -n1

atcc0: cavity status =
Cavity Number: 1
Frequency: 0 Hz
VSWR: 1.00
Tuning Status: Tuned
Master/Slave: Slave
Alarm: No alarm generated
Software: Ok
Channel Spacing: Ok
VSWR: Ok
Master/Slave: Ok
Motor Alarm: Ok
Tuning Error: Ok
Status > can -odpm1 -cread -vstatus
dpm1: status = No alarm generated
2-4 6866600D04-C December 2006

Table 2-3 Variables Readable from the CAN bus Units (Continued)
Digital Auto-Tune
Power
Supply
Meter Combiner
Alarm > can -odpm0 -cread -valarm
dpm0: alarm = (0x0):
Software: Ok
VSWR: Ok
Forward > can -odpm1 -cread -vfwd_pwr
Power dpm1: forward power = 0.00 Watt
Reverse > can -odpm1 -cread -vrev_pwr

Power dpm1: reverse power = 0.00 Watt
VSWR > can -odpm1 -cread -vvswr

dpm1: vswr = 1.00
VSWR > can -odpm1 -cread -vvswr_alarm_th
Alarm dpm1: vswr alarm threshold = 3.20
Threshold
DPM > can -odpm1 -cread –vtemp
Temperature dpm1: dpm temperature = 50.00 Degree
Celcius
Status > can -opsu0 -cread -vstatus
psu0: status = (0xCF):
DC Output: Present
AC Input: Present
DC Input: Not Present
Battery: Not Charging
AC/DC: AC
Fans: 3
Alarm: Alarm generated
Alarm > can -opsu0 -cread -valarm
psu0: alarm = (0x27):
DC Fail: Ok
Over Temp: Ok
DC Src Fail: Alarm
AC Src Fail: Ok
SW corrupt: Ok
Fan 1 Fail: Alarm
Fan 2 Fail: Alarm
Fan 3 Fail: Alarm
Force DC > can -opsu0 -cread -vforce_dc
psu0: force DC setting = Off
DC operation > can -opsu1 -cread -vdc_op
– No AC psu1: DC operation-no AC setting = Off
AC operation > can -opsu0 -cread -vac_op

– No DC psu0: AC operation-no DC setting = Off
Fan Speed > can -opsu1 -cread -vfan_speed

psu1: fan speed = 0
Fan > can -opsu1 -cread -vfan_config
Configuration psu1: fan configuration = (0x7):
Fan 1: Mounted
Fan 2: Mounted
Fan 3: Mounted
6866600D04-C December 2006 2-5

Table 2-3 Variables Readable from the CAN bus Units (Continued)
Digital Auto-Tune
Power
Supply
Meter Combiner
PSU > can -opsu0 -cread -vpsu_temp
Temperature psu0: psu temperature = 50.00 Degree
Celcius
Ambient > can -opsu1 -cread -vamb_temp
Temperature psu1: ambient temperature = 30.00 Degree
Celcius
Battery > can -opsu0 -cread -vbat_volt
Voltage psu0: battery voltage = 2.70 Volt
Battery > can -opsu1 -cread -vbat_temp

Temperature psu1: battery temperature = 100.00
Degree Celcius
Battery > can -opsu0 -cread -vbat_curr
Current psu0: battery current = 0.00 Amp
7V Voltage > can -opsu0 -cread -v7v_volt

psu0: 7V voltage = 7.17 Volt
7V Current > can -opsu1 -cread -v7v_curr
psu1: 7V_current = 0.00 Amp
28.5 V > can -opsu0 -cread -v28.5v_volt
Voltage psu0: 28.5V voltage = 28.57 Volt
28.5 V > can -opsu0 -cread -v28.5v_curr

Current psu0: 28.5V current = 0.00 Amp
Fan Voltage > can -opsu0 -cread -vfan_volt

psu0: fan voltage = 16.10 Volt
PSU Power > can -opsu0 -cread -vpwr
psu0: psu power = 0.00 Watt
Writing CAN bus unit variables:

Commands for writing variables to the various CAN bus units share a common syntax:
can –o<object> -cwrite –v<variable name> -d<variable value>
The following table lists the names of the variables that can be written to the different
CAN bus units together with examples of their use.
Table 2-4 Writing CAN Bus unit Variables
Digital Auto-Tune
Power
Supply
Meter Combiner
Cavity Tune > can -oatcc0 -cwrite -vtune_to -d100
Timeout
VSWR Alarm > can -oatcc0 -cwrite -vvswr_alarm_th
Threshold -d2.0
>
VSWR Alarm > can -odpm1 -cwrite -vvswr_alarm_th
Threshold -d2.0
2-6 6866600D04-C December 2006

Table 2-4 Writing CAN Bus unit Variables (Continued)

Digital Auto-Tune
Power
Supply
Meter Combiner
Force DC > can -opsu0 -cwrite -vforce_dc -doff
DC operation > can -opsu0 -cwrite -vdc_op -doff

– No AC
AC operation > can -opsu0 -cwrite -vac_op -doff
– No DC
Fan Speed > can -opsu0 -cwrite -vfan_speed -d4
Fan > can -opsu0 -cwrite -vfan_config -d3
Configuration
Parking a cavity in an Auto-Tune Cavity Combiner:

The command for parking a cavity in an Auto-Tune Cavity Combiner has the following syntax:
can –o<atcc object> -cpark -n<cavity number>
Table 2-5 Parking a Cavity in an Auto-Tune Cavity Combiner
Command for parking a cavity in an Auto-Tune Cavity Combiner

Purpose Park a cavity in an Auto-Tune Cavity Combiner
Syntax can –o<atcc object> -cpark –n<cavity number>
Examples > can -oatcc0 -cpark -n2
Comment atcc object is one of atcc0, atcc1, atcc2 and atcc3 cavity number must be between 1 and 4
Sending Reset Frames to CAN bus units:

For fault-finding and diagnostic purposes it is possible to send Reset frames on the CAN bus.
There are four types of reset frames and they can either be broadcast to all units on the bus or sent
to a single unit. For broadcasts the command has the following syntax:
can –oplatform -creset -r<reset type>
For sending resets to a single unit the command has the following syntax:
can –o<object> -creset -r<reset type>
Table 2-6 Sending Reset Frames to CAN Bus Units
Command for sending reset frames on the CAN bus

Purpose Send a Reset frame on the CAN bus
Syntax can –o<object> -creset –r<reset type>
Examples > can -oplatform -creset –rpor
> can –opsu0 –creset -rct
Comment The four reset types are:
• por Power-On-Reset
• cc Clear Command
6866600D04-C December 2006 2-7

Table 2-6 Sending Reset Frames to CAN Bus Units (Continued)

Command for sending reset frames on the CAN bus
• ct Reset Channel Type

• rn Register New
Reset type cc cannot be sent to the platform object (i.e. cannot be broadcast).
Sending and displaying Low-level Frames to/from CAN bus units:

For fault-finding and diagnostic purposes it is possible to directly send and display received low-level
frames on the CAN bus. CAN-Bus frames consisting of an 11-bit identifier field, a 4-bit length field and an
8-byte data field can be sent. Before CAN-Bus frames can be received, a CAN-Bus receive channel must
be opened. Received frames are displayed on the console, when the user enters a <cariage return>. Each
time <carriage return> is pressed, one received frame is displayed. When the CAN-Bus receive channel is
closed, no frames can be received. The following table list the commands that support this function:
Table 2-7 Sending and Displaying Low-level Frames to/from CAN Bus Units
Low-level commands for sending and receiving frames on the CAN bus
Purpose Enable display of received CAN bus frames on the MMI console
Syntax can –oplatform -copen
Example > can -oplatform -copen
CAN-Bus receive channel opened
>
Comment
Purpose Disable display of received CAN bus frames on the MMI console
Syntax can –oplatform -cclose
Example > can -oplatform -cclose
CAN-Bus receive channel closed
>
Comment
Purpose Send a frame on the CAN bus

Syntax can -oplatform -csend –i<identifier> -l<length> -d<data>
Example > can -oplatform -csend -i200 -l1 -d9B
>
Comment The identifier is entered in hex and represents 11 bits comprising 5 bits Channel
Type, 4 bits Message Opcode and 2 bits Frame Sequence Type The length must
be between 1 and 8 The data is entered as a string of up to 8 hex digit pairs, each
pair representing one byte, e.g. 66778899AABBCCDD
Description:
2-8 6866600D04-C December 2006

MTS Man Machine Interface Commands adc_scaling_factor
The Site Controller board communicates with power supplies (psu), digital power meters (dpm) and
auto-tune cavity combiners (atcc) via a CAN bus. Power supplies, digital power meters and auto-tune
cavity combiners are units on the CAN bus. In order for the Site Controller to know which units are
mounted in the base station, the user must enter the mounted units in a CAN bus unit mapping list.
The Site Controller uses this list to check that all mounted units register their presence on the CAN
bus at power up. The can command can be used to maintain this mapping list.
The various CAN units have a number of variables (e.g. psu voltage level or dpm power measurements)
which can be read or written. The can command can be used to read and write value in these variables.
For diagnostic purposes thecan command can also be used to send reset frames to units,
send raw data frames to units, display raw data frame received from units and display various
statistics characterizing the performance of the CAN bus.
This command can be used for:
• Displaying the contents of the mapping list
• Adding and deleting CAN bus units (power supplies, digital power meters and
auto-tune cavity combiners) to/from the mapping list
• Changing the position of CAN bus units in the mapping list
• Deleting the entire mapping list
• Reading and writing the values of CAN bus units
• Parking a cavity in an atcc
• Sending reset frames to units
• Sending raw data frames to CAN bus units.
• Displaying raw data frames received from CAN bus units.
Received CAN-Bus frames are not displayed on the console before the user enters a <carriage
return>. One received frame will be displayed for each <carriage return> pressed.
adc_scaling_factor
Syntax:
Read operations:
asf | adc_scaling_factor –o<object>
Write operations:
asf | adc_scaling_factor –o<object> –p<port> –s<scaler>
Description:
Control the A/D scaling factor settings.
Options:
<object> A character string representing the object assigned to the A/D converter. Valid settings:
6866600D04-C December 2006 2-9

analog_digital_converter Chapter 2: Test Application Commands
• ps
• ps1…6
ps=ps1. ps1 is local, ps2…6 are remote.

<port> An integer value selecting the A/D converter port.
<scaler> A floating-point value used to scale the A/D port reading.
Output:
Port 1 Scallar<prd><scaler>
.
.
Port n Scallar<prd><scaler>
<scaler> A floating point value representing assigned to the A/D converter scaler
Example:
> asf –ops
Port 1 Scallar = 3.08000
> asf –ops –p1 –s2.5
>
analog_digital_converter
Syntax:
Read operations:
adc | analog_digital_converter –o<object>
Description:
Reads values of the A/D converters on the power supplies. It displays both raw and scaled values.
Options:
<object> A character string representing the object assigned to the A/D converter. Valid settings:
• ps
• ps1..6
Note: ps = ps1. ps1 is local, ps2..6 are remote.

Output:
Port 1 unscaled<prd><data>
.
.
Port n unscaled<prd><data>
2-10 6866600D04-C December 2006

MTS Man Machine Interface Commands alarm_force
Port 1 scaled<prd><scaled_data>
.
.
Port n scaled<prd><scaled_data>
<data> A floating point value representing the unscaled A/D converter voltage.
<scaled_data> A floating point value representing the scaled A/D converter voltage.
Example:
factory> adc –ops
Port 1 unscaled=3.08000
.
.
Port 1 scaled=29.13110
.
.
factory>
alarm_force
Syntax:
Write operations:
af | alarm_force –o<object> –f<fault_map>
Description:
Forces/Clears a specific hardware alarm.
Options:
<object> A character string representing the object assigned to the alarm control. Valid settings:
• platform, ps1->6, control, xhub2..6, gpsr
<fault_map> A hexadecimal value bit map representing the alarms to be forced/cleared.

Output:
None
Example:
6866600D04-C December 2006 2-11

alarm_log Chapter 2: Test Application Commands
The following MMI cmd will set the PowerSupply alarm that have the same fault map bit setting.
> af –ops –f00000001
The following MMI cmd will clear all PowerSupply alarms.

> af –ops –f0
alarm_log
Syntax:
al | alarm_log –l<log_type>
Description:
Displays the alarm log contents, this is will include the following: fault (HW), exception (SW), and errors (SW).
Options:
<log_type> A character string representing the alarm category to be displayed. Valid settings:
• fault
• error
• exception
• all
Output:
Exception type:
alarm type=EXCEPTION
time stamp<prd><time_stamp>
record num<prd><record__num>
exception id<prd><excep_id>
severity<prd><excep_severity>
detail 1<prd><detail>
Error type:
alarm type=ERROR
record num<prd><record_num>
error id<prd><error>
description<prd><desc>
Fault type:
alarm type=FAULT
record num<prd><record_num>
fault id<prd><fault_id>
2-12 6866600D04-C December 2006

MTS Man Machine Interface Commands alarms
object id<prd><core_object>
severity<prd><fault_severity>
action taken<prd><action_taken>
action recom<prd><action_recomm>
size<prd><user_data_size>
<possible_user_data>
Example:
> al –lfault
alarm type=FAULT
time stamp=0000000565
record num=6
fault id=INDETERMINATE_FAILURE
object id=PLATFORM
severity=CLEARED
action taken=PA_POWER_CUTBACK_CLEAR
action recom=0000000000
size=0x00000001
level2 diagnosis=INDETERMINATE_FAILURE
contributing alarms:
fault id[0]=TX_FWD_PWR_HIGH
object id[0]=CORE_PA1
severity[0]=CLEARED
action taken[0]=PA_POWER_CUTBACK_CLEAR
action recom[0]=0000000000
user data[0]=
>
alarms
Syntax:
Read operations:
alarms –ofault_hndlr
Description:
Displays the current active hardware alarms.
Options:
Output:
> alarms –ofault_hndlr
>
Example:
ACTIVE_FAULT 1<prd><fault_id>
.
.
ACTIVE_FAULT n<prd><fault_id>
<fault_id> A character string representing the platform fault condition.
6866600D04-C December 2006 2-13

alarm_log_clear Chapter 2: Test Application Commands
alarm_log_clear
Syntax:
Write operations:
alc | alarm_log_clear
Description:
Clears the alarm log contents.
Options:
None
Output:
None
Example:
> alc
>
alarm_log_enable
Syntax:
Read operations:
ale | alarm_log_enable
Write operations:
ale | alarm_log_enable –s<state>
Description:
Controls the alarm logging enable state. If enabled, all unmasked alarm events are logged.
Options:
<state> A character string representing the state of the alarm log feature. Valid settings:
• on
• off
Output:
State<prd><state>
Example:
> ale
State=off
>
> ale –son
>
2-14 6866600D04-C December 2006

MTS Man Machine Interface Commands atten_default
> ale
State=on
atten_default
Syntax:
Read operations:
fcp -orxch1 -patten_default
Write operations:
fcp -orxch1 -patten_default -v{0 | 9}
Description:
Command for configuring the BR to an MTS2 or MTS4.
Options:
Valid settings:
• 0 - should be set if the BRC will be part of the MTS-4.
• 9 - should be set if the BRC will be part of the MTS-2.
battery_settings
Syntax:
Read operations:
bs | battery_settings –o<object>
Write operations:
bs | battery_settings -o<object> -t <target> -s<setting>
Description:
This command controls the settings used to interface with a battery.
ps type only supports ac_and_48v_dc and ac_only, battery type supports only 48.
Options:
<object> A character string indicating the object controlling the battery settings. Valid settings:
• ps
• ps1…6
6866600D04-C December 2006 2-15

backplane_slotid_long_text Chapter 2: Test Application Commands
ps = ps1. ps1 is local, ps2…6 are remote

<target> A character string representing the target settings. Valid settings:
• bat_type
• bat_volt
• charge_mode
• ps_type
<setting> A character string representing the desired setting for the target. Valid settings:
• For target = bat_type
setting = {none, cd_tel_agm_vrla, cd_mps_agm_vrla, ex_marathon_agm_vrla,
ex_powerfit_agm_vrla, ex_sprinter_agm_vrla, ex_dryfit_gel_vrla, ex_flooded_lead_ant,
ex_flooded_lead_cal, agm_vrla, gel_vrla, flooded, saft_nicad, alcad_nicad}
• For target = charge_mode
setting = {enable, disable, equalize}
• For target = bat_volt
setting = {24, 36, 48}
• For target = ps_type
setting = {ac_and_48v_dc, ac_and_36v_dc, ac_and_24v_dc, ac_only}
Output:
Battery Type<prd><bat_type>
Battery Voltage<prd><bat_voltage>
Charging Mode<prd><charge_mode>
PS Type<prd><bat_mode>
Example:
factory> bs -ops -tbat_type -sflooded
factory> bs -ops -tps_type -sac_and_48v_dc
factory> bs -ops -tbat_volt -s48
factory> bs -ops -tcharge_mode -senable
factory> bs -ops
Battery Type=flooded
Battery Voltage=48.000000
Charging Mode=enable
PS Type=ac_and_48v_dc
backplane_slotid_long_text
Syntax:
Read operations:
bslt | backplane_slotid_long_text –o<object>
Description:
2-16 6866600D04-C December 2006

MTS Man Machine Interface Commands calibration_factor
Reads the Site Controller card slot location information( slot ID) and backplane type (backplane ID).
Options:
<object> A character string representing the object assigned to the backplane slot. Valid settings: platform
Output:
bslt<prd><type>-<id>
Example:
factory> bslt –oplatform
bslt=01-00
factory>
calibration_factor
Syntax:
Read operations:
cf | calibration_factor -o<object>
Write operations:
cf | calibration_factor -o<object> -c<cal_factor_name> -f<cal_factor>
Description:
Sets and reads calibration factor of the Site Controller’s OCXO.
Options:
<object> A character string representing the object assigned to control the calibra-
tion factor. Valid settings: platform
<cal_factor_name> A character string representing the calibration factor identifier. Valid settings: ocxo1
<cal_factor> An interger value representing the calibration factor setting.
Output:
<cal_factor_id 1><prd><cal_factor>
<cal_factor_id 1> A string which identifies the calibration factor. Valid settings: ocxo1
Example:
factory> cf -oplatform
ocxo1=0x64
factory>
factory> cf -oplatform -cocxo1 -f100
factory>
6866600D04-C December 2006 2-17

comm_port_parms Chapter 2: Test Application Commands
comm_port_parms
Syntax:
Read operations:
cpp | comm_port_parms -o<object> (for serial and lan)
cpp | comm_port_parms -o<object> -c<port> (for switch ports)
Write operations:
cpp | comm_port_parms –o<object> -b<baud> -p<oper_mode> -l<line_mode> (for serial)
cpp | comm_port_parms –o<object> -m<mac_address> -i<ip_address>
-p<oper_mode> -l<line_mode> (for lans)
cpp | comm_port_parms –o<object> -c<port> -p<oper_mode> -l<line_mode> (for switch ports)
Description:
Controls serial communication ports, Ethernet communication ports and Ethernet switch ports settings.
This MMI sets and reads the baud rate and other settings of the Site Controller’s serial communication
ports. It also sets and reads the MAC address, the IP address, duplex mode (line mode), the communication
speed and the loopback mode of the Site Controller CPU Ethernet communication ports. Finally, it sets
and reads duplex mode and communication speed of the Site Controller’s Ethernet switch ports. When
loopback mode is set, “fsd – fru_self_diagnostic” mmi can be used to perform loopback tests.
• For FRUs with only one switch, use front panel switch definitions.
• If cpp mmi used to set loopback test configuration path for lan1 and lan3 objects, it is
required to provide both line_mode=100_base_full_duplex and oper_mode=ext_loopback
parameters on switch1-port0 object. Loopback test will not function correctly
unless full duplex bit is set on switch1-port0.
• If normal mode of operation was not restored on switch1-port0 object, after warm
reboot SC will keep previously set values. In this case fsd mmi command on lan1
and lan3 will report incorrectly current mode as external loopback mode while the
platform software will be configured for internal loopback. Normal functionality
can be restored by setting switch1-port0 to normal mode.
• Platform does not support internal (on MCU level) loopback settings for LAN1 and
LAN3 objects. Cpp mmi for lan1 and lan3 does not provide possibility to set any
other oper_mode except “normal”. Because of this limitation, lan1 and lan3 objects
can not be tested with internal loopback mode on MCU level.
• Line mode settings are not supported for switches and LANs without integrated EPHY. The
command will report error “Invalid argument” while trying to set line mode on lan1, lan3, on
ports 9, 11 of local and remote switches and on ports 20, 22 of local switch1 – back panel.
• IP addresses and MAC addresses written for LANs 1 to 3 are stored in non-volatile
memory. I.e. they will survive a power-down/power-up cycle.
Options:
<object> A character string representing the object assigned to control the communication port. Valid settings:
2-18 6866600D04-C December 2006

MTS Man Machine Interface Commands comm_port_parms
• lan1,2,3
• serial1,2,4
• switch1(local FP and BP unit as a whole )
• switch2...6 (remote switches)
<baud_rate> A integer value representing the serial port baud rate setting. Valid settings:
9600, 19200 (other values are not supported on SummitSC)
<mac_address> A hexadecimal value representing the station lan port mac address. Valid
settings: any valid MAC address in the form 112233445566
<oper_mode> A character string representing the operational mode setting. Valid settings:
• Normal (normal mode of object operations)
• int_loopback ( not valid for switch ports and LAN1, LAN3)
• ext_loopback (not valid for LAN1 and LAN3)
<line_mode> A character string representing line mode of the operation. Valid settings
(lan and switch objects with integrated ephy):
• 10_base_half_duplex
• 10_base_full_duplex
• auto_negotiate
<port> A character string representing the switch port. Valid settings: p0…10 (front panel
switch1 and remote switches), p11…21 (back panel switch1)
For FRUs with only one switch, use front panel switch definitions.
Output:
Lan :
line mode<prd>< mode>
MAC address<prd><mac_address>
IP address<prd><ip_address>
oper mode<prd> <oper_mode>
Serial:
baud<prd><baud_rate>
data bits<prd><data_bits>
stop bits<prd><stop_bits>
parity<prd><parity>
6866600D04-C December 2006 2-19

comm_port_parms Chapter 2: Test Application Commands
echo mode<prd><echo_mode>
flow control<prd><flow_cntrl>
delimiters<prd><delimiter>
Switch Ports:
port<prd><port>
< mode> A character string representing the line mode of the operation. Valid settings:
• Serial — a character string representing serial line mode of the operation:
half_duplex; full_duplex; Undefined
• Lan and switches — a character string representing ethernet’s mode of the operation:
10_base_half_duplex; 10_base_full_duplex; 100_base_half_duplex; 100_base_full_duplex;
1000_base_half_duplex; 1000_base_full_duplex; auto_negotiate
<mac_address> A character string representing the MAC address of the the station lan port.
Valid settings: any valid MAC address in the form 112233445566
<ip_address> character string representing the ip address of the station lan port. Valid
settings: any valid IP address in the form 111.222.333.444
<data_bits> A integer value representing the number of data bits in the serial transfer. Valid settings: 8
<stop_bits> A integer value representing the number of stop bits in the serial transfer. Valid settings: 1
<parity> A character string representing the parity. Valid settings: none
<echo_mode> A character string representing the echo mode used in the serial transfer. Valid settings: on
<flow_cntrl> A character string representing the flow control used in the serial transfer. Valid settings: none
<delimiter> A integer value representing the number of delimiters used in the serial transfer. Valid settings: 0
Example:
Mapping of objects between TestApp and Platform:
lan1...3 - LAN1…3
Serial1, 2,4 - TTY1, TTY2, TTY4
switch1 - LAN_SWITCH1 (SC front and back panel switches as a whole)
switch2 - LAN_SWITCH2 (remote xhub2)
Mapping of between TestApp switch ports and Platform ports:
Local front panel switch1 and remote xhub ports
P0 - SWITCH_PORT_1
P1 - SWITCH_PORT_2
2-20 6866600D04-C December 2006

MTS Man Machine Interface Commands comm_port_parms
P2 - SWITCH_PORT_3
P3 - SWITCH_PORT_4
P4 - SWITCH_PORT_5
P5 - SWITCH_PORT_6
P6 - SWITCH_PORT_7
P7 - SWITCH_PORT_8
P8 - SWITCH_PORT_9 (mii1 no EPHY)
P9 - SWITCH_PORT_10 (Gb1)
P10 - SWITCH_PORT_11 (gmii1 no EPHY)
Local back panel switch ports
P11 - SWITCH_PORT_12
P19 - SWITCH_PORT_20 (mii1 no EPHY)
P20 - SWITCH_PORT_21 (Gb1)
P21 - SWITCH_PORT_22 (gmii1 no EPHY)
factory> comm_port_parms –olan1
MAC Address=112233445500
IP Address=0.0.0.0
oper mode=normal
factory>
factory> comm_port_parms –oserial1
baud=9600
line mode=full_duplex
data bits=8
stop bits=1
parity=none
echo mode=off
flow control=none
delimiter=0
factory>
factory> comm_port_parms –oswitch1 –cp1
port=1 line mode=10_base_half_duplex
factory>factory> cpp –olan1 –m112233445566 –i111.222.233.244
factory>
factory> cpp –olan2 –l10_base_half_duplex
factory>
factory> cpp –oserial1 –b9600
6866600D04-C December 2006 2-21

chipset_reg Chapter 2: Test Application Commands
factory>
To set internal loopback mode on PHY level for lan1 and lan3 loopback tests run:
> cpp –oswitch1 –cp0 –l100_base_full_duplex –pext_loopback
chipset_reg
Syntax:
Read operations:
Command format 1: cr | chipset_reg –o<object> -c<chip_id> [-r<register_id>]
Command format 2: cr | chipset_reg –o<object> -c<chip_id> -p<page> -f<offset> -s<size>
Write operations:
Command format 1: cr | chipset_reg –o<object> -c<chip_id> -r<register_id> -v<value>
Command format 2: cr | chipset_reg –o<object> -c<chip_id> -p<page> -f<offset> [-s<size>] –v<value>
Description:
Provides access to the registers of several devices on the Site Controller card. It sets and reads registers of
the alarm card, the real time clock, the Ethernet switch and the standalone Ethernet PHY.
Options:
<object> A character string representing the object assigned to control the chipset register. Valid settings:
• controller
• switch1 (local)
• switch2..6 (remote)
• ps
• ps1..6
• ac1
ps = ps1. ps1 is local, ps2...6 are remote
ac1 is the local alarm card (iac).

Table 2-8 Chipset_reg options
object Format 1 Format 2

controller X X
switch1..6 — X
2-22 6866600D04-C December 2006

MTS Man Machine Interface Commands chipset_reg
Table 2-8 Chipset_reg options (Continued)

object Format 1 Format 2
ps X —
ps1..6 X —
ac1 — X
<chip_id> An integer value representing the hardware integrated circuit containing the register. Valid settings:
• ac_reg (alarm card registry)
• rtc_reg (real time clock registry)
• fp (front panel switch)
• bp (back panel switch)
• phy1
• ps_dac1
• ps_dac2
• ocxo_dac
Table 2-9 Chipset_reg options
chip\obj controller switch1 switch2..6 ps / ps1..6 ac1 Format 1 Format 2

ac_reg — — — — X — X
rtc_reg X — — — — X —
fp — X X — — — X
bp — X — — — — X
phy1 X — — — — X —
ps_dac1 — — — X — X —
ps_dac2 — — — X — X —
ocxo_dac X — — — X X —
<register_id> An integer value representing the register identifier.

<page> An 8-bit hexadecimal value representing the register page to be accessed. Not optional.
<offset> An 8-bit hexadecimal value representing the offset to be accessed. Not optional.
<size> An integer value representing the number of data bytes in the register to be read or written. This
parameter is optional; if not specified, it will be automatically calculated from the <value>. If the value is not
byte multiple (i.e. 0xFFF), an argument error will be returned by the MMI. Verification of mismatch between
the specified size and the actual size of the value is not done at MMI level. Valid settings: <integer>.
no validation is done to the size entered therefore the user should be careful with the
usage of this parameter as he could overwrite important data.
<value> A hexadecimal value to be written.
6866600D04-C December 2006 2-23

chipset_reg Chapter 2: Test Application Commands
Output:
Format 1 read operation output (cr –o<object> -c<chip_id> [-r<register_id>])
<chip_id> Register <reg_id 1><prd><value>
.
.
<chip_id> Register <reg_id n><prd><value>
: If the register ID it is not specified, the content of all registers of the selected chip_id will
be displayed. Otherwise, only the selected register’s value will be shown.
Format 2 read operation output (cr –o<object> -c<chip_id> -p<page> -f<offset> -s<size>)
Object<prd><object>
Chip_id<prd><chip_id>
Page<prd><page>
Offset<prd><offset>
Size<prd><size>
Value<prd><value>
The displayed <size>, refers to the actual read size, not to the requested one.
Example:
> cr –ocontroller –crtc_reg
rtc_reg Register 0x00=0x00000023
rtc_reg Register 0x02=0x000000a2
rtc_reg Register 0x07=0x000000b7
rtc_reg Register 0x08=0x000000da
rtc_reg Register 0x09=0x000000fc
rtc_reg Register 0x0a=0x000000aa
rtc_reg Register 0x0b=0x000000bf
rtc_reg Register 0x0c=0x00000000
rtc_reg Register 0x0d=0x000000f3
rtc_reg Register 0x0e=0x00000006
rtc_reg Register 0x0f=0x000000ef
rtc_reg Register 0x11=0x000000fa
rtc_reg Register 0x13=0x000000ff
rtc_reg Register 0x15=0x000000fe
rtc_reg Register 0x17=0x000000ef
rtc_reg Register 0x19=0x0000005f
rtc_reg Register 0x1a=0x00000000
rtc_reg Register 0x1b=0x0000005f
rtc_reg Register 0x1d=0x0000005f
2-24 6866600D04-C December 2006

MTS Man Machine Interface Commands chipset_reg

rtc_reg Register 0x1f=0x000000bf
rtc_reg Register 0x21=0x000000f7
rtc_reg Register 0x22=0x0000000e
rtc_reg Register 0x23=0x000000bf
rtc_reg Register 0x25=0x000000ba
rtc_reg Register 0x2a=0x000000c0
rtc_reg Register 0x2b=0x000000ef
rtc_reg Register 0x2d=0x0000003b
rtc_reg Register 0x2f=0x000000ff
rtc_reg Register 0x31=0x000000ba
rtc_reg Register 0x35=0x000000fb
rtc_reg Register 0x37=0x000000b7
rtc_reg Register 0x39=0x000000a9
rtc_reg Register 0x3a=0x0000000a
rtc_reg Register 0x3b=0x000000db
rtc_reg Register 0x3d=0x000000fe
rtc_reg Register 0x3f=0x000000ff
>
> cr –ocontroller –crtc_reg –r8 –vda
>
> cr – ocontroller –crtc_reg –r8
rtc_reg Register 0x08=0x000000da
> > cr – ocontroller –cphy1
phy1 Register 0x00=0x00000000
phy1 Register 0x01=0x0000780d
phy1 Register 0x03=0x000061e3
phy1 Register 0x0a=0x00000000
phy1 Register 0x0b=0x00000000
phy1 Register 0x0c=0x00000000
phy1 Register 0x0d=0x00000000
phy1 Register 0x0e=0x00000000
phy1 Register 0x0f=0x00000000
6866600D04-C December 2006 2-25

digital_analog_converter Chapter 2: Test Application Commands

phy1 Register 0x18=0x0000f010
phy1 Register 0x1a=0x00009f10
phy1 Register 0x1b=0x00000088
phy1 Register 0x1c=0x00000820
phy1 Register 0x1d=0x00000000
phy1 Register 0x1e=0x00000000
phy1 Register 0x1f=0x0000000b
>
> cr – ocontroller –cphy1 –r4 –vabcd
> cr – ocontroller –cphy1 –r4
>
> cr –oswitch1 –cfp –p0 –f1c –s1
Object=switch1
Chip_id=fp
Page=0x00000000
Offset=0x0000001c
Size=1
Value=0x00
>
> cr –oswitch1 –cfp –p0 –f1c –s1 –v8f
>
digital_analog_converter
Syntax:
Write operations:
dac | digital_analog_converter –o<object> -c<chip_id> -r<reg_id> -v<value>
Description:
Writes the power supply digital to analog converters.
Options:
<object> An character string representing the object assigned to the DAC. Valid settings: ps_loc
<chip_id> An character string representing the chip_id inside the object. Valid settings: ps_dac1; ps_dac2
<reg_id> An integer value representing the reg_id inside the chip. Valid settings: 0..7
<value> A integer value representing the value to write in the DAC.
Output:
N/A
Example:
> dac -ops_loc -cps_dac1 -r0 -v128
>
> dac -ops_loc -cps_dac2 -r7 -v128
>
2-26 6866600D04-C December 2006

MTS Man Machine Interface Commands e1_external_loopback
e1_external_loopback
Syntax:
Write operations:
e1el | e1_external_loopback –o<object> -d<deviceidd> -c<command>
e1el | e1_external_loopback –o<object> -d<deviceidd> -c<command> -n<no. of
packets> (command = senddata)
Description:
Opens and closes E1 links and sends and receives HDLC packets over those links.
Options:
<object> A character string representing the object owning the E1 interface. Valid settings: platform
<deviceid> A character string representing E1 interface. Valid settings: e1a; e1b
<command> A character string representing the command to be executed. Valid
settings: openlink; closelink; senddata
<no. of packets> A decimal value representing the number of HDLC packets to be sent. Note: All HDLC
packets are 27 bytes long and contain the same data. Valid settings: 1 – 4.294.967.295
Output:
senddata (successful):
The <deviceid> HDLC pkt transmission/reception PASSED
Number of pkt sent=<no of packets sent>
Number of pkt recv=<no of packets sent>
senddata (unsuccessful):
The <deviceid> HDLC pkt transmission/reception FAILED
Number of pkt sent=<no of packets sent>
Number of pkt recv=<no of packets received>
<deviceid> A character string representing E1 interface. Valid settings: E1a; E1b

< no of packets sent > A decimal value representing the number of HDLC packets sent.
< no of packets received > A decimal value representing the number of HDLC
packets received with correct CRC.
Example:
> e1el -oplatform -de1a -copenlink
The E1a link is opened successfully.
> e1el -oplatform -de1a -csenddata -n30
The E1a HDLC pkt transmission/reception PASSED
Number of pkt sent=30
Number of pkt recv=30
> e1el -oplatform -de1b -copenlink
The E1b link is opened successfully.
> e1el -oplatform -de1b -csenddata -n100
The E1b HDLC pkt transmission/reception FAILED
Number of pkt sent=100
Number of pkt recv=97
> e1el -oplatform -de1b -ccloselink
6866600D04-C December 2006 2-27

fru_configuration_parameter Chapter 2: Test Application Commands
The E1b link is closed successfully.

> e1el -oplatform -de1b -ccloselink
The E1b link is already closed!
> e1el -oplatform -de1a -ccloselink
The number of lost memory (mem. leakage)=0
The E1a link is closed successfully.
fru_configuration_parameter
Syntax:
Read operations:
fcp | fru_configuration_parameter –o<object> -p<parameterid>
Write operations:
fcp | fru_configuration_parameter –o<object> -p<parameterid> -v<value>
Description:
Provides access to configuration parameters which are stored on the non-volatile memory of Site
Controller’s EEPROM, local power supply,remote power supplies and XHUBs.
Options:
<object> A character string representing the object assigned to the fault management
monitoring control. Valid settings:
• control
• ps
• ps1..6
• xhub2..6
• encryption
• plat_eeprom
• ps = ps1. ps1 is local, ps2..6 are remote.

• Only read operation is supported for encryption and plat_eeprom objects.
• MAC addresses stored in LANx_MAC_ADDR (where x is 1, 2 or 3) will be used as the
default MAC addresses of LANs 1 to 3 when the Test Application starts. However, If
MAC addresses have been stored using the "cpp" command, these values will override
the LANx_MAC_ADDR values. I.e. MAC addresses stored using the "cpp" command
take precedence over MAC addresses stored using the "fcp" command.
<parameterid> A character string representing the fru configuration parameter identifier.

<value> A character string representing the fru configuration parameter value.
Output:
2-28 6866600D04-C December 2006

MTS Man Machine Interface Commands fault_management_enable
<parameterid><prd><value>
Example:
> fcp –ocontrol –pmanuf_loc
manuf_loc=IL02
> > fcp –ocontrol –pmanuf_loc –vIL03
>
> fcp –oencryption –pone_wire_device_info
Family Code = 0x23
HW Identifier = 0xa5f22e000000
CRC = 0x5f
> fcp –oencryption –pone_wire_device_info –v0
Platform Failed
>
fault_management_enable
Syntax:
Read operations:
fme | fault_management_enable –o<object>
Write operations:
fme | fault_management_enable –o<object> -s<state>
Description:
Controls the hardware fault management enabled state.
Options:
monitoring control. Valid settings: fault_hndlr
<state> A character string representing the state of the fault management feature. Valid settings: on; off
Output:
Mode<prd><state>
Example:
> fme –ofault_hndlr –son
>
> fme –ofault_hndlr
Mode=on
>
fault_management_interval
Syntax:
Read operations:
6866600D04-C December 2006 2-29

e1_frm_config Chapter 2: Test Application Commands
fmi | fault_management_interval –o<object>

Write operations:
fmi | fault_management_interval –o<object> -s<scaling_factor>
Description:
Controls the hardware fault management periodic monitoring interval.
Options:
monitoring control. Valid settings: fault_hndlr
<scaling_factor> A float value representing the periodic monitoring interval scaling
factor. Valid settings: 0.2 Up to 10
Output:
Scaling factor<prd><scaling_factor>
Example:
> fmi –ofault_hndlr –s3
>
> fmi –ofault_hndlr
Scaling factor=3
>
e1_frm_config
Syntax:
Read operations:
frm | e1_frm_config –o<object> -d<deviceidd> -c<command>
Write operations:
frm | e1_frm_config –o<object> -d<deviceidd> -c<command>
Description:
Reads and writes the registers in the E1 framer chip.
Options:
<object> A character string representing the object owning the E1 interface. Valid settings: platform
<deviceid> A character string representing E1 interface or framer chip. Valid settings: e1a; e1b; frm
<command> A character string representing the command to be executed. Valid settings – read commands:
• status deviceid = frm, reports the state of the framer chip (ALIVE or DEAD)
• lb_status deviceid = e1a or e1b, reports the loopback state
• version deviceid = frm, reports the version of the framer chip firmware
Valid settings – write commands:
2-30 6866600D04-C December 2006

MTS Man Machine Interface Commands fru_self_diagnostic
• reset deviceid = frm, resets the framer chip

• int_enable deviceid = e1a or e1b
• int_disable deviceid = e1a or e1b
• activate_line deviceid = e1a or e1b
• deactivate_line deviceid = e1a or e1b
• rst_all_lb deviceid = e1a or e1b
• idle deviceid = e1a or e1b
• rst_idle deviceid = e1a or e1b
• local deviceid = e1a or e1b
• rst_local deviceid = e1a or e1b
• remote deviceid = e1a or e1b
• rst_remote deviceid = e1a or e1b
• line deviceid = e1a or e1b
• rst_line deviceid = e1a or e1b
• payload deviceid = e1a or e1b
• rst_payload deviceid = e1a or e1b
• internal deviceid = e1a or e1b
• rst_internal deviceid = e1a or e1b
Example:
> frm -oplatform -dfrm -cstatus
The Framer is ALIVE
> > frm -oplatform -de1a -clb_status
All loopbacks are DISABLED on e1a
>
> frm -oplatform -dfrm -cversion
Framer SW Version=5
>
> frm -oplatform -de1a -clocal
> frm -oplatform -de1a -clb_status
Loopback is ENABLED on e1a
fru_self_diagnostic
Syntax:
Read operations:
fsd | fru_self_diagnostic -o<object> -t<test>
Description:Initiates a different, including loopback, tests on the passed object. It returns result string
” pass” or “fail”. The loopback test consist of verifying data integrity for a given transmit-receive loop.
The type of loopback on specified object (internal or external) depends on specific objects configurations.
6866600D04-C December 2006 2-31

fru_self_diagnostic Chapter 2: Test Application Commands
This can be done with cpp MMI command. The user can also use cr mmi to provide test specific switch
configuration. For external loopback the test requires external dungle. Correct loopback functionality for
lan1…3 objects should be provided with unmanaged switch mode as explained below.
Options:
<object> A character string representing the object under the test. Valid settings:
• lan1...3
• serial1,2,4
• uhso1
• ac1…ac12 (ac1, ac3, ac5, ac7, ac9, ac11 – integrated alarm cards; ac2, ac4,
ac6, ac8, ac10, ac12 – external alarm cards)
<test> loopback
Output:
test<prd><test_status>
<test_status> A character string representing the result of test. Valid settings:

• pass
• fail
Example:
Mapping of objects between TestApp and Platform
lan1...3 - LAN1…3
serial1, 2,4 - TTY1, TTY2, TTY4
uhso1 - CORE_UHSO (Rubidium)
ac1 - ALARM_CARD1 (integrated SC alarm card)
ac2 - ALARM_CARD2 (external SC alarm card)
ac3 - ALARM_CARD3 (xhub 2 integrated alarm card)
ac4 - ALARM_CARD4 (xhub 2 external alarm card)
SC board reset and configuration of unmanaged mode for front and back panel switches:
reset -oswitch1
cr -oswitch1 -cfp -p00 -f1E -s1 -vFB
cr -oswitch1 -cfp -p00 -f00 -s1 -v00
cr -oswitch1 -cfp -p00 -f0B -s1 -v06
cr -oswitch1 -cfp -p00 -f1C -s1 -v00
2-32 6866600D04-C December 2006

cr -oswitch1 -cfp -p00 -f1D -s1 -v00

cr -oswitch1 -cbp -p00 -f00 -s1 -v00
cr -oswitch1 -cbp -p00 -f0B -s1 -v06
cr -oswitch1 -cbp -p00 -f1C -s1 -v00
cr -oswitch1 -cbp -p00 -f1D -s1 -v00
SC board configuration to prevent application blocking if external dungle present on

lan ports during internal loopback tests:
cr -oswitch1 -cfp -p00 -f0B -s1 -v06
cr -oswitch1 -cfp -p00 -f1D -s1 -v00
cr -oswitch1 -cbp -p00 -f0B -s1 -v06
cr -oswitch1 -cbp -p00 -f1D -s1 -v00
cr -oswitch1 -cfp -p31 -f0A -s2 -v0000
cr -oswitch1 -cfp -p31 -f0E -s2 -v0000
cr -oswitch1 -cfp -p31 -f2A -s2 -v0000
cr -oswitch1 -cfp -p31 -f2E -s2 -v0000
6866600D04-C December 2006 2-33

fru_self_diagnostic Chapter 2: Test Application Commands

cr -oswitch1 -cbp -p31 -f0A -s2 -v0000
cr -oswitch1 -cbp -p31 -f0E -s2 -v0000
cr -oswitch1 -cbp -p31 -f2A -s2 -v0000
cr -oswitch1 -cbp -p31 -f2E -s2 -v0000
This script includes previous unmanaged mode script.

Default external loopback on serial1 object:
> fsd -oserial1 -tloopback
You must place a dungle on the port to test now.
-----Press the SPACE bar to continue-----
Starting test...
test=pass
>
Default external loopback on serial4 object with external test path set to EAC:
> fsd -oserial4 -tloopback
Starting test...
test=pass
>
Default external loopback on ac2 object with serial 4 used as a loopback packets source and
external test path set to EAC (equivalent to previous step):
> fsd –oac2 -tloopback
Starting test...
test=pass
>
Internal loopback on lan1 object with lan1 used as a loopback packets source and external
loopback test path set on switch1-port0 ephy:
> cpp –oswitch1 –cp0 –l100_base_full_duplex –pext_loopback
2-34 6866600D04-C December 2006

> fsd -olan1 -tloopback

INTERNAL LOOPBACK MODE; NO DUNGLE ON THE PORT
Starting test...
test=pass
>
loopback test path set on switch1-port0 ephy during previous step:
Starting test...
test=pass
>
External loopback on lan1 object with lan1 used as a loopback packets source and external
loopback test path provided by external dungle:
> cpp –oswitch1 –cp0 –pnormal
Starting test...
test=pass
>
> cpp –olan3 –pnormal
> fsd –olan3 -tloopback
Starting test...
test=pass
>
> cpp –olan2 –pnormal
Starting test...
test=pass
>
Internal loopback on lan2 object with lan2 used as a loopback packets source and internal
loopback test path set on lan2 MCU level:
> cpp –olan2 –pint_loopback
Starting test...
test=pass
>
6866600D04-C December 2006 2-35

firmware_version Chapter 2: Test Application Commands
loopback test path set on the lan2 ephy:
> cpp –olan2 –pext_loopback
Starting test...
test=pass
>
firmware_version
Syntax:
Read operations:
fv | firmware_version –o<object>
Description:
Displays the run-time firmware versions.
Options:
<object> A character string representing the object assigned to the firmware version
query control. Valid settings: platform
Output:
Multiple:
Test Application Version<prd><testapp_version>
OS Version<prd><os_version>
Core Software Ver<prd><core_version>
BootFlashEntry[0]<prd>ID: <entry_id>, Ver: <version>, Status: <status>
.
.
BootFlashEntry[n=valid entries]<prd>ID: <entry_id>, Ver:
<version>, Status: <status>
Boot Sequencer Version<prd><boot_seq_version>
FPGA Version<prd><fpga_version>
<testapp_version> A character string representing the Test Application version number.

Valid settings: Any version in the form A00.00.00
<os_version> A character string representing the operating system name and version number. Valid
settings: Any operating system name and version in the form <OS_Name> 0.0.0
<core_version> A character string representing the Core version number. Valid set-
tings: Any version in the form A00.00.000
<entry_id> A character string representing the entry point identifier. Valid settings: Boot0, TestApp
<version> A character string representing the version of entry point. Valid settings:
Any version in the form A00.00.00
<status> A character string representing the status of the entry point. Valid settings:
PLATFORM_SUCCESS PLATFORM_BAD_CHKSUM
2-36 6866600D04-C December 2006

MTS Man Machine Interface Commands gps
<boot_seq_version> A character string representing the Boot sequencer version. Valid

settings: Any version in the form A00.00.00
<fpga_version> A character string representing the FPGA version. Valid set-
tings: Any version in the form A0.0.0
Example:
> fv –oplatform
Test Application Version =E15.04.07
OS Version =OSE 4.5.2
Core Software Ver=PLAT_R06.78.037
BootFlashEntry[0] =ID: TestApp, Ver: E04.02.00, Status: CORE_SUCCESS
BootFlashEntry[1] =ID: Platform, Ver: ff.ff.ff, Status: Unknown
BootFlashEntry[2] =ID: TestApp, Ver: E04.02.00, Status: CORE_SUCCESS
BootFlashEntry[3] =ID: Platform, Ver: ff.ff.ff, Status: Unknown
BootFlashEntry[4] =ID: Boot0, Ver: 00.00.01, Status: CORE_SUCCESS
BootFlashEntry[5] =ID: Boot0, Ver: 00.00.01, Status: CORE_BAD_CHKSUM
version =Controller Rev No : R08.03.00
version =Controller Kit No : KitNo1
version =MZ Kit No : KitNo2
version =Control Board ICD Rev : R08.03.00
version =Fpga Ver : 0x01000001
version =Core Software Ver : PLAT_R06.78.037
version =Platform ID : 0x00000008
version =Alarm Card HW Ver : R08.02.01
version =Alarm Card PLD Ver : R08.02.00
version =Ethernet Switch Hw Ver : R08.03.00
version =OCXO Hw Ver : R08.02.00
version =Boot Sequencer Ver : R08.03.00
version =TwelveM Structure Ver : 0xFFFFFFFF
version =TwelveM Structure Checksum: 0xFFFFFFFF
version =Cabinet ID : 0xFFFFFFFF
version =Born On Date : June 03, 2004
version =Last Test Date : LastTestDate
version =Manufacturer Date : ManufDate
version =Manufacturer Info 1 : ManufInfo1
version =Manufacturer Info 2 : ManufInfo2
version =Manufacturer Location : ManufLoc
version =Ref 12M : Ref12M
gps
Syntax:
Read operations:
gps –o<object> -c<command>
gps –o<object> -c<command> -s<time_type> (command = time)
Write operations:
gps –o<object> -c<command> -a<altitude> -g<longitude> -l<latitude> (command = location)
gps –o<object> -c<command> -s<time type> -d<day> -m<month> -y<year> -t<time> (command = time)
gps –o<object> -c<command> -k<angle> (command = mask)
Description:
6866600D04-C December 2006 2-37

gps Chapter 2: Test Application Commands
Configures the GPS receiver and displays its status and current location information.
Options:
<object> A character string representing the object to the GPS. Valid settings: platform
<command> A character string representing the command to be executed. Valid settings:
• status (read-only)
• location
• time
• mask
<time_type> Select either the GPS time or the UTC time calculated by the GPS. Valid
settings: GPS (Default value), UTC
<altitude> New altitude provided to the GPS as initial setting, expressed in meters with a
resolution of 0.01. Valid settings: -1000.00..18288.00.
<longitude> New longitude provided to the GPS as initial setting, expressed in degrees
with a decimal part. Valid settings: -180.000..180.000
<latitude> New latitude provided to the GPS as initial setting, expressed in degrees
<day> The day to provide to the GPS. Valid settings: 1..31
<month> The month to provide to the GPS. Valid settings: 1..12
<year> The 4 digits year to provide to the GPS Valid settings: 2000..9999
<time> The current time to provide to provide to the GPS in the hh:mm:ss format.
Valid settings: 00:00:00..23:59:59
<angle> Satellite mask angle in degrees. Valid settings: 0..89 (Zero indicate no mask)
Output:
Status:
Model Number<prd><model_number>
Lock State<prd><lock_state>
Tracking State<prd><tracking state>
Longitude<prd><gpsr_longitude>
Latitude<prd><gpsr_latitude>
Altitude<prd><gpsr_altitude>
DOP<prd><dilution_of_precision>
Number of visible satellites<prd><gpsr_visible_sat>
Number of tracked satellites<prd><gpsr_tracked_sat>
Channel1 SVID<prd><Satellite ID>
Mode<prd><tracking mode>
Strength<prd><signal strength>
.
.
.
Channel12
SVID<prd><Satellite ID>
2-38 6866600D04-C December 2006

MTS Man Machine Interface Commands gps
location:
Latitude<prd><value>
Longitude<prd><value>
Altitude<prd><value>
time:
gps <time_ type><prd><month>/<day>/<year> <time>
mask:
gps mask angle<prd><mask angle>
<model_number> GPS model number provided by the device. Valid settings: GPS module specific string
<lock_state> Indicate if the timing reference of the GPS is locked and usable. Valid settings: locked not locked.
<tracking state> Current tracking state of the GPS receiver. Valid settings:
• No FIX
• Site Survey
• Position Hold
• 2D FIX
• 3D FIX
<gpsr_longitude> Current longitude as determined by the GPS receiver or the value used to
preset the longitude. Valid settings: -180.000..180.000
<gpsr_latitude> Current latitude as determined by the GPS receiver or the value used to
preset the latitude. Valid settings: -90.000..90.000
<gpsr_altitude> Current altitude as determined by the GPS receiver or the value used to preset the
altitude in meter (2 digits after the dot) Valid settings: -1000.00..18288.00
<dilution_of_precision> Value of the dilution of precision. Valid settings: 0.0..99.9
<gpsr_visible_sat> Number of satellites visible to the GPS unit. Valid settings: 0..12
<gpsr_tracked_sat> Number of tracked satellites by the GPS unit. Valid settings: 0..12
<Satellite ID> SVID of the satellite tracked on this channel. Valid settings: GPS module specific string
<tracking mode> Current tracking mode of this channel Valid settings:
• code search
• code acquire
• AGC set
• preq acquire
• bit sync detect
• message sync detect
• satellite time available
• ephemeris acquire
• Available for position
6866600D04-C December 2006 2-39

gps Chapter 2: Test Application Commands
<signal strength> Signal strength received by this channel. Valid settings: GPS module specific string.
<mask angle> Specifies the desired satellite mask angle in degrees. Valid settings: 0..89
Example:
> gps –oplatform –cstatus
Model Number=P273T12T11
Lock State=not locked
Tracking State=GPSR is not tracking any satellites
Longitude=-180.00 degrees
Latitude=-90.00 degrees Altitude=8672.00 m
DOP= 0.0 Number of visible satelites= 0
Number of tracked satelites= 0
Channel 1
SVID= 26
mode=code search
strength= 0.00
Channel 2
SVID= 24
mode=code search
strength= 0.00
Channel 3
SVID= 1
mode=code search
strength= 0.00
Channel 4
SVID= 7
mode=code search
strength= 0.00
Channel 5
SVID= 17
mode=code search
strength= 0.00
Channel 6
SVID= 4
mode=code search
strength= 0.00
Channel 7
SVID= 10
mode=code search
strength= 0.00
Channel 8
SVID= 14
mode=code search
strength= 0.00
Channel 9
SVID= 23
mode=code search
strength= 0.00
Channel 10
SVID= 16
mode=code search
strength= 0.00
Channel 11
SVID= 21
mode=code search
strength= 0.00
Channel 12
SVID= 15
mode=code search
strength= 0.00
2-40 6866600D04-C December 2006

MTS Man Machine Interface Commands igps
>
> gps –oplatform –cmask
gps mask angle=89
>
> gps –oplatform –cmask –k89
>
> gps –oplatform –ctime –sUTC
gps UTC=2/1/2004 14:01:05
>
> gps –oplatform –clocation –a18288.00 –g180.00 –l90.00
>
> gps –oplatform –ctime –sUTC –d1 –m2 –y2004 –t14:01:01
>
igps
Syntax:
Read operations:
gps –o<object> -c<command>
gps –o<object> -c<command> -s<time_type> (command = time)
Write operations:
gps –o<object> -c<command> -a<altitude> -g<longitude> -l<latitude> (command = location)
gps –o<object> -c<command> -s<time type> -d<day> -m<month> -y<year> -t<time> (command = time)
gps –o<object> -c<command> -k<angle> (command = mask)
Description:
Configures the internal GPS receiver and displays its status and current location information.
The first request to get the time will return the value 0/0/0 0:00:00. Subsequent
requests will return the correct time.
Options:
<object> A character string representing the object to the GPS. Valid settings: platform
<command> A character string representing the command to be executed. Valid settings:
• status (read-only)
• location
• time
• mask
<time_type> Select either the GPS time or the UTC time calculated by the GPS. Valid
settings: GPS (Default value); UTC
6866600D04-C December 2006 2-41

igps Chapter 2: Test Application Commands
<altitude> New altitude provided to the GPS as initial setting, expressed in meters with a
resolution of 0.01. Valid settings: -1000.00..18288.00
<longitude> New longitude provided to the GPS as initial setting, expressed in degrees
<latitude> New latitude provided to the GPS as initial setting, expressed in degrees
<day> The day to provide to the GPS. Valid settings: 1..31
<month> The month to provide to the GPS. Valid settings: 1..12
<year> The 4 digits year to provide to the GPS. Valid settings: 2000..9999
<time> The current time to provide to provide to the GPS in the hh:mm:ss format.
Valid settings: 00:00:00..23:59:59
<angle> Satellite mask angle in degrees. Valid settings: 0..89 (Zero indicate no mask)
Output:
Status:
Model Number<prd><model_number>
Lock State<prd><lock_state>
Tracking State<prd><tracking state>
Longitude<prd><gpsr_longitude>
Latitude<prd><gpsr_latitude>
Altitude<prd><gpsr_altitude>
DOP<prd><dilution_of_precision>
Number of visible satellites<prd><gpsr_visible_sat>
Number of tracked satellites<prd><gpsr_tracked_sat>
Channel1
.
.
.
Channel12
Location:
Latitude<prd><value>
Longitude<prd><value>
Altitude<prd><value>
time:
gps <time_ type><prd><month>/<day>/<year> <time>
mask:
gps mask angle<prd><mask angle>
<model_number> GPS model number provided by the device. Valid settings: GPS module specific string
<lock_state> Indicate if the timing reference of the GPS is locked and usable. Valid settings: locked; not locked
2-42 6866600D04-C December 2006

MTS Man Machine Interface Commands igps
<tracking state> Current tracking state of the GPS receiver Valid settings:
• No FIX
• Site Survey
• Position Hold
• 2D FIX
• 3D FIX
<gpsr_longitude> Current longitude as determined by the GPS receiver or the value used to
preset the longitude. Valid settings: -180.000..180.000
<gpsr_latitude> Current latitude as determined by the GPS receiver or the value used to
preset the latitude. Valid settings: -90.000..90.000
<gpsr_altitude> Current altitude as determined by the GPS receiver or the value used to preset the
altitude in meter (2 digits after the dot). Valid settings: -1000.00..18288.00
<dilution_of_precision> Value of the dilution of precision. Valid settings: 0.0..99.9
<gpsr_visible_sat> Number of satellites visible to the GPS unit. Valid settings: 0..12
<gpsr_tracked_sat> Number of tracked satellites by the GPS unit. Valid settings: 0..12
<Satellite ID> SVID of the satellite tracked on this channel. Valid settings: GPS module specific string.
<tracking mode> Current tracking mode of this channel. Valid settings:
• code search
• code acquire
• AGC set
• preq acquire
• bit sync detect
• message sync detect
• satellite time available
• ephemeris acquire
• Available for position
<signal strength> Signal strength received by this channel. Valid settings: GPS module specific string.
<mask angle> Specifies the desired satellite mask angle in degrees. Valid settings: 0..89
Example:
> igps -oplatform -cstatus
Lock State=not locked
Tracking State= Longitude= 0.00 degrees
Latitude= 0.00 degrees
Altitude= 0.00 m
DOP=0.0
Number of visible satellites= 3
Number of tracked satellites= 2
Channel 1
SVID= 14
6866600D04-C December 2006 2-43

igps Chapter 2: Test Application Commands
mode=code search
strength=47.60 dB Hz
Channel 2
SVID= 17
mode=preq acquire
Channel 3
SVID= 24
mode=code search
Channel 4 SVID= 3
mode=preq acquire
Channel 5
SVID= 5
mode=code search
Channel 6
SVID= 1
mode=code search
strength= 0.00 dB Hz
Channel 7
SVID= 1
mode=code search
Channel 8
SVID= 1
mode=code search
Channel 9
SVID= 1
mode=code search
Channel 10
SVID= 1
mode=code search
Channel 11
SVID= 1
mode=code search
Channel 12
SVID= 1
mode=code search
>
> gps –oplatform –cmask
gps mask angle=89
>
> gps –oplatform –cmask –k89
>
> gps –oplatform –ctime –sUTC
gps UTC=2/1/2004 14:01:05
>
> gps –oplatform –clocation –a18288.00 –g180.00 –l90.00
>
> gps –oplatform –ctime –sUTC –d1 –m2 –y2004 –t14:01:01
>
2-44 6866600D04-C December 2006

MTS Man Machine Interface Commands kit_number
kit_number
Syntax:
Read operations:
kn | kit_number –o<object>
Write operations:
kn | kit_number -o<object> -s<kit_number>
Description:
Controls the FRU kit number setting.
Options:
<object> A character string representing the object assigned to control the FRU kit number. Valid settings:
• control
• ps
• ps1..6
• xhub2..6
ps = ps1. ps1 is local, ps2..6 are remote.

<kit_number> A character string representing the FRU kit number setting. Valid settings:
Any string with printable characters and no spaces.
Output:
kit_number<prd><kit_number>
Example:
> kn –ocontrol –s25
> kn –ocontrol
kit_number=25
led_config
Syntax:
Read operations:
lc| led_config –o<object> -l<led_id>
Write operations:
lc | led_config -o<object> -l<led_id> -s<state> -r<rate> -d<duty> -c<color>
Description:
6866600D04-C December 2006 2-45

led_config Chapter 2: Test Application Commands
Controls the platform LED configuration. This command offers enhanced capability over the led command.
Table 2-10 lc MMI Objects, led_id and LED Color State Mapping
mmi object led_id color state

ps, ps2…6 status green, off, blink
ps, ps2….6 alarm red, off, blink
Ps, ps2….6 fan_fail Red, off, blink
fan, fan2…6 alarm red, off, blink
controller status green, off, blink
controller alarm red, off, blink
xhub2…6 status green, off, blink
xhub2….6 alarm red, off, blink
lc MMI can’t set the remote fan leds when the fan is off.
Options:
<object> A character string representing the object assigned to control the led’s. Valid settings:
• ps, ps2...6
• fan,fan2...6
• xhub2…6
• controller
ps = ps1. ps1 is local, ps2...6 are remote.
fan = fan1 fan1 is local, fan2...6 are remote.

<led_id> A character string representing the led identifier. Valid settings: fan_fail, status, alarm.
Refer to the specific ICD of each object.

<state> A character string representing the led state. Valid settings: on, off, blink.
<rate> A character string representing the led blink rate.
2-46 6866600D04-C December 2006

MTS Man Machine Interface Commands led
This attribute is only applicable with a state attribute setting of blink.

Valid settings: vslow, slow, med, fast, vfast.
<duty> An integer value representing the led blink duty cycle in percent.
This attribute is only applicable with a state attribute setting of blink.

Valid settings: 0, 25, 50, 75, 100
<color> A character string representing the led color. Valid settings: color1, color2, color3
Output:
<led_id 1>
state<prd><setting>
rate<prd><setting>
duty<prd><setting>
color<prd><setting>
Example:
>lc -ops -lfan_fail -sblink -d25 -rvslow -ccolor1
> lc -ops -lfan_fail
fan_fail
state<prd>blink
rate<prd>vslow
duty<prd>25
color<prd>color1
>
led
Syntax:
Read operations:
led -o<object>
Write operations:
led -o<object> -l<led_pattern>
Description:
Controls the front-panel LEDs. This MMI turns off a specified front-panel LED or turns it on to a specified color.
Options:
<object> A character string representing the object assigned to control the led’s. Valid settings: platform.
<led_pattern> A left justified hexadecimal value representing the front panel led pattern setting. Valid led_ids:
• cntrl_01, cntrl_02, cntrl_03, cntrl_04, cntrl_05, cntrl_06.
6866600D04-C December 2006 2-47

load Chapter 2: Test Application Commands
• The LED pattern is represented as an unsigned int. Each LED gets two bits.
The bit val¬ues are defined as follows: 00: LED is off; 01: LED is colour
1; 10: LED is colour 2; 11: LED is colour 3;
• The pattern should be right justified with the least significant bits corresponding to the
lowest or rightmost (physical location of front panel) LED and the most significant bits
representing the top or leftmost (physical location on front panel) LED.
Output:
Led_pattern<prd><led_pattern>
Example:
> led -oplatform
led_pattern=0000
>
>led -oplatform -l3cc
>
load
Syntax:
Write Operations:
load –m<method> -h<host_ip> -p<path/filename> -t<target>
Description:
Downloads a hex-file (also known as an srec-file) from a TFTP server and programs it into the flash memory.
The TFTP server must be connected via a LAN to the redundant Site Controller Ethernet Port.
• lan2 (Redundant Site Controller LAN) must be connected to a network.

• lan2 (Redundant Site Controller LAN) must have valid IP Address on same subnet
as the TFTP server (subnet mask = 255.255.255.0)
• TFTP Server must be running and configured properly on PC which contains software to load.
• Firewall on TFTP Server PC must be disabled
• Hex-file to download must not be larger than 16 Mbytes (16777216 bytes)
Options:
<method> A character string representing the file download protocol. Valid settings: tftp
<host_ip> A character string representing the standard IP formatted address of the host to download
from. Valid settings: any valid IP address in the form 111.222.333.444
<path/filename> A character string representing the path and filename of the file to be downloaded.
Valid settings: any valid path and S-Record filename.
2-48 6866600D04-C December 2006

MTS Man Machine Interface Commands login
<target> A character string representing the location where the file will be downloaded. Valid settings: flash
Output:
Downloading hex file from TFTP server...
<num_received_pkts> 512-byte packets (<num_received_bytes>) received
Processing S records...
<num_records> records processed
Programming block 1 of 1 (offset = <address>, size(bytes) = <size>)
Please wait! This may take up to <programming_duration>
<num_received_pkts> A decimal integer value representing the number of TFTP packets received.
<num_received_bytes> A decimal integer value representing the number of bytes received.
<num_records> A decimal integer value representing the number of S-Records processed.
<address> A hexadecimal integer value representing the address in the flash memory where
the programming starts. The value is relative to the start of the flash memory chip, which
in this version of the Test Application is 0xFE000000.
<size> A decimal integer value representing the number of bytes programmed.
<programming_duration> Decimal integer values representing time it will take to program
the flash memory expressed in minutes and seconds.
In case hex file is larger than 16 Mbytes (16777216 bytes):
> load -mtftp -h169.254.24.57 -pTSC_RLJ_TESTAPP_20_APR_06_just_over_16MB.hex
-tflash
32769 512-byte packets (16777218 bytes) received - downloading failed.
TFTP file exceeds maximum size of 16777216 bytes
>
Example:
> load -mtftp -h169.254.24.57 -pTSC_RLJ_TESTAPP_20_APR_06_b_B.tmp -tflash
17444 512-byte packets (8931090 bytes) received
Processing S records...
159495 records processed
Programming block 1 of 1 (offset = 0x1740000, size(bytes) = 3189584)
Please wait! This may take up to 9 minutes and 39 seconds
>
login
Syntax:
Write operations:
login –u<user_id>
Description:
Allows the user to login as one of valid users (developer, factory or field). Each user type is giving
access to specific set of MMIs commands and their access rights (read and/or write).
Options:
6866600D04-C December 2006 2-49

logout Chapter 2: Test Application Commands
user_id> A character string representing the user id to be logged in as. Valid settings:
• field
• factory
• dev
Output:
password:
Example:
login –ufactory
factory>
logout
Syntax:
Operations:
logout
Description:
Allows the user to log out of the current MMI command access level.
Options:
N/A
Output:
N/A
Example:
factory> logout
>
lrr - last_reset_reason
Syntax:
Read operations:
lrr | last_reset_reason -o<object>
Description:
Gives the reason for which a reset last occurred on the Site Controller card.
Options:
<object> A character string representing the object to access for the last reason. Valid settings: platform.
2-50 6866600D04-C December 2006

MTS Man Machine Interface Commands memory
Output:
Last reset reason<prd><last_reset>
< last_reset > A string which identifies the reason that caused the last reset. Valid settings:
• GS_RESET_BUTTONS -> Push-button
• GS_RESET_SOFTWARE -> Software Request
• GS_RESET_POWERUP -> Power-On
• GS_RESET_HOST -> Host Request
• HOST_SOFT_RESET
• GS_RESET_WDG -> watchdog reset
Example:
> lrr -oplatform
last reset reason:=GS_RESET_POWERUP -> Power-On
>
memory
Syntax:
Read operations:
memory -o<object> -f<offset> -l<length> -w<width>
Write operations:
memory -o<object> -f<offset> -l<length> -v<value>
Description:
Provides the user a means to read and write in volatile and non-volatile memory space contents.
Operations can be performed in various word sizes and length.
• User should always write to the reserved user section for objects spd_eeprom and
boot_eeprom, the valid offset range of spd_eeprom is from 0x80 to 0x100 and
boot_eeprom offset range is from 0x1f00 to 0x1fff.
• Request to display the first 8 bytes of RTC RAM is provided by CR MMI.
Table 2-11 Mapping between MMI Objects and MMI APIs
MMI Object MMI API

encryption CTRL_EEPROM6_MEM
plat_eeprom PLAT_EEPROM_MEM
flash0 CTRL_FLASH0_MEM
6866600D04-C December 2006 2-51

memory Chapter 2: Test Application Commands
Table 2-11 Mapping between MMI Objects and MMI APIs (Continued)
MMI Object MMI API
rtc_ram CTRL_EEPROM4_MEM
mass_store1 MASS_STORAGE0_MEM
boot_eeprom CTRL_EEPROM2_MEM
spd_eeprom CTRL_EEPROM8_MEM
Options:
<object> A character string representing the memory object. Valid settings:
• mass_store1
• flash0
• address (for peek and poke operations)
• rtc_ram
• plat_eeprom (for 1-wire memory in the backplane)
• encryption (for 1-wire protection memory in the board)
• boot_eeprom
• spd_eeprom
<offset> A hexadecimal value representing the starting address of the memory block.
Offset is a virtual offset from the start of a memory region/device. It may/ may
not map directly to a physical memory address.
<length> A hexadecimal value representing the length of the memory block.
: length will be restricted to device/region specific limitations such as device size, block
size, etc.. For Read operations, <length> indicates the number of bytes to be read as per the
following formula: (length*width)/8 is equal to the nb of bytes read. For Write operations,
<length> is optional with a default value of 1, as in one of<value>. Thus, the number of
bytes to write is determined by Test Application using the following formula: bytes =
<length> *sizeof (<value>). This also implies that if <length> is greater than 1, the<value>
is repeated successively in memory <length> times in the write data buffer.
<width> An integer value representing the block size of the data. For Read Operations,
this parameter is optional with the default being 32. For Write Operations, It’s not
applicable (not supported). Valid Settings: 8, 16, 32, 64
<value> A hexadecimal value representing the data to be written.
Output:
offset +00 +01 +02 +0n
2-52 6866600D04-C December 2006

MTS Man Machine Interface Commands memory_parameters
<offset+1((length-(size/8)) /(size/8))> x1 x2 x3 xn+1

<offset+2((length-(size/8) /(size/8))> xn+2 xn+3 xn+4 x2n+2
<offset+m((length-(size/8)) /(size/8))> xa xb xc xa+m+n
<offset+m((length-(size/8)) /(size/8))> The hexadecimal value of the beginning address of each

row of n + 1 bytes. +00, +01, +02, +0n The hexadecimal offset of each column from the
address listed in the first row. Numbers of columns are determined by its size, byte only has
one column, word has 2, long has 4 and double has 8 columns.
xa+m+n The hexadecimal value of the memory location at the address found by adding
the row offset to the column offset.
Example:
> memory –omass_store1 -f10000 -l4 -v3F4D
> memory –omass_store1 -f10000 -l4 –w16
offset +00 +01
00000000 3f 4d
00000002 3f 4d
00000004 3f 4d
00000006 3f 4d
> memory –oplat_eeprom -f010 -l3 –w32
offset +00 +01 +02 + 03
00000000 12 12 01 23
00000004 00 00 01 23
00000008 00 fa 34 c9
>
> memory –ospd_eeprom -f010 -l3 -v5F
>
> memory -oaddress -f0 -l1 -w64
offset +00 +01 +02 +03 +04 +05 +06 +07
00000000 02 00 80 00 00 04 22 01
> memory -oaddress -f0 -l8 -vaa
offset +00 +01 +02 +03 +04 +05 +06 +07
00000000 aa aa aa aa aa aa aa aa
> memory -oaddress -f0 -l1 -v0200800000042201
offset +00 +01 +02 +03 +04 +05 +06 +07
00000000 02 00 80 00 00 04 22 01
>
memory_parameters
Syntax:
Read operations:
mp | memory_parameters -o<object>
Write operations:
mp | memory_parameters -o<object> -c<write_blocking_cycles> -d<write_block-
ing_duration> -e<erase_blocking_state>
Description:
Controls the memory access operational parameter setting.
6866600D04-C December 2006 2-53

memory_parameters Chapter 2: Test Application Commands
Options:
<object> A character string representing the object assigned to control the memory
parameters. Valid settings: compact_flash; flash.
<write_blocking_cycles> An integer value representing the number of write cycles between blocking
states during all write operations. Valid settings: any positive integer.
A value of 0 results in no blocking i.e. busy looping.

<write_blocking_duration> An integer value representing the duration in milliseconds the blocking
state will block during all write operations. If the <write_blocking_cycles> argument is set to a
value of 0 this argument is ignored. Valid settings: any positive integer.
A value of 0 results in blocking only if there are other tasks of the same priority ready to
run. Busy looping will be used if no other same priority tasks are ready.
<erase_blocking_state> A character string representing the state of erase blocking. Valid settings: on; off
A setting of off results in no blocking i.e. busy looping.

Output:
Write Cycles Between Blocking<prd><write_blocking_cycles>
Write Blocking Duration<prd><write_blocking_duration>
Erase Blocking State<prd><erase_blocking_state>
<write_blocking_cycles> A string which identifies the blocking cycles. Valid set-

tings: Any positive number or zero.
<write_blocking_duration> An integer which identifies the number of milliseconds of the
blocking state. Valid settings: Any positive number or zero.
< erase_blocking_state > A string representing the state of erase blocking. Valid settings: on, off
Example:
> mp -oflash
Write Cycles Between Blocking=0
Write Blocking Duration=1
Erase Blocking State=off
>
> mp -oflash -c1 -d2 –eon
>
> mp -oflash
Write Cycles Between Blocking=1
Write Blocking Duration=2
Erase Blocking State=on
>
2-54 6866600D04-C December 2006

MTS Man Machine Interface Commands pps_enable
pps_enable
Syntax:
Read operations:
pe | pps_enable -o<object>
Write operations:
pe | pps_enable -o<object> -s<state>
Description:
Permits to enable and disable the synchronization of the Site Controller with the 1PPS signal.
Options:
<object> A character string representing the object assigned to the 1PPS enable/dis-
able signal. Valid settings: platform.
<state> A character string representing the 1PPS state. Valid settings: on, off
Output:
State<prd><state>
Example:
> pe -oplatform
State=off
>
> pe -oplatform -soff
>
ping
Syntax:
Read operations:
ping -h<host_ip>
Description:
Executes the IP network ping feature.
• Ping is available only using the Lan2 connection.

• The user should reset the SC board after using the Ping command.
• The user need to set the local IP address before using Ping: > cpp
–olan2 –i192.168.2.58
Options:
6866600D04-C December 2006 2-55

platform_number Chapter 2: Test Application Commands
<host_ip> A character string representing the host IP address to ping. Valid settings:
any valid IP address in the form 111.222.333.444
Output:
32 bytes received from <ip_address>:icmp_seq = 1
.
.
32 bytes received from <ip_address>:icmp_seq = 4
Packets Transmitted<prd><tx_packets>
Packets Received<prd><rx_packets>
Packet Loss %<prd><loss>
<tx_packets> A integer value representing the number of packets transmitted.

Valid settings: any positive integer.
<rx_packets> A integer value representing the number of packets received. Valid settings: any positive integer.
<loss> A floating point value representing the packet loss percent. Valid settings: any positive value.
Example:
Success in finding the machine on the lan:
> cpp –olan2 –i192.168.2.58
> ping -h192.168.2.153
32 bytes received from 192.168.2.153:icmp_seq = 0
Packets Transmitted=4
Packets Received=4
Packet Loss %=0.000000
>
When it fails to find the machine on the lan:

> cpp –olan2 –i192.168.2.58
> ping -h10.32.92.64
Request time out
Request time out
Request time out
Request time out
platform_number
Syntax:
Read operations:
pn | platform_number -o<object>
Description:
Displays the platform number setting.
Options:
2-56 6866600D04-C December 2006

MTS Man Machine Interface Commands reset
<object> A character string representing the object assigned to control the platform
number query. Valid settings: platform.
Output:
Controller platform id<prd><Control data>
<Control data> A character string representing the platform number setting of the controller
board. This includes both numeric and character descriptions. Undefined controller in
the case of an invalid or unrecognized configuration.
Example:
> pn –oplatform
Controller platform id=8 Summit Site Controller MPC8560 based
>
reset
Syntax:
Write operations:
reset -o<object>
Description:
Forces the hard or soft reset of Site Controller board.
Options:
<object> A character string representing the object assigned to control the reset feature. Valid settings:
• platform (hard reset of the Site Controller board)
• control (soft reset of the Site Controller board)
• xhub2..6
• switch1
• peer1..36
Output:
N/A
Example:
> reset -oxhub2
>
> reset -oplatform
revision_number
Syntax:
6866600D04-C December 2006 2-57

reference_source Chapter 2: Test Application Commands
Read operations:
rn | revision_number -o<object>
Write operations:
rn | revision_number -o<object> -s<string>
Description:
Controls the FRU revision number setting.
Options:
<object> A character string representing the object assigned to control the revi-
sion number setting. Valid settings:
• control
• ps
• ps1..6
• xhub2...6
ps = ps1. ps1 is local, ps2...6 are remote.

<string> A character string representing the FRU revision number in the format AABB.CC.DD.
Valid settings: <Platform specific range>
Output:
revision_number<prd><string>
Example:
> rn -ocontrol -s R10.10.10
>rn -ocontrol
revision_number=R10.10.10
>
reference_source
Syntax:
Read operations:
rs | reference_source -o<object>
Write operations:
rs | reference_source -o<object> -s<source>
Description:
Selects the frequency reference source or gets the current selection.
Options:
2-58 6866600D04-C December 2006

MTS Man Machine Interface Commands real_time_clock
<object> A character string representing the object to access for the frequency ref-
erence. Valid settings: platform.
<source> A character string representing the source of the frequency reference. Valid settings:
• ext_ref
• rubidium
• redundant_sc
• fp_cal_port
• int_ref (read only, cannot be set)
Output:
Reference Source<prd><source>
Example:
> rs -oplatform
Reference Source=int_ref
>
> reference_source -oplatform -sext_ref
>
real_time_clock
Syntax:
Read operations:
rtc | real_time_clock -o<object>
Write operations:
rtc | real_time_clock -o<object> -t<time>
Description:
Sets and gets time of the real time clock. Time is given in number of seconds since 1st January 1970.
Options:
<object> A character string representing the object assigned to control the real time
clock setting. Valid settings: rt_clock.
<time> An integer value representing the time in seconds (UNIX epoch time: sec-
onds since midnight 1970 Jan 1st).
Output:
Time<prd><time>
Example:
> rtc -ort_clock
Time=31786949
3 Jan 1971 21:42:29 GMT
>
6866600D04-C December 2006 2-59

rx_fru_config Chapter 2: Test Application Commands
> rtc -ort_clock -t2678400

>
rx_fru_config
Syntax:
Read operations:
fcp -orxch1 -prx_fru_config
Write operations:
fcp -orxch1 -prx_fru_config -v{1 | 2 | 4 | 3 | 5 | 6 | 7}
Description:
Controls the receiver branches to be present in a Base Radio.
Options:
Valid settings:
• 1 - Receiver branch 1 enabled
• 3 - Receiver branches 1, 2 enabled
• 7 - Receiver branches 1, 2, 3 enabled
status
Syntax:
Read operations:
status -o<object>
Description:
Displays the platform and FRUs status information.
2-60 6866600D04-C December 2006

MTS Man Machine Interface Commands status
• status –ops1..n will only display presence detection. The rest of the infor-
mation will be provided with the bs MMI.
• Only lan2 is supported. lan1 and lan3 are not supported because they don’t have a PHY.
Options:
<object> A character string representing the object assigned to control the status query. Valid settings:
• compact_flash
• flash0
• platform
• switch{1..6}
• lan2
• xhub{2..6}
• ps
• ps(1..6)
ps=ps1 ps1 is local and ps(2->6) are remote. xhub1 does not exist since
an xhub is a remote component.
Output:
Compact Flash:
CompactFlash Bank Serial Number<prd><serial_num>
CompactFlash Bank Firmware Version<prd><fw_version>
CompactFlash Bank Model<prd><model>
CompactFlash Bank Start Address<prd><physical address>
CompactFlash Bank Internal Buffer size<prd><int_buff_size>
CompactFlash Bank Size<prd><size>
CompactFlash Bank Sector size <prd><sector_size>
CompactFlash Bank Number of sectors<prd><num_sectors>
Flash Memory:
Flash Bank(n) Start Address<prd><physical address>
Flash Bank(n) Size<prd><size>
Flash Bank(n) Sector(1)<prd><sector_offset(1)>,<sector_ad-
dress(1)>,<sector_size(1)>
...
Flash Bank(n) Sector(n)<prd><sector_offset(n)>,<sector_ad-
dress(n)>,<sector_size(n)>
Platform:
Redundant SC presence detect<prd><pres_detect>
Power Supply presence detect<prd><pres_detect>
Power Supply functional state<prd><func_state>
Fan Module presence detect<prd><pres_detect>
6866600D04-C December 2006 2-61

status Chapter 2: Test Application Commands
Fan Module functional state<prd><func_state>

Rubidium clock active<prd><active_state>
Rubidium clock state<prd><lock_state>
CP2 Input Clock presence detect<prd><pres_detect>
OCXO Oven ready state<prd><ready_state>
Backplane ID<prd><bck_id>
Slot ID<prd><slot_id>
SC Online state<prd><online_state>
Fan power switch functional state<prd><pres_detect>
Power Supply:
Power Supply <prd><pres_detect>
Xhub:
Power Supply presence detect<prd><pres_detect>
Power Supply functional state<prd><func_state>
Fan Module presence detect<prd><pres_detect>
Fan Module functional state<prd><func_state>
Switch:
Ethernet port (0)<prd><link_status>, <line mode>
Ethernet port (1)<prd><link_status>, <line mode>
...
Ethernet port (n)<prd><link_status>, <line mode>
Note: Ethernet ports 0..7, 9 are on the front switch:
ports 0-7: 10/100 Mbits/s
port 9: 10/100/1000 Mbits/s
Ethernet ports 11...18, 20 are on the back switch.
ports 11-18: 10/100 Mbits/s
port 20: 100/1000 Mbits/s
Only ports with Ephy will have their status reports, so ports from 0 to 7, port9,
ports from 11 to 18 and port 20 will be reported.
<active_state> A character string representing the active state of the device. Valid settings: active not active.
<app size> An integer value representing the number of bytes available to the Application in a memory.
<bck_id> An integer value representing the SC backplane ID.
<func_state> A character string representing the functional state of the device.
Valid settings: functional, failure.
<int_buf_size> An integer value representing the internal buffer size of the mass storage device.
<line_mode> A character string representing the line mode of an Ethernet port. Valid settings:
• unknown
• 10 base half duplex
• 10 base full duplex
2-62 6866600D04-C December 2006

MTS Man Machine Interface Commands time_reference
<link_status> A character string representing the link status of an ethernet port. Valid settings: up, down.
<lock_state> A character string representing the lock state of the device. Valid settings: locked unlocked.
<model> A character string representing the manucfacturer model of the mass storage device.
<num_sectors> An integer value representing the number of sectors in the mass storage device.
<online_state> An character string representing the SC online_state. Valid settings: online offline.
<physical address> A hexadecimal value representing the physical start address corresponding
to the Platform zero offset in the memory bank.
<pres_detect> A character string representing the detected presence of the device.
Valid settings: present, not present
<ready_state> A character string representing the ready state of the device. Valid settings: ready, not ready.
<sector_address> A hexadecimal value representing the physical address of the memory sector.
<sector_offset> A hexadecimal value representing the offset of the memory sector.
<sector_size> An integer value representing the number of bytes in a memory sector.
<serial_num> An character string representing the the serial number of the compact flash device.
<size> An integer value representing the number of bytes starting from the Plat-
form zero offset in a memory bank.
<slot_id> An integer value representing the SC slot ID.
Example:
factory> status -oplatform
Redundant SC presence detect=not present
Power Supply presence detect=not present
Power Supply functional state=functional
Fan Module presence detect=not present
Fan Module functional state=functional
Rubidium clock active=not active
Rubidium clock state=unknown
CP2 Input Clock presence detect=not present
Fan power switch functional state=functional
OCXO Oven ready state=ready
Backplane ID=0
Slot ID=0
SC Online state=online
factory>
time_reference
Syntax:
Read operations:
tr | time_reference -o<object>
6866600D04-C December 2006 2-63

temp_sensor Chapter 2: Test Application Commands
Write operations:
tr | time_reference -o<object> -v<value>
Description:
Selects the time reference source or gets the current selection.
Options:
<object> A character string representing the object to access for the time reference. Valid settings: platform.
<value> A character string representing the time reference. Valid settings:
• ext_1pps
• gps
• redundant_sc
• cp2_link
Output:
TimeRef<prd><value>
Example:
> tr -oplatform
TimeRef=gps
>
> time_reference -oplatform -vext_1pps
>
temp_sensor
Syntax:
Read operations:
ts | temp_sensor -o<object>
Description:
Displays the Site Controller’s board temperature.
Options:
<object> A character string representing the temperature sensor. Valid settings: platform.
Output:
Temp<prd><value><C>
Example:
> ts -oplatform
> Temp=-15C
2-64 6866600D04-C December 2006

MTS Man Machine Interface Commands watchdog_settings
watchdog_settings
Syntax:
Read operations:
ws -o<object>
Write operations:
ws -o<object> -s<status> -v<value>
Description:
Provides access to the Site Controller’s card watchdog timer. Permits to enable the
watchdog, set and read its time-out period.
Options:
<object> A character string representing the object for the watchdog timer. Valid settings: watchdog.
<status> A character string representing the status. Valid settings: enable, disable
<value> A positive integer representing the timeout value. Valid settings: <Device specific value>
Output:
Watchdog<prd><status> timeout<prd><timeout value> msec
The value returned will be the actual watchdog value that the Platform was able to
achieve. The value may be different from the value used in the set command due
to hardware limitations. For example: for the specified value of 120000 in the set
operation, a value of 161464 is returned by the Platform.
Example:
> ws -owatchdog
Watchdog=enable=timeout=161464 msec
>
> ws -owatchdog -senable -v120000
>
6866600D04-C December 2006 2-65

watchdog_settings Chapter 2: Test Application Commands
2-66 6866600D04-C December 2006

Chapter
3
BOOT1 Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BOOT1: used for loading the actual SC Application or loading the Test Application.
BOOT1 Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
ATTRIB
Syntax:
Syntax1: attrib [-bare] [-n | -a | -aClear] [<file1> [<file2> ...]]
Syntax2: attrib [-bare] [-v <verStr>] [-d <dateStr>] [<comp1> [<comp2> ...]]
Syntax3: attrib [-bare] [-update] [-dump] [<comp1> [<comp2> ...]]
Description:
The attrib command displays or edits information associated with hardware and file
components within the Site Controller.
Options:
Table 3-1 Common Options:
Option Description
-bare Suppress display of heading, paging & results.
-n Sets file(s) to be used as next after reset. Valid file must exist
-a Set file archive flag.
-aClear Clear file archive flag.
-v <verStr> Set version label of component (no spaces!).
-d <dd/mm/yyyy> <hh:mm:ss> Set component upgraded date & time.
6866600D04-C December 2006 3-1

boot Chapter 3: BOOT1 Commands
Table 3-1 Common Options: (Continued)

Option Description
-update Update component data automatically.
-dump Display as commands to paste/re-enter.
-all Display all versions including log files, etc.
<comp> Specifies the component to set/display.
<file> Filename of file to set. None sets all files.
Example:
attrib Displays all attributes
attrib tsc.code.1 brc.code.1 Displays the attributes of brc.code.1 and tsc.code.1
attrib -v R03.01.00 tsc.code.1 Sets the version of tsc.code.
boot
Syntax:
boot [<flashimage>|<filepath>]
Description:
boot according to argument or configuration
build_info
Syntax:
build_info
Description:
print build info of the image
bview
Syntax:
bview
Description:
view the boot configuration
3-2 6866600D04-C December 2006

MTS Man Machine Interface Commands cd
cd
Syntax:
cd [<dirname>]
Description:
change the working directory
chmod
Syntax:
chmod <mode> <path> ...
Description:
change access mode of files
cp
Syntax:
cp <source> ... <destination>
Description:
The cp command copies one or more files to a destination directory or copies one file to a new name.
ethstat
Syntax:
ethstat <interface name>
Description:
Display Ethernet statistics
exit
Syntax:
exit
Description:
6866600D04-C December 2006 3-3

fdir Chapter 3: BOOT1 Commands
exit shell session
fdir
Syntax:
fdir
Description:
list flash images
finstall
Syntax:
finstall [-b] <name> <filepath> [<base>]
Description:
install image in flash (at address)
format
Syntax:
format [-f] <volume> [<params>]
Description:
format a volume
fusage
Syntax:
fusage
Description:
display flash usage
go
Syntax:
3-4 6866600D04-C December 2006

MTS Man Machine Interface Commands help
go [<addr>]
Description:
go to specified address or last load entrypoint
help
Syntax:
help [<command> ...]
Description:
Without parameter, prints syntax and description of all available commands.
Provide a command as a parameter to get the description of a given command.
ifattach
Syntax:
ifattach -h
Description:
attach or detach an interface
ifconfig
Syntax:
ifconfig -a | interface [options
Description:
configure network interface
ifstat
Syntax:
ifstat <interface name>
Description:
Display interface statistics
6866600D04-C December 2006 3-5

inetcfg Chapter 3: BOOT1 Commands
inetcfg
Syntax:
inetcfg -h
Description:
Get/set INET configuration
ipaddr
Syntax:
ipaddr [<new ipaddr> [<new netmask>]]
Description:
Display or change IP address and netmask
load
Syntax:
load <filepath> [<base>].
Description:
The load command loads the image at a given location.
login
Syntax:
login [-d <device>] [<username>]
Description:
Log the user in.
ls
Syntax:
ls [-acil] [<dirname> ...]
Description:
3-6 6866600D04-C December 2006

MTS Man Machine Interface Commands mkdir
The ls command lists the specified files or the files and subdirectories in that direc-
tory where the command is executed.
mkdir
Syntax:
mkdir <directory> ...
Description:
create directories
mload
Syntax:
mload <filepath> <base>
Description:
load memory from (raw) file
mount
Syntax:
mount <volume> <fmtmgr> <device> [<params>]
Description:
mount a volume
mv
Syntax:
mv <source> ... <destination>
Description:
rename/move files
6866600D04-C December 2006 3-7

netstat Chapter 3: BOOT1 Commands
netstat
Syntax:
netstat
Description:
Display network statistics
ping
Syntax:
ping [options] host
Description:
send ICMP ECHO_REQUEST packets to host.
This command might not be available due to security reasons.
pwd
Syntax:
pwd
Description:
print the working directory
reset
Syntax:
reset
Description:
Reset the system.
rm
Syntax:
3-8 6866600D04-C December 2006

MTS Man Machine Interface Commands rmdir
rm [-f] <filename> ...

Description:
remove files
rmdir
Syntax:
rmdir [-f] <directory> ...
Description:
remove (empty) directories
route
Syntax:
route <add | delete | print>
Description:
[dest mask gateway] add/delete/list routes
shell
Syntax:
shell [<cmd> ...] / [-f <file>]
Description:
invoke shell [to execute command]
shutdown
Syntax:
shutdown [-r]
Description:
shutdown system [ and reset]
6866600D04-C December 2006 3-9

sleep Chapter 3: BOOT1 Commands
sleep
Syntax:
sleep <seconds>
Description:
sleep for a number of secondse
stat
Syntax:
stat <pathname> ...
Description:
report information about file/directory
sync
Syntax:
sync <volume>
Description:
synchronize volume with disk
testapp
Syntax:
testapp
Description:
executes test application
tftp
Syntax:
tftp <host_ip> {get|put} [-d <host_dir>] {-a[lltsclogs] | [file1 ...]}
Description:
3-10 6866600D04-C December 2006

MTS Man Machine Interface Commands traceroute
The tftp command allows files to be uploaded to or downloaded from a remote computer. The remote
host whose IP address is specified by host_ip must be running TFTP server software.
Options:
-d Specifies the source or destination directory on the host machine. The directory
name must end with a “/” or “\” character.
-a For a put operation, indicates that all TSC log files should be sent.
traceroute
Syntax:
traceroute [options] destination
Description:
print hop-by-hop path to destination.
ttcp
Syntax:
ttcp -h
Description:
Performance test tool
unmount
Syntax:
unmount [-f] <volume>
Description:
unmount a volume
vols
Syntax:
6866600D04-C December 2006 3-11

vols Chapter 3: BOOT1 Commands
vols [<volume> ...]

Description:
report volume statistics
3-12 6866600D04-C December 2006

Chapter
4
Site Controller Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Site Controller Application Commands

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
ARP
Syntax:
arp
Description:
The arp command displays the current ARP (Address Resolution Protocol) lookup table maintained
internally by the IP protocol stack in the Site Controller. This table shows the Site Controller's
mapping of MAC addresses to IP addresses of the devices connected to it.
Options:
Example:
SC>
ATTRIB
Syntax:
Syntax1: attrib [-bare] [-n | -a | -aClear] [<file1> [<file2> ...]]
Syntax2: attrib [-bare] [-v <verStr>] [-d <dateStr>] [<comp1> [<comp2> ...]]
Syntax3: attrib [-bare] [-update] [-dump] [<comp1> [<comp2> ...]]
Description:
6866600D04-C December 2006 4-1

ATTRIB Chapter 4: Site Controller Commands
The attrib command displays or edits information associated with hardware and file
components within the Site Controller.
Options:
Table 4-1 Attribute Bit Values:
Bit Summary Description

r Readable File exists
w Writable File does not exist
a Archive File has been modified
n Next File will be used next after reset
c Current File is currently being used
f Fallback File will be used next if site fails
Table 4-2 Common Options:
Option Description
-c Sets file(s) to be used as current now
-n Sets file(s) to be used as next after reset. Valid file must exist
-cn Sets file(s) to be used as current and next. Valid file must exist
-f Sets file(s) to be used as fallback if next fails

-fClear Clears the fallback bit (if set) for the specified file(s)
-nClear Clears the next bit (if set) for the specified file(s)
-passed Sets file(s) as passed, i.e. working. If any fallback has been set, then this will clear it
-failed Sets file(s) as failed, i.e. faulty. If any fallback has been set, then this will select it
to be used next and clear the fallback
file Specifies file to set. If no file is given, then used all current files
-v Sets component(s) version string
-d Sets component(s) upgraded date
Table 4-3 Other Options:
Option Description
-install Sets a file as valid
-remove Sets a file as invalid. Clears the date and version string
-update Update date and readable flag data from hardware and filing system
4-2 6866600D04-C December 2006

MTS Man Machine Interface Commands BRLOCK
Table 4-4 Options available at any time and with any syntax:
Option Description
-all Display current versions as well
-bare Does not page information or display the header text
-verboseOff Turn display of SWDL errors/information off
-verboseErrors Turn display of SWDL errors only on
-verboseAll Turn display of SWDL errors and information on
Table 4-5 General Parameters:
Option Description
verStr Version label for the component
dateStr The upgraded date string (hh:mm:ss) for the component
component Specifies the component to set/display
Example:
attrib Displays all attributes
attrib tsc.code.1 brc.code.1 Displays the attributes of brc.code.1 and tsc.code.1
attrib -c tsc.code.1 brc.code.1 Sets the brc.code.1 and tsc.code.1 to be used now
attrib -v R03.01.00 tsc.code.1 Sets the version of tsc.code.
BRLOCK
Syntax:
brlock
brlock -status br_number
brlock -clear br_number
brlock -clearall
Description:
Following a VSWR alarm all BRs are locked. The brlock command allows the service personnel to ascertain
the lock status of BRs and unlock individual BRs. brlock -clear br_number clears the lock from an individual br;
brlock -clearall clears the lock from all brs; brlock -status br_number returns the lock status for an individual br.
6866600D04-C December 2006 4-3

BTS_TYPE Chapter 4: Site Controller Commands
BTS_TYPE
Syntax:
bts_type
Description:
The bts_type command displays the kind of Base Station. This information is also
available via status sc command.
Example:
SC: bts_type -?
bts_type [-mts4 | -mts2 | -?] Display or set the BTS type
-mts4 = Set BTS type to MTS4 (requires reset to take effect!)
-mts2 = Set BTS type to MTS2 (requires reset to take effect!)
-? = Display help for this command
SC: bts_type
BTS type: MTS2
CLS
Syntax:
cls
Description:
The cls command attempts to clear the screen by sending the ANSI codes ^[[0;0H^[[J to the standard output..
DISPLAY CONFIG
Syntax:
display config [-quick | -ip]
Description:
The display config command display the current configuration data of the Site Controller. By default, this
command displays all of the configurable parameters set in the configuration data file downloaded from the
BTS Service Software. Options are provided to allow useful subsets of this information to be displayed.
Options:
-ip Display all IP addresses and port settings.
-quick Display site and zone ID, adjacencies, LST enabled flag, GPS status, and all address ranges.
4-4 6866600D04-C December 2006

MTS Man Machine Interface Commands EAS_OUT
EAS_OUT
Syntax:
eas_out
Description:
Command for controlling the user control outputs. The user control outputs are two
user definable output signals on the MTS.
.EGOP
Syntax:
.egop [-e <min_gc_id> <max_gc_id> | -d | -?]
Description:
Modifies/displays the values for the 'Extended GC on PDCH' subfeature'
The “-?” option displays the help for this command
No arguments displays the current value stored in the MIB
The “-d” option disables the feature
The “-e <min_gc_id> <max_gc_id>“ option enables the feature using the range [min_gc_id, max_gc_id] (inc)
In order for any change to take place, the TSC must be restarted.
If a group call is set up to an ID within a configured range of group IDs, the RF site will
set up the group call on all PDCHs active at the site.
Group ID range are stored in the Site Controller configuration, along with an enable/disable switch. Three new
configuration parameters are added: group ID range lower bound <min_gc_id>, group ID range upper bound
<max_gc_id , enable/disable switch. The new functionality (group call to an ID within a configured range of
group IDs set up on all PDCHs) only works if the switch is set to 'enabled'. The switch is default set to 'disabled'.
In this release, it will only be possible to modify the new configuration parameters via the Site Controller MMI.
The new configuration parameters will be active-on-reset, meaning that after having modified them
via the Site Controller MMI, it will be necessary to reset the TSC in order for the modifications to
take effect. System performance will be affected when this feature is used.
EXIT
Syntax:
exit
Description:
This command is used to log out the user and terminate the MMI. If the user was logged
in via telnet, the connection is dropped.
6866600D04-C December 2006 4-5

HELP Chapter 4: Site Controller Commands
HELP
Syntax:
help
Description:
The help command displays a list of all available commands and a short synopsis of their
use, comprising an option list and a brief description.
All commands support a ‘-?’ option which displays a description of that command and
its usage, including a brief description of each parameter.
KILL
Syntax:
kill <Console ID>
Description:
Disconnects the specified console, logging the user out first. The console ID can be found
by using the who command, and must not specify the current console (the logout or exit
commands can be used to terminate the current session).
KVL
Syntax:
kvl
Description:
The kvl command entered via the front serial port of the Site Controller configures the front port for
communication with the Key Variable Loader device. If no valid KVL communication is received within 60
seconds, then the port returns to normal operation. Since the front serial port is normally used by the MMI, no
MMI commands may be entered via this port until the communication with the Key Variable Loader device has
been terminated. The success of this operation is indicated at the Key Variable Loader device only. Following
termination of communication by the KVL, the front serial port automatically returns to normal MMI mode.
LOCK
Syntax:
lock
4-6 6866600D04-C December 2006

MTS Man Machine Interface Commands LOG
Description:
The lock command places the BTS into the locked state. While in the locked state, the BRs are prevented
from keying. The MMI waits while the Site Controller performs the operation before returning to the user.
The call processing operation will be shut down gracefully when a lock command is issued.
LOG
Syntax:
log [-inform | -minor | -major | -fatal] <string>
Description:
The log command saves the specified string into one of the TSC’s log files. The string may be up to
approximately 80 characters in length, and will be converted to lower case before being saved. If
no option is specified, the minor (Fault/Event) log will be used by default.
The # character is the MMI comment character. If this character is used in the
string, then any text following it will be discarded.
Options:
-inform Saves string to the information (Volatile) log
-minor Saves string to the minor (Fault/Event) log
-major Saves string to the major (Major Event) log
-fatal Saves string to the fatal (Major Event) log
LOGOUT
Syntax:
logout
Description:
The logout command logs out a user, it is the same command as "EXIT".
LS
Syntax:
ls [-acil] [<dirname> ...]
Description:
6866600D04-C December 2006 4-7

MAX_WSVR Chapter 4: Site Controller Commands
The ls command lists the specified files or the files and subdirectories in that direc-
tory where the command is executed.
MAX_WSVR
Syntax:
max_wsvr
Description:
Command for configuring the max VSWR acceptable on a DPM.
MIRROR
Syntax:
mirror [portID <in|out|both|port_true|off> | -?]
Description:
Modifies/displays ethernet switch mirroring state..
Options:
\n (No arguments) = Display mirroring state for all ports
\n portID = Display mirroring state of port no. portID (portID=0,...,10)
\n portID in = Enable mirroring all received frames on port no. portID
\n portID out = Enable mirroring all transmitted frames on port no. portID
\n portID both = Enable mirroring all frames on port no. portID
\n portID port_true = Set port no. portID as a mirror capture port
\n portID off = Disable mirroring on port no. portID
\n -? = Display help for this command
Port IDs:
Table 4-6 Roles of Switch Ports
Switch Port Interface

Port 0(10/100) CPU on Redundant SC
Port 1(10/100) Not used
Port 2(10/100) XHUB
Port 3(10/100) Service Port
Port 4(10/100) BR4
4-8 6866600D04-C December 2006

MTS Man Machine Interface Commands NETSTAT
Table 4-6 Roles of Switch Ports (Continued)

Switch Port Interface
Port 5(10/100) BR3
Port 6(10/100) BR2
Port 7(10/100) BR1
Port 8 (MII/IMP) MPC8560 FCC1
Gigabit Port 0 Not used
Gigabit Port 1 (GMII) MPC8560 TSEC1
NETSTAT
Syntax:
netstat [-s]
Description:
The netstat command displays the current active TCP/IP connections to the Site Con-
troller and the current active UDP ports.
Options:
-s Display the current statistics associated with the IP, TCP, UDP and ICMP protocols.
PASSWORD
Syntax:
password
Description:
Upon entry of the password command, the user will be prompted to enter the existing password. A correct
entry will result in a request for the new password, and the presentation of the restriction to which it must
conform. If the entry is valid, the user will be prompted to re-enter the new password.
A message will then be displayed informing the user whether a change has been made. The command
will change the appropriate password according to the newly entered password.
PING
Syntax:
ping [-n] [-l] [ip_address]
Description:
6866600D04-C December 2006 4-9

PORT Chapter 4: Site Controller Commands
The ping command enables the user to send an ICMP ping message to be sent to the
specified IP address over a connected IP network. This command is not available on System
Releases that do not support the redundant TSC.
If the IP address is not specified, the help text will be displayed. If -n is not specified it
will use the default, as specified in the options text for -n.

Options:
-n number of packet to be sent
-l ping data size
PORT
Syntax:
port
Description:
Command for site controller switch port enabling and disabling..
RESET
Syntax:
reset
Description:
The reset command causes the Site Controller to perform a hardware reset, which is roughly
equivalent to pressing the front panel RESET button.
RGPS_DELAY
Syntax:
rgps_delay [-set <delay> | -invalidate]
Description:
The rgps_delay command sets the transmission time delay for the cable connecting the RGPS (Remote GPS)
receiver to the Site Controller. The time delay is only to be set when an independently powered RGPS receiver is
being used. By setting a time delay the Site Controller assumes that a independently powered RGPS is present.
4-10 6866600D04-C December 2006

MTS Man Machine Interface Commands SITE_LOCATION
Options:
-set Set the transmission time delay to the entered value. Must be entered in nanoseconds.
-invalidate This command invalidates the transmission time delay value.
This command is not available on System Releases that do not support the
use of a remote GPS antenna.
SITE_LOCATION
Syntax:
site_location
site_location {-reset | -valid}
site_location -co_ordinates [N | S] deg: min: sec [W | E] deg: min: sec H metres
Description:
This command allows resetting, setting and checking of the site location. The system needs to
determine its location in order to synchronize its timing with other sites.
When a remote GPS is used, the position information is relevant to the re-
mote GPS and not to the BTS.
Options:
-reset Clears any site location information from permanent memory. The Site Controller
will perform GPS site survey when it is next restarted.
-valid Determine if a valid site location has been stored in permanent memory.
-co_ordinates Sets the lattitude, longitude and height co-ordinates for the site location.
If the TSC is moved, the site_location -reset command must be entered immediately after
first power up to allow the system to calculate its new location.
Example:
site_location Determine location of site
site_location -reset Clear any stored site location
site_location -valid Determine if site location valid
site_location N54:12:45.789 W1:6:12.345 H174 Set the site location
6866600D04-C December 2006 4-11

STATUS BR Chapter 4: Site Controller Commands
The system must be restarted for these commands to have any effect.
STATUS BR
Syntax:
status br [cabinet | position]
Description:
The status br command returns information relating to a single BR or all BRs. If entered without cabinet
and position parameters, the command causes the information for all BRs to be displayed in a table.
If no response is received from a BR, then the entries in the table are made with a series of dashes.
Options:
cabinet The cabinet in which the BR is physically located.
position The position of the specified BR within the cabinet.
The cabinet and position parameters must be entered directly next to each
other without any separating spaces, so a BR in cabinet 1 position 1 would be
checked with the command “status br 11”.
STATUS BSL
Syntax:
status bsl [-r]
Description:
The status bsl command will display the current status of the base site link, includ-
ing the results of any tests performed.
Options:
-r Resets the statistics for the base site link.
STATUS BSLQ
Syntax:
status bslq [-r]
4-12 6866600D04-C December 2006

MTS Man Machine Interface Commands STATUS BTS
Description:
The status bslq command displays the statistics for the transmission queues associated with the X.21 interface.
Options:
-r Resets the statistics for the X.21 transmission queues.
STATUS BTS
Syntax:
status bts [-l]
Description:
The status bts command displays state information for various BTS subsystems.
Options:
-l Long output format. In addition to the state, the associated probable cause and time of
last state change trap are displayed on each subsystem.
STATUS CRTP
Syntax:
status crtp [-r]
Description:
The status crtp command displays the current CRTP (Compressed Real Time Protocol) statistics.
Options:
-r Resets these CRTP statistics
STATUS EAS
Syntax:
status eas [ -p9 | -all | -m ]
Description:
The status eas command displays the status of all the alarm contacts of the EAS.
Status results are displayed in a table.
The table contains input/output number, a textual description, and a status (o.k./alarm for inputs and
active/inactive for outputs). The inputs and outputs are displayed in separate sections in the table.
Options:
6866600D04-C December 2006 4-13

STATUS FR Chapter 4: Site Controller Commands
-p9 This option gets the status of the plug number entered (-p9 parameter is required in MTS,
but it matches rear plug 9 in the EBTS EAS hardware.
-all This option shows all inputs (including disabled inputs).
-m This option starts continuous status monitoring.
STATUS FR
Syntax:
status fr [-r]
Description:
The status fr command displays the current statistics associated with the frame relay protocol layer.
Options:
-r Resets these frame relay statistics
STATUS FRF
Syntax:
status frf [-r]
Description:
The status frf command displays the current statistics associated with frame re-
lay fragmentations and reassembly.
Options:
-r Resets the frame relay fragmentation statistics
STATUS KEYS
Syntax:
status keys
Description:
The status keys command displays the security key status information.
STATUS LMI
Syntax:
4-14 6866600D04-C December 2006

MTS Man Machine Interface Commands STATUS PEER
status lmi [-r]

Description:
The status lmi command displays the current LMI (Local Management Interface) statistics. The LMI protocol
monitors the PVCs (Permanent Virtual Circuit) that link the Site Controller to the Core Routers.
Options:
-r Resets these LMI statistics
STATUS PEER
Syntax:
status peer
Description:
The status peer command displays information on the other site controller's current functional status
and its identity position. A valid id will only be displayed if the peer TSC is responding and correctly
configured. The command is only applicable for an BTS with a dual site controller configuration. This
command is not available on System Releases that do not support the redundant TSC.
STATUS RIGMP
Syntax:
status rigmp [-r]
Description:
The status rigmp command displays the current statistics associated with robust IGMP
(Internet Group Membership Protocol).
Options:
-r resets these robust IGMP statistics
STATUS SC
Syntax:
status sc [-all]
Description:
The status sc command displays preliminary diagnostics information on the TSC. This includes the
health of the TSC, the trunking state, the internal state and the site link status.
Options:
6866600D04-C December 2006 4-15

STATUS SEC Chapter 4: Site Controller Commands
-all Displays the internal state of the cell and BRs.
STATUS SEC
Syntax:
status sec
Description:
The status sec command displays security parameters used by the Site Controller.
STATUS SRI
Syntax:
status sri [-gps | -sr | -t | -stat_show | -stat_reset | -p]
Description:
The status sri command provides general information on the health of the Site Reference system. This
includes the Site Reference and GPS operational status, UTC, GPS and local times and 1PPS signal status.
Options:
-gps Displays detailed status of the GPS receiver including a satellite tracking report.
-sr Provides details of the site reference internal state status sri [-all | -t | -p | -stat_show | -stat_reset]
-t Displays GPS receiver identifier.
-p Displays continuously updated satellite tracking information.
-stat_show Display GPS statistics.
-stat_reset Reset GPS statistics.
When a remote GPS is used, the position information is relevant to the re-
mote GPS and not to the BTS
TFTP
Syntax:
tftp <host_ip> {get|put} [-d <host_dir>] {-a[lltsclogs] | [file1 ...]}
Description:
4-16 6866600D04-C December 2006

MTS Man Machine Interface Commands TIMEZONE
The tftp command allows files to be uploaded to or downloaded from a remote computer. The remote
host whose IP address is specified by host_ip must be running TFTP server software.
Options:
-d Specifies the source or destination directory on the host machine. The directory
name must end with a “/” or “\” character.
-a For a put operation, indicates that all TSC log files should be sent.
TIMEZONE
Syntax:
timezone [ [+|-]{0..14}:{00|30} ]
Description:
Command for configuring the MTS timezone..
Options:
[ [+|-]{0..14}:{00|30} ] — Set the Site Controller time zone relative to GMT.
Example:
SC> timezone +1:00
Sets the time zone to GMT +1.
UNLOCK
Syntax:
unlock
Description:
The unlock command places the Site Controller into the unlocked state from the current state.
VER
Syntax:
ver [-h]
Description:
The ver command displays version information for Site Controller software and, optionally, the Site Controller
hardware. If entered without options, the firmware and application version numbers are displayed.
Options:
6866600D04-C December 2006 4-17

WHO Chapter 4: Site Controller Commands
-h Displays both hardware and software information.
WHO
Syntax:
who
Description:
This command displays a list of users logged in or connected to the TSC. The information
displayed includes the user name, port, and access mode. If the user name field is blank, then
a telnet connection exists but no user is logged in over it.
If a user is logged into a Base Radio, then the user name is displayed as “Unknown”.
atc # get device_id

Syntax:
atc # get device_id
Description:
The atc # get device_id command returns the device id. The device id contains three numbers:
vendor id, hw rev number and software revision number.
Example:
SC>atc 1 get device_id
Device ID 000.080.123
atc # get kit_number

Syntax:
atc # get kit_number
Description:
The atc # get kit_number returns the kit number
SC> atc 1 get kit_number
Kit Number 0123456N78
4-18 6866600D04-C December 2006

MTS Man Machine Interface Commands atc # get vendor_serial
atc # get vendor_serial

Syntax:
atc # get vendor_serial
Description:
The atc # get vendor_serial returns the Vendor serial number
Example:
SC>atc 1 get vendor_serial
Vendor serial number 12D145521145A421105
atc # get track_id

Syntax:
atc # get track_id
Description:
The atc # get track_id command return the Motorola Track ID (which is used to identify the unit on the bus).
Example:
SC>atc 1 get track_id
Track ID JTH0512345
atc # get status

Syntax:
atc # get status
Description:
The atc # get status command return the status register
Example:
SC>atc 1 get status
Status 0x00 - All OK
atc # get alarm

Syntax:
atc # get alarm
Description:
6866600D04-C December 2006 4-19

atc # set cav_tune_timo Chapter 4: Site Controller Commands
The atc # get alarm command return the alarm register

Example:
SC>atc 1 get alarm
Alarm 0x00 - No Alarm
atc # set cav_tune_timo

Syntax:
atc # set cav_tune_timo <timeout>
Description:
The atc # set cav_tune_timo command sets the timeout period between finetuning of the cavities. The timeout
is given in minutes (range 0 to 2880) or “$FFFF” to set an infinite timeout. The ATCC will respond with
one of the following: parking time to set OK, invalid time period, invalid cavity number.
Example:
SC>atc 1 set cav_tune_timo inf
Cavity all
Fine tuning Timeout infinite
atc # get cav_tune_timo

Syntax:
atc # get cav_tune_timo
Description:
atc 1 get cav_tune_timo
Example:
SC>Cavity all
Cavity all
Tune Timeout 62 mins
atc # cav_park
Syntax:
atc # cav_park <cav>
Description:
The atc # cav_park command instructs the Autotuner to park the specified cavity. The ATCC will respond with
one of the following cavity status indicators: cavity parked, park conflict (signal present), invalid cavity number.
4-20 6866600D04-C December 2006

MTS Man Machine Interface Commands atc # set cav_vswr_alm
Example:
SC>atc 1 cav_park 1
Command executed OK
atc # set cav_vswr_alm

Syntax:
atc # set cav_vswr_alm <cav> <threshold>
Description:
The atc # set cav_vswr_alm command establishes a threshold for initiating a VSWR alarm on the specified
cavity. The threshold must be in the range 1.00 to 10.00. The default value is 10. The ATCC will respond
with one of the following cavity status indicators: set, invalid VSWR, invalid cavity.
Example:
SC>atc 1 set cav_vswr_alm 1 3.3
Cavity 1
VSWR Threshold 03.30
atc # get cav_vswr_alm

Syntax:
atc # get cav_vswr_alm <cav>
Description:
The atc # get cav_vswr_alm command displays the VSWR alarm threshold for the given cavity.
Example:
SC>atc 1 get cav_vswr_alm 2
Cavity 2
Cavity Status 0e - Tuned, Enabled, Present, No RF,
Mismatched, No Alarm
atc # get cav_status

Syntax:
atc # get cav_status <cav>
Description:
The atc # get cav_status command displays the full status for the given cavity. The Frequency, Input Power,
Reflected Power, VSWR, Alarm Status Flags and Cavity Status Flags are displayed. The ATCC will
respond with one of the additional following information: park position offset, parking timeout, cavity
status flags (parked, faulted, invalid cavity number, tuned, tuning, freq. miss match).
6866600D04-C December 2006 4-21

dpm # get device_id Chapter 4: Site Controller Commands
Example:
SC>atc 1 get cav_status 1
Cavity 1
Cavity Freq. 380000000 Hz
Input Power 37.68 dBm
Reflected Power 33.12 dBm
VSWR Ratio 2.15
Alarm Status 00 -
Cavity Status 0e - Tuned, Enabled, Present, No RF,
Mismatched, No Alarm
dpm # get device_id

Syntax:
dpm # get device_id
Description:
The dpm # get device_id command returns the device id. The device id contains three numbers:
Example:
SC>dpm 1 get device_id
Device ID 000.080.123
dpm # get kit_number

Syntax:
dpm # get kit_number
Description:
The dpm # get kit_number returns the kit number
Example:
SC>dpm 1 get kit_number
dpm # get vendor_serial

Syntax:
dpm # get vendor_serial
Description:
The dpm # get vendor_serial returns the Vendor serial number
4-22 6866600D04-C December 2006

MTS Man Machine Interface Commands dpm # get track_id
Example:
SC>dpm 1 get vendor_serial
dpm # get track_id

Syntax:
dpm # get track_id
Description:
The dpm # get track_id command return the Motorola Track ID (which is used to identify the unit on the bus).
Example:
SC>dpm 1 get track_id
Track ID JTH0512345
dpm # get status

Syntax:
dpm # get status
Description:
The dpm # get status command return the status register
Example:
SC>dpm 1 get status
Status 0x00 - All OK
dpm # get alarm

Syntax:
dpm # get alarm
Description:
The dpm # get alarm command return the alarm register
Example:
SC>dpm 1 get alarm
Alarm 0x00 - No Alarm
6866600D04-C December 2006 4-23

dpm # get fwd power Chapter 4: Site Controller Commands
dpm # get fwd power

Syntax:
dpm # get fwd power
Description:
The dpm # get fwd power command returns the current value of forward power. The command
displays the input power for the specified cavity DPM in Watt. The DPM will respond with
one of the following status indicators: DPM OK of DPM failure.
This command should be used only when the transmitter is keyed to obtain accurate results.
Example:
SC>dpm 1 get fwd_power
Input Power 37.68 Watt
DPM Status 20 – DPM OK
dpm # get rev_power

Syntax:
dpm # get rev_power
Description:
The dpm # get rev_power command displays the reverse power for the specified DPM in Watt. The
DPM will respond with one of the following status indicators: DPM OK of DPM failure.
Example:
SC>dpm 1 get rev_power
reverse Power 7.68 Watt
DPM Status 20 – DPM OK
dpm # get vswr

Syntax:
dpm # get vswr
Description:
The dpm # get vswr command displays the VSWR ratio for the specified DPM. The DPM will
respond with one of the following status indicators: DPM OK of DPM failure.
Example:
SC>DPM 1 get vswr
VSWR Ratio 2.15
4-24 6866600D04-C December 2006

MTS Man Machine Interface Commands dpm # set vswr_alm
DPM Status 0e DPM OK
dpm # set vswr_alm

Syntax:
dpm # set vswr_alm <threshold>
Description:
The dpm # set vswr_alm command establishes a threshold for initiating a VSWR alarm. The
threshold must be in the range 1.00 to 10.00. The default value is 10. The DPM will respond
with one of the following status indicators: set, invalid VSWR.
Example:
SC>dpm 1 set vswr_alm 3.3
dpm # get vswr_alm

Syntax:
dpm # get vswr_alm
Description:
The dpm # get vswr_alm command displays the VSWR alarm threshold.
Example:
SC>dpm 1 get vswr_alm
VSWR Threshold 4.40
DPM Status 0x00 - All OK
psu # get device_id

Syntax:
psu # get device_id
Description:
The psu # get device_id command returns the device id. The device id contains three numbers:
Example:
SC>psu 1 get device_id
Device ID 000.080.123
6866600D04-C December 2006 4-25

psu # get kit_number Chapter 4: Site Controller Commands
psu # get kit_number

Syntax:
psu # get kit_number
Description:
The psu # get kit_number returns the kit number
Example:
SC>psu 1 get kit_number
psu # get vendor_serial

Syntax:
psu # get vendor_serial
Description:
The psu # get vendor_serial returns the Vendor serial number
Example:
SC>psu 1 get vendor_serial
psu # get track_id

Syntax:
psu # get track_id
Description:
The psu # get track_id command return the Motorola Track ID (which is used to identify the unit on the bus).
Example:
SC>psu 1 get track_id
Track ID JTH0512345
psu # get status

Syntax:
psu # get status
Description:
4-26 6866600D04-C December 2006

MTS Man Machine Interface Commands psu # get alarm
psu # get status command return the status register

Example:
SC>psu 1 get status
Status 0xCF - DC out: present, AC in: present, DC in: not
present, AC operation, Alarm
psu # get alarm

Syntax:
psu # get alarm
Description:
The psu # get alarm command returns the alarm register
Example:
SC>psu 1 get alarm
Alarm 0x20 - DC in fail
psu # get battery_voltage

Syntax:
psu # get battery_voltage
Description:
The psu # get battery_voltage returns the battery voltage in Volts.
Example:
SC>psu 1 get battery_voltage
Battery Voltage 48.6V
Status 0E – All ok
psu # get battery_current

Syntax:
psu # get battery_current
Description:
The psu # get battery_current returns the battery current in Ampers.
Example:
SC>psu 1 get battery_current
Battery Current 5.2A
6866600D04-C December 2006 4-27

psu # get battery_temperature Chapter 4: Site Controller Commands
psu # get battery_temperature

Syntax:
psu # get battery_temperature
Description:
The psu # get battery_temperature returns the battery temperature in Celsius.
Example:
SC>psu 1 get battery_temperature
Battery Temperature 28°C
psu # set force_dc

Syntax:
psu # set force_dc
Description:
Controls the PSU to force the usage of the DC input if usable, disregard presence of AC. If
DC is outside the usable range for the PSU, the PSU shall indicate an alarm using the DC-fail
output. If DC input voltage comes below 43V ±2% and If AC is usable the PSU shall take
the input power from AC. Disregarding a Force-DC control input.
Force DC operation on a bad DC supply, PSU or Battery.
Bad DC supply is defined as a DC source which voltage drops below 43V in a few milliseconds when the PSU
is forced to operate on DC. In case of a force DC command and bad DC supply the 28.5V output voltage is
allowed to drop down to 27V for a maximum of 5 second, while the PSU will automatically switch back to AC
mode and the 28.5V will rise from 27V to 28.5V During this sequence the DC out alarm should be suppressed.
Example:
SC>psu 1 set force_dc
Command executed OK
psu # get force_dc

Syntax:
psu # get force_dc
Description:
The psu # get force_dc returns the setting of the Force DC
4-28 6866600D04-C December 2006

MTS Man Machine Interface Commands psu # set dc_operation
Example:
SC>psu 1 get force_dc
Force DC is active
psu # set dc_operation

Syntax:
psu # set dc_operation
Description:
The psu # set dc_operation configures the psu to use the DC input. The PSU will in
this configuration not make any AC fail alarms.
Example:
SC>psu 1 set dc_operation
Command executed OK
psu # get dc_operation

Syntax:
psu # get dc_operation
Description:
The psu # get dc_operation returns the setting of the dc_operation
Example:
SC>psu 1 get dc_operation
PSU is configured to DC Operation
psu # set ac_operation

Syntax:
psu # set ac_operation
Description:
The psu # set ac_operation configures the psu to use the AC input. The PSU will in
this configuration not make any DC fail alarms.
Example:
SC>psu 1 set ac_operation
Command executed OK
6866600D04-C December 2006 4-29

psu # get ac_operation Chapter 4: Site Controller Commands
psu # get ac_operation

Syntax:
psu # get ac_operation
Description:
The psu # get ac_operation returns the setting of the ac_operation
Example:
SC>psu 1 get ac_operation
PSU is configured to AC Operation
psu # get 7v_voltage

Syntax:
psu # get 7v_voltage
Description:
The psu # get 7v_current returns the 7V dc output current in Ampers.
Example:
SC>psu 1 get 7v_current
7V current 3.2A
psu # get 28.5v_voltage

Syntax:
psu # get 28.5v_voltage
Description:
The psu # get 28.5v_voltage returns the 28.5V dc output voltage in volts
Example:
SC>psu 1 get 28.5v_voltage
28.5V Voltage 28.4V
psu # get 28.5v_current

Syntax:
4-30 6866600D04-C December 2006

MTS Man Machine Interface Commands psu # get fan_voltage
psu # get 28.5v_current

Description:
The psu # get 28.5v_current returns the 28.5V dc output current in Ampers.
Example:
SC>psu 1 get 28.5v_current
28.5V current 2.7A
psu # get fan_voltage

Syntax:
psu # get fan_voltage
Description:
The psu # get fan_voltage returns the FAN dc output voltage in volts.
Example:
SC>psu 1 get fan_voltage
FAN Voltage 18V
psu # get power

Syntax:
psu # get power
Description:
The psu # get power returns the total output power of the PSU.
Example:
SC>psu 1 get power
PSU Power 358W
psu # get psu_temperature

Syntax:
psu # get psu_temperature
Description:
The psu # get psu_temperature returns the internal temperature of the PSU in Celsius
6866600D04-C December 2006 4-31

psu # get ambient_temperature Chapter 4: Site Controller Commands
Example:
SC>psu 1 get psu_temperature
PSU Temperature 38°C
psu # get ambient_temperature

Syntax:
psu # get ambient_temperature
Description:
The psu # get ambient_temperature returns the ambient temperature measured at air intake on the PSU
Example:
SC>psu 1 get ambient_temperature
Ambient Temperature 25°C
psu # set fan_speed

Syntax:
psu # set fan_speed <fanspeed>
Description:
The psu # set fan_speed sets the minimum fan speed, this command should only be used in special cases.
Fan speed can be set in 7 stages 1=12V, 2=14V,3=16V,4=18V,5=20V,6=22V and 7=24V..
Example:
SC>psu 1 set fan_speed 4
Command executed OK
psu # get fan_speed

Syntax:
psu # get fan_speed
Description:
The psu # get fan_speed returns the setting of the fan speed
Example:
SC>psu 1 get fan_speed
FAN Speed 4
4-32 6866600D04-C December 2006

MTS Man Machine Interface Commands psu # set fan_config
psu # set fan_config

Syntax:
psu # set fan_config
Description:
The psu # set fan config informs the PSU regarding how many fans are connected to the PSU.
Example:
SC>psu 1 set fan_config 2
Command executed OK
psu # get fan_config

Syntax:
psu # get fan_config
Description:
The psu # get fan_config returns the setting of the fan_config
Example:
SC>psu 1 get fan_config
Number of FANs 2
psu # start_fan
Syntax:
psu # start_fan
Description:
In the case were a technician replaces a FAN kit and the FAN’s does not start automatically the
command psu # start_fan can be used. It forces the fan voltages to 24V and check the Alarm/Status
to ensure the fan is running and then return to current state.
Example:
SC>psu 1 start_fan
Command executed OK
can reboot
Syntax:
6866600D04-C December 2006 4-33

can reset Chapter 4: Site Controller Commands
can reboot <type> #

Description:
The can reboot forces the CAN-unit to reboot.
Example:
SC>can reboot dpm 1
Command send
can reset
Syntax:
can reset <type> #
Description:
The can reset forces the CAN-unit to reset.
Example:
SC>can reset dpm 1
Command send
can view_mapping_list
Syntax:
can view_mapping_list
Description:
The can view_mapping_list command prints the mapping list.
Example:
SC>can view_mapping_list
Mapping list:
Device Track ID
DPM 1 JTH0500100
PSU 1 JTH0500200
can add_mapping
Syntax:
can add_mapping <device> <Track ID>
Description:
4-34 6866600D04-C December 2006

MTS Man Machine Interface Commands can remove_mapping
The can view_add_mapping command adds a mapping to the list. If device already
exist in the list it will overwrite the old mapping.
Example:
SC>can add_mapping dpm 1 JTH0500100
dpm 1 mapped to JTH0500100
can remove_mapping
Syntax:
can remove_mapping <device>
Description:
The can remove_mapping command removes a mapping from the list.
Example:
SC>can remove_mapping dpm 1
dpm 1 removed from mapping
can change_mapping
Syntax:
can change_mapping <From Track ID> <To Track ID>
Description:
The can change_mapping command changes a mapping.
Example:
SC>can change_mapping JTH0500100 JTH0500101
dpm 1 mapping changed to JTH0500101
can check_mapping
Syntax:
can check_mapping
Description:
The can check_mapping command checks and print the status of the mapping.
Example:
SC>can check_mapping
Units are present:
Device Track ID
6866600D04-C December 2006 4-35

can check_mapping Chapter 4: Site Controller Commands
DPM 1 JTH0500101
PSU 1 JTH0500200
Units are not present:
DPM 2 JTH0500105
Track ID not mapped
JTH0500102
4-36 6866600D04-C December 2006

Chapter
5
Base Radio Commands
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Base Radio Test Application Commands

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Test Application is a powerful mode, inappropriate use of Test Application MMI
can lead to a permanent hardware failure. Please proceed with extreme caution.
cabinet_id
Syntax:
cabinet_id -o<object> –c<cabinet>
Description:
This command is used to display/change the cabinet id settings of the Base Radio Station. This
is one of the values sent back to the ACG in a BR registration msg.
Options:
-o(object)=platform
-c(cabinet id)=1,8,1,No Units
Example:
> cabinet_id -oplatform -c1
> cabinet_id -oplatform
Cabinet ID=1
6866600D04-C December 2006 5-1

position_id Chapter 5: Base Radio Commands
position_id
Syntax:
position_id -o<object> –p<cposition>
Description:
This command is used to display/change the position id settings of the Base Radio Station. This
is one of the values sent back to the ACG in a BR registration message.
Options:
-o(object)=platform
-p(position id)=1,6,1,No Units
Example:
> cabinet_id -oplatform -c1
> position_id -oplatform -p1
> cabinet_id -oplatform
Cabinet ID=1
> position_id -oplatform
Position=1
fv -oplatform
Syntax:
fv -oplatform
Description:
Checks the current version of all system components.
power
Syntax:
power -otxch1 -a<value>
power -otxch1
Description:
Gets or sets the current output power level.
Example:
> power -otxch1 -a35
set the maximum power.
5-2 6866600D04-C December 2006

MTS Man Machine Interface Commands freq
freq
Syntax:
freq -otx_all -f<frequency>
freq -orx_all -f<frequency>
freq -otx_all
freq -orx_all
Description:
Controls the transmit/receive channel frequency.
Options:
freq -otx_all -f<frequency> — sets the transmitter frequency
freq -orx_all -f<frequency> — sets the receiver frequency
freq -otx_all — gets the transmitter frequency
freq -orx_all — gets the receiver frequency
Base Radio Application Commands

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
AIEA
Syntax:
aiea
Description:
This aiea command returns the Air interface Encryption and Authentication configuration.
AIR_TRACER
Syntax:
air_tracer [get | off | on default | on <ip> encrypt | clear | both]
Description:
6866600D04-C December 2006 5-3

AIR_TRACER_MODE Chapter 5: Base Radio Commands
Enable or disable air_tracer or get its status.

Examples:
a) CSS: air_tracer
Use one of:
• air_tracer get
• air_tracer off
• air_tracer on default
• air_tracer on <ip> encrypt | clear | both
b) CSS: air_tracer on 10.0.253.100 both

c) CSS: air_tracer get
IP = 10.0.253.100
channel 1 mode = both
d) CSS: air_tracer off
AIR_TRACER_MODE
Syntax:
air_tracer_mode [x x x x]
Description:
The air_tracer_mode command sets the Mode of the TMV output to clear, encrypted or both.
Example:
CSS: air_tracer_mode E C B C
CCIMMUN
Syntax:
ccimmun
Description:
The ccimmun command returns the Control Channel Immunity configuration.
5-4 6866600D04-C December 2006

MTS Man Machine Interface Commands CHANSTAT
CHANSTAT
Syntax:
chanstat
Description:
Displays current channel usage on BR.
CLS
Syntax:
cls
Description:
The cls command causes a VT100 clear screen escape sequence followed by a cursor location
(top left) command to be sent to the console screen.
DEKEY
Syntax:
dekey
Description:
The dekey command stops all RF transmission.
After the command is entered, an indication of a successful transmission stop is returned.
EXIT
Syntax:
exit
Description:
This command is used to log out the user and terminate the MMI. If the user was logged
in via telnet, the connection is dropped.
GET ACTIVE_TRACES
Syntax:
6866600D04-C December 2006 5-5

GET ABACUS Chapter 5: Base Radio Commands
get active_traces
Description:
Displays a list of active report traces, to local and remote MMIs
GET ABACUS
Syntax:
get abacus
Description:
Displays abacus registers.
GET ALARMS
Syntax:
get alarms
Description:
The get alarms command returns any BR alarm conditions.
If alarm conditions exist, every active alarm is returned.
If no alarm conditions exist, a message is returned indicating alarms have not been detected.
GET BAND
Syntax:
get band
Description:
Displays the operating band of the BR.
GET BTS_TYPE
Syntax:
get bts_type
Description:
The get bts_type command prints the current BTS_TYPE setting on the BR MMI.
5-6 6866600D04-C December 2006

MTS Man Machine Interface Commands GET CABINET
Example:
get bts_type
BTS type: MTS2
GET CABINET
Syntax:
get cabinet
Description:
This command returns the cabinet position of the current Base Radio.
GET CONFIG
Syntax:
get config
Description:
Displays the current configuration of the BR.
GET EX_AD
Syntax:
get ex_ad [port]
Description:
The get ex_ad command returns the current hexadecimal value of all A/D ports (0 to 11)
on the Exciter module with their interpreted voltages.
If the variable for the port number is not entered, the current value of all ports are returned.
GET EXT_REF
Syntax:
get ext_ref
Description:
Show the external reference status.
6866600D04-C December 2006 5-7

GET FWD_PWR Chapter 5: Base Radio Commands
GET FWD_PWR
Syntax:
get fwd_pwr
Description:
The get fwd_pwr command returns the current value of forward power. This reading is taken from the built-in
power meter of the RF Power Amplifier module. The results are returned in Watts and dBm.
This command should be used only when the transmitter is keyed to obtain accurate results.
GET INFO
Syntax:
get info
Description:
Displays BRC hardware and configuration information. This includes software and hardware revision numbers,
transmit and receive frequencies and power. The DSP software version is only available when the BR is keyed.
GET JAVELIN
Syntax:
get javelin
Description:
Displays javelin registers.
GET LOG_INFO
Syntax:
get log_info
Description:
Displays information on the selected BR log.
5-8 6866600D04-C December 2006

MTS Man Machine Interface Commands GET MAX_VSWR
GET MAX_VSWR
Syntax:
get max_vswr
Description:
The get max_vswr command returns the maximum VSWR before an alarm is triggered, as measured
by the built-in power meters of the RF Power Amplifier module.
GET PA_AD
Syntax:
get pa_ad [port]
Description:
The get pa_ad command returns the current hexadecimal value of all A/D ports ( 0 to 11) on
the Power Amplifier module with their interpreted voltages.
GET PA_STATUS
Syntax:
get pa_status
Description:
Displays all configuration information and current status relating to the PA.
GET POSITION
Syntax:
get position
Description:
The get position command returns the position number of where the current BR is mounted within
a selected cabinet. This does not represent the cabinet in which the BR resides.
GET PLATFORM
Syntax:
6866600D04-C December 2006 5-9

GET REF_PWR Chapter 5: Base Radio Commands
get platform
Description:
Display BR hardware revision information.s.
GET REF_PWR
Syntax:
get ref_pwr
Description:
The get ref_pwr command returns the current value of reflected power. This reading is taken from the built-in
power meter of the RF Power Amplifier module. The results are returned in Watts and dBm.
This command should only be used when the transmitter is keyed to obtain accurate results.
GET RPTR_STATUS
Syntax:
get rptr_status
Description:
The get rptr_status command returns the overall status of the base radio.
GET RX(n)_AD
Syntax:
get rx1_ad [port]
get rx2_ad [port]
get rx3_ad [port]
Description:
The get rx(n)_ad command returns the current hexadecimal value of all A/D ports (0 to 11)
on the Receiver module with their interpreted voltages.
GET RX_FREQ
Syntax:
5-10 6866600D04-C December 2006

MTS Man Machine Interface Commands GET RX_FRU_CONFIG
get rx_freq
Description:
The get rx_freq command returns the programmed receiver frequency for the current BR.
GET RX_FRU_CONFIG
Not supported from the Base Radio application. See "rx_fru_config" on page 2-60.
GET SYS_GAIN
Syntax:
get sys_gain
Description:
The get sys_gain command returns the enabled/disabled status of the system gain factor.
GET TIME
Syntax:
get time
Description:
Display the current system time (GMT).
GET TOMAHAWK
Syntax:
get tomahawk
Description:
Displays tomahawk registers.
GET TX_FREQ
Syntax:
get tx_freq
6866600D04-C December 2006 5-11

GET VSWR Chapter 5: Base Radio Commands
Description:
The get tx_freq command returns the programmed transmitter frequency for the current BR.
GET VSWR
Syntax:
get vswr
Description:
The get vswr command calculates the current VSWR, as measured by the built-in power meters of the RF Power
Amplifier module. This command should only be used when the transmitter is keyed to obtain accurate results.
HELP
Syntax:
help
Description:
The help command displays a list of all available commands and a short synopsis of their
use, comprising an option list and a brief description.
All commands support a ‘-?’ option which displays a description of that command and
its usage, including a brief description of each parameter.
KEY
Syntax:
key
Description:
The key command starts the RF transmission of the BR at default TX power.
After the command is entered, an indication is printed that the key-up process has started. As soon as the trans-
mission has started and the default TX power has been reached the command returns the current output power.
KVL
Syntax:
5-12 6866600D04-C December 2006

MTS Man Machine Interface Commands LOGOUT
kvl
Description:
The kvl command entered via the front serial port of the Site Controller configures the front port for
communication with the Key Variable Loader device. If no valid KVL communication is received within 60
seconds, then the port returns to normal operation. Since the front serial port is normally used by the MMI, no
MMI commands may be entered via this port until the communication with the Key Variable Loader device has
been terminated.The success of this operation is indicated at the Key Variable Loader device only. Following
termination of communication by the KVL, the front serial port will automatically return to normal MMI mode.
LOGOUT
Syntax:
logout
Description:
The logout command logs out a user, it is the same command as "EXIT".
lstalm
Syntax:
lstalm
Description:
Displays list of application and core alarms.
lstalmtr
Syntax:
lstalmtr
Description:
Displays list of transient alarms.
RESET
Syntax:
reset
Description:
6866600D04-C December 2006 5-13

VER Chapter 5: Base Radio Commands
The reset command causes the Base Radio to perform a hardware reset, which is roughly
equivalent to pressing the front panel RESET button.
VER
Syntax:
ver [-h]
Description:
The ver command displays version information for Base Radio software and, optionally, the Site Controller
hardware. If entered without options, the firmware and application version numbers are displayed.
Options:
-h Displays both hardware and software information.
SET CABINET
Syntax:
set cabinet {1 | 2 | 3| 4 | 5 | 6 | 7 | 8}
Description:
This command permanently stores the data in EEPROM and is not lost when you exit test mode.
Set cabinet parameter must only be set to “1”.
The set cabinet command sets the cabinet number of the BR.
Incorrectly setting these parameters on a remote session may result in a site visit.
SET LAPD_TRACE
Syntax:
set lapd_trace
Description:
Command for controlling LAPD tracing to MMI.
5-14 6866600D04-C December 2006

MTS Man Machine Interface Commands SET LOG_ROUTING
SET LOG_ROUTING
Syntax:
set log_routing
Description:
Command for controlling routing of logging information.
SET MAX_VSWR
Syntax:
set max_vswr {1.1..4.0}
Description:
The set max_vswr command sets the maximum VSWR for the internal BR power monitor.
The power is rolled back if this value is reached. (The Base Radio may shut down if the
excessive VSWR condition still exists after power roll-back).
SET POSITION
Syntax:
set position {1 | 2 | 3 | 4 | 5 | 6}
Description:
This command permanently stores the data in EEPROM and is not lost when you exit test mode.
The set position command programs the position number of where the current BR is mounted within
a selected cabinet. This does not represent the cabinet in which the BR resides.
Incorrectly setting these parameters on a remote session may result in a site visit.
SET PD_TRACE
Syntax:
set pd_trace
Description:
Command for controlling PD tracing to MMI.
6866600D04-C December 2006 5-15

SET RX_FREQ Chapter 5: Base Radio Commands
SET RX_FREQ
Syntax:
set rx_freq {380.000..390.000}
Description:
The set rx_freq command programs the receiver frequency in the 380.000..390.000 MHz band. The receive
frequency for each receiver within a selected BR are programmed at the same time with this command.
The programmed receiver frequency must be in the range of 380.000..390.000 MHz in 6.25 kHz increments.
Within the RF subsystem of the Dimetra BTS, several variations of a given Field Replaceable
Unit (FRU) or assembly may exist in which each variation corresponds to a specific
frequency range. Any receive or transmit frequencies assigned to a Base Radio via a
command must conform to any existing hardware constraints.
SET RX_FRU_CONFIG
Not supported from the Base Radio application. See "rx_fru_config" on page 2-60.
SET SYS_GAIN
Syntax:
set sys_gain {on | off}
Description:
The set sgc_gain command enables/disables the system gain factor from being used.
SET TRACES_OFF
Syntax:
set traces_off
Description:
Turns off all active report traces. This includes alarm reports and any other traces that may be enabled
5-16 6866600D04-C December 2006

MTS Man Machine Interface Commands SET TX_FREQ
SET TX_FREQ
Syntax:
set tx_freq {380.000..390.000}
Description:
The set tx_freq command programs the transmit frequency in the 380.000..390.000 MHz band. When
this command is entered, the transmitter frequency is programmed into the BRC.
The programmed transmitter frequency must be in the range of 380.000..390.000 MHz in 6.25 kHz increments.
Within the RF subsystem of the Dimetra BTS, several variations of a given Field Replaceable Unit (FRU) or
assembly may exist in which each variation corresponds to a specific frequency range. Any receive or transmit
frequencies assigned to a Base Radio via a command must conform to any existing hardware constraints.
SET SCT_DISP
Syntax:
set sct_disp
Description:
Command for controlling state transition trap tracing to MMI.
SET SM_TRACE
Syntax:
set sm_trace
Description:
Command for controlling state transition tracing to MMI.
6866600D04-C December 2006 5-17

SET SM_TRACE Chapter 5: Base Radio Commands
5-18 6866600D04-C December 2006

A
Appendix
Glossary
heading heading
A/D Analogue-to-Digital
A Amperes
AC Alternating Current
ACT Active
AGC Automatic Gain Control
AIC Ampere Interrupting Capacity
AIS Alarm Indication Signal (Keep Alive)
ASC Automatic Synchronized Configuration
ARP Address resolution Protocol
ASCII American Standard Code for Information Interchange
ASIC Application Specific Integrated Circuit
ATCC Auto Tune Cavity Combiner
Aux Auxiliary
avg average
AWG American Wire Gauge

bd baud
BDM Background Debug Mode
BER Bit Error Rate
BERT Bit Error Rate Test
BNC Baby “N” Connector
BPV Bipolar Variation
BR Base Radio
BRC Base Radio Controller
BW Bandwidth
C/(N + I) Carrier Power to Noise + Interference Ratio
CAN Controller Area Network
CD Carrier Detect
CLK Clock
cm centimetre
CMOS Complementary Metal Oxide Semiconductor
CNE Central Network Equipment
6866600D04-C December 2006 A-1

SET SM_TRACE Appendix A: Glossary
heading heading
CPU Central Processing Unit
CRTP Compressed Real Time Protocol
CSA Cross-Sectional Area (wire size)
CTL Control (Base Radio Control)
CTS Clear to Send
D/A Digital-to-Analogue
DAC Digital to Analog Converter
DB-9 9-pin D-subminiature
dB Decibel
dBc Decibel relative to carrier
dBm Decibels relative to 1mW
DC Direct Current
DCSPLY DC Supply
deg degree
DIP Dual In-line Package
div division
DLCI Data Link Connection Identification
DMA Direct Memory Access
DOP Dilution of Precision
DPM Digital Power Monitor
DRAM Dynamic Random Access Memory
DSP Digital Signal Processor
DTE Data Terminal Equipment
DVM Digital Volt Meter
EAC External Alarm Card
EAS Environmental Alarms System
E-NET Ethernet
EEPROM Electronically Erasable Programmable Read Only Memory
EIA Electronics Industry Association
ELP Ethernet LAN PCI (card)
EMI Electro-Magnetic Interference
EPROM Erasable Programmable Read Only Memory
EPHY Ethernet Physical Layer Protocol
ESI Ethernet Serial Interface
A-2 6866600D04-C December 2006

MTS Man Machine Interface Commands SET SM_TRACE
heading heading
ESCC European System Component Centre
ESSC European System Support Centre

ETSI European Telecommunications Standards Institute
EXC Exciter
F Farad
FB Feedback
FNC Forced Non-Synchronized Configuration
FNE Fixed Network Equipment
FPGA Field Programmable Gate Array
freq frequency
FRU Field Replaceable Unit
GND Ground
GPS Global Positioning System
GPSR GPS Receiver
HC Hybrid Combiner
HDLC High Level Data Link Control
HVAC Heating Ventilation Air Conditioning
Hz Hertz
I/O Input/Output
IC Integrated Circuit
ICD Interface Control Document
ICMP Internet Control Message Protocol
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronic Engineers
IF Intermediate Frequency
in inches
inj injection
kg kilogram
kHz kilohertz
KVL Key Variable Loader
LAN Local Area Network
LAPD Link Access Procedure D-Channel
lbs pounds
LDM Linear Driver Module
LED Light Emitting Diode
LFM Linear Final Module
6866600D04-C December 2006 A-3

heading heading
LMI Local Management Interface
LNA Low Noise Amplifier
LO Local Oscillator
LOS Loss of Signal
LST Local Site Trunking
MAC Medium Access Control
MAU Media Access Unit
max maximum
Mb/s Megabits per second
MCU Microprocessor Control Unit
MER Message Error Rate
MGB Master Ground Bar
MGN Multi-Grounded Neutral
MHz MegaHertz
min minimum
min. minute
mm millimetre
MMI Man-Machine Interface
MPM Multiple Peripheral Module
MS Mobile Station
ms millisecond
mV milliVolt
mW milliWatt
N.C. Normally Closed
N.O. Normally Open
Nm Newton-metre (torque)
no. number
NTU Network Terminating Unit
NTWK Network
NVM Non volatile memory
P/N Part Number
PA Power Amplifier
PC Personal Computer
PDOP Positional Dilution of Precision
pF picoFarad
A-4 6866600D04-C December 2006

heading heading
PLL Phase Locked Loop
PPM Parts Per Million
PPS Pulse Per Second
PSU Power Supply Unit
pwr power
PVC Permanent Virtual Circuit
Qty Quantity
R1 Receiver #1
R2 Receiver #2
R3 Receiver #3
RAM Random Access Memory
RCV Receiver
Ref Reference
RF Radio Frequency
RFDS RF Distribution System
RFS RF System
RGPS Remote GPS
RMC Receiver Multi-Coupler
RMS Root Mean Square
ROM Read Only Memory
RSSI Received Signal Strength Indication
RTC Real-Time Clock
Rx Receive
S/W Software
SC Site Controller
SCI Serial Communications Interface
sec second
SELV Safety Extra Low Voltage (circuit)
SGC Software Gain Control
SINAD Signal Plus Noise Plus Distortion to Noise Plus Distortion Radio
SPI Serial Peripheral Interface
SPST Single-Pole, Single-Throw
SRAM Static Random Access Memory
SRI Site Reference ISA (card)
SS Surge Suppressor
SSC System Status Control
6866600D04-C December 2006 A-5

heading heading
SSI Synchronous Serial Interface
ST Status
STAT Status
Std Standard
SVID System V Interface Definition
SwMI Switching and Management Infrastructure
TCP Transmission Control Protocol
TDM Time Division Multiplex
TDMA Time Division Multiple Access
TDR Time-Domain Reflectometer
TESS TETRA EBTS Service Software
TETRA TErrestrial Trunked RAdio system
TFTP Trivial File Transfer Protocol
TSA timeslot Assigner
TSC TETRA Site Controller
TSI Time Slot Interface
TTL Transistor - Transistor - Logic
Tx Transmit
TXD Transmit Data
TXDSP Transmit Digital Signal Processor
Txlin IC
typ Typical
UHSO Ultra-High Stability Oscillator
UTC Universal Time Coordinate
UTP User Datagram Protocol
V Volt
Vac Volts - alternating current
VCXO Voltage-Controlled Crystal Oscillator
VDC Volts - direct current
VFWD Voltage representation of Forward Power
Vp-p Voltage peak-to-peak
VREF Voltage representation of Reflected Power
VSWR Voltage Standing Wave Radio
W Watt
A-6 6866600D04-C December 2006

heading heading
WDT Watchdog Timer
WP Write Protect
XCVR Transceiver
6866600D04-C December 2006 A-7

A-8 6866600D04-C December 2006

Index
Index
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
B
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Base Radio Application Commands Base Radio Application Commands (contd.)

Application Commands Application Commands (contd.)
AIEA . . . . . . . . . . . . . . . . . . . 5-3 GET VSWR. . . . . . . . . . . . . . . . 5-12
AIR_TRACER . . . . . . . . . . . . . . 5-3 HELP . . . . . . . . . . . . . . . . . . . 5-12
AIR_TRACER_MODE . . . . . . . . . . 5-4 KEY . . . . . . . . . . . . . . . . . . . 5-12
CCIMMUN . . . . . . . . . . . . . . . . 5-4 KVL . . . . . . . . . . . . . . . . . . . 5-12
CHANSTAT. . . . . . . . . . . . . . . . 5-5 RESET . . . . . . . . . . . . . . . . . . 5-13
CLS . . . . . . . . . . . . . . . . . . . 5-5 sample . . . . . . . . . . . . . . . 5-10, 5-15
DEKEY. . . . . . . . . . . . . . . . . . 5-5 Sample . . . . . . . . . . . . . . . . . . 5-7
EXIT . . . . . . . . . . . . . . . . . . . 5-5 SET CABINET . . . . . . . . . . . . . . 5-14
GET ABACUS . . . . . . . . . . . . . . 5-6 SET LAPD_TRACE . . . . . . . . . . . . 5-14
GET ACTIVE_TRACES. . . . . . . . . . 5-5 SET LOG_ROUTING . . . . . . . . . . . 5-15
GET ALARMS . . . . . . . . . . . . . . 5-6 SET PD_TRACE . . . . . . . . . . . . . 5-15
GET BAND . . . . . . . . . . . . . . . . 5-6 SET POSITION . . . . . . . . . . . . . . 5-15
GET BTS_TYPE . . . . . . . . . . . . . 5-6 SET RX_FREQ . . . . . . . . . . . . . . 5-16
GET CONFIG. . . . . . . . . . . . . . . 5-7 SET RX_FRU_CONFIG . . . . . . . . . . 5-16
GET EX_AD . . . . . . . . . . . . . . . 5-7 SET SCT_DISP . . . . . . . . . . . . . . 5-17
GET EXT_REF . . . . . . . . . . . . . . 5-7 SET SM_TRACE . . . . . . . . . . . . . 5-17
GET FWD_PWR . . . . . . . . . . . . . 5-8 SET SYS_GAIN . . . . . . . . . . . . . 5-16
GET INFO . . . . . . . . . . . . . . . . 5-8 SET TRACES_OFF . . . . . . . . . . . . 5-16
GET JAVELIN . . . . . . . . . . . . . . 5-8 SET TX_FREQ . . . . . . . . . . . . . . 5-17
GET LOG_INFO . . . . . . . . . . . . . 5-8 VER . . . . . . . . . . . . . . . . . . . 5-14
GET MAX_VSWR . . . . . . . . . . . . 5-9 Base Radio . . . . . . . . . . . . . . . . . 5-3
GET PA_AD . . . . . . . . . . . . . . . 5-9 Test Application Commands
GET PA_STATUS . . . . . . . . . . . . . 5-9 rx_fru_config . . . . . . . . . . . . . . . 2-60
GET PLATFORM . . . . . . . . . . . . . 5-9 Base Radio Commands . . . . . . . . . . . . . 5-1
GET POSITION . . . . . . . . . . . . . . 5-9 Test Application Commands
GET REF_PWR . . . . . . . . . . . . . . 5-10 cabinet_id . . . . . . . . . . . . . . . . . 5-1
GET RPTR_STATUS . . . . . . . . . . . 5-10 freq . . . . . . . . . . . . . . . . . . . . 5-3
GET RX_FRU_CONFIG. . . . . . . . . . 5-11 fv -oplatform . . . . . . . . . . . . . . . 5-2
GET RX(n)_AD . . . . . . . . . . . . . . 5-10 position_id . . . . . . . . . . . . . . . . 5-2
GET SYS_GAIN . . . . . . . . . . . . . 5-11 power . . . . . . . . . . . . . . . . . . . 5-2
GET TIME . . . . . . . . . . . . . . . . 5-11 Base Radio Test Application Commands
GET TOMAHAWK . . . . . . . . . . . . 5-11 Base Radio . . . . . . . . . . . . . . . . . 5-1
GET TX_FREQ . . . . . . . . . . . . . . 5-11 BOOT1 Commands . . . . . . . . . . . . . . 3-1
C
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Commands
MMI Commands. . . . . . . . . . . . . . . 1-1
6866600D04-C December 2006 IX-1

Index
I
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction . . . . . . . . . . . . . . . . . . 1-1
M
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MMI Commands (contd.) MMI Commands (contd.)

Man-Machine Interface. See MMI Commands . . 1-1 Access Levels and Modes . . . . . . . . . . 1-1
MMI Commands Conventions and Syntax . . . . . . . . . . . 1-2
S
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Site Controller Application Commands . . . . . 4-1 Site Controller Commands (contd.)

Site Controller Commands . . . . . . . . . . . 4-1 BOOT1 Commands (contd.)
BOOT1 Commands sleep . . . . . . . . . . . . . . . . . . . 3-10
ATTRIB . . . . . . . . . . . . . . . . . 3-1 stat . . . . . . . . . . . . . . . . . . . . 3-10
boot . . . . . . . . . . . . . . . . . . . 3-2 sync . . . . . . . . . . . . . . . . . . . 3-10
build_info . . . . . . . . . . . . . . . . . 3-2 testapp . . . . . . . . . . . . . . . . . . 3-10
bview . . . . . . . . . . . . . . . . . . . 3-2 tftp . . . . . . . . . . . . . . . . . . . . 3-10
cd . . . . . . . . . . . . . . . . . . . . 3-3 traceroute . . . . . . . . . . . . . . . . . 3-11
chmod . . . . . . . . . . . . . . . . . . 3-3 ttcp . . . . . . . . . . . . . . . . . . . . 3-11
cp . . . . . . . . . . . . . . . . . . . . 3-3 unmount . . . . . . . . . . . . . . . . . 3-11
ethstat . . . . . . . . . . . . . . . . . . 3-3 vols. . . . . . . . . . . . . . . . . . . . 3-11
exit . . . . . . . . . . . . . . . . . . . . 3-3 Site Controller Application Commands
fdir . . . . . . . . . . . . . . . . . . . . 3-4 ARP . . . . . . . . . . . . . . . . . . . 4-1
finstall . . . . . . . . . . . . . . . . . . 3-4 atc # cav_park . . . . . . . . . . . . . . . 4-20
format . . . . . . . . . . . . . . . . . . 3-4 atc # get alarm. . . . . . . . . . . . . . . 4-19
fusage . . . . . . . . . . . . . . . . . . 3-4 atc # get cav_status . . . . . . . . . . . . 4-21
go . . . . . . . . . . . . . . . . . . . . 3-4 atc # get cav_tune_timo . . . . . . . . . . 4-20
help. . . . . . . . . . . . . . . . . . . . 3-5 atc # get cav_vswr_alm . . . . . . . . . . 4-21
ifattach . . . . . . . . . . . . . . . . . . 3-5 atc # get device_id . . . . . . . . . . . . . 4-18
ifconfig . . . . . . . . . . . . . . . . . . 3-5 atc # get kit_number . . . . . . . . . . . . 4-18
ifstat . . . . . . . . . . . . . . . . . . . 3-5 atc # get status. . . . . . . . . . . . . . . 4-19
inetcfg . . . . . . . . . . . . . . . . . . 3-6 atc # get track_id . . . . . . . . . . . . . 4-19
ipaddr. . . . . . . . . . . . . . . . . . . 3-6 atc # get vendor_serial . . . . . . . . . . . 4-19
LOAD . . . . . . . . . . . . . . . . . . 3-6 atc # set cav_tune_timo . . . . . . . . . . 4-20
login . . . . . . . . . . . . . . . . . . . 3-6 atc # set cav_vswr_alm. . . . . . . . . . . 4-21
ls . . . . . . . . . . . . . . . . . . . . . 3-6 ATTRIB . . . . . . . . . . . . . . . . . 4-1
mkdir . . . . . . . . . . . . . . . . . . . 3-7 BRLOCK . . . . . . . . . . . . . . . . . 4-3
mload . . . . . . . . . . . . . . . . . . . 3-7 BTS_TYPE . . . . . . . . . . . . . . . . 4-4
mount. . . . . . . . . . . . . . . . . . . 3-7 can add_mapping . . . . . . . . . . . . . 4-34
mv . . . . . . . . . . . . . . . . . . . . 3-7 can change_mapping. . . . . . . . . . . . 4-35
netstat . . . . . . . . . . . . . . . . . . 3-8 can check_mapping . . . . . . . . . . . . 4-35
ping . . . . . . . . . . . . . . . . . . . 3-8 can reboot . . . . . . . . . . . . . . . . . 4-33
pwd. . . . . . . . . . . . . . . . . . . . 3-8 can remove_mapping . . . . . . . . . . . 4-35
reset . . . . . . . . . . . . . . . . . . . 3-8 can reset . . . . . . . . . . . . . . . . . 4-34
rm . . . . . . . . . . . . . . . . . . . . 3-8 can view_mapping_list. . . . . . . . . . . 4-34
rmdir . . . . . . . . . . . . . . . . . . . 3-9 CLS . . . . . . . . . . . . . . . . . . . 4-4
route . . . . . . . . . . . . . . . . . . . 3-9 DISPLAY CONFIG . . . . . . . . . . . . 4-4
shell . . . . . . . . . . . . . . . . . . . 3-9 dpm # get alarm . . . . . . . . . . . . . . 4-23
shutdown . . . . . . . . . . . . . . . . . 3-9 dpm # get device_id . . . . . . . . . . . . 4-22
IX-2 6866600D04-C December 2006

MTS Man Machine Interface Commands Index
Site Controller Commands (contd.) Site Controller Commands (contd.)

Site Controller Application Commands (contd.) Site Controller Application Commands (contd.)
dpm # get fwd power . . . . . . . . . . . 4-24 psu # set fan_speed . . . . . . . . . . . . 4-32
dpm # get kit_number . . . . . . . . . . . 4-22 psu # set force_dc . . . . . . . . . . . . . 4-28
dpm # get rev_power. . . . . . . . . . . . 4-24 psu # start_fan . . . . . . . . . . . . . . . 4-33
dpm # get status . . . . . . . . . . . . . . 4-23 RESET . . . . . . . . . . . . . . . . . . 4-10
dpm # get track_id . . . . . . . . . . . . . 4-23 RGPS_DELAY . . . . . . . . . . . . . . 4-10
dpm # get vendor_serial . . . . . . . . . . 4-22 SITE_LOCATION. . . . . . . . . . . . . 4-11
dpm # get vswr . . . . . . . . . . . . . . 4-24 STATUS BR . . . . . . . . . . . . . . . 4-12
dpm # get vswr_alm . . . . . . . . . . . . 4-25 STATUS BSL . . . . . . . . . . . . . . . 4-12
dpm # set vswr_alm . . . . . . . . . . . . 4-25 STATUS BSLQ . . . . . . . . . . . . . . 4-12
EAS_OUT . . . . . . . . . . . . . . . . 4-5 STATUS BTS . . . . . . . . . . . . . . . 4-13
.EGOP . . . . . . . . . . . . . . . . . . 4-5 STATUS CRTP . . . . . . . . . . . . . . 4-13
EXIt . . . . . . . . . . . . . . . . . . . 4-5 STATUS EAS . . . . . . . . . . . . . . . 4-13
help. . . . . . . . . . . . . . . . . . . . 4-6 STATUS FR. . . . . . . . . . . . . . . . 4-14
KILL . . . . . . . . . . . . . . . . . . . 4-6 STATUS FRF . . . . . . . . . . . . . . . 4-14
KVL . . . . . . . . . . . . . . . . . . . 4-6 STATUS KEYS . . . . . . . . . . . . . . 4-14
LOCK . . . . . . . . . . . . . . . . . . 4-6 STATUS LMI . . . . . . . . . . . . . . . 4-14
LOG . . . . . . . . . . . . . . . . . . . 4-7 STATUS PEER . . . . . . . . . . . . . . 4-15
LOGOUT . . . . . . . . . . . . . . . 4-7, 5-13 STATUS RIGMP . . . . . . . . . . . . . 4-15
LS . . . . . . . . . . . . . . . . . . . . 4-7 STATUS SC. . . . . . . . . . . . . . . . 4-15
lstalm . . . . . . . . . . . . . . . . . . . 5-13 STATUS SEC . . . . . . . . . . . . . . . 4-16
lstalmtr . . . . . . . . . . . . . . . . . . 5-13 STATUS SRI . . . . . . . . . . . . . . . 4-16
MAX_WSVR . . . . . . . . . . . . . . . 4-8 TFTP . . . . . . . . . . . . . . . . . . . 4-16
MIRROR . . . . . . . . . . . . . . . . . 4-8 TIMEZONE. . . . . . . . . . . . . . . . 4-17
NETSTAT. . . . . . . . . . . . . . . . . 4-9 UNLOCK . . . . . . . . . . . . . . . . . 4-17
password . . . . . . . . . . . . . . . . . 4-9 VER . . . . . . . . . . . . . . . . . . . 4-17
PING . . . . . . . . . . . . . . . . . . . 4-9 WHO . . . . . . . . . . . . . . . . . . . 4-18
PORT . . . . . . . . . . . . . . . . . . . 4-10 Test Application Commands
psu # get 28.5v_current . . . . . . . . . . 4-30 adc_scaling_factor . . . . . . . . . . . . . 2-9
psu # get 28.5v_voltage . . . . . . . . . . 4-30 alarm_force . . . . . . . . . . . . . . . . 2-11
psu # get 7v_voltage . . . . . . . . . . . . 4-30 alarm_log . . . . . . . . . . . . . . . . . 2-12
psu # get ac_operation . . . . . . . . . . . 4-30 alarm_log_clear . . . . . . . . . . . . . . 2-14
psu # get alarm . . . . . . . . . . . . . . 4-27 alarm_log_enable . . . . . . . . . . . . . 2-14
psu # get ambient_temperature . . . . . . . 4-32 alarms . . . . . . . . . . . . . . . . . . 2-13
psu # get battery_current . . . . . . . . . . 4-27 analog_digital_converter . . . . . . . . . . 2-10
psu # get battery_temperature. . . . . . . . 4-28 atten_default . . . . . . . . . . . . . . . 2-15
psu # get battery_voltage . . . . . . . . . . 4-27 backplane_slotid_long_text. . . . . . . . . 2-16
psu # get dc_operation . . . . . . . . . . . 4-29 battery_settings . . . . . . . . . . . . . . 2-15
psu # get device_id . . . . . . . . . . . . 4-25 calibration_factor . . . . . . . . . . . . . 2-17
psu # get fan_config . . . . . . . . . . . . 4-33 canbus . . . . . . . . . . . . . . . . . . 2-1
psu # get fan_speed . . . . . . . . . . . . 4-32 chipset_reg . . . . . . . . . . . . . . . . 2-22
psu # get fan_voltage . . . . . . . . . . . 4-31 comm_port_parms . . . . . . . . . . . . . 2-18
psu # get force_dc . . . . . . . . . . . . . 4-28 digital_analog_converter . . . . . . . . . . 2-26
psu # get kit_number. . . . . . . . . . . . 4-26 e1_external_loopback . . . . . . . . . . . 2-27
psu # get power . . . . . . . . . . . . . . 4-31 e1_frm_config . . . . . . . . . . . . . . . 2-30
psu # get psu_temperature . . . . . . . . . 4-31 fault_management_enable . . . . . . . . . 2-29
psu # get status . . . . . . . . . . . . . . 4-26 fault_management_interval . . . . . . . . . 2-29
psu # get track_id . . . . . . . . . . . . . 4-26 firmware_version . . . . . . . . . . . . . 2-36
psu # get vendor_serial. . . . . . . . . . . 4-26 fru_configuration_parameter . . . . . . . . 2-28
psu # set ac_operation . . . . . . . . . . . 4-29 fru_self_diagnostic . . . . . . . . . . . . 2-31
psu # set dc_operation . . . . . . . . . . . 4-29 gps . . . . . . . . . . . . . . . . . . . . 2-37
psu # set fan_config . . . . . . . . . . . . 4-33
6866600D04-C December 2006 IX-3

Index
Site Controller Commands (contd.) Site Controller Commands (contd.)

Test Application Commands (contd.) Test Application Commands (contd.)
help. . . . . . . . . . . . . . . . . . . . 2-1 platform_number . . . . . . . . . . . . . 2-56
igps. . . . . . . . . . . . . . . . . . . . 2-41 pps_enable . . . . . . . . . . . . . . . . 2-55
kit_number . . . . . . . . . . . . . . . . 2-45 real_time_clock . . . . . . . . . . . . . . 2-59
last_reset_reason . . . . . . . . . . . . . 2-50 reference_source. . . . . . . . . . . . . . 2-58
led . . . . . . . . . . . . . . . . . . . . 2-47 reset . . . . . . . . . . . . . . . . . . . 2-57
led config . . . . . . . . . . . . . . . . . 2-45 revision_number. . . . . . . . . . . . . . 2-57
load. . . . . . . . . . . . . . . . . . . . 2-48 status . . . . . . . . . . . . . . . . . . . 2-60
login . . . . . . . . . . . . . . . . . . . 2-49 temp_sensor . . . . . . . . . . . . . . . . 2-64
logout. . . . . . . . . . . . . . . . . . . 2-50 time_reference. . . . . . . . . . . . . . . 2-63
memory . . . . . . . . . . . . . . . . . . 2-51 ws - watchdog_settings. . . . . . . . . . . 2-65
memory_parameters . . . . . . . . . . . . 2-53 Software Commands
ping . . . . . . . . . . . . . . . . . . . 2-55 MMI Commands. . . . . . . . . . . . . . . 1-1
T
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Test Application Commands . . . . . . . . . . 2-1
IX-4 6866600D04-C December 2006

6866600D04 MMI Commands RevC

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

6866600D04 MMI Commands RevC

Uploaded by

Copyright:

Available Formats

Dimetra IP

MTS Man Machine Interface Commands

© 2007 Motorola, Inc.

Edition Description Date

6866600D04-C December 2006 i

ii 6866600D04-C December 2006

Volume 5 Volume 7 Volume 8

Booklet 9-1: Master Site

Security/Authentication Feature Manuals

6802700U92 6881132E24 6881003Y85 6802800U66 6802800U67 6802800U62

AUC Crypto End to End Air Interface Backup/Restore Network Telephone

KVL 3000 Plus Provisioning Data MCC 7500

Affiliation Application Authentication Performance FullVision RCM RCM

Software UCM ZCM ZoneWatch System and KMF TESS

EMEA Systems Support Centre (ESSC)

Jays Close, Viables Industrial State

European Systems Component Centre (ESCC)

Motorola GmbH CGISS

Parts Identification and Ordering

EMEA Test Equipment Support

Updated Versions of this Manual

MTS Man Machine Interface Commands

Chapter 2: Test Application Commands

6866600D04-C December 2006 iii

Chapter 3: BOOT1 Commands

iv 6866600D04-C December 2006

Chapter 4: Site Controller Commands

6866600D04-C December 2006 v

vi 6866600D04-C December 2006

can reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

Chapter 5: Base Radio Commands

6866600D04-C December 2006 vii

viii 6866600D04-C December 2006

Table 2-1: CAN Bus Related Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

6866600D04-C December 2006 ix

This page intentionally left blank.

x 6866600D04-C December 2006

MTS Man Machine Interface Commands

What is Covered In This Manual?

Helpful Background Information

6866600D04-C December 2006 xi

The warning icon implies potential system damage if the instructions or

xii 6866600D04-C December 2006

Access Levels and Modes

6866600D04-C December 2006 1-1

The syntax for each command is presented as follows:

1-2 6866600D04-C December 2006

Test Application: provides facilities for setup, diagnostic and testing.

Test Application Commands

6866600D04-C December 2006 2-1

Power Digital Auto-Tune CAN

Managing the CAN bus unit mapping list:

Commands for adding, deleting and changing CAN bus units

2-2 6866600D04-C December 2006

Purpose Delete the entire mapping list

Reading CAN bus unit variables:

6866600D04-C December 2006 2-3

Track Track Track > can -oatcc1 -cread -vtrackid

Number Number Number atcc1: track id = COM0632845

Status > can -oatcc0 -cread -vstatus

VSWR Alarm > can -oatcc0 -cread -vvswr_alarm_th

Cavity Status > can -oatcc0 -cread -vcav_status -n1

2-4 6866600D04-C December 2006