IEC TR 61967-1-1:2010

Integrated circuits - Measurement of electromagnetic emissions - Part 1-1: General conditions and definitions - Near-field scan data exchange format

IEC/TR 61967-1-1:2010 provides guidance for exchanging data generated by near-field scan measurements. The described exchange format could also be used for near-field scan data generated by simulation software. It should be noted that, although it has been developed for near-field scan, its use is not restricted to this application. The exchange format can be applied to emission, immunity and impulse immunity near-field scan data in the frequency and time domains. The scope of this technical report includes neither the methods used for the measurements or simulations, nor the software and algorithms used for generating the exchange file or for processing or viewing the data contained therein.
This publication contains colours which are considered to be useful for the correct understanding of its contents.

Circuits intégrés - Mesure des émissions électromagnétiques - Partie 1-1: Conditions générales et définitions - Format d'échange de données de cartographie en champ proche

La CEI/TR 61967-1-1:2010 constitue un guide pour l'échange de données générées par des mesures de cartographie en champ proche. Le format d'échange décrit peut également être utilisé pour des données de cartographie en champ proche générées par un logiciel de simulation. Il convient de noter que bien que celui-ci ait été élaboré pour une cartographie en champ proche, son utilisation n'est pas limitée à cette application. Le format d'échange peut être appliqué à des données de cartographie en champ proche d'émission, d'immunité et d'immunité aux impulsions dans les domaines fréquentiel et temporel. Le domaine d'application de ce rapport technique ne comporte ni les méthodes utilisées pour les mesures ou les simulations, ni le logiciel et les algorithmes utilisés pour générer le fichier d'échange ou pour traiter ou consulter les données qui y sont contenues.
Cette publication indique qu'elle contient des couleurs qui sont considérées comme utiles à une bonne compréhension de son contenu.

General Information

• Status: Published
• Publication Date: 10-May-2010
• ICS: 31.200 - Integrated circuits. Microelectronics
• Technical Committee: SC 47A - Integrated circuits
• Current Stage: DELPUB - Deleted Publication
• Start Date: 28-Aug-2015
• Completion Date: 26-Oct-2025

Relations

• Revised: IEC TR 61967-1-1:2015 - Integrated circuits - Measurement of electromagnetic emissions - Part 1-1: General conditions and definitions - Near-field scan data exchange format
• Effective Date: 05-Sep-2023

Standards Content (Sample)

IEC/TR 61967-1-1 ®
Edition 1.0 2010-05
TECHNICAL
REPORT
RAPPORT
TECHNIQUE
colour
inside
Integrated circuits – Measurement of electromagnetic emissions –
Part 1-1: General conditions and definitions – Near-field scan data exchange
format
Circuits intégrés – Mesure des émissions électromagnétiques –
Partie 1-1: Conditions générales et définitions – Format d'échange de données
de cartographie en champ proche

IEC/TR 61967-1-1:2010
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by
any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either IEC or
IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite
ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie
et les microfilms, sans l'accord écrit de la CEI ou du Comité national de la CEI du pays du demandeur.
Si vous avez des questions sur le copyright de la CEI ou si vous désirez obtenir des droits supplémentaires sur cette
publication, utilisez les coordonnées ci-après ou contactez le Comité national de la CEI de votre pays de résidence.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: [e-mail]
Web: www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: [e-mail]
Tel.: [phone]
Fax: [phone]
A propos de la CEI
La Commission Electrotechnique Internationale (CEI) est la première organisation mondiale qui élabore et publie des
normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

A propos des publications CEI
Le contenu technique des publications de la CEI est constamment revu. Veuillez vous assurer que vous possédez
l’édition la plus récente, un corrigendum ou amendement peut avoir été publié.
ƒ Catalogue des publications de la CEI: www.iec.ch/searchpub/cur_fut-f.htm
Le Catalogue en-ligne de la CEI vous permet d’effectuer des recherches en utilisant différents critères (numéro de référence,
texte, comité d’études,…). Il donne aussi des informations sur les projets et les publications retirées ou remplacées.
ƒ Just Published CEI: www.iec.ch/online_news/justpub
Restez informé sur les nouvelles publications de la CEI. Just Published détaille deux fois par mois les nouvelles
publications parues. Disponible en-ligne et aussi par email.
ƒ Electropedia: www.electropedia.org
Le premier dictionnaire en ligne au monde de termes électroniques et électriques. Il contient plus de 20 000 termes et
définitions en anglais et en français, ainsi que les termes équivalents dans les langues additionnelles. Egalement appelé
Vocabulaire Electrotechnique International en ligne.
ƒ Service Clients: www.iec.ch/webstore/custserv/custserv_entry-f.htm
Si vous désirez nous donner des commentaires sur cette publication ou si vous avez des questions, visitez le FAQ du
Service clients ou contactez-nous:
Email: [e-mail]
Tél.: [phone]
Fax: [phone]
IEC/TR 61967-1-1 ®
Edition 1.0 2010-05
TECHNICAL
REPORT
RAPPORT
TECHNIQUE
colour
inside
Integrated circuits – Measurement of electromagnetic emissions –
Part 1-1: General conditions and definitions – Near-field scan data exchange
format
Circuits intégrés – Mesure des émissions électromagnétiques –
Partie 1-1: Conditions générales et définitions – Format d'échange de données
de cartographie en champ proche

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
PRICE CODE
INTERNATIONALE
XA
CODE PRIX
ICS 31.200 ISBN 978-2-88910-927-2
– 2 – TR 61967-1-1 © IEC:2010
CONTENTS
FOREWORD.4
INTRODUCTION.6
1 Scope.7
2 Normative references .7
3 Terms, definitions and abbreviations .7
3.1 Terms and definitions .7
3.2 Abbreviations .8
4 General syntax rules and guidelines .8
4.1 General .8
4.2 XML requirements .8
4.2.1 General .8
4.2.2 XML declaration .8
4.2.3 XML elements .8
4.2.4 Root element .9
4.2.5 Comments .9
4.2.6 Line terminations .9
4.2.7 Element hierarchy.9
4.3 Keyword requirements.10
4.3.1 General .10
4.3.2 Keyword characters .10
4.3.3 Keyword syntax .10
4.3.4 Root element keywords .10
4.4 File structure .10
4.4.1 General .10
4.4.2 File names.10
4.4.3 File paths .11
4.4.4 Single XML file .11
4.4.5 Multiple XML files .11
4.4.6 Separate data files .11
4.4.7 Additional files.12
4.4.8 File compression .12
4.5 Values.13
4.5.1 General .13
4.5.2 Numerical value syntax.13
4.5.3 Numerical value with units syntax .13
4.5.4 Text string .13
4.5.5 Valid units .13
4.6 Coordinate systems.15
4.6.1 General .15
4.6.2 Cartesian coordinate system .16
4.6.3 Cylindrical coordinate system .17
4.6.4 Spherical coordinate system.17
4.6.5 Coordinate offsets .18
4.6.6 Image coordinates .18
4.7 Field type and orientation .20
4.8 Data syntax .23

TR 61967-1-1 © IEC:2010 – 3 –
4.8.1 General .23
4.8.2 Data with coordinate information .23
4.8.3 Data without coordinate information.24
4.8.4 Data format .24
4.8.5 Data notation.24
4.9 Performance factor.27
4.10 Images .29
4.10.1 General .29
4.10.2 Image file types .29
4.10.3 Image file name and path .29
Annex A (informative) Example files.30
Annex B (normative) Valid keywords.38
Annex C (normative) Keyword usage rules.42
Bibliography.51

Figure 1 – Multiple XML files.11
Figure 2 – XML files with data files .12
Figure 3 – Additional files .13
Figure 4 – Right-hand cartesian coordinate system.16
Figure 5 – Left-hand cartesian coordinate system .16
Figure 6 – Cylindrical coordinate system.17
Figure 7 – Spherical coordinate system .18
Figure 8 – Offsets and image positioning (right-hand cartesian).19
Figure 9 – Offsets and image positioning (left-hand cartesian) .19
Figure 10 – Field orientation – Right-hand cartesian coordinate system .20
Figure 11 – Field orientation – Left-hand cartesian coordinate system .21
Figure 12 – Field orientation – Cylindrical coordinate system.21
Figure 13 – Field orientation – Spherical coordinate system .22

Table 1 – Valid logarithmic units .15
Table 2 – Relationship between azimuth, zenith angles and field component .23
Table 3 – Permitted values for the keyword: Coordinates.23
Table 4 – Order of measurement points when coordinates are not included .26
Table 5 – Performance factor linear units.28
Table 6 – Performance factor logarithmic units .28
Table A.1 – Data matrix .34
Table A.2 – Magnetic field strength.36
Table A.3 – Magnetic field strength.37
Table C.1 – File header keywords.42
Table C.2 – Global keywords .43
Table C.3 – Component section keywords .43
Table C.4 – Setup section keywords .44
Table C.5 – Probe section keywords .47
Table C.6 – Data section keywords .48

– 4 – TR 61967-1-1 © IEC:2010
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
INTEGRATED CIRCUITS –
MEASUREMENT OF ELECTROMAGNETIC EMISSIONS –

Part 1-1: General conditions and definitions –
Near-field scan data exchange format

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
The main task of IEC technical committees is to prepare International Standards. However, a
technical committee may propose the publication of a technical report when it has collected
data of a different kind from that which is normally published as an International Standard, for
example “state of the art”.
IEC 61967-1-1, which is a technical report, has been prepared by subcommittee 47A:
Integrated circuits, of IEC technical committee 47: Semiconductor devices.

TR 61967-1-1 © IEC:2010 – 5 –
The text of this technical report is based on the following documents:
Enquiry draft Report on voting
47A/827A/DTR 47A/833/RVC
Full information on the voting for the approval of this technical report can be found in the
report on voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts of the IEC 61967 series under the general title Integrated circuits –
Measurement of electromagnetic emissions can be found on the IEC website.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
Future standards in this series will carry the new general title as cited above. Titles of existing
standards in this series will be updated at the time of the next edition.

IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
– 6 – TR 61967-1-1 © IEC:2010
INTRODUCTION
Near-field scan measurements, as described for example in IEC 61967-3, and simulations
generate a large amount of data. Many different formats are used for storing the data, thereby
rendering its exchange extremely difficult.
The proposed format is intended to facilitate exchange of near-field scan data between
industrials, academics, EDA tool vendors and end customers. It is based on the well-known
XML format, which is both machine and human readable. Its structure allows the files to be
generated and processed on any operating system. In order to limit the file size, it is possible
to store the information and data in a single file or multiple files. Moreover, the ASCII-based
XML format allows the files to be compressed to a very high level with readily available
compression software.
The three conventional coordinate systems (cartesian, cylindrical and spherical) are
supported by the proposed exchange format. Information on the device under test, the test
set-up, the probe, etc., is also included in the files. Notes and links to external documents
allow complex test environments to be well described.
The version of the exchange format described in this technical report is 1.0. Future revisions
will add items, such as new keywords and rules, considered to be "enhancements" to Version
1.0. Consequently, all future revisions will be considered supersets of Version 1.0, allowing
backward compatibility.
TR 61967-1-1 © IEC:2010 – 7 –
INTEGRATED CIRCUITS –
MEASUREMENT OF ELECTROMAGNETIC EMISSIONS –

Part 1-1: General conditions and definitions –
Near-field scan data exchange format

1 Scope
This part of IEC 61967 provides guidance for exchanging data generated by near-field scan
measurements.
The described exchange format could also be used for near-field scan data generated by
simulation software.
It should be noted that, although it has been developed for near-field scan, its use is not
restricted to this application.
The exchange format can be applied to emission, immunity and impulse immunity near-field
scan data in the frequency and time domains.
The scope of this technical report includes neither the methods used for the measurements or
simulations, nor the software and algorithms used for generating the exchange file or for
processing or viewing the data contained therein.
2 Normative references
The following referenced documents are indispensable for the application of this document.
For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies.
ISO 8879, Information processing – Text and office systems – Standard Generalized Markup
Language (SGML)
ANSI INCITS 4:1986, Information Systems – Coded Character Sets – 7-Bit American National
Standard Code for Information Interchange (7-Bit ASCII)
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply:
3.1.1
section
XML element placed one level below the root element or within another section; contains one
or more XML elements, but no value
3.1.2
parent
keyword, one level above another keyword (child)

– 8 – TR 61967-1-1 © IEC:2010
3.1.3
child
keyword, one level below another keyword (parent)
3.2 Abbreviations
EDA Electronic Design Automation
NFS Near-Field Scan
XML eXtensible Markup Language
SGML Standard Generalized Markup Language
4 General syntax rules and guidelines
4.1 General
The following rules and guidelines ensure that files intended for exchange will be correctly
recognised and processed by viewers and processors. Examples of XML files conforming to
the present exchange format are given in An ne x A
4.2 XML requirements
4.2.1 General
This exchange format uses XML 1.0 fourth edition to structure the information. XML is derived
from the standard generalized markup language (SGML) (ISO 8879).
The rules below ensure that the NFS files can be parsed correctly by an XML parser.
4.2.2 XML declaration
Although the XML declaration is optional in an XML file, the near-field scan file should include
an XML declaration, dedicated to basic XML parsers. An NFS file parser does not interpret
this header.
A file header example is given below:


The XML declaration shall be the first line of the file.
4.2.3 XML elements
All information is saved in the form of XML elements. Each element starts with a start-tag and
ends with an end-tag. The start-tag consists of a keyword enclosed in triangular brackets,
“”. The end-tag consists of the same keyword prefixed by the character "/" and
enclosed in brackets, “”. Content in the form of text is enclosed by a start-tag and
an end-tag.
An example of an element is given below:
 
text 
 
It is also allowed to write an element on the same line, for example, to include short content.
text
TR 61967-1-1 © IEC:2010 – 9 –
The contents of an element may consist of one or more other elements or a value (numerical,
or alphanumerical). For clarity, tab characters may be used for indenting. Except when used
for surrounding keywords, triangular brackets "<" and ">" shall not be part of content.
An empty element may be included to indicate that a particular keyword exists, but has no
content:

4.2.4 Root element
The XML file shall contain one, and only one, root element. It encloses all the other elements
and is therefore the sole parent element to all the other elements. The start-tag of the root
element is placed at the beginning of the file or after the XML declaration when present. The
end-tag of the root element is at the last entry of the file.
4.2.5 Comments
Comments may be inserted into the file between “”. An example is given below:


Comments can be inserted anywhere in the file, except inside start- and end-tags, and written
on a single line or on several lines. All text enclosed by comment brackets is considered as a
comment and may be ignored.
4.2.6 Line terminations
In order to facilitate readability, it is usual to organise the file into lines. The line termination
sequence shall be either a linefeed character or a carriage return character followed by a
linefeed character.
4.2.7 Element hierarchy
The order of the elements is not important, but their hierarchy shall be respected.
example layout:
.

.
.

.
An acceptable equivalent layout of the example:
.
.

.
.

In this layout the order is changed, but the hierarchy is respected.
An unacceptable layout of the example:
.
.
– 10 – TR 61967-1-1 © IEC:2010
.

.

In this layout the hierarchy is not respected.
4.3 Keyword requirements
4.3.1 General
Keywords, placed in start- and end-tags, are used to introduce descriptions, values and
sections that are specific to NFS measurements and simulations. A list of keywords is given in
Annex B and a more detailed description of each keyword is given in An ne x C. So m e
keywords, such as Frequencies, Unit, List, etc, may be present in several sections. A parent
keyword is required when a child keyword is present. The rules below ensure that the file can
be correctly parsed by an NFS parser.
4.3.2 Keyword characters
Only ASCII characters, as defined in ANSI Standard X3.4-1986, may be used in the files. The
use of characters with codes greater than hexadecimal 07E is not allowed. Also, ASCII control
characters (those numerically less than hexadecimal 20) are not allowed, except for tabs or in
a line termination sequence. For example, the "°" character (ASCII 176) is not permitted. Only
alphabetical or numerical characters can be used to write keywords. Spaces are not permitted.
If needed, the underscore "_" character can separate the parts of a multi-word keyword.
4.3.3 Keyword syntax
The content of the files is case sensitive. All keywords shall be written in lower case starting
with an upper case letter.
4.3.4 Root element keywords
As described in 4.2.4, all elements of the file shall be enclosed within the root element. The
following keywords are reserved for root elements and shall not be used for any other
purposes in the file:
EmissionScan
ImmunityScan
If the proposed XML file format is used for other applications, other keywords may be used in
the root element, but NFS parsers may not be able to parse the file.
4.4 File structure
4.4.1 General
The information to be exchanged may be stored in a single XML file or in several XML and
data files. The following rules and guidelines ensure that the files can be correctly located by
an NFS parser.
4.4.2 File names
To facilitate portability between operating systems, file names should have a base name of no
more than forty characters followed by a period ".", followed by a filename extension of no
more than three characters. The file name and extension shall use characters from the set
(space, " ", 0 x 20 is not included):

TR 61967-1-1 © IEC:2010 – 11 –
a b c d e f g h i j k l m n o p q r s t u v w x y z
0 1 2 3 4 5 6 7 8 9 _ ^ $ ~ ! # % & - { } ) ( @ ' `

4.4.3 File paths
In order to ensure portability and compressibility, only relative paths can be used to define a
path name. An absolute path is not exportable and is not permitted. The relative path shall
start with "./" to indicate that the path name of the picture file will be appended to the path of
the current XML file. It is not permitted to browse to a higher level from the current XML path
(e.g. by using "./"). A file name without "./" is assumed to be located in the same directory as
the current XML file.
4.4.4 Single XML file
When the information is contained in a single XML file, it shall conform to the rules and
guidelines applicable to XML files, as described in 4.2.
Data is included in the Data section of the file within the XML element using the keyword: List.
4.4.5 Multiple XML files
The XML document is divided into several sections having the root element as parent. Such a
section contains information on a particular part of the NFS environment and is defined by
keywords such as Component, Setup, Probe, Data, etc. Each XML file may contain one or
more sections and shall conform to the rules and guidelines applicable to XML files as
described in 4.2.
In order to ensure portability and compressibility, all the XML files shall be placed in the same
directory, as shown in Figure 1. The NFS parser shall parse all the XML files that are in the
main directory.
Main directory
XML_File1.xml
XML_File2.xml
XML_File3.xml
XML_FileN.xml
IEC  870/10
Figure 1 – Multiple XML files
4.4.6 Separate data files
Information may be contained in a single file or multiple XML files and the data contained in
one or more additional data files. XML files shall conform to the rules and guidelines
applicable to XML files, as described above and in 4.2. Data files shall contain only lines of
data as described in 4.8. The names and paths of the data files are defined by the keyword:
Data_files and shall conform to 4.4.2 and 4.4.3.
In order to ensure portability and compressibility, the data files shall be placed either in the
same directory as the XML files or in a sub-directory located at the same level or a lower level
as the XML files, as shown in Figure 2. It is not permitted to locate the additional files at a
higher level than the XML files.

– 12 – TR 61967-1-1 © IEC:2010
4.4.7 Additional files
An XML file may contain references to other files such as image files (Keyword: Image) and
document files (Keyword: Documentation). In order to ensure portability and compressibility,
these additional files shall be placed either in the same directory as the single XML file or in a
sub-directory located at the same level or a lower level as the XML files, as shown in Figure 3.
It is not permitted to locate the additional files at a higher level than the XML files.
4.4.8 File compression
When compressing the file system, care shall be taken to include the paths of the various
XML and data files in the compressed file. This ensures that, when decompressed, the file
structure is conserved. The paths are not required when all files are stored in the same
directory.
Main directory Main directory
XML_File1.xml XML_File1.xml
XML_File2.xml XML_File2.xml
Data_file1.dat
Data_file2.dat
Sub-directory
Data_fileN.dat Data_file1.dat
Data_file2.dat
Data_fileN.dat
IEC  871/10 IEC  872/10
Figure 2a – Data files in the same directory Figure 2b – Data files in a sub-directory
Figure 2 – XML files with data files

TR 61967-1-1 © IEC:2010 – 13 –
Main directory Main directory
File1.xml File1.xml
File2.xml File2.xml
Image.jpg
Document1.doc
Sub-directory
Document2.pdf
Image.jpg
Document1.doc
Document2.pdf
IEC  873/10 IEC  874/10
Figure 3a – Additional files in the same directory Figure 3b – Additional files in a sub-directory
Figure 3 – Additional files
4.5 Values
4.5.1 General
When an element contains a value, this may be a numerical value (e.g. “123.45”), a numerical
value with units (e.g. “123.45MHz”) or a text string (e.g. “This is text string number 2”).
4.5.2 Numerical value syntax
Numerical values may be expressed in decimal form with the period as the decimal separator
(e.g. “123.45”) or in scientific form (e.g. 1.2345e2). Spaces " " and commas "," which are often
used as thousand separators, and other characters, are not allowed.
In cases where several numerical values are required, they shall be separated by spaces " "
or tab characters.
4.5.3 Numerical value with units syntax
The numerical value (see 4.5.2) is followed by valid units, as described in 4.5.5 (e.g.
123.45MHz). Spaces are not allowed between the numerical value and the units.
4.5.4 Text string
A text string may represent a word recognised by the NFS parser or it may be a file name, a
description, etc. A text string may contain any of the alphanumerical characters given in 4.3.2.
4.5.5 Valid units
Units may be expressed as simple linear units or as logarithmic units (dB).
Although not strictly a near-field parameter, power flux density has also been included in the
list of valid units for completeness.
Valid units are:
V = volt A = ampere W = watt  ohm

– 14 – TR 61967-1-1 © IEC:2010
Hz = hertz m = metre s = second
Inverse units are also valid:
S = siemens =1/ohm
Combined units are permitted, such as:
V/m = volt per metre
A.m = ampere metre
/V.m = per volt metre
Valid scaling factors are:
T = tera: 1e12 k = kilo: 1e3  n = nano: 1e-9
G = giga: 1e9  m = milli: 1e-3  p = pico: 1e-12
M = mega: 1e6  u = micro: 1e-6  f = femto: 1e-15

When no scaling factors are specified, the appropriate base units are assumed. These are
volts, amperes, watts, ohms, siemens, hertz, metres and seconds. Abbreviations for the units
(e.g., pV, nA, ms, MHz) shall be used, except ohm, which shall be written in full.
All temperatures shall be represented in degrees Celsius. Symbol "°C" is not required.
Angles shall be expressed in degrees. The symbol "°" is not required.
Units are case sensitive.
Table 1 shows a list of valid logarithmic units. The logarithmic units for performance factor
contain brackets in order to avoid confusion with other units (e.g. dBm for dB milliwatt
and dB(m) for dB metre).
TR 61967-1-1 © IEC:2010 – 15 –
Table 1 – Valid logarithmic units
Usage Symbol Unit Reference
Ratio dB decibel 1
Power dBW dB watt 1 W
Power dBm dB milliwatt 1 mW
Voltage dBV dB volt 1 V
Voltage dBuV dB microvolt 1 uV
Current dBA dB ampere 1 A
Current dBuA dB microampere 1 uA
Electric field strength dBV/m dB volt per metre 1 V/m
Electric field strength dBuV/m dB microvolt per metre 1 uV/m
Magnetic field strength dBA/m dB ampere per metre 1 A/m
Magnetic field strength dBuA/m dB microampere per metre 1 uA/m
2 2
Power flux density dB watt per square metre
dBW/m 1 W/m
2 2
Power flux density dB milliwatt per square metre
dBm/m 1 mW/m
a dB(V.m) dB volt metre 1 V.m
Performance factor
a dB(A.m) dB ampere metre 1 A.m
Performance factor
a dB(ohm.m) dB ohm metre
1 Ω.m
Performance factor
a dB(ohm/m) dB ohm per metre
1 Ω/m
Performance factor
a dB(S.m) dB siemens metre 1 S.m
Performance factor
a dB(S/m) dB siemens per metre 1 S/m
Performance factor
a dB(m) dB metre 1 m
Performance factor
a dB(/m) dB per metre 1/m
Performance factor
a dB(/V.m) dB per volt metre 1/(V.m)
Performance factor
a dB(/A.m) dB per ampere metre 1/(V.m)
Performance factor
2 2
a dB volt per square metre
dB(V/m ) 1 V/m
Performance factor
2 2
a dB ampere per square metre
dB(A/m ) 1 V/m
Performance factor
2 2
a dB per square metre
dB(/m ) 1/m
Performance factor
2 2
a dB square metre per volt
dB(m /V) 1 m /V
Performance factor
2 2
a dB square metre per ampere
dB(m /A) 1 m /A
Performance factor
2 2
a dB square metre
dB(m ) 1 m
Performance factor
The corresponding linear units are also permitted.
a
Details of the performance factor are given in 4.9.

4.6 Coordinate systems
4.6.1 General
The near-field scan data may be based on cartesian, cylindrical or spherical coordinate
systems. The keyword: Coordinates defines the coordinate system used in the technical
report. The right-hand cartesian coordinate system is used by default.

– 16 – TR 61967-1-1 © IEC:2010
4.6.2 Cartesian coordinate system
In order to accommodate different scan table coordinate systems and existing documents,
cartesian coordinates may be either right-hand (see Figure 4) or left-hand (see Figure 5).
However, the right-hand cartesian coordinate system is preferred and shall be used whenever
possible.
F
z
Z
F
y
F
x
P(x,y,z)
z
x
Y
y
X
IEC  875/10
Figure 4 – Right-hand cartesian coordinate system
F
z
Z
F
x
F
y
P(x,y,z)
z
y
X
x
Y
IEC  876/10
Figure 5 – Left-hand cartesian coordinate system

TR 61967-1-1 © IEC:2010 – 17 –
4.6.3 Cylindrical coordinate system
Although the scan equipment may be orientated differently, the cylindrical coordinate system
assumes that the polar plane (r, A) lies in the XY plane of a cartesian coordinate system and
that the linear axis (h) lies in the z-direction of a cartesian coordinate system, as shown in
Figure 6.
Z
F
h
F
A
F
r
P(r,A,h)
r ≥ 0
0 ≤ A < 360°
h
r
Y
A
X
IEC  877/10
Figure 6 – Cylindrical coordinate system
4.6.4 Spherical coordinate system
Similarly, the spherical coordinate system assumes that the azimuth angle (A) lies in the XY
plane of a cartesian coordinate system and that the zenith angle (B) lies between the Z-axis
of a cartesian coordinate system and the vector r, as shown in Figure 7. In order to avoid the
use of negative angle values, the zenith angle shall be used in preference to the elevation
angle (angle between the XY-plane and the vector r), which is used for antenna radiation
diagrams, for example.
– 18 – TR 61967-1-1 © IEC:2010
F
r
Z
F
A
F
B
B
P(r,B,A)
r ≥ 0
r
0 ≤ A < 360°
0 ≤ B < 180°
Y
A
X
IEC  878/10
Figure 7 – Spherical coordinate system
4.6.5 Coordinate offsets
Provision is provided for the origin of the scan area to be offset from the origin of the scan
table, for example. The offset is specified using the keywords: X0, Y0, Z0, R0, H0, A0 and B0.
Figure 8 and Figure 9 show the offsets for right-hand and left-hand cartesian coordinates
respectively. Offsets in the cylindrical and spherical coordinate systems are used in a similar
way.
4.6.6 Image coordinates
The scan information can be overlaid with a picture of the component. The image dimensions
are specified with the keywords: Xsize, Ysize, Zsize, Rsize, Hsize, Asize and Bsize. The
origin of the image may be offset from the origin of the scan table this offset is specified using
the keywords: Xoffset, Yoffset, Zoffset, Roffset, Hoffset, Aoffset and Boffset. Figure 8 and
Figure 9 show the offsets and dimensions of the image for right-hand and left-hand cartesian
coordinates respectively.
In the cartesian coordinate system the overlay of an image is usually in the XY plane, but it is
also possible to overlay it in the XZ or YZ planes. This is specified by the pairs of keywords
used for the size (e.g. Xsize and Ysize) and offset (e.g. Xoffset and Yoffset), etc) of the image.
When using spherical or cylindrical coordinates, the flat picture has no meaning. Nevertheless,
a picture of the component, measurement setup, etc. may be included, even though it cannot
be overlaid on the scan. In this case, no size and offset keywords shall be included in the
document.
More details of how images shall be included in the project are given in 4.10.

TR 61967-1-1 © IEC:2010 – 19 –
Y
Z axis is vertical (positive upwards)

Ymax
Scan area
Ysize
Image
Y0
Yoffset
Image origin
Xsize
X
X0
Xmax
Absolute origin
Xoffset
Scan area origin
IEC  879/10
Figure 8 – Offsets and image positioning (right-hand cartesian)

Scan area origin
Absolute origin
Xoffset
Xmax
X0
X
Image origin
Xsize
Yoffset
Y0
Ysize
Scan area
Image
Ymax
Z axis is vertical (positive upwards)
Y IEC  880/10
Figure 9 – Offsets and image positioning (left-hand cartesian)

– 20 – TR 61967-1-1 © IEC:2010
4.7 Field type and orientation
The field type is specified using the keyword: Field. Typically, the value will be "E" for the
electrical field and "H" for the magnetic field. If the orientation of the field is not included in
the data, the value can be enhanced by adding the field component, e.g.: Ex, Hz, Eh, Hr, etc.
The Figure 10 to Figure 13 also show the field
...