iSAR System Handbook v2.2

System Handbook

iSAR2

Immediate SAR Systems

System Handbook V 2.2

Schmid & Partner Engineering AG

August 22, 2010

Contents

I General iv

II Equipment Description 1

1 Safety Considerations 21.1 Mass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 Electrical Shock . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 Shock and Vibration . . . . . . . . . . . . . . . . . . . . . . . 21.4 RF Radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.5 Disposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Functional Description 42.1 Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . 42.2 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.3 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.4 iSAR Flat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.5 iSAR Head . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.6 CRANE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.7 Typical Applications . . . . . . . . . . . . . . . . . . . . . . . 12

2.7.1 SAR Assessment . . . . . . . . . . . . . . . . . . . . . 122.7.2 SAR Assessment of Spatial Diversity DUT . . . . . . 132.7.3 Determination of Worst-Case Configurations . . . . . 132.7.4 QA Applications . . . . . . . . . . . . . . . . . . . . . 132.7.5 Relative Assessment of Output Power . . . . . . . . . 132.7.6 Time Stability Evaluations . . . . . . . . . . . . . . . 142.7.7 Remote Programming . . . . . . . . . . . . . . . . . . 142.7.8 Production Line Integration / 3rd Party Applications 142.7.9 R&D . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.8 Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3 Data Processing & Evaluation 163.1 Spatial Peak Averaged SAR . . . . . . . . . . . . . . . . . . . 173.2 Comparison of Amplitude and Pattern . . . . . . . . . . . . 17

i

Contents

3.3 Measurement Combiner . . . . . . . . . . . . . . . . . . . . . 18

III Usage 20

4 Installation 214.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.1.1 Unpacking iSAR Flat . . . . . . . . . . . . . . . . . . 214.1.2 Unpacking iSAR Head . . . . . . . . . . . . . . . . . . 224.1.3 Connections . . . . . . . . . . . . . . . . . . . . . . . . 23

4.2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.2.1 Windows XP Installation . . . . . . . . . . . . . . . . 234.2.2 Windows 7 Installation . . . . . . . . . . . . . . . . . 28

4.3 Calibration Files . . . . . . . . . . . . . . . . . . . . . . . . . 344.4 National Instruments GPIB to USB adapter for CMU200 con-

trol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.4.1 Software Installation . . . . . . . . . . . . . . . . . . . 354.4.2 Hardware Installation . . . . . . . . . . . . . . . . . . 35

5 Operation 375.1 iSAR2 GUI System Requirements . . . . . . . . . . . . . . . . 385.2 iSAR2 GUI Overview . . . . . . . . . . . . . . . . . . . . . . . 385.3 Ribbon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5.3.1 Main Menu . . . . . . . . . . . . . . . . . . . . . . . . 405.3.2 iSAR2 Measurement Tabs . . . . . . . . . . . . . . . . 415.3.3 iSAR2 Configuration . . . . . . . . . . . . . . . . . . . 47

5.4 3-D Visualization Toolbar . . . . . . . . . . . . . . . . . . . . 565.4.1 Orbit . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.4.2 Pan . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.4.3 Zoom In/Out . . . . . . . . . . . . . . . . . . . . . . . 565.4.4 Zoom All . . . . . . . . . . . . . . . . . . . . . . . . . 575.4.5 Zoom Selection . . . . . . . . . . . . . . . . . . . . . . 575.4.6 Move SAR Legend . . . . . . . . . . . . . . . . . . . . 575.4.7 Rotate display 90 . . . . . . . . . . . . . . . . . . . . . 575.4.8 2D View . . . . . . . . . . . . . . . . . . . . . . . . . . 575.4.9 Measurement View Only . . . . . . . . . . . . . . . . . 575.4.10 Tile Views . . . . . . . . . . . . . . . . . . . . . . . . . 585.4.11 Display Saved View 1 . . . . . . . . . . . . . . . . . . 585.4.12 Display Saved View 2 . . . . . . . . . . . . . . . . . . 585.4.13 Display Saved View 3 . . . . . . . . . . . . . . . . . . 585.4.14 Smooth/Contoured Colour Display . . . . . . . . . . . 585.4.15 Log/Linear Scaling . . . . . . . . . . . . . . . . . . . . 585.4.16 Manual/Auto Ranging . . . . . . . . . . . . . . . . . . 585.4.17 Python Interpreter Window . . . . . . . . . . . . . . . 59

Schmid & Partner Engineering AG, iSAR2 Manual V 2.2, Aug. 2010 ii

General

5.4.18 Auto-Save Measurement Log Window . . . . . . . . . 595.5 iSAR2 Measurement Display Views . . . . . . . . . . . . . . . 59

5.5.1 Quick Access Commands . . . . . . . . . . . . . . . . 595.6 Message Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.7 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

A Performance Evaluation of iSAR2 versus DASY 68

B IronPython Application Programming Interface (API) 72

C Material Safety Data Sheet 86

Schmid & Partner Engineering AG, iSAR2 Manual V 2.2, Aug. 2010 iii

Part I

General

iv

General

COPYRIGHT

Copyright © 2004-2010 Schmid & Partner Engineering AG. All rights re-served. This document is provided by Schmid & Partner Engineering AG forinformational purposes only to licensed users of the iSAR2 software prod-uct and is furnished on an “AS IS” basis, that is, without any warranties,whatsoever, expressed or implied. Information in this document is subjectto change without notice. The software described in this document is fur-nished under a license agreement. The software may be used or copied onlyin accordance with the terms of this agreement. No part of this publica-tion may be reproduced, stored in a retrieval system, transmitted, or copiedin any form or by any means, electronic or mechanical, including photo-copying and recording, for any purpose other than the purchaser’s sole use,without the written permission of Schmid & Partner Engineering AG. iSAR& iSAR2, DASY, DASY4 & DASY5, SEMCAD and SPEAG are registeredtrademarks of Schmid & Partner Engineering AG. Microsoft and Windowsare registered trademarks of the Microsoft Corporation. Other brand andproduct names are trademarks or registered trademarks of their respectiveholders.

Schmid & Partner Engineering AGZeughausstrasse 438004 ZurichSwitzerland

Visit our Web site: http://www.speag.com

Schmid & Partner Engineering AG, iSAR2 Manual V 2.2, Aug. 2010 v

http://www.speag.com

General

About this manual

The iSAR2 System Handbook contains five chapters: Safety Considerations,Functional Description, Data Processing & Evaluation, Installation, and Op-eration. There are also two appendices: ‘Performance Evaluation of iSAR2

versus DASY’ and ‘IronPython Application Programming Interface (API)’.The Safety Considerations chapter gives general guidelines on how to

operate and handle the equipment to ensure the user’s safety.The Functional Description provides basic knowledge on the operating

principle of the iSAR2. Included are a hardware overview, the specifica-tions, and maintenance instructions to ensure correct measurements. Alsoincluded are descriptions of the iSAR Flat and the iSAR Head, and calibra-tion information.

The Data Processing & Evaluation chapter provides the informationabout the algorithms used to determine the SAR values, how several mea-surements can be combined to enhance accuracy and repeatability, and howto determine the degree of correspondence of amplitude and SAR distribu-tions between current and reference measurements.

The Installation chapter is comprised of three parts: how to correctlyset up the hardware, how to successfully install the software and where tocopy the calibration files.

The Operation chapter provides comprehensive information on softwareoperations and features. Explanations of software configuration, settingsand parameters are included.

The Appendix entitled ‘Performance Evaluation of iSAR2 versus DASY’describes a comparison between iSAR and DASY measurements.

The Appendix entitled ‘IronPython Application Programming Interface(API)’ describes the modules and classes that can be used for scripting usingthe IronPython interface.

If you have any questions related to matter beyond the scope of thismanual, do not hesitate to contact us by email ([email protected]).

Schmid & Partner Engineering AG, iSAR2 Manual V 2.2, Aug. 2010 vi

General

Declaration of CE Conformity

Item Immediate SAR SystemType / Version No SD 001 001, SD 001 002, SD 001 003,

SD 003 001Manufacturer / Origin Schmid & Partner Engineering AG

Zeughausstrasse 438004 Zurich, Switzerland

Contact [email protected]: +41 44 245 9700

General

The iSAR2 (immediate SAR) is designed to measure the induced field andthe specific absorption rate (SAR) distribution of RF emissions from hand-sets and wireless devices in the frequency range from 0.4 to 6 GHz and fora power level up to several Watts. The devices are positioned on the ab-sorber block in radiating mode. A sensor array inside the absorbing materialmeasures the signals and forwards the processed information to a personalcomputer (PC) connected via a USB interface for data storage and represen-tation. User supplied PCs and radiating sources (devices under test) are tobe operated together with the system, but are not provided with it (exceptas an option).

CE Conformity

We declare the iSAR2 System in the specified configuration to be conformantwith:

• Directive Low Voltage 73/23/EWG modified

• Directive Electromagnetic Compatibility 89/336/EWG modified

• EN 55011 Class A

• EN 61000-6-1

Date: 23.2.2008 Signature / Stamp F. Bomholt

Schmid & Partner Engineering AG, iSAR2 Manual V 2.2, Aug. 2010 vii

Part II

Equipment Description

1

Chapter 1

Safety Considerations

This product and related documentation must be reviewed for familiariza-tion with safety considerations and instructions before operation.

1.1 Mass

Due to the required volume of the absorber block, the mass is approximately30.5 kg for the iSAR Head and 33.5 kg for the iSAR Flat. At least twopersons with appropriate equipment are required to unpack / pack / movethe system. It should be positioned on a horizontal stable support, capableof supporting the weight of the iSAR2 in order to ensure safe operation andavoid harm to the operator(s).

1.2 Electrical Shock

There are no serviceable parts inside the iSAR2. Do not open the unitor loosen the feet at its base. Before moving the unit, switch it off anddisconnect the power line and other cables.

Keep the ventilation slots at the base of the metal housing clear forcorrect ventilation to avoid overheating. It should be separated from otherequipment on all sides by a minimum distance of 5 cm. The ambient temper-ature at the air inlet must be kept within the specified range of 19− 25 C.

1.3 Shock and Vibration

The black coated absorber block consists of a sealed housing with a 2 mmdielectric cover plate. Avoid shocks to the equipment and mechanical pres-sure to the cover plate in order to maintain the unit’s integrity and to avoiddamage.

2

CHAPTER 1. SAFETY CONSIDERATIONS Equipment Description

1.4 RF Radiation

Radiating ‘devices under test’ are not part of the iSAR2. It is the responsi-bility of the user to follow all regulations regarding such RF emitting devices.PC and wiring connected to the iSAR2 must be at a safe distance from theemitting sources. Filtering beads on cables and operation in a shielded roommay be required.

1.5 Disposal

The equipment is conformant to the RoHS requirements for measurementequipment. Lead has only been used for contacts in the sensor array whereit could not be avoided for technological reasons.

The iSAR2 must not be disposed of in an uncontrolled manner into theenvironment. Please return it to the manufacturer for proper disposal.

Schmid & Partner Engineering AG, iSAR2 Manual V 2.2, Aug. 2010 3

Chapter 2

Functional Description

2.1 Hardware Overview

Figure 2.1: iSAR2 - Immediate SAR systems

4

CHAPTER 2. FUNCTIONAL DESCRIPTION Equipment Description

An iSAR2 system consists of the following partsiSAR2 iSAR Flat: 360× 360× 270 mm, 33.5 kg

iSAR Head: 360× 360× 290 mm, 30.5 kgProtection cover (flatonly)

stainless steel

Power cableUSB cable max. 4.5 m without repeaterNull Modem cable D 9-pin 1 to 1 cable 5 meterManualSoftware including GUI Software, calibration, in-

stallation filesPackaging material 2 fixation belts for cover and lifting;

foam coated boxLaptop PC (optional) with Windows operating system

Figure 2.2: iSAR2 connector bay



The connector bay has the following elements (from left to right, top tobottom)

Mains connector for power cable, with On / Off switchIdentification labelSerial link RS-232 sub D 9-pin, for service purposes

and firmware download (2 RXD, 3 TXD,5 GND, 7 RTS, 8 CTS)

Gate In Gate In, > 5 kΩ, max. +7 V, threshold+1.4 V typ.

USB link USB type B receptable connector, inter-face to PC

GND 4 mm socket connected to shield & groundLEDs∗

- EXTG on gate signal at BNC connector- PWR on firmware started- COM on PC initialized iSAR2 as USB device

blinking receiving commands from PC- GATE on integrating of measured data

∗ only iSAR2 series 001 002 B or later



2.2 Specifications

Power supply voltage 100−240 VAC, 47−63 Hz (phase, neutral,ground)

Current consumption < 3 A (internal fuse, not operator accessi-ble)

Power consumption typically 150 WOperating temperature nominally 19− 25 C, not exposed to sun

or heat radiationVentilation 2 internal ventilators, temperature con-

trolledStorage temperature 5− 30 CAbsorbing material dielectric parameters within ±10 % of

IEC 62209 and IEEE 1528 target param-eters at 22 C

Absorbing block size Flat: 320× 320× 120 mmHead: 320× 320× 140 mm

Sensor distance 4 mm from absorber material surface,6 mm from top surface

Frequency range 0.5− 3 GHz (< 0.4− 6 GHz)Number of sensors 256 (8× 16× 2)Active area 120× 240 mmMeasurement grid reso-lution

15 mm

Sensitivity < 0.05 W/kgDynamic range 100 W/kg (continuous wave)Measurement time user selectable, minimum < 3 sCalibration sensors individually calibrated for specific

communication systems and frequencybands.

Main frequencies 835 MHz - 2450 MHz, other frequencies onrequest

CommunicationSystems∗

CW, GSM, GPRS, UMTS, IS-2000, IS-91, IS-95, IS-136, iDEN, Bluetooth, IEEE802.11.

Repeatability typically < 0.1 dB with combiner (see Sec-tion 3.3)

Accuracy typically < 1 dB in comparison to DASY5for 1 g and 10 g spatial SAR (at 22 C and1 h after switch-on)

∗ The full list is at http://www.speag.com/speag/services/calibration/ communica-

tion system.php.



2.3 Maintenance

The iSAR2 is intended for operation in a laboratory type environment orproduction line testing.

iSAR2 should be kept in a controlled environment whenever possible,without exposure to solar or heat radiation, dust, high humidity, liquidsand extreme temperatures. Avoid condensating humidity on the unit: allowtemperature adaptation after transportation in cool environment, and leavethe unit packaged for several hours before opening it in a warm (and humid)environment.

No further user maintenance is required. The unit contains no userserviceable elements.

For cleaning of all surfaces, use a moistened micro-fiber cloth. Some mildsoap may be added to the water if necessary. Disconnect the power prior tocleaning to avoid electric shock.

2.4 iSAR Flat

The iSAR Flat contains a planar array of 2-D sensors embedded in a blockof broad-band absorbing material. The planar configuration of the iSARFlat is equivalent to SAR area scan tests in the body mounted positionaccording to IEC 62209: Part II. A 2 mm shell thickness and broadbandabsorbing material are equivalent to the flat phantom conditions.

A choice of two broadband simulating materials is available. The stan-dard iSAR Flat is filled with a material simulating head tissue parameters,in accordance with IEC 62209: Part II. The iSAR Flat (Muscle) is filledwith a broadband absorbing material simulating muscle tissue parametersfor testing in accordance with FCC OET Bulletin 65 Supplement C. To keepthe characteristics close to the target values, the iSAR2 should be operatedin a temperature controlled environment of ideally 22 C.

Figure 2.3: Sensor array (before embedding) and amplifier array (shieldingremoved)



The array covers an area of 120 × 240 mm in a 15 mm grid. The stablelightweight structure fixes the sensors at a distance of 4± 0.1 mm from thesurface of the absorbing material. Each sensor consists of an orthogonal pairof small E-field dipoles with a detector diode. Their demodulated outputsignals are fed via highly-resistive lines to the back of the absorber block viaa shield to the amplifier array.

Each sensor signal is fed to its own amplifier channel so that all sig-nals are evaluated during the specified time interval. The digitized signalsfrom the individual channels are fed via the USB to the host PC for evalu-ation and presentation. Prior to final assembly and calibration, a completefunctionality test is run on the iSAR (see Figure 2.4).

Figure 2.4: A complete functionality test is conducted before final assemblyand calibration

A cooling system reduces heat dissipation from the electronics onto theabsorber block. Two temperature controlled ventilators transfer the dissi-pated heat from the shielded electronics to the outside. This allows pro-longed operation without overheating the absorber block.

Local SAR is determined from the E-field and the absorbing materialparameters. The orthogonal pair of E-field sensors isotropically measures thedominant transversal component of the E-field induced by the device undertest. The normal component, which is usually smaller, is omitted. Basedon the SAR data available in the grid, algorithms are applied to estimatethe spatial peak SAR values. For further details on the data available foranalysis, please refer to Section 5.

A set of low-permittivity, low-loss spacers is also available. The standard



thicknesses are 1, 2, 5, 10, 15 mm, and other sizes are available upon request.The spacers ensure the required separation between the surface and phone.The spacers can be stacked to achieve several different separation distances.

Figure 2.5: iSAR Flat with the set of low-permittivity, low-loss spacers of1, 2, 5, 10 and 15 mm thickness

2.5 iSAR Head

The iSAR Head is equivalent to the iSAR Flat except that the shape of themeasurement surface is formed to follow the ear-to-mouth line of the SAMHead Phantom as specified in IEEE-1528, IEC 62209 II, FCC OET 65 C,etc. This line is extruded in an orthogonal direction, resulting in a 2 mmthick cylindrically shaped shell with an ear spacer.

The iSAR Head is also equipped with a phone holder to ensure securepositioning of the DUT (see Figure 2.6). The DUT holder is an elasticarm attached to a spring loaded mechanism. The tip of the DUT holder isequipped with an anti slip rubber point to ensure a good grip on the DUT.The spring-loaded mechanism can be released by pressing the yellow buttonon the side of the iSAR Head.

A set of masks enabling easy and accurate positioning of the device intilt positions is available. Masks are available for 6 or 15 tilt positionswith respect to the touch position. Other angles are also available uponrequest. Figure 2.7 shows a clam shell phone in the 15 tilt position onthe iSAR Head. The phone is secured in its position by the phone holder.The +15 face mask can be removed easily for DUT measurements in cheekposition.



Figure 2.6: iSAR Head illustrating Phone Holder operation, and 15 mask

Figure 2.7: iSAR Head with the set of low-permittivity, low-loss masksenabling accurate tilt positions at 6 (left) and 15 (right) with respect tothe touch position

2.6 CRANE

CRANE enables testing of wireless devices on the iSAR Flat or iSAR Headwith hands-free cables or data cables attached, as shown in Figure 2.8.CRANE emulates the identical test configurations on DASY4 and DASY5that are used in the standardized test configurations, as specified in inter-national standards. In these standards, the cables are allowed to hang downbelow the phantoms, e.g., below the TwinSAM or ELI phantoms.

CRANE supports many types and lengths of cables. It has a solid metalbase for stability. The body is made of material (carbon fiber and PolyamidePA6) that is rigid and non-perturbing of the iSAR measurements. The



height of CRANE can be adjusted over a range of 550 mm to 1000 mmabove the iSAR Flat or iSAR Head. The maximum load bearing weight is200 grams.

Figure 2.8: CRANE supporting a hands-free cable connected to a mobilephone. The cable is suspended above the mobile phone to reduce the influ-ence of the cable position on the radiated performance.

2.7 Typical Applications

2.7.1 SAR Assessment

iSAR2 systems evaluate SAR using the same or similar techniques that aredescribed in the Fast SAR recommendations of IEC 62209-2 and IEEE 1528(2009 draft). Despite certain limitations of the phantom and measurementgrid, such as the limited size or shape, the fixed resolution (that can be en-hanced by the combiner), the neglected z-component, and the measurementin only one plane (4 mm below the surface), the obtained results closely cor-relate to the measurements obtained with the most precise DASY5 scanner.The accuracy limitations resulting from the fixed measurement resolutionare easily overcome by combining multiple measurements at different orien-tations (see Section 3.3). An extensive study showed excellent agreement



between the results of iSAR2 and DASY5 (see Appendix A: PerformanceEvaluation of iSAR2 versus DASY).

iSAR2 supports pre-compliance testing and substantially reduces com-pliance testing time.

2.7.2 SAR Assessment of Spatial Diversity DUT

Traditional scanners require very specialized DUT software for evaluatingtransmitters with spatial diversity properties, since they measure time se-quentially. Special software of the DUT is not required with the iSAR2

systems, since the entire absorption pattern is measured within the same(user-defined) time integral. Therefore, in addition to the true SAR values,important information about the DUT performance in loaded conditions canbe compiled with the iSAR2 systems.

2.7.3 Determination of Worst-Case Configurations

Modern multi-band devices require multiple tests for a complete SAR evalu-ation. To reduce the testing time, IEC 62209 II explicitly allows the usage offast SAR systems such as the iSAR2. Worst-case frequencies and operatingmodes can be identified easily and quickly.

In addition to the very short time consumption of single tests, the soft-ware also automatically runs sequences supported by a base station simula-tor. Programming of frequencies and bands of an Rohde & Schwarz CMU200 is shown in Section 5.3.3.7.

2.7.4 QA Applications

Small changes in the RF relevant parts can significantly affect the SAR level.The influence of the antenna design / layout, antenna or ground contacts,shields or material changes on the SAR can be investigated efficiently andquickly. In the quality control process, for example, production deviationsthat influence the RF radiation (power or pattern) can be identified reliably.Due to the short measurement time and automation capabilities, it is evenpossible to test each device individually.

2.7.5 Relative Assessment of Output Power

SAR is proportional to the emitted power of a device. For a given geometryand arrangement relative to the iSAR2, the relative power can be measuredwith high precision. Each sensor is calibrated precisely over the full dynamicrange for the chosen communication system modulation.



2.7.6 Time Stability Evaluations

Stability issues causing variations in the output power can be easily in-vestigated with the Timesweep function (see Section 5.3.3.3). Long-timeevaluations of stability or battery drainage can be documented graphically,as shown below. Timesweep data can also be automatically logged into a filefor further analysis (see Section 5.3.3.8: Auto-Save and Logging, for moreinformation).

2.7.7 Remote Programming

Remote control of the iSAR2 without the GUI using customer specific pro-grams (for example: Microsoft VC++, Microsoft VB, Microsoft VC#, Mi-crosoft VJ#, Microsoft IronPython, National Instruments LabView, Agi-lent VEEPro) is possible. For more information on this, please email [email protected].

The Python interpreter (see Section 5.4.17) also provides access to ex-tended automation by allowing scripts to be executed from within the iSAR2

GUI.Further specific control of the measurement interval is possible by pro-

viding a logical gate or trigger signal (see Section 2.1). Synchronizationwithout an operator allows for highly automated applications. Customerspecific solutions are possible for integration into specific automated envi-ronments.

2.7.8 Production Line Integration / 3rd Party Applications

The software is designed such that SPEAG can quickly integrate the systeminto any 3rd party applications.

2.7.9 R&D

The functionality of iSAR2 as described above (in Sections 2.7.1 — 2.7.8),when combined with OTA evaluations, provides everything necessary toevaluate the performance of DUTs when operating close to the human body.SPEAG also offers various high-end phantoms for OTA usage such as thestandardized OTA phantoms or phantoms mimicking the load of iSAR2 (seeFigure 2.9).

2.8 Calibration

For each specific communication system (frequency and modulation), aset of parameters is used to calibrate the individual sensors and chan-nels, allowing precise measurements of the power-averaged E-field and SAR.The calibration file includes all these parameters plus the validity range.


CHAPTER 2. FUNCTIONAL DESCRIPTION Eq. Description

Figure 2.9: High-precision OTA phantoms for transmitter evaluations at theear and body-mounted operations including hand phantoms and masks.

The full list of calibration modes is at http://www.speag.com/speag/ ser-vices/calibration/communication system.php. For further information, pleasecontact [email protected].

Yearly recalibration is recommended.If sensor degradation is observed please contact [email protected].


Chapter 3

Data Processing &Evaluation

Figure 3.1: iSAR2 GUI showing the three measurment views - left: measure-ment view (current measurement); middle: reference view; right: differenceview (comparison of the measurement distribution against the reference dis-tribution).

16

CHAPTER 3. DATA PROCESSING & EVALUATION Eq. Description

3.1 Spatial Peak Averaged SAR

Various standards require the determination of the cubic volume with thehighest integrated SAR content. Standards typically specify 1g or 10g spa-tial peak averaged SAR. Using iSAR2, these values are automatically com-puted for every acquired measurement (or measurement combination) usinga new, fast algorithm that is based on the MOTOROLA FAST SAR ap-proach. It should be noted that iSAR2 only measures a 2-D distribution.Therefore, in order to be able to perform the integration, the measuredvalues have to be extrapolated from the measurement plane (both up tothe iSAR2 surface and down into the iSAR2 bulk medium). This is doneassuming an exponential decay along the iSAR2 surface normal with a fre-quency and medium dependant decay rate as determined in [IEEE Trans. onMTT, vol. 52, no. 8, pp. 2013−2020, 2004]. Furthermore, to compensate foriSAR2’s coarse measurement grid, cubic spline interpolation is used to re-fine the distribution. Due to iSAR2’s homogeneous material distribution, thecube size for a given mass can easily be computed and is a constant through-out the measurement volume. The algorithm then continuously shifts thecube over the entire measurement domain and determines the spatial peakaveraged SAR.

3.2 Comparison of Amplitude and Pattern

Here, the goal is to compare a reference distribution to a new measurement(or measurement combination). The comparison produces two results: amatch value and a difference plot. The latter is much more sophisticatedthan the results achieved from subtracting one distribution from the other.To correctly interpret the results and to set the input parameters appropri-ately, it is crucial to understand the steps involved. There are essentiallyfive steps:

• Interpolation: Both the reference image and the new measurementare interpolated to an identical working resolution. This resolutionis typically (much) higher than the iSAR2 array step size and canbe set using the parameter ‘Interpolation step size’ in the ‘Reference’parameter settings.

• Scaling: The possible variations in (device) output power are com-pensated by scaling the values of the measurement to the level of thereference. The ratio of their 1g spatial peak averaged SAR is used.The relative intensity of the images is displayed as ‘Scale’ above thedifference plot.

• Registration: Using a multigrid method, the scaled measurement dis-tribution is shifted and rotated to optimally correspond to the refer-


CHAPTER 3. DATA PROCESSING & EVALUATION Eq. Description

ence distribution. A mask that specifies the overlap area is established.

• Difference map generation: The interpolated, scaled and registeredimages are now compared. A variation of the gamma method (wellknown in radiation medicine) is used. It searches for correspondingpoints in the two distributions. Two input parameters are needed:the spatial tolerance (tols) which specifies how strongly the distancebetween the corresponding points is weighted, and a value tolerance(tolf ) that specifies how strongly the deviations in measured SAR areweighted. The latter can either be specified as an absolute toleranceor as a tolerance relative to the spatial peak averaged SAR. For everypoint in the measurement distribution it then calculates the normal-ized difference to every point in the reference distribution using theformula √

(ds/tols)2 + (df/tolf )2 (3.1)

whereby ds is the distance between the two points and df the SARdifference between the two points. Both spatial distances and SARdifferences increase the normalized difference. The two points with thesmallest normalized difference are considered as corresponding pointsin the two measurements. For every point the difference plot showsthe normalized difference to its corresponding point (multiplied by thevalue tolerance). A high value in the difference plot therefore indicatesa large normalized distance to the corresponding point indicating dif-ferences in the radiation pattern.

• Match value determination: The match value is easily determinedbased on the difference map. The ratio of points in the overlap areaof the measurement and the reference distribution have a normalizeddistance between corresponding points smaller than one.

3.3 Measurement Combiner

The measurement combiner can be used to combine multiple measurementsin order to enhance the resolution and to statistically improve the radiationpattern determination. It is strongly based on the distribution comparison.The first measurement is used as a reference image. The following steps areperformed:

• Interpolation: All images are interpolated to an identical working res-olution. This resolution is typically (much) higher than the iSAR2

array size and can be set using the parameter ‘Interpolation step size’in the parameter settings.

• Registration: This involves registration of scaled images, calculationof match values and determination of weight masks. The images are


CHAPTER 3. DATA PROCESSING & EVALUATION Usage

scaled to the intensity of the first image using their 1g spatial peakaveraged SAR and aligned to the first image using the registrationprocedure. The match value is determined. If the match value islower than a user specified threshold (‘Minimum match’ criterion),or if the difference in 1g spatial peak averaged SAR is larger than auser specified tolerance, the image is ignored in the averaging process.For each image a weight mask is generated. Its purpose is to ensurethat points near measurement sensors, where the interpolation givesmore reliable estimations of the SAR value, are given greater weightthan points more removed from the measurement sensors. The weightdecreases linearly with the distance to the nearest sensor.

• Weighted Averaging: Using the registered images and the obtainedweight masks, a weighted averaging over the images that have notbeen scaled is performed resulting in a more highly resolved, morereliable combined measurement.

1 2 3 4 5 6 7 8 9 10−0.3

−0.2

−0.1

0

0.1

0.2

0.3

0.4

Combination (N)

SA

R 1

g de

viat

ion

to D

AS

Y |

dB

meas 1meas 2meas 3

Figure 3.2: The use of the combiner enables a significant increase in theprecision of the assessment as it eliminates uncertainties such as interpola-tion, sensor isotropy and sensor-to-sensor calibration variations. Typicallyit increases the repeatability to better than ± 0.1dB.


Part III

Usage

20

Chapter 4

Installation

4.1 Hardware

4.1.1 Unpacking iSAR Flat

Prepare a stable, horizontal table able to safely support the equipment witha mass of at least 40 kg.

Open the packaging so the four base feet are visible at the top. Removethe foam protection.

Verify that the fixation belts are tight. Use the fixation belts to lift theunit from the box and place it carefully on the table.

WARNING: The iSAR Flat is heavy. Two persons are re-quired to lift it out of the box. Please do NOT lift the iSARFlat unit by the four feet, as this may damage them.

Figure 4.1: iSAR Flat top down in packaging lifted by two people via sup-plied straps. Place top down when unpacking.

With the belt and protection cover still mounted, first put the iSAR2

on its side (belt side without locks) and then on its four feet in the final,upright position.

21

CHAPTER 4. INSTALLATION Usage

Figure 4.2: iSAR Flat with the belts on the table turned on its side and infinal upright position with feet on the table.

Remove the belts and the protection cover for operation.

4.1.2 Unpacking iSAR Head

The iSAR Head is not packed upside down to avoid damage of the fragilephone holder. To unpack it, please remove the foam protection and lift theiSAR Head from the box by reaching to the bottom of the steel enclosure.

WARNING: The iSAR Head is heavy. Two persons arerequired to lift it out of the box. Please do NOT lift theiSAR Head by the phone holder, as this will likely damageit.

Figure 4.3: iSAR Head in the packaging.



Figure 4.4: iSAR Head being lifted out of packaging by two people andplaced on the table.

4.1.3 Connections

• Verify main switch is set to off.

• Connect the power line to a grounded voltage outlet according to thespecifications.

• Connect the USB cable to the PC.

• Check that the air in- and outlets are not covered and allow free airflow from the side and the bottom. The air outlet is at the left side(with the connectors at the back).

• If required, an extra ground wire can be connected to the shielding /metal structure to avoid possible low frequency coupling.

• Do not yet switch on the iSAR2, until the iSAR2 software is installed.

For advanced requirements in the precision of measurement, allow pas-sive stabilization of the absorber block temperature to the controlled en-vironment temperature and switch on the iSAR2 electronics for about onehour before commencing measurement.

4.2 Software

4.2.1 Windows XP Installation

Please follow the steps below. The order of the steps is important.

4.2.1.1 Step 1

Make sure the iSAR2 unit is switched off.



4.2.1.2 Step 2

Install the iSAR2 application software by opening the Setup.exe file youreceived. This will copy the iSAR2 application files into a folder of yourchoice. The suggested folder is Program Files/iSAR 2.x.x.x.

4.2.1.3 Step 3

Connect iSAR2 with the PC using the USB cable provided.

4.2.1.4 Step 4

Turn on the iSAR2 device. Windows will detect the new hardware and willshow the Found New Hardware Wizard. Tell it not to search the WindowsUpdate service by selecting No, not this time, and press Next.

Figure 4.5: Step 4

4.2.1.5 Step 5

On the next page, tell the wizard to Install from a list or specific location, andpress Next again.

4.2.1.6 Step 6

The Wizard now asks you to Please choose your search and installation options.Tell it to search for the driver software in the iSAR2 application folder,by unchecking the Search removable media option and checking Include thislocation in the search, and then browse to the folder where you installed theiSAR2 software. Press Next.



Figure 4.6: Step 5

Figure 4.7: Step 6

4.2.1.7 Step 7

Windows should now find a driver information file named virtualserial.inf inthe iSAR2 application folder. It will show you the Hardware Installationdialog, confirming that you are installing software for iSAR CDC (virtualCOM). Ignore the warning about the Windows Logo test and select ContinueAnyway.



Figure 4.8: Step 7

4.2.1.8 Step 8

The wizard has completed the hardware installation. Click Finish to con-tinue.

Figure 4.9: Step 8

4.2.1.9 Step 9

After installing the driver, you should see a new COM port in the WindowsDevice Manager in the Ports (COM & LPT) section. The port is labelediSAR CDC (virtual com) (COMn), where n is a COM port number which isautomatically assigned. Each USB connector on the PC maps to a different



COM port.

Figure 4.10: Step 9



4.2.2 Windows 7 Installation

Please follow the steps below. The order of the steps is important.

4.2.2.1 Step 1

Make sure the iSAR2 unit is switched off.

4.2.2.2 Step 2

Install the iSAR2 application software by opening the Setup.exe file youreceived. This will copy the iSAR2 application files into a folder of yourchoice. The suggested folder is Program Files/iSAR 2.x.x.x.

4.2.2.3 Step 3

Go to the Windows 7 Start Menu Search Box and type in change deviceinstallation settings.

Figure 4.11: Step 3

Click on the link to this applet.



4.2.2.4 Step 4

Figure 4.12: Step 4

Select No, let me choose what to do.Select Never install driver software from Windows Update.(You can reset this later in the same way, but please note, that for every

USB connector you would like to use in controlling an iSAR2 device, thisdriver installation procedure will have to be repeated, so it is recommendedthat you repeat this installation procedure now for each USB connector onyour personal computer.)

Select Save Changes.

4.2.2.5 Step 5

Connect iSAR2 with the PC using the USB cable provided.

4.2.2.6 Step 6

Turn on the iSAR2 device. Windows will detect the new hardware and willshow that it had a problem installing the drivers for it. That is ok.

4.2.2.7 Step 7

Go to the Windows 7 Start Menu Search Box and type in device manager.

4.2.2.8 Step 8

Click on the link to this applet. Under other device should be an entry forUnknown Device.



Figure 4.13: Step 7



4.2.2.9 Step 9

Right-click on this and select Update Driver Software.

Figure 4.14: Step 9

4.2.2.10 Step 10

Select Browse my computer for driver software.

4.2.2.11 Step 11

Under Search for driver software in this location navigate to the iSAR2

application folder. Do not select Let me pick from a list of devicedrivers on my computer. Click Next.



Figure 4.15: Step 10





4.2.2.12 Step 12

Ignore the warning about Windows not being able to verify the publisherand select Install this driver software anyway.

4.2.2.13 Step 13

Windows should now find a driver information file named virtualserial.inf inthe iSAR2 application folder. It will show you the Hardware Installationdialog, confirming that you are installing software for iSAR CDC (virtualCOM).




4.3 Calibration Files

With each of your iSAR2’s, you received a number of calibration files, one foreach communication system and frequency band ordered. These files havenames like 1012 GSM 1800 1710-1785 2006-10-12.iSAR.Calibration. Whenyou first run the iSAR2 software, it will prompt you to install a device.

Navigate to the folder of calibration files that came on the iSAR2 softwareCD, or to any other calibrations directory locally on your computer thatcontains files of devices that you would like to install. See 5.5.1.1 for moreinformation on this function and how to install additional devices.



4.4 National Instruments GPIB to USB adapterfor CMU200 control

For automatic DUT connection settings and call establishment with theRhode and Schwarz CMU200 in iSAR2, Rhode and Schwarz recommendsthe purchase of the following National Instruments GPIB to USB adapter :http://sine.ni.com/nips/cds/view/p/lang/en/nid/201586.

4.4.1 Software Installation

Before any National Instruments GPIB driver installation, all previous GPIBdriver software should be removed from the personal computer.

With the purchase of a NI GPIB adapter, the necessary installationsoftware is usually supplied on a CD. Alternativly download the driver fromthe National Instruments homepage:

http://joule.ni.com/nidu/cds/view/p/lang/en/id/1529

4.4.2 Hardware Installation

Verify the proper installation of your GPIB Adapter with National Instru-ments software Measurement and Automation Explorer (NI-MAX).

Connect the CMU200 to the GPIB Adapter and the GPIB adapter toyour personal computer, then press ’Scan for Instruments’ in the NI-MAXsoftware. The screen updates and the CMU200 will be represented in theleft panel tree under ’Devices and Interfaces’ by a list of 11 instruments.See ??. Verify in the middle lowest panel that the GPIB address (PAD)is set to the same address as in the CMU200 dialog (5.3.3.7) and that thedescription contains Rhode and Schwarz CMU200. ’Instrument XX’ entriesdescribe separate sub addresses from specific CMU200 software options. Donot attempt to change these.

If the CMU200 is not found please doublecheck your GPIB connectors.Also verify the address settings in the CMU200 dialog.

Once this is done and verfied, connection via the iSAR2 software is pos-sible, and easy.


http://sine.ni.com/nips/cds/view/p/lang/en/nid/201586

http://joule.ni.com/nidu/cds/view/p/lang/en/id/1529


Figure 4.19: National Instruments Measurement and Automation Explorer


Chapter 5

Operation

Figure 5.1: iSAR2 software GUI

37

CHAPTER 5. OPERATION Usage

5.1 iSAR2 GUI System Requirements

The following are the minimum PC system requirements as a platform forthe iSAR2 GUI.

• Intel Pentium4 2.8GHz CPU (or AMD equivalent).

• 512MB of RAM.

• A 3-D accelerated graphics display adapter card with 128MB of on-board memory that supports the latest OpenGL drivers currentlyavailable.

• Windows 7 or Windows XP Operating System (with Service Pack 2).Windows 7 is recommended.

• A screen with 32bit colour depth and a resolution of 1280x1024 pixelsor better.

You must ensure that your hardware is set up properly before using theiSAR2 software.

Note: When running the iSAR2 software on Windows 7, it is advisedthat the Windows User has Adminstrator privileges.

5.2 iSAR2 GUI Overview

The iSAR2 GUI has a view window consisting of a ribbon bar, a visualizationtoolbar, three measurement view subwindows, a messaging bar and a statusbar right at the bottom of the GUI.

The ribbon bar is shown at the top of the application and providescontrol. The toolbar is the thin strip of buttons between the three viewsand the ribbon bar and also provides control. It provides quick access tovisualization settings for the 3-D display. Furthermore, it gives access to apython interpreter.

The three measurement views provide a synchronized interactive 3-Ddisplay consisting of the current measurement, a reference (or golden) mea-surement, and a difference between these two measurements.

The message bar provides import informational, warning and error mes-sages.

These measurements are overlayed on a 3-D view of the iSAR2 devicecurrently in use. This software automatically adjusts its display to thecorrect device being used. The user may zoom in and out of measurementviews and rotate them to whatever viewing position is desirable. The relativesizes of the three measurement views can be adjusted by dragging the verticalsplitter bars between them. The cursor changes to a when it is over asplitter bar for dragging.



The current measurement and reference measurement views display thefollowing additional information regarding the measurement:

• A short description including date and time stamp.

• If loaded from file, the filename.

• 1g, 10g and Peak SAR values (in mW/g) when displaying SAR, elsethe peak voltage or peak e-field when these displays are selected.

• The peak SAR, as a green normal-vector line to the surface at thepoint of the peak SAR (see Figure 5.2).

• The name of the DUT, if provided.

• The type of the DUT, if provided.

• The serial number of the DUT, if provided.

• The spacing used in measurement with the DUT.

Figure 5.2: Green normal-vector line to the surface at the point of the peakSAR

The difference view displays the deviation (in % matching) as extrainformation.

A right-click anywhere over one of the three measurement views yields apop-up menu for quick access to the most frequently used menu functions.

Error messages may also pop up on top of the application window.



5.3 Ribbon bar

The ribbon bar consists of a main menu, a measurement section, and aconfiguration section.

5.3.1 Main Menu

The main menu of the ribbon bar provides the following functionality:

Figure 5.3: Ribbon bar main menu

• ‘Open...’ - opens a .ISAR measurement file stored on disk.

• ‘Save As File...’ - will store the current measurement to a .ISARmeasurement file on disk.

• ‘Save As Image...’ - will store the current measurement to an imagefile stored on disk. If in timesweep mode, this function will store thetimesweep graphic to an image file stored on disk.

• ‘SAR Data Export...’ - will export the current measurement to a textfile stored on disk.

• ‘Import SAR from DASY...’ - will import a text file of a SAR mea-surement as stored on disk when exported from DASY via SEMCAD.For more information, please see Section 5.3.2.3.



• ‘Open Timesweep Sequence...’ - a stored Timesweep session can bereloaded and displayed.

• ‘Print’ - will allow for a print-preview, the configuration of print set-tings, and printing of the current measurement views. If a Timesweepgraphic is visible, this will be printed.

• ‘About’ - displays some basic information regarding the GUI applica-tion.

• ‘Exit’ - will close the application.

5.3.2 iSAR2 Measurement Tabs

Figure 5.4: Ribbon bar showing measurement tab

5.3.2.1 iSAR

Figure 5.5: iSAR panel in Measurement tab

The iSAR panel contains iSAR2 device selection controls (see below),and zeroing functionality (see Section 5.5.1.2).

The drop-down list will list all available iSAR devices that have beenconfigured in the ’Calibrations’ directory, and will thus allow for the switch-ing of control between these devices if they are correctly connected andpowered on.

5.3.2.2 Acquisition

The Acquisition panel contains all acquisition related controls for the se-lected iSAR2 device.



Figure 5.6: Acquisition panel in Measurement tab

The Single button triggers a measurement. Acquired measurement datais displayed in the Measurement display view.

To take a single measurement, and add that to the combiner, use theCombiner button. Each time that the Combiner button is pressed, anothermeasurement is collected and combined with the others to create a newmeasurement value. The Measurement display view displays the new mea-surement value.

For repeated measurements, click the Continuous button. This will trig-ger measurements as fast as possible, depending on the speed of the systemthe iSAR2 software is installed on.

For repeated measurements over a desired timespan and at a desiredinterval, click the Timesweep button.

Figure 5.7: Screenshot of Timesweep measurements in progress

For measurements using the Rohde & Schwarz 200 Universal Radio Com-munication Tester exercising a mobile device, click the CMU200 button.Please note that the use of this device with the iSAR2 software requires a



National Instruments GPIB to USB (see 4.4) adapter be purchased and in-stalled on the computer running this software. Other GPIB device vendorsare not supported by SPEAG or Rohde & Schwarz, but can work with a bitof experimentation.

Acquired measurements are displayed repeatedly until stopped with theStop button.

Please note that the Single, Continuous and Timesweep button graphicswill only go yellow (active) if an iSAR2 device is connected. The CMU200button graphics will only go yellow if a CMU200 device is connected. If noneis connected, they will remain grey. The Stop button will only be functionalwhen necessary i.e. when measurements are in progress.

The Clear Combiner button clears the measurement collection. The num-ber of combined measurements in the current measurement collection andthe repeatability (the standard deviation of the 1-gram or 10-gram SARvalues, whichever is largest) are also displayed in the acquisition panel.

Follow these three steps to use the Combiner feature:

• take the first measurement when the device is positioned straight in thecenter of the field. This allows for a centered absorption pattern witheither zero or only the lowest values at the edge of the measurementfield;

• shift and rotate the device slightly (less than 45 degrees), measureand add this data set to the previous measured data to obtain a moreprecise data set based on the combination of all measurements. It willnot add the data set if the registration fails. In this case, you mighthave rotated the device by too large a margin or it may have movedduring the measurements.

• this procedure can be stopped if the 10 g value has converged. Therequired number of measurements depends on the distribution; usually,no more than 5− 10 measurements are required.

5.3.2.3 Reference Measurement

The current measurement may be used, or a previously saved measurementfile may be imported as a reference for comparison for the selected iSAR2

device, e.g. the SAR distribution of the golden device. This measurementcan be used for evaluating differences to the current measurement.

The Reference panel displays the acquisition date and time of the refer-ence measurement if acquired by iSAR2, or the date and time of import ifacquired by DASY, and allows for the comparison of the current measure-ment to this reference. This is done by pressing the Compare button.



Figure 5.8: Reference panel in Measurement tab



To import a DASY measurement into iSAR2, the file should first beloaded into SEMCAD, as illustrated in Figure 5.9.

Figure 5.9: How to open a DASY file in SEMCAD.

Once this file is loaded into SEMCAD, only Area Scan SAR datashould be exported, as illustrated in Figure 5.10.

Figure 5.10: How to export SAR data from a DASY file loaded in SEMCAD.

Selecting Field Data Export... from Area Scan SAR data will thenbring up the Post-Processing control as illustrated in Figure 5.11. Pleasetake careful note that all settings highlighted in red must be selected,and that the Export Data... button as highlighted in blue must be usedto do the actual data export. To clarify, these settings should be

• ’Value of SAR in mW/g’ checkbox enabled.

• ’Header Information’ checkbox enabled.

• ’Coordinates’ checkbox enabled.

• ’Use 6 (or more) Digits’.

Please take note of where you stored this output, and load this file intoiSAR2. If you encounter any problems, please email all measurement fileswith a problem description to [email protected].



Figure 5.11: Export settings for DASY files to be exported to iSAR2 inSEMCAD.

5.3.2.4 Calibration

Figure 5.12: Calbration panel in Measurement tab

The Calibration panel allows for the selection of frequency and commu-nication system settings of the selected iSAR2 device to match those beingtested of your device under test. iSAR2 uses these settings to convert sensorvoltages to SAR values. You can only select from among those communi-cation systems your iSAR2 was calibrated for. You can enter any sourcefrequency within the limits of the selected system. For certain communica-tions systems, you can intelligently select either source frequency or channelnumber with the former being calculated from the latter and vice versa. Forcommunication systems where this is not possible, the channel configurationis disabled.

5.3.2.5 Display Components

Figure 5.13: Display panel in Measurement tab

The Display panel allows for the selection of the quantity to be displayedin the Measurement and Reference display views. This setting affects all



selectable iSAR2 devices. Options are either SAR, E-Field or sensor voltage.SAR is the default selection. X, Y or Total selects the individual componentspicked up by the X or Y sensors, or the total value of the quantity ateach measurement point. The sensor voltage values are used mainly formaintenance and service purposes.

5.3.3 iSAR2 Configuration

Figure 5.14: Ribbon bar showing configuration tab

5.3.3.1 Measurement

Figure 5.15: Measurement dialog

These settings affect the currently selected iSAR2 device.Typical integration time is 0.1 to 0.5 s. Checking the Test mode box

and then acquiring a new measurement injects test data instead of readingsfrom the hardware. Please note that the test mode produces synthetic mea-surements injected into the post-processing for test purposes only - for realmeasurements do not forget to switch this off!

5.3.3.2 DUT (Device Under Test)

These settings affect the currently selected iSAR2 device.



Figure 5.16: Device Under Test dialog

This control allows for the configuration of vital measured DUT informa-tion. This information persists in stored measurement files and the structur-ing of logging sessions and data. NOTE: It is HIGHLY recommended thatthis information is accurately configured when measuring each DUT, as onlythen will logging session and logged data be meaningful. See below, Section5.3.3.8: Auto-Save and Logging, for more information.

5.3.3.3 Timesweep

Figure 5.17: Timesweep dialog

These settings affect the currently selected iSAR2 device.This control allows for the configuration of the desired timesweep interval

and duration. The duration is limited to a minimum of twice the interval,and the interval is limited to a minimum of 2 seconds plus measurementintegration time (See above, Section 5.3.3.1: Measurement, for this setting)between measurements.



5.3.3.4 Display Range

Figure 5.18: Display dialog

These settings affect all iSAR2 devices.With this dialog, the ranges of values for the colour legends are set.

Three display ranges can be set (see Section 3).

• The minimum and maximum range of the local SAR values for themeasurement view.

• The minimum and maximum range of the local SAR values for thereference view.

• The range of 0 to the specified Absolute or Relative value in the differ-ence view.

The sensors detecting peak voltage overflow appear red: in such a case,the measurement needs to be repeated at lower power.

iSAR2 also estimates the peak spatial SAR values of 1 g and 10 g, whichare displayed in the views when SAR is selected. These values are estimatedas described in Chapter 3.

5.3.3.5 Combiner

These settings affect the currently selected iSAR2 device.The use of the combiner enables the combination of different measure-

ments of the same device in different positions and orientations with respectto the sensor grid. This allows a significant increase in the precision ofthe assessment since it eliminates uncertainties such as interpolation, sensorisotropy and sensor-to-sensor calibration variations. Typically it increases



Figure 5.19: Combiner dialog

the repeatability to better than ± 0.1dB. Details of the principles used aredescribed in Chapter 3.

Individual measurements that constitute the current combined measure-ment are visible in a list on the combiner control. Selecting a measurementwill enable the displaying thereof in the Measurement View of the iSARsoftware. If an individual measurement is not desired in the combiner out-put, selecting the Remove selected measurement from combiner button belowthe list will remove the currently selected measurement.

Scaling tolerance is the percent tolerance between the new measurementand the combiner reference. If the new measurement is outside this toler-ance, an error message will appear and it will be rejected from the combiner.

Minimum match is a threshold for the matching of the new measurementto the combiner reference (see Section 3.3 for more information). If thematch is less than the Minimum match threshold, an error message willappear and it will be rejected from the combiner.

The Spatial matching tolerance and the Relative SAR matching toleranceare the values tols and tolf used for the generation of the difference map, asdescribed in Section 3.2.

Both the reference image and the new measurement are interpolated toan identical working resolution. This resolution is typically (much) higherthan the iSAR2 array step size and can be set using the parameter Interpo-lation resolution. Four values can be selected: Extra fine, Fine, Medium orCoarse. Higher resolutions give a more accurate comparison but are moretime consuming to evaluate.



Figure 5.20: Comparator dialog

5.3.3.6 Comparator

These settings affect the currently selected iSAR2 device.The compare function compares a measured distribution to a reference

distribution. It provides a chart about the deviations per point plus thepercentage of points matching the tolerance criteria defined. In addition,the scale factor of the amplitude is provided. The comparison automaticallyperforms the following steps:

• Both the measured and the reference distributions are interpolated toa higher resolution.

• The scaling factor between the measured and reference distributionsis determined based on the 1 g spatial peak SAR values. In most caseswhen testing equivalent phones, this Scale factor corresponds to thedifferences in the antenna input power of the two measurements.

• In a pattern matching step, the measured distribution is shifted androtated to optimally fit the reference distribution.

• For every measurement point in the overlap area, the best correspond-ing point in the reference image is identified. If that point is not toodistant and has a similar value, it contributes to the matching per-centage. The distance combined with the value differences determinethe color and the value of the corresponding chart Display section Dif-ference | Absolute and Difference | Relative.

Press the Compare button to execute a comparison.The resolution can be specified in the field Interpolation step size. The

tolerances for spatial differences and value differences for the comparisoncan be specified as well.



Figure 5.21: CMU200 dialog

Typical values for the comparator settings are: Spatial tolerance: 1 to7 mm (default: 3 mm), Relative SAR tolerance: 1 to 100% (default: 10%),Interpolation step size: 1, 3 or 5 mm (default: 3 mm).

5.3.3.7 CMU200

Please read and execute 4.4 carefully before executing the rest of these in-structions.

Only one iSAR2 at any given time may be used with the CMU200, asthe CMU200 can only communicate with a single handset at any given time.

This CMU200 dialog allows for the setup of radio communication teststo be automatically integrated into the SAR measurement process.

The CMU200 driver statuses are displayed in the message bar. Forconvenience, they are also displayed in this dialog (CMU200 Driver StatusLog). Please note: if a CMU200 can not be found, this functionality will bedisabled.

The following general hardware settings are available per test setup:



• GPIB Address. This is the CMU200 GPIB device address. This has tobe configured before any communication between the iSAR2 softwareand CMU200 can occur.

• RF In. This is the physical RF input port on the front panel of theCMU200, where your test antenna should be connected. The defaultis ‘2’.

• RF Out. This is the physical RF output port on the front panel of theCMU200, where your test antenna should be connected. The defaultis ‘2’.

Please note: According to Rohde & Schwarz, it is recommended to useport 2 for RF In/Out when using the CMU200.

A ‘Set’ button affects these changes.The following specific hardware settings are available per communication

band:

• Ext.In.Att. This is the input attenuation applied to the selected RFinput port. The default is ‘36dB’.

• Ext.Out.Att. This is the output attenuation applied to the selected RFoutput port. The default is ‘36dB’.

A ‘Set’ button affects these changes.A communication test sequence of communication band and communi-

cation channel can be created with the following controls:

• Add to list. This appends the currently selected ‘band:channel’ com-bination to the end of the sequence.

• Select test by sequence number. These controls allow for the selectionof a test in the test sequence based on its execution order.

• Modify selected test. This will change the currently selected test (inselected position) with the newly selected ‘band:channel’ combination.

• Insert new test at selection. This will insert currently selected ‘band:channel’combination into the selected position.

• Remove selected test. This will remove the currently selected test fromthe sequence.

Ensure that your DUT and SIM are able to support the desired commu-nication system. If not, this will not work.

All settings and test sequences may be stored to disk and loaded fromdisk via the Save to disk and Load to disk buttons.



Figure 5.22: Pop-up message for establishing a call from the mobile.

Figure 5.23: Auto-Save and Logging dialog

To start a CMU200 test, one initiates the sequence by pressing the Ac-quire CMU200 button.

At a certain point after initiating the measurement sequence, the messageof Figure 5.22 will appear. When it does, ensure the mobile handset is turnedon and registered with the CMU200 so that there is a signal strenth indicatorshowing, before attempting a call. Any number may be used in initiatingthis call. Only at that point should you press ‘OK’. The test sequence willthen run.

When performing band-handovers, this message may appear again ascommunication systems are changed. When it does, watch the signal strengthindicator and when it has returned, reinitiate a call, and press ‘OK’ again.The process will continue.



5.3.3.8 Auto-Save and Logging

Please note that it is important for this feature that the DUT information iscorrectly configured.

The following auto-save and logging groups/sessions can be configuredwith this dialog:

• All Measurements.

• CMU200 Measurements.

• Timesweep Measurements.

• Combiner Measurements and combinations.

When these features are enabled with their respective Enable Auto-Saveof Measurement Files and Enable Logging to Excel check-boxes, measure-ments will be stored to these locations on disk, within a sub-folder createdfrom the iSAR2 Serial Number, and their information will be appended toa comma-seperated-value log file also found in the desired locations.

All measurements are stored in *.ISAR format.All log files are stored as SessionLog.csv.Double-clicking on such a file will automatically open it in Microsoft

Excel (if installed) where a whole host of analytical functionality may beused as desired.

If you do not have Microsoft Excel, you may download and use OpenOf-fice to perform the same functions.

Log information is in the following format: “Date — Time — DUT SerialNumber — DUT Name — DUT Type — DUT Spacing — Modulation —Frequency — Peak SAR — 1g SAR — 10g SAR — Filename”.

All session sub-folders are created by name with the following format:iSAR Serial Number/DUT SerialNumber +DUT Name +Year +Month +-Day +Hour +Minute +Second. The configured DUT information deter-mines the first half of the name format, and the time-stamp of the firstmeasurement determines the second half of the name format.

Feature ‘All Measurements’ will log the information and store a copy ofeach measurement taken. Measurement names include a date and times-tamp.

Feature ‘CMU200 Measurements’ will log the information and store a copyof each measurement taken when executing a CMU200 test sequence, in asession-based sub-folder created in the desired location. Measurement nameshave the following format cmu200 +SequenceNumber +CommunicationSystem+Channel.

Feature ‘Timesweep Measurements’ will log the information and store acopy of each measurement taken when executing the Timesweep function,



in a session-based sub-folder created in the desired location. Measurementnames have the following format timesweep+TimeInSeconds.

Feature ‘Combiner Measurements’ will store a copy of each measurementtaken and store the combination measurement each time a measurement isadded to the combiner, in a group-based sub-folder created in the desired lo-cation. Clearing the combiner will allow for a new combination group. Mea-surement names have the following format combiner +measurementadded+SequenceNumber. Combined measurements will have the following formatcombiner +measurementcombination+1 +to +LastCombinedMeasurement-SequenceNumber.

By default, all these features are disabled at installation.

5.4 3-D Visualization Toolbar

These settings apply to all iSAR2 devices being controlled.

Figure 5.24: 3-D Visualization Toolbar

5.4.1 Orbit

The mode button allows for the orbiting of the display in 3-dimensionalspace (i.e., changing the viewing angle) using the pointing device.

5.4.2 Pan

The mode button allows for the panning of the display without chang-ing the viewing angle using the pointing device.

5.4.3 Zoom In/Out

The mode button allows for the zooming in or out of the displaywithout changing the viewing angle using the pointing device. When thisbutton is selected:

• Holding down the left button and dragging the pointer down will zoomin.

• Holding down the left button and dragging the pointer up will zoomout.



Please note that with pointing devices that have a wheel between the left andright buttons, it is much easier to zoom in and out by scrolling the wheelforward or backward.

5.4.4 Zoom All

The button zooms the entire 3-D model to fit into view without chang-ing the viewing angle.

5.4.5 Zoom Selection

The button zooms the entire selected region into view without changingthe viewing angle. Selection is achieved by using the left button of thepointing device and dragging the pointer to create the desired viewing region.

5.4.6 Move SAR Legend

The button allows for the operator to move the SAR legend to a moredesirable position in the 3D display window. Movement is achieved by usingthe left button of the pointing device and dragging the pointer.

5.4.7 Rotate display 90

The button will change the display, at the current zoom, to the 2Dview (see next section) if not already there, and rotate it 90 anti-clockwisefor each press thereafter.

5.4.8 2D View

The button changes the viewing angle of the display to be looking‘down’ squarely at the device and zooms in on the measurement region.

5.4.9 Measurement View Only

The button removes the reference and difference views and only dis-plays the measurement view.



5.4.10 Tile Views

The button tiles all three display views (measurement, reference, dif-ference) with equal spacing.

5.4.11 Display Saved View 1

The button changes the view to the first saved view. To change thesaved views, see Section 5.5.1.5.


The button changes the view to the second saved view. To change thesaved views, see Section 5.5.1.5.


The button changes the view to the third saved view. To change thesaved views, see Section 5.5.1.5.

5.4.14 Smooth/Contoured Colour Display

The button toggles the display colour shading to be contoured (dis-cretized) or smooth (non-discretised).

5.4.15 Log/Linear Scaling

The button toggles the display data scaling between linear and loga-rithmic.

5.4.16 Manual/Auto Ranging

The button toggles the display range between auto-ranging and thedesired manual settings as configured in the display dialog described in Sec-tion 5.3.3.4.



5.4.17 Python Interpreter Window

For those who like to program and would like to use iSAR2 with other 3rd

Party devices, the button displays/hides the Python interpreter whichcan be used to integrate iSAR2 with anything imaginable.

This interpreter is powered by IronPython and the Microsoft .NETframework that forms part of the Windows Operating System. The im-plications of this are that anything that is possible in the .NET frameworkis possible from this interpreter interface.

More detailed information about using IronPython for iSAR can befound in Appendix B: IronPython Application Programming Interface. Formore details regarding IronPython, see also (http://www.codeplex.com/IronPython).There is a useful tutorials section that can be downloaded.

An example of how to use the iSAR2 from this Python interface canbe found in ‘CoreEx.py’ found in the application directory that is part ofthe software distribution. A basic GPIB interface is also exposed throughPython, but you may wish to use a different one.

The following figure illustrates how to invoke this example script. Theexample creates a simple thread using the System.Threading.Threadclass in the .NET framework that sleeps for 3 seconds and then calls theAcquire method of the iSAR2 Core engine selected in the test script. EachiSAR2 configured by calibration is accessible via this interface.

The Core engines exposed by this interface are the same ones used inthe iSAR2 application, and so all GUI configurations apply.

Please note that almost anything that we have not yet thought aboutis possible via this interface. For more information, good suggestions orwishes, feel free to email us at [email protected].

5.4.18 Auto-Save Measurement Log Window

The button displays/hides the auto-save measurement log window.The corresponds to the ’All Measurements’ log file and is disabled when thislogging feature is disabled. The format is the same as the log file output.See Section 5.3.3.8: Auto-Save and Logging, for more information.

5.5 iSAR2 Measurement Display Views

5.5.1 Quick Access Commands

Right clicking anywhere in one of the three display view subwindows givesquick access to the following command groupings.


http://www.codeplex.com/IronPython


Figure 5.25: Python Interpreter Window

5.5.1.1 Install iSAR2

The Install iSAR quick access command should be used to install new iSAR2

devices into your system as well as to upgrade currently installed iSAR2

devices with the latest calibration files, as supplied by SPEAG.All that is required is to navigate to the folder containing calibration

files of iSAR2 devices that you would like to install.When prompted to do so, restart the iSAR2 application to effect these

configuration changes.This command works recursively on a folder.

5.5.1.2 Zero iSAR2

The Zero iSAR button acquires a measurement used to compensate for thesensors’ offset voltages 1. Before beginning the zeroing measurement, ensure

1Offset voltages may be present in the sensors and electronics. In order to allowaccurate measurement of low SAR levels, these incidental offsets must be compensatedfor. The Zero iSAR command measures the voltages present and applies a compensationin the E-field and SAR evaluations. Further, it provides a quick sanity check of the setup,and causes a warning to be issued in the case of excessive offset voltages, because in such



Figure 5.26: Auto-Save Measurement Log Window

Figure 5.27: Quick access command groups

that any radiating devices close to the iSAR2 are switched off and have beenso for a few minutes. Furthermore, if your iSAR2 came with a shieldingcover, put the shielding cover on top of the iSAR2 before the offset voltagesare measured in order to minimize effects due to residuals. If not, ensureall radiating sources are nowhere near the iSAR2. Measured offsets remainin effect until you exit the iSAR2 application. A warning message pops upif the offset voltages exceed a specified limit. Please follow the instructionsgiven there. Static effect values from the calibration will be applied in thecase that the Zero iSAR command is not used.

5.5.1.3 Combiner

The combiner commands allow for adding measurements to be combined,and clearing combined measurements.

5.5.1.4 Reference Measurement

The ‘reference measurement’ commands allow for:

• The selection of a measurement as the reference (or golden) measure-ment, by either using the current measurement in memory or import-

cases the validity of the calibration could be affected.



Figure 5.28: ‘Combiner’ quick access commands

ing a measurement that has been stored somewhere on disk.

• Comparison of the current measurement to the reference measurement.

• Clearing of the reference measurement.

Figure 5.29: ‘Reference Measurement’ quick access commands

5.5.1.5 Save Views

The ‘save views’ commands allow for persistant storing of three desireddisplay views.

Figure 5.30: ‘Save view’ quick access commands

5.5.1.6 Configuration Settings

The ‘configuration settings’ commands allow for configuration of device andapplication settings in the secondary tab of the ribbon control. See Section5.3.3: iSAR2 Configuration for more details.



Figure 5.31: ‘Configuration Settings’ quick access commands



5.6 Message Bar

Figure 5.32: Message Bar with ’clear’ menu

The message bar provides useful informational, warning and error mes-sages.

The height of the message bar can be adjusted using the pointing deviceto click and drag the bar between the message bar and the 3D-Displaywindows.

The icon on the left within the message bar indicates the lowest level ofmessages that has been displayed since start-up or clearing of this display.

Message levels are categorized from highest to lowest as such:

• Information.

• Warning.

• Error.

The message bar can be cleared by right-clicking anywhere on its surfaceto bring up its context menu, and then selecting ’clear’



5.7 Status Bar

Figure 5.33: Status Bar on GUI bottom

The Status Bar displays status of the currently selected iSAR2 device.It is split into three visible sections:

• A status update. This is used to display the iSAR2 temperatureswhen the iSAR2 is idle, or the progress status of the current operation,followed by the measurement acquisition time.

• The the most recent calibration date of the currently selected iSAR2

device.

• NUM, SCROLL and CAPS lock enabled states.


Index

2D View, 57

Acquisition, 41Auto-Save and Logging, 54Auto-Save Measurement Log Window,

59Average SAR, 17, 19, 49

Calibrated Source, 46Calibration, 7, 14, 34CMU200, 42, 52, 54COM Port, 26Combined Measurement, 61Combiner, 18, 49, 50Communication systems, 7Comparison, 17, 51Configuration, 62Conformity, vii, 3Connections, 23Connector, 6Cover Plate, 2CRANE, 11

DASY, 45, 68Data Evaluation, 16Device Drivers, 23, 28Device Under Test, 47Dimensions, 5, 7Display, 49Display Components, 46Display saved view 1, 58Display saved view 2, 58Display saved view 3, 58Disposal, 3

Environment, 8

Functional Description, 4

Green normal vector, 39

Hardware, 4, 21Head, 7

Installation, 21Interpolation, 17, 18iSAR Flat, 8iSAR Head, 10iSAR2, 5iSAR2 GUI, 16, 37, 38iSAR2 GUI System Requirements, 38

Link, 6Loading DASY files, 45, 46Log/linear scaling, 58

Main Menu, 40Maintenance, 8Manual/auto ranging, 58Map, 18Match, 18Material Safety Data Sheet, 86Measurement, 42, 47Measurement view only, 57Medium, 7MOTOROLA FAST SAR, 17Move SAR legend, 57Multiple Device Support, 41

National Instruments GPIB Adapter,35

Offset Compensation, 60Operation, 37Orbit, 56

Pan, 56

66

INDEX Usage

Parts, 5Plate, 2Python, 59–61, 72

Quick Access Commands, 59–62

Radiation, 7Reference Measurement, 43, 61Registration, 17, 18Repeatability, 7Reverse Combination, 50RF Radiation, 3Ribbon bar, 40–42, 44, 46–49, 65Rotate display 90, 57

Safety, 2SAR Tolerance, 52Scaling, 17, 51Sensors, 7, 9Shielded Room, 3Shock, 2Smooth/Contoured colour display, 58Software, 23Spatial Tolerance, 18, 52Specifications, 7Status, 65

Temperature, 7Tile Views, 58Timesweep, 42, 48Toolbar, 56

Unpacking iSAR Flat, 21Unpacking iSAR Head, 22USB, 6, 24, 29

Value Tolerance, 18Ventilation, 2, 7

Weight, 2, 5, 21Windows 7, 28Windows XP, 23

Zero, 41, 60Zoom All, 57Zoom In/Out, 56Zoom Selection, 57


Appendix A

Performance Evaluation ofiSAR2 versus DASY

68

Intermediate Report

Performance Evaluation ofiSAR2 versus DASY5 and/or DASY4

Sergey Perov1, Claudio Leubler2 , Jeton Kastrati2,Sven Kuhn1, Niels Kuster1

1 IT’IS Foundation, 2 SPEAG

Zurich, February 2009

Executive Summary

The IT’IS Foundation was mandated by SPEAG (Switzerland) to compare the peak spatialSAR values assessed with the iSAR2 systems to those determined with the DASY systems byapplying standard protocols. The following steps were performed for the comparison:

• Twelve phones were selected by the IT’IS Foundation and purchased in Zurich. Theselection criteria included a wide representation of current phone designs (candy-bar (CB),clam-shell (CS) and slider (S) phones), reported SAR values and sizes.

• Each phone was evaluated with a DASY4 and/or DASY5 system by one or two opera-tors. The measurement protocol strictly followed the standardized procedures as definedin IEC62209-I and IEC62209-II, whereby both the 1 g and 10 g values were evaluated.Additional measurements were conducted to resolve any discrepancies.

• Each phone was measured with an iSAR Head and iSAR Flat (Software Version 2.0 Beta)by different operators. Each measurement was based on 10 single measurements that wererandomly shifted on the grid, i.e., along the ear line for iSAR Head and in all directionsparallel to the top plate including rotations for iSAR Flat. The upper part of the DASY5device holder was also mounted to the devices for iSAR evaluations to eliminate the po-tential differences of measurements with and without the holder on the induced fields. Thevalues shown in Table 1 represent the average of all the measurements, varying less than0.3 dB.

The results summarized in Table 1 provide the average, standard deviations and maximumand minimal differences. Since iSAR head is based on the ear-point to mouth line, it representsabsorption conditions that are between left and right hand sides. Thus, the iSAR values werealso compared to the average of both head-side DASY measurements. The following observationsand conclusions were made:

• the average deviations are less than 0.5 dB except when the phone is positioned to be indirect contact with the surface of the flat phantom (d = 0 mm).

• the standard deviations of less than 0.5 dB and the maximum deviations of less than±1.2 dB exceed expectations, particularly for the head phantom.

• iSAR Flat underestimates the exposure, especially for patterns with extreme hotspots.An obvious but not yet verified explanation is that iSAR Flat ignores the z-componentand only measures in one plane that is 4 mm below the surface while DASY measuresall components in 3D. Since the decay is much steeper and the Z-components are morepronounced for very localized exposures, a significant underestimation of the exposure mayresult. However, additional studies are required to determine the cause of these deviationsof up to nearly 3 dB and to develop compensation algorithms.

• in some cases, the phone holder had a significant impact on the induced fields. iSAR,however, can also be used to verify that the holder does not increase the SAR based ontolerated standards.

• the iSAR2 systems have proven to be very effective tools for reliable estimations of the peakspatial SAR values while offering excellent reproducibility, particularly when applying thecombiner.

2

Phon

e&

Syst

emiS

AR

Hea

dvs

DA

SY

5&4

iSA

RFla

tvs

DA

SY

5&4

Pho

neM

odel

Syst

emH

ead

Rig

htH

ead

Lef

tA

vera

geL

&R

Fla

tP

hant

omT

ouch

Tou

chT

ouch

d=

0m

md

=15

mm

1g10

g1g

10g

1g10

g1g

10g

1g10

gdB

dBdB

dBdB

dBdB

dBdB

dB

Nok

ia(C

B)

6120

GSM

900

-0.5

-0.7

-0.5

-0.7

-0.6

-0.8

-0.6

0.0

0.3

0.3

Nok

ia(C

B)

6120

UM

TS

0.0

0.0

-0.1

0.0

-0.1

0.0

-0.1

0.1

0.3

0.3

Mot

orol

a(C

S)v1

050

GSM

900

-1.0

-1.1

-1.1

-1.2

-1.0

-1.2

-0.4

0.0

0.0

0.0

Mot

orol

a(C

S)v1

050

UM

TS

-0.1

-0.1

0.2

0.1

0.1

0.0

0.2

0.4

0.1

0.1

Nok

iaN

avi

(S)

6111

GSM

900

-0.1

-0.4

-0.7

-0.9

-0.6

-0.8

-0.5

-0.4

0.0

0.0

Nok

iaN

avi

(S)

6112

UM

TS

0.0

-0.4

-0.4

-0.5

-0.2

-0.4

-1.1

-0.6

-0.3

-0.2

LG

(CB

)K

U99

0G

SM90

0-0

.5-0

.6-0

.3-0

.4-0

.4-0

.5-2

.0-1

.00.

0-0

.1L

G(C

B)

KU

994

UM

TS

0.9

0.6

-0.2

-0.3

0.3

0.1

-0.6

-0.2

0.0

0.0

iPho

ne(C

B)

8GB

GSM

900

-0.1

-0.5

-0.2

-0.7

-0.2

-0.6

-0.5

0.2

-0.4

-0.6

iPho

ne(C

B)

8GB

UM

TS

-0.9

-1.2

-0.9

-1.2

-0.9

-1.2

-0.7

0.1

0.6

0.6

Sony

(S)

W76

0iG

SM90

0-0

.1-0

.4-0

.5-0

.7-0

.3-0

.6-0

.8-0

.6-0

.6-1

.1So

ny(S

)W

760i

UM

TS

1.6

1.2

0.3

0.1

0.9

0.6

-1.2

-1.0

0.1

0.1

HT

C(C

B)

P37

00G

SM90

0-0

.3-0

.6-0

.1-0

.4-0

.3-0

.6-1

.1-0

.7-0

.1-0

.2H

TC

(CB

)P

3700

UM

TS

0.1

-0.3

-1.4

-1.4

-0.7

-0.9

-1.2

-0.5

-0.1

0.0

Mot

orol

a(C

S)v9

80G

SM90

0-0

.5-0

.4-0

.9-1

.1-0

.7-0

.8-1

.1-0

.80.

40.

4M

otor

ola

(CS)

W37

5G

SM90

0-1

.1-0

.60.

10.

3-0

.5-0

.2-1

.1-1

.2-1

.2-1

.1N

okia

(CS)

6085

GSM

900

0.9

0.9

0.1

0.0

0.5

0.4

-1.7

-1.5

0.3

0.3

Sam

sung

(S)

J700

GSM

900

-0.1

-0.2

0.1

0.0

0.0

-0.1

-0.6

-0.5

1.2

1.1

Sony

Eri

csso

n(C

B)

K70

0iG

SM90

0-0

.10.

0-0

.5-0

.5-0

.3-0

.3-2

.7-2

.1-0

.4-0

.4A

vera

ge-0

.1-0

.3-0

.4-0

.5-0

.3-0

.4-0

.9-0

.50.

00.

0St

dev

0.7

0.6

0.5

0.5

0.5

0.5

0.7

0.6

0.5

0.5

Max

1.6

1.2

0.3

0.3

0.9

0.6

0.2

0.4

1.2

1.1

Min

-1.1

-1.2

-1.4

-1.4

-1.0

-1.2

-2.7

-2.1

-1.2

-1.1

Tab

le1:

Dev

iati

ons

ofth

epe

aksp

atia

lSA

Rva

lues

asse

ssed

byiS

AR

Hea

dan

diS

AR

Fla

tco

mpa

red

toth

eva

lues

obta

ined

byD

ASY

5an

dD

ASY

4fo

rva

riou

sph

ones

mea

sure

dat

GSM

900

and

UM

TS

(CB

:ca

ndy-

bar,

CS:

clam

-she

llan

dS:

slid

erph

ones

)

3

Appendix B

IronPython ApplicationProgramming Interface(API)

72

CONTENTS 1

Contents

1 Module Index 1

1.1 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 Class Index 1

2.1 Class List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

3 Module Documentation 1

3.1 GridPointState Enumeration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

4 Class Documentation 1

4.1 iSAR::CommunicationSystemHelper Class Reference . . . . . . . . . . . . . . . . . . . . 1

4.1.1 Detailed Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

4.1.2 Member Function Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . 2

4.2 iSAR::Core Class Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3



4.3 iSAR::Gpib Class Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4



4.4 iSAR::GridPoint Class Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5


4.4.2 Property Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4.5 iSAR::Measurement Class Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6


4.5.2 Constructor & Destructor Documentation . . . . . . . . . . . . . . . . . . . . . . 6



4.6 iSAR::Position Class Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8



5 Example Documentation 8

5.1 CoreEx.py . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Generated on Wed Jun 17 16:43:56 2009 for iSAR 2.0 by Doxygen

1 Module Index 2

1 Module Index

1.1 Modules

Here is a list of all modules:

GridPointState Enumeration 1

2 Class Index

2.1 Class List

Here are the classes, structs, unions and interfaces with brief descriptions:

iSAR::CommunicationSystemHelper 1

iSAR::Core 3

iSAR::Gpib 4

iSAR::GridPoint 5

iSAR::Measurement 6

iSAR::Position 8

3 Module Documentation

3.1 GridPointState Enumeration

This enum forms the IronPython ’core’ grid point state.

iSAR::GridPointState Unknown, Missing, Valid, OutOfRange ;

4 Class Documentation

4.1 iSAR::CommunicationSystemHelper Class Reference

Public Member Functions

• Dictionary< int, String∧ >∧ GetAvailableCalibrations ()• void SetCalibration (int iCal)• void SetChannel (int iChan)• void SetFrequency (double dFreq)• bool IsChannelFrequencyMapAvailable ()• Dictionary< int, double >∧ GetAvailableChannelsAndFrequencies ()


4.1 iSAR::CommunicationSystemHelper Class Reference 3

4.1.1 Detailed Description

This class forms the IronPython ’communications’ utility module. This module should be used whensetting desired communications system calibrations, channels or frequencies.

4.1.2 Member Function Documentation

4.1.2.1 Dictionary<int, String∧> ∧

iSAR::CommunicationSystemHelper::GetAvailableCalibrations()

Retrieve all available calibrations.

Returns a dictionary of KEY:VALUE mappings of all available calibrated communication systems currentlyconfigured for iSAR.

Use the integer KEY values when selecting a particular communications system.

For more help on the dictionary type, please see:

http://msdn.microsoft.com/en-us/library/xfhwa508.aspx .

4.1.2.2 Dictionary<int, double> ∧

iSAR::CommunicationSystemHelper::GetAvailableChannelsAndFrequencies ()

Retrieve all available channels and frequencies.

When the currently selected iSAR calibration’s mapping is known, this returns a dictionary of CHAN-NEL:FREQUENCY. In this case you must use only one of these provided channels/frequency’s whensetting the desired channel or frequency. Setting the channel will also set the mapped frequency and viceversa.

In the cases where they are not available, only ’frequency’ may be set within the range defined by thecalibration.

If this function is called when no mapping is known, and exception will be raised.

4.1.2.3 bool iSAR::CommunicationSystemHelper::IsChannelFrequencyMapAvailable ()

Indicates the availability of channel-to-frequency mapping for current calibration.

Returns ’true’ when the currently selected iSAR calibration’s CHANNEL:FREQUENCY mapping isknown. In this case the mapping should be retrieved by calling ’GetAvailableChannelsAndFrequencies’and only these values may by used. ’Channel’ or ’Frequency’ may be set. Setting the ’channel’ will mapthe correct ’frequency’ and vice versa.

Returns ’false’ when not known. In this case only ’frequency’ may be set, and this is limited to a range asdetermined by the calibration. This range may by attained by calling ’GetFrequencyRange’.


4.2 iSAR::Core Class Reference 4

4.1.2.4 void iSAR::CommunicationSystemHelper::SetCalibration (int iCal)

Set source device calibrated communication system.

Selects the desired input calibration in iSAR.

Input parameter is the calibrations KEY value. All KEYs can be obtained with the ’GetAvailableCalibra-tions()’ method.

4.1.2.5 void iSAR::CommunicationSystemHelper::SetChannel (int iChan)

Set source device transmission channel.

Selects the desired communications channel of the currently configured iSAR calibration.

Input parameter is the desired ’channel’ number.

This function should be called ONLY if the call to ’IsChannelFrequencyMapAvailable()’ returns ’true’,otherwise frequency should be set.

4.1.2.6 void iSAR::CommunicationSystemHelper::SetFrequency (double dFreq)

Set source device transmission frequency.

Selects the desired communications frequency of the currently configured iSAR calibration.

Input parameter is the desired ’frequency’.

The documentation for this class was generated from the following file:

• Core_Net.h

4.2 iSAR::Core Class Reference


• void Acquire ()• Measurement∧ GetMeasurement ()


This class forms the IronPython ’core’ module.

This module can be seen as representing the iSAR hardware.

Typically one would want to trigger SAR measurement acquisition from this module and also possibly re-trieve these measurements themselves. The iSAR GUI software auto-save and logging feature (see chapter’5.3.3.8 Auto-Save and Logging’ in the iSAR System Handbook) still functions when triggering ’Acquire’through this ’core’ module via IronPython.

Please note: not all entities of this class are documented, only those suggested for external use.


4.3 iSAR::Gpib Class Reference 5


4.2.2.1 void iSAR::Core::Acquire ()

Take a SAR reading.

Triggers SAR measurement acquisition in iSAR.

4.2.2.2 Measurement ∧ iSAR::Core::GetMeasurement ()

Get last SAR measurement. This returns the last acquired SAR measurement.


• Core_Net.h

4.3 iSAR::Gpib Class Reference


• void Send (int gpib_address, String∧ command)• String∧ SendReceive (int gpib_address, String∧ command)


This class forms the IronPython ’gpib’ module.

Use this module for scripting integration of 3rd party devices that communicate via GPIB.

Typical such devices one may want to automate processes and thus synchronize iSAR core module mea-surements with could be:

• Agilent 8960,

• Rohde&Schwarz CMU200, but there may be many others that you may need in your application ofiSAR. If so, this is the place to do such things.


4.3.2.1 void iSAR::Gpib::Send (int gpib_address, String∧ command)

Send to device.

Use this command to transmit GPIB commands that do not require a command-response. These commandstypically do NOT end in a ’?’.

Inputs are the GPIB device address and the GPIB command string.


4.4 iSAR::GridPoint Class Reference 6

4.3.2.2 String ∧ iSAR::Gpib::SendReceive (int gpib_address, String∧ command)

Send to device and return response.

Use this command to transmit GPIB commands that require a command-response. These commands typi-cally end in a ’?’.

Inputs are the GPIB device address and the GPIB command string.

Return value is the device response string.


• Core_Net.h

4.4 iSAR::GridPoint Class Reference

Properties

• GridPointState State [get, set]• double Value [get, set]• iSAR::Position Position [get, set]


This class forms the IronPython ’core’ GridPoint.

It is represents the Position, GridPointState and value of a measurement point, for the selected measurementquantity, in a grid of measurements as returned by the iSAR.

4.4.2 Property Documentation

4.4.2.1 iSAR:: Position iSAR::GridPoint::Position [get, set]

See Position.

4.4.2.2 GridPointState iSAR::GridPoint::State [get, set]

See GridPointState Enumeration.

4.4.2.3 double iSAR::GridPoint::Value [get, set]

Value of the gridpoint for the selected quantity.


• Core_Net.h


4.5 iSAR::Measurement Class Reference 7

4.5 iSAR::Measurement Class Reference


• Measurement ()• ∼Measurement ()• Grid∧ GetVoltageComponent (int icomp)• Grid∧ GetVoltage ()• Grid∧ GetSarComponent (int icomp)• Grid∧ GetSar ()• double GetAveragedSar (double mass_g)• void Save (System::String∧ path)• void Load (System::String∧ path)

Properties

• System::DateTime AcquisitionDateTime [get]


This class represents the IronPython ’core’ measurement. A measurement contains all data relevant to aSAR acquisition at a particular point in time.

4.5.2 Constructor & Destructor Documentation

4.5.2.1 iSAR::Measurement::Measurement ()

Create an empty measurement.

4.5.2.2 iSAR::Measurement::∼Measurement ()

Measurement destructor. This should not be necessary as managed IronPython uses .NET memory man-agement.


4.5.3.1 double iSAR::Measurement::GetAveragedSar (double mass_g)

Return averaged SAR. This computes the averaged SAR for a given mass per gram. Input mass in gram,and the averaged SAR is returned.

4.5.3.2 Grid ∧ iSAR::Measurement::GetSar ()

Return iSAR total SAR. This extracts the iSAR sensor grid SAR values as a combined total.


4.5 iSAR::Measurement Class Reference 8

4.5.3.3 Grid ∧ iSAR::Measurement::GetSarComponent (int icomp)

Return iSAR component SAR values. This extracts the iSAR sensor grid SAR values per component.

• For the X-directional sensors only, input 0.

• For the Y-directional sensors only, input 1.

4.5.3.4 Grid ∧ iSAR::Measurement::GetVoltage ()

Return iSAR total voltages. This extracts the iSAR sensor grid voltages values as a combined total.

4.5.3.5 Grid ∧ iSAR::Measurement::GetVoltageComponent (int icomp)

Return iSAR component voltage values. This extracts the iSAR sensor grid voltage values per component.

• For the X-directional sensors only, input 0.

• For the Y-directional sensors only, input 1.

4.5.3.6 void iSAR::Measurement::Load (System::String∧ path)

Load measurement from disk.

4.5.3.7 void iSAR::Measurement::Save (System::String∧ path)

Save measurement to disk. This saves the measurement to disk at desired location with desired filename.Please note that if ’auto-save and logging’ is enabled in the GUI (which it is by default), each measurementtaken with the ’Acquire’ function is stored already. This should only be used to store a specific measurmentin a specific place.


4.5.4.1 System:: DateTime iSAR::Measurement::AcquisitionDateTime [get]

Measurement acquisition information. This returns a System::DateTime structure describing the acquisi-tion date and time of this measurement.


• Core_Net.h


4.6 iSAR::Position Class Reference 9

4.6 iSAR::Position Class Reference

Properties

• double X [get, set]• double Y [get, set]• double Z [get, set]


This class forms the IronPython ’core’ position.

It represents the spatial position of measurement point in a grid of measurements as returned by the iSAR.


4.6.2.1 double iSAR::Position::X [get, set]

X axis position of this point.

4.6.2.2 double iSAR::Position::Y [get, set]

Y axis position of this point.

4.6.2.3 double iSAR::Position::Z [get, set]

Z axis position of this point.


• Core_Net.h

5 Example Documentation

5.1 CoreEx.py

The following example file is included in the iSAR Software source distribution.

All illustrative example functions are prefixed with ’example_’.

#--------------------------------------------------------------------------------

## CoreEx.py##--------------------------------------------------------------------------------


5.1 CoreEx.py 10

## Description## This example demonstrates the use of the iSAR IronPython interface# and some .NET Framework classes via the IronPython interpreter in the iSAR# GUI software.## For more information, please see:## ’iSAR System Handbook v2.x’, 5.4.15(Python Interpreter Window).##--------------------------------------------------------------------------------

## Available Modules## ’core’ - The iSAR hardware can be controlled/accessed via this module.# ’gpib’ - 3rd party devices (like the Agilent 8960 or Rohde&Schwarz CMU200 or

# any device with a GPIB interface) can be controlled using 3rd party

# GPIB adapters via the ’gpib’ module.# ’comsys’ - The iSAR calibrated communication systems utility.##--------------------------------------------------------------------------------

## Some useful information:## IronPython allows for the use of Python modules (excluding C libraries)# as well as the entire .NET Framework, from a python scripting interface.# iSAR only incorporates .NET 2.0. For more information on IronPython,# please see http://www.codeplex.com/Wiki/View.aspx?ProjectName=IronPython.## The .NET framework API can be readily found on the internet.##--------------------------------------------------------------------------------

## Author : Eugene Grobbelaar# email : [email protected] | [email protected]## Copyright (c) 2009 Schmid & Partner Engineering AG, Zurich, Switzerland##--------------------------------------------------------------------------------

#--------------------------------------------------------------------------------

## Necessary .NET Framework modules...#import Systemimport clrimport math

## Adjust the path to the iSAR.dll in your configuration.# For the default iSAR installation this should be correct.## this is the release way...clr.AddReferenceToFileAndPath("iSAR.dll")

## The modules we want to use exist in the ’iSAR’ namespace#import iSAR


5.1 CoreEx.py 11

from iSAR import core # this is the iSAR hardware ’core’from iSAR import gpib # this is the iSAR raw gpib interfacefrom iSAR import comsys # this is the iSAR utility you must use for working with

# the communication systems your iSAR is calibrated for.

## .NET Framework Threading support.## AS a starter, and and an example of how one can use the# .NET framework to develop custom scripting I chose to create# a .NET thread that does something.## See:# http://msdn.microsoft.com/en-us/library/e1dx6b2h.aspx#from System.Threading import Thread, ThreadStart

## This example function loads an iSAR measurement file from# disk and displays 1g and 10g averaged SAR.#def example_DumpFileOnHarddisk():

# create empty measurement...measurement = iSAR.Measurement()# load the measurement file from disk -> substitute this for# a valid measurement on your disk...measurement.Load("c:\\center_ref.iSAR")print "Acquisition Time:", measurement.AcquisitionDateTimeprint "Avg. SAR 1 g:", measurement.GetAveragedSar(1.0), "W/kg"print "Avg. SAR 10 g:", measurement.GetAveragedSar(10.0), "W/kg"# print the SAR measurement grid...sar = measurement.GetSar()# X size dimension = element 0 of the array.# Y size dimension = element 1 of the array.Nx = sar.Size[0]Ny = sar.Size[1]for ix in range(Nx):

for iy in range(Ny):# This is a measurement point...to see all members AFTER# extracting the point do ’print dir(pt)’pt = sar.At[ix, iy]print pt.Position.X, pt.Position.Y, pt.Value

## Let a thread take a measurement every 3s until it is told to abort...#def RunProc():

while True:try:

# This aquires a measurement on the iSAR hardware...core.Acquire()# execute the loop every 3000ms...its in anycase a good# idea to wait a while for the ’Acquire’ action to# complete before a measurment is retrieved.System.Threading.Thread.Sleep(3000)# Retrieve the measurment from the core...meas = core.GetMeasurement()print "*****************"print "Acquisition Time:", meas.AcquisitionDateTimeprint "Avg.SAR 1g:", meas.GetAveragedSar(1.0), "W/kg"print "Avg.SAR 10g:", meas.GetAveragedSar(10.0), "W/kg"

except Exception, e:print e.args # arguments stored in .argsexample_ThreadSuspend()


5.1 CoreEx.py 12

t = Thread(ThreadStart(RunProc))

## This starts a test thread looping every 3s, taking a measurement,# displaying the acquisition time and 1g/10g averaged sar to the console.#def example_ThreadStart():

if t.IsAlive:t.Resume()print ’Resuming test thread...’

else:t.Start()print ’Starting test thread...’

## This suspends the test thread.#def example_ThreadSuspend():

print ’Suspending test thread...’t.Suspend()

## This terminates the test thread.#def example_ThreadEnd():

t.Abort()

## The GPIB interface is very simple:## ’send’ - this transmits a GPIB string synchronously# to the connected device. This should only be used# for those commands that have no response i.e.# commands that dont end in a ’?’.## ’sendreceive’ - this transmits a command and returns the response# synchronously. This should only be used for# those commands that have a response i.e.# commands that end with a ’?’.## The following function queries the identity of a connected device# at gpib address 10.#gpibaddress = 10def example_QueryGpibDeviceIdentity():

devID = gpib.SendReceive(gpibaddress,"*IDN?")print devID

def example_ExcerciseComsSys():## Get a .NET dictionary of all available calibrations.## A dictionary is a map of key-value pairs. In this case its an#’int:string’mapping.# The string is the name represented in the iSAR GUI element where# calibrations are set.# The key is an integer number you should use to set the desired# calibration in your iSAR.dictOfCal = comsys.GetAvailableCalibrations()

print ’\n<--------------- Currently available calibrations:’for i in dictOfCal.Keys:

print ’(’,i,’)’, dictOfCal[i]

# PLEASE NOTE: This example was created for ’GSM 1800’ which is# calibration 4 on my list...


5.1 CoreEx.py 13

selCal = 4

# SO now you know what the available coms systems are...you can set them# using the keys returned by the dictionary like this:print ’\n<--------------- Setting calibration : ’,dictOfCal[selCal]comsys.SetCalibration(selCal);

# For channels/frequencies the iSAR built-in intelligence has to be# utilised. Most communication systems ’channel:frequency’ mappings# are available in the iSAR, but not all. In the case where they are# available, you must use only ’channels/frequencies’ provided by the# ’comsys’ module. In the cases where they are not available, only# ’frequency’ may be selected within range defined by the calibration.## To determine whether the selected calibration’s ’channel:frequency’# mapping is known:chFrMap = 0;

if(comsys.IsChannelFrequencyMapAvailable()):print ’\n|*> Channel:frequency map for ’,dictOfCal[selCal],’:’## The currently configured calibration’s frequency:channels are# mapped and known...do the following...## Get a .NET dictionary of all channel:frequency mappingschFrMap = comsys.GetAvailableChannelsAndFrequencies()# These are all the channels and frequencies configurable in iSAR

for j in chFrMap.Keys:print ’channel ’,j,’ = ’,chFrMap[j],’ MHz’

print ’\n|*> Selecting ch ’,513,’ (= freq ’,chFrMap[513],’ MHz)’comsys.SetChannel(513);print ’\n|*> Selecting freq ’,chFrMap[515],’ MHz (= ch ’,515,’)’comsys.SetFrequency(chFrMap[515])

#else:## The currently configured calibration’s frequency:channels are# not known...so frequency can be manually set.#


Appendix C

Material Safety Data Sheet

86

Doc No 772 – SL AGx U12 – A Page 1 (2)

Material Safety Data Sheet 1 Identification of the substance and of the manufacturer / origin Item Head Tissue Simulation Gel U12

Muscle Tissue Simulation Gel U12 Type No SL AGH U12, SL AGM U12,

used e.g. in iSAR types SD 001 002 GF, SD 001 003 GF, SD 003 001 BE Series No N/A Manufacturer / Origin Schmid & Partner Engineering AG

Zeughausstrasse 43 8004 Zürich Switzerland Phone +41 44 245 9700, Fax +41 44 245 9779, [email protected]

Use of the substance: Gel simulating physical parameters of Head or Muscle Tissue in the RF range to several GHz. The gel is embedded in a closed absorbing block inside the iSAR 2 Composition / Information on ingredients The Item is composed of the following ingredients: H2O Water, 55 – 80% Emulgators,Gelatinizers 15 – 30% Vegetable Oil 5 – 20% NaCl Sodium Chloride, 0 – 1% Preventol-D7 Preservative, 0.1 – 0.2%

aqueous preparation, (CAS# 55965-84-9), containing 5-chloro-2-methyl-3(2H)-isothiazolone and 2-methyyl-3(2H)-isothiazolone, relevant for safety; Refer to the respective Safety Data Sheet*.

3 Hazards identification Symbol Xi Irritant R-phrases: 36/38 Irritating to eyes and skin 43 May cause sensitization by skin contact 4 First aid measures After skin contact: Wash off with plenty of water and soap After eye contact: Rinse out with plenty of water with the eyelid held open, call an ophthalmologist After swallowing: Make victim drink plenty of water, the mouth should be rinsed out several times. Do not induce vomiting. 5 Fire-fighting measures Not required 6 Accidental release measures Do not allow to enter sewerage system in large quantities. The preservative can be destroyed with sodiumhydrogensulfite. The material is pudding-like at room temperature and can be dried in air (by evaporation of water) before disposal. 7 Handling and storage Handling: Keep in open container not exposed to air to avoid water evaporation. Storage: No special measures against fire or explosion required.

Doc No 772 – SL AGx U12 – A Page 2 (2)

8 Exposure controls / personal protection Hand protection: e.g. rubber or plastic gloves Avoid contact with skin and eyes. Wash hands after working with substance. 9 Physical and chemical properties Form: elastic pudding-like at room temperature, high viscous liquid at > 60°C Colour: yellowish to light brown, opaque Odour: odorless pH-Value: neutral, with tendency to lower pH values. Boiling point: 100°C Density: ~ 1 g/cm^3 10 Stability and reactivity No hazardous decomposition products expected. 11 Toxicological information Irritation to skin and eyes: tendency to corrosive reaction due to contained preservative. In susceptible people, sensitization is possible. 12 Ecological information Do not allow to enter waters, waste water, or soil. In order to avoid adverse effects on the degradation activity of a sewage plant due to the preservative contained, the preservative concentration must not exceed 3mg/l, which up to 1000 times lower than the amount contained. Considerable amounts of water must therefore be added to amounts spilled into sewers or waste water. 13 Disposal considerations If the unit containing the gel is not opened or damaged, the gel is inert. If removed from the container, the gel can be disposed of by incineration. To reduce the volume, its amount can be reduced by drying (water evaporation) in air. The preservative can be destroyed with sodiumhydrogensulfite. 14 Transport information Not subject to transport regulations. No UN number is applicable Avoid temperatures below 0°C and above 40 °C. 15 Regulatory information Labeling according to EC Directives Symbol Xi Irritant R-phrases: 36/38 Irritating to eyes and skin 43 May cause sensitization by skin contact MAK value for the preservative is 0.05mg/m^3, corresponding to a concentration of <25mg/m^3 of the final product. 16 Other information * Safety relevant information bases on: [1] MSDS for Preventol D7 (Art.Nr.: 329049/08 by Bayer AG, Leverkusen, Germany ) Release date: 09.07.2010 Responsible: FB

Documents

iSAR System Handbook v2.2