EN IEC 62769-6-100:2023
(Main)Field Device Integration (FDI®) - Part 6-100: Technology Mapping - .Net
Field Device Integration (FDI®) - Part 6-100: Technology Mapping - .Net
IEC 62769-6-100:2023 specifies the technology mapping for the concepts described in the Field Device Integration (FDI®[1]) standard. The technology mapping focuses on implementation regarding the components FDI® Client and User Interface Plug-in (UIP) using the Runtime .NET. This runtime is specific only to the WORKSTATION platform as defined in IEC 62769‑4. [1] FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires permission of the trade name holder.
Feldgeräteintegration (FDI®) - Teil 6-100: FDI-Technologieabbildungen - .Net
Intégration des appareils de terrain (FDI®) - Partie 6-100: Mapping de technologies - .Net
L'IEC 62769-6-100:2023 spécifie le mapping de technologies pour les concepts décrits dans la norme d'intégration des appareils de terrain (FDI®[1], Field Device Integration). Le mapping de technologies porte essentiellement sur la mise en œuvre des composants Client FDI® et Plugiciel d'interface utilisateur (UIP, User Interface Plug-in) à l'aide de l'environnement d'exécution .NET. Cet environnement d'exécution n'est spécifique qu'à la plateforme WORKSTATION définie dans l'IEC 62769‑4. [1] FDI est une marque déposée de l’organisation à but non lucratif Fieldbus Foundation, Inc. Cette information est donnée à l'intention des utilisateurs du présent document et ne signifie nullement que l'IEC approuve le détenteur de la marque ou l'emploi de ses produits. La conformité n'exige pas l'utilisation de la marque. L'utilisation de la marque exige l'autorisation du détenteur de la marque.
Integracija procesne naprave (FDI®) - 6-100. del: Preslikava tehnologije - .Mreža (IEC 62769-6-100:2023)
Standard IEC 62769-6-100:2023 določa preslikavo tehnologije za koncepte, opisane v standardu za integracijo procesne naprave (FDI®[1]). Preslikava tehnologije se osredotoča na izvajanje v zvezi z odjemalcem FDI® in vtičnikom uporabniškega vmesnika (UIP), ki uporabljata čas izvajanja .NET. Ta čas izvajanja je specifičen samo za platformo DELOVNE POSTAJE, kot je opredeljeno v standardu IEC 62769-4.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2023
Integracija procesne naprave (FDI®) - 6-100. del: Preslikava tehnologije - .Mreža
(IEC 62769-6-100:2023)
Field Device Integration (FDI®) - Part 6-100: Technology Mapping - .Net (IEC 62769-6-
100:2023)
Feldgeräteintegration (FDI®) - Teil 6-100: FDI-Technologieabbildungen - .Net (IEC
62769-6-100:2023)
Intégration des appareils de terrain (FDI®) - Partie 6-100: Mapping de technologies -
.Net (IEC 62769-6-100:2023)
Ta slovenski standard je istoveten z: EN IEC 62769-6-100:2023
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN STANDARD EN IEC 62769-6-100
NORME EUROPÉENNE
EUROPÄISCHE NORM June 2023
ICS 25.040.40; 35.100.05
English Version
Field Device Integration (FDI®) - Part 6-100: Technology
Mapping - .Net
(IEC 62769-6-100:2023)
Intégration des appareils de terrain (FDI®) - Partie 6-100: Feldgeräteintegration (FDI®) - Teil 6-100: FDI-
Mapping de technologies - .Net Technologieabbildungen - .Net
(IEC 62769-6-100:2023) (IEC 62769-6-100:2023)
This European Standard was approved by CENELEC on 2023-05-19. CENELEC members are bound to comply with the CEN/CENELEC
Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Türkiye and the United Kingdom.
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2023 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 62769-6-100:2023 E
European foreword
The text of document 65E/868/CDV, future edition 1 of IEC 62769-6-100, prepared by SC 65E
"Devices and integration in enterprise systems" of IEC/TC 65 "Industrial-process measurement,
control and automation" was submitted to the IEC-CENELEC parallel vote and approved by
CENELEC as EN IEC 62769-6-100:2023.
The following dates are fixed:
• latest date by which the document has to be implemented at national (dop) 2024-02-19
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2026-05-19
document have to be withdrawn
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.
Any feedback and questions on this document should be directed to the users’ national committee. A
complete listing of these bodies can be found on the CENELEC website.
Endorsement notice
The text of the International Standard IEC 62769-6-100:2023 was approved by CENELEC as a
European Standard without any modification.
In the official version, for Bibliography, the following note has to be added for the standard indicated:
IEC 61804 (series) NOTE Approved as EN IEC 61804 (series)
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements 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.
NOTE 1 Where an International Publication has been modified by common modifications, indicated by (mod),
the relevant EN/HD applies.
NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available
here: www.cencenelec.eu.
Publication Year Title EN/HD Year
IEC 62769-1 2021 Field Device Integration (FDI) - Part 1: Overview EN IEC 62769-1 2021
IEC 62769-2 - Field Device Integration (FDI®) - Part 2: Client EN IEC 62769-2 -
IEC 62769-4 - Field Device Integration (FDI®) - Part 4: FDI EN IEC 62769-4 -
Packages
IEC 62769-6 - Field Device Integration (FDI®) - Part 6: FDI EN IEC 62769-6 -
Technology Mappings
IEC 62769-6-100 ®
Edition 1.0 2023-04
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside ®
Field Device Integration (FDI ) –
Part 6-100: Technology Mapping – .Net ®
Intégration des appareils de terrain (FDI ) –
Partie 6-100: Mapping de technologies – .Net
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100.05 ISBN 978-2-8322-6809-4
– 2 – IEC 62769-6-100:2023 © IEC 2023
CONTENTS
FOREWORD . 4
1 Scope . 6
2 Normative references . 6
3 Terms, definitions, abbreviated terms, acronyms and symbols . 6
3.1 Terms and definitions . 6
3.2 Abbreviated terms and acronyms . 7
3.3 Symbols . 7
4 Technical concepts . 7
4.1 General . 7
4.1.1 Overview . 7 ®
4.1.2 FDI Type Library . 7
4.2 UIP representation . 8
4.3 UIP executable representation . 9
4.4 UIP executable compatibility rules . 9
4.5 Allowed .NET CLR versions . 9
4.5.1 General . 9
4.5.2 CLR compatibility strategy . 10
4.5.3 How to identify the .NET target platform of a UIP . 10
4.6 UIP Deployment . 11
4.7 UIP Life-cycle . 11
4.7.1 General . 11
4.7.2 UIP Assembly activation steps . 11
4.7.3 UIP Assembly deactivation steps . 13
4.7.4 Backward compatibility . 14 ®
4.8 Interaction between an FDI Client and a UIP . 14
4.8.1 Handling of standard UI elements . 14
4.8.2 Non-blocking service execution . 15
4.8.3 Blocking service execution. 16
4.8.4 Cancel service execution . 16
4.8.5 Threading . 17
4.8.6 Timeout . 18
4.8.7 Exception handling . 18
4.8.8 Type safe interfaces . 19
4.8.9 Globalization and localization . 19
4.8.10 WPF Control handling . 20
4.8.11 Win Form handling . 20
4.9 Security . 20
4.9.1 General . 20
4.9.2 Access permissions . 20
4.9.3 Code identity concept . 21
5 Interface definition . 21
Bibliography . 26
®
Figure 1 – FDI Type Library structure . 8
Figure 2 – .NET surrogate process . 10
Figure 3 – Identification of Run-time Version. 10
IEC 62769-6-100:2023 © IEC 2023 – 3 –
Figure 4 – Example snippet of a UIP host config file for the binding redirect . 14
Figure 5 – IAsyncPattern based asynchronous service execution example . 16
Figure 6 – Blocking service execution example using IAsyncResult based pattern . 16
Figure 7 – Cancel service processing sequence example . 17
Figure 8 – Exception source . 19
Table 1 – Base Property Services . 21
Table 2 – Device Model Services . 22
Table 3 – Access Control Services . 22
Table 4 – Direct Access Services . 22
Table 5 – Hosting Services . 23
Table 6 – UIP Services . 24
Table 7 – Base Data Types . 24
Table 8 – Special Types . 25
– 4 – IEC 62769-6-100:2023 © IEC 2023
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________ ®
FIELD DEVICE INTEGRATION (FDI ) –
Part 6-100: Technology Mapping – .NET
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.
IEC 62769-6-100 has been prepared by subcommittee 65E: Devices and integration in
enterprise systems, of IEC technical committee 65: Industrial-process measurement, control
and automation. It is an International Standard.
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/868/CDV 65E/925/RVC
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
IEC 62769-6-100:2023 © IEC 2023 – 5 –
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
A list of all parts in the IEC 62769 series, published under the general title Field device ®
integration (FDI ), can be found on the IEC website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The "colour inside" logo on the cover page of this document 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 – IEC 62769-6-100:2023 © IEC 2023 ®
FIELD DEVICE INTEGRATION (FDI ) –
Part 6-100: Technology Mapping – .NET
1 Scope
This part of IEC 62769 specifies the technology mapping for the concepts described in the Field
®1
Device Integration (FDI ) standard. The technology mapping focuses on implementation ®
regarding the components FDI Client and User Interface Plug-in (UIP) using the Runtime .NET.
This runtime is specific only to the WORKSTATION platform as defined in IEC 62769-4.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements 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. ®
IEC 62769-1:2021, Field device integration (FDI ) – Part 1: Overview ®
IEC 62769-2, Field device integration (FDI ) – Part 2: Client
® ®
IEC 62769-4, Field device integration (FDI ) – Part 4: FDI Packages ®
IEC 62769-6, Field device integration (FDI ) – Part 6: Technology Mappings
3 Terms, definitions, abbreviated terms, acronyms and symbols
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62769-1 as well as
the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http:www.iso.org/obp
3.1.1
Application Domain
isolated environment where applications execute
3.1.2
Assembly
reusable, version information providing, and self-describing building block of a CLR application
___________
FDI is a registered trademark of the non-profit organization Fieldbus Foundation, Inc. This information is given
for the convenience of users of this document and does not constitute an endorsement by IEC of the trademark
holder or any of its products. Compliance does not require use of the trade name. Use of the trade name requires
permission of the trade name holder.
IEC 62769-6-100:2023 © IEC 2023 – 7 –
3.1.3 ®
FDI Type Library
typescript file that contains the interfaces and data types that are used for the data exchange ®
and interaction between a UIP and an FDI Client
3.1.4
Global Assembly Cache
machine-wide code cache that stores Assemblies specifically designated to be shared by
several applications
3.1.5
Windows Registry
system-defined database in which applications and system components store and retrieve
configuration data
3.2 Abbreviated terms and acronyms
For the purposes of this document, the abbreviated terms and acronyms given in IEC 62769-1,
IEC 62769-6, as well as the following apply.
MSI Microsoft Installer
WPF Windows Presentation Foundation
UML Unified Modeling Language
3.3 Symbols
Figures in this document use the graphical symbols according to l'ISO/IEC 19505-1 (UML 2.0).
4 Technical concepts
4.1 General
4.1.1 Overview
In 4.1.2, 4.2, 4.3, 4.4, and 4.5, this document describes the technology base for UIP
implementation based on the runtime .NET Framework CLR4, the hardware and software
environment including the related implementation rules. Clause 4 follows a lifecycle (use case)
oriented approach.
Subclause 4.6 describes the copy deployment procedures and related implementation rules for ®
the UIP and the FDI Client. UIP executable instantiation and termination is described in 4.7. ®
Subclause 4.8 defines the rules about interaction between the FDI Client and the UIP. Security ®
related definitions are written in 4.9. The service interface definitions for the FDI Client and
the UIP are found in Clause 5. ®
4.1.2 FDI Type Library
The Device Access Services and the UIP Services can be modelled as .NET interfaces
passing .NET data type arguments. These interfaces and data types are used for the data ®
exchange and interaction between the UIP and the FDI Client. For runtime error handling
purposes during interface method calls .NET exceptions classes are defined.
– 8 – IEC 62769-6-100:2023 © IEC 2023
® ®
The FDI .NET interfaces, data types, and exception classes are defined in a single FDI Type ®
Library. The FDI Type Library is provided within a Nuget Package, which contains one or more
strong named assemblies. The file name of this Nuget Package shall be Fdi..nupkg.
® ®
The FDI Type Library shall be versioned as per IEC 62769-1:2021, 8.1. The FDI Type Library ®
is part of the FDI Core Technology as per IEC 62769-1:2021, 8.3.2.1. Therefore, it directly
® ®
influences the FDI Technology Version. All compatible changes of the FDI Type Library lead ®
to an increase of the minor portion of the FDI Technology Version. Incompatible changes lead ®
to an increase of the major portion of the FDI Technology Version (see IEC 62769-1:2021, ®
8.3.2.2). The version information of the FDI Type Library can be found in FCG TS10099.
® ®
The FDI Type Library is signed with a single unique key by the issuer of the file. The FDI ®
Type Library shall be installed separately as part of every FDI Client installation. User Interface
® ®
Plug-Ins (UIP) and the FDI Client Application shall use this instance of the FDI Type Library.
® ®
UIPs shall not carry or deploy the FDI Type Library. The FDI Client is responsible to provide
means to allow updates of this type library over time. ®
Figure 1 shows the FDI Type Library structure.
®
Figure 1 – FDI Type Library structure
NOTE The composite structure diagram shows only the core interfaces that implement the interfaces defined in
IEC 62769-2.
4.2 UIP representation
The UIP Variant can contain either a single or multiple runtime modules (.NET Assembly) and
their related supplementary files (for example: resource files). The runtime module of the UIP
Variant is called UIP executable. The supplementary file(s) of the UIP Variant is/are called UIP
supplement(s).
UIP supplement(s) is/are stored under (a) subfolder(s) of the UIP executable installation
directory.
EXAMPLE Examples of UIP supplementary data files include resource files and application configuration data.
IEC 62769-6-100:2023 © IEC 2023 – 9 – ®
The supported RuntimeIds and .NET Framework versions for a specific FDI Technology ®
Version are specified in FCG TS10099 FDI Technology Management.
The UIP Variant shall be self-contained. All UIP required libraries (.NET Assemblies) required
by a UIP Variant are stored within the same Folder.
4.3 UIP executable representation
The implementation of the UIP depends on the type of user interface elements that can be ®
embedded into the user interface hosting environment of the FDI Client. UIP shall be
implemented as a .NET System.Windows.Forms class UserControl or a WPF
System.Windows.Controls class UserControl.
UIP executables and their required libraries shall have strong names. The signing of a strong
named Assembly can be done using a self-generated key.
NOTE The identity of strong named Assemblies consists of a name, version, culture, public key token and digital
signature.
UIP executables and their required libraries shall be shipped with file containing the public key
in order to enable Assembly verification.
4.4 UIP executable compatibility rules
The compatibility rules for different versions of the UIP component are specified in IEC 62769-4.
The compilation target platform for the UIP shall be "anyCPU". If this is not feasible the UIP
shall be shipped in two variants. One UIP variant shall be compiled for target platform "x86".
The second UIP variant shall be compiled for target platform "x64". The compilation platform
target shall be described in the catalog.xml file which is defined in IEC 62769-4. This
catalog.xml file contains an xml element "CpuInformation" that describes the User Interface
Plug-in variant. The allowed values that shall be used in the xml element "CpuInformation" are
"anyCPU", "x86" or "x64".
4.5 Allowed .NET CLR versions
4.5.1 General
Specific CLR versions are released for the execution of software components built with
specific .NET Framework versions. The .NET CLR version 4.0 is used to execute software
components built with .NET Framework 4.0. .NET Components are built for one CLR version
only but can be able to run also under a newer CLR version.
® ®
FDI Clients can be built based on CLR version 4.0 or future versions. An FDI Client has to
realize the following situations when starting a UIP.
• When the UIP to be started was built for the same run-time, the UIP can be started in the ®
FDI Client as usual.
• When the UIP to be started was built with another CLR version and is not compiled for the ®
current running CLR version, the FDI Client shall start the UIP in a surrogate process with
the adequate CLR version. (More details are described in 4.5.2.)
Taking this behavior in account, a UIP shall be developed for CLR version 4.0 or any future
version. In case the CLR versions do not match, the UIP shall be started in a separate process. ®
The UIP will then not be displayed as an integrated module within the FDI Client. It is up to ®
the FDI Client to realize the surrogate process.
– 10 – IEC 62769-6-100:2023 © IEC 2023
4.5.2 CLR compatibility strategy ®
In the future, FDI Clients and UIPs will be permitted to be built on different incompatible
versions of the CLR.
® ®
If an FDI Client detects that a UIP requires a CLR that is not compatible with the FDI Client, ®
the FDI Client can use a proxy class that enables interaction with the UIP built using a different
version of the CLR. ®
The FDI Client loads a proxy UIP executable, creates an instance of the proxy class, and
delegates the execution of the UIP to this proxy. The proxy starts a process with the required
CLR and executes the UIP in this surrogate process. The proxy classes provide the standard
® ®
FDI interfaces. The FDI Client can use these interfaces to interact with the UIP executed in
the surrogate process.
Figure 2 – .NET surrogate process
4.5.3 How to identify the .NET target platform of a UIP
The .NET target platform CLR version information for which a certain Assembly is compiled can
be extracted by means of .NET Framework library functions (see Figure 3).
Figure 3 – Identification of Run-time Version
®2
NOTE The Visual Studio 2008 and 2010 IDE allow developers to select the .NET Framework target. The selection ®
of a .NET Framework target older than the base for the current Visual Studio IDE automatically creates a
configuration file listed as "app.config" within the solution explorer. This file only reflects the current complier setting.
The compiler does not read that file.
___________
Visual Studio is the trademark of Microsoft Corporation. This information is given for the convenience of users of
this document and does not constitute an endorsement by IEC of the trademark holder or any of its products.
Compliance does not require use of the trademark. Use of the trademark requires permission of the trademark
holder.
IEC 62769-6-100:2023 © IEC 2023 – 11 –
4.6 UIP Deployment
The general UIP installation rules are outlined in IEC 62769-2. The UIP executable shall not be
registered within the Global Assembly Cache.
The "strong-name" rule ensures that related Assemblies of different versions of the UIP can
coexist during runtime. ®
The FDI Client implementation ensures that UIP deployment works independently from current
user credentials. (See the NOTE below.)
NOTE Certain operating system managed folders require specific access rights, for example, modifications in folder
"Program Files" require "Administrator" rights. The Windows operating system provides several means to allow an
application running with restricted user rights, to execute actions with administrator privileges transparent to the
user, for example, special restriction handling for identified directories, services with administration rights,
executables that are configured to automatically run with administration rights. The alternative is to copy UIP
executables into folders writeable for "normal" users.
4.7 UIP Life-cycle
4.7.1 General
The UIP state machine, outlined in IEC 62769-2, is composed of the Loaded, Created,
Operational, Deactivated and Disposed states. The mechanisms affecting state changes are
described in 4.7.
® ® ®
After the FDI Client has stored the UIP executable on the FDI Client the FDI Client loads
the UIP Assemblies dynamically into the memory and executes the related logic by calling the ®
corresponding FDI specified interface functions. ®
Subclause 4.7 describes rules about how the FDI Client shall activate and deactivate the UIP.
4.7.2 UIP Assembly activation steps
4.7.2.1 Load ®
The FDI Client shall load the UIP executables by using the LoadFrom mechanism. The .NET
framework provides System.Reflection.Assembly.LoadFrom for this purpose:
The LoadFrom mechanism behaves as follows.
• LoadFrom
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...