ISO/IEC 14763-3:2014/COR1:2015
(Corrigendum)Corrigendum 1 - Information technology - Implementation and operation of customer premises cabling - Part 3: Testing of optical fibre cabling
- BACK
- 22-Mar-2015
- 29.060.10
- 35.200
- ISO/IEC JTC 1/SC 25
Corrigendum 1 - Information technology - Implementation and operation of customer premises cabling - Part 3: Testing of optical fibre cabling
This consolidated version consists of the second edition (1990), its amendment 1 (1997) and its amendment 2 (1997). Therefore, no need to order amendments in addition to this publication.
General Information
Relations
Standards Content (Sample)
IEC 2015
ISO/IEC 14763-3
Edition 2.0 2014-06
INFORMATION TECHNOLOGY – IMPLEMENTATION AND OPERATION
OF CUSTOMER PREMISES CABLING –
Part 3: Testing of optical fibre cabling
CO RRI G E NDUM 1
Table 4 – Connecting hardware attenuation
Replace, in the second row,
in column 4, "SMF, Attenuation (random mated)", the existing value "0,30 dB max.", by "0,25 dB max."
and
in column 5, "SMF, Attenuation (mated against reference)", the ex
...
This May Also Interest You
ISO/IEC 29341-19-10:2011(E) describes the service definition which is compliant with the UPnP Device Architecture version 1.0. This service-type enables the following functions: - Driving a motor between two fixed end limits. - Reaching any position written in percentage of the full run (optional). - Returning the actual blind position written in percentage of the full run (optional).
- Standard18 pagesEnglish languagesale 15% off
- 13-Oct-2011
- 29.060.10
- 35.200
- ISO/IEC JTC 1
ISO/IEC 29341-16-1:2011(E) defines an architecture that will address the issue of reporting and tracking power states of nodes in a network. The UPnP Low Power solution is designed to enable nodes in the network to report and track the Low Power states of other nodes in the network. Additionally, for nodes that support wake up capabilities, this architecture addresses methods to wake up those nodes when required. The objective of the UPnP Low Power solution is to allow UPnP devices to conserve energy and still be discoverable by UPnP Control Points. The UPnP Control Point will be aware of the UPnP devices and services implemented on a Low Power device even when the Low Power device is in a power savings mode. This architecture document defines two UPnP services that comprise the UPnP Low Power framework: Low Power device service and Basic Power Management Proxy service.
- Standard35 pagesEnglish languagesale 15% off
- 29-Aug-2011
- 29.060.10
- 29.060.20
- 35.200
- ISO/IEC JTC 1
ISO/IEC 29341-18-13:2011(E) describes a service definition which is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as RATAConfig service. The RATAConfig service is a UPnP service that allows control points to provision and configure the parameters that are required for enabling a Remote Access Server to accept and a Remote Access Client to initiate remote access connections. This service provides control points with the following functionality: - Determine the Remote Access Transport Agents that can be configured by the service. - Determine the delivery mechanisms for credentials supported by the service. - Configure Remote Access Transport Agent profiles. - Management of Remote Access Transport Agent profiles.
- Standard44 pagesEnglish languagesale 15% off
- 29-Aug-2011
- 29.060.10
- 35.200
- ISO/IEC JTC 1
ISO/IEC 29341-18-11:2011(E) covers service definition and is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as RADAConfig service. This service type enables configuration of the in-band synchronization mechanism between Remote Access Clients and Remote Access Server.
- Standard12 pagesEnglish languagesale 15% off
- 29-Aug-2011
- 29.060.10
- 35.200
- ISO/IEC JTC 1
ISO/IEC 29431-18-10:2011(E) describes a service definition which is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as InboundConnectionConfig service. The InboundConnectionConfig service is a UPnP service that allows control points to configure the parameters that will enable the service to test if the host device is reachable from the internet. InboundConnectionConfig uses Dynamic DNS to manage at least one public address for home-network services; it uses STUN to ensure that any intermediate NAT device is navigatable, i.e. it is a full-cone NAT. Thus, this service provides control points with the following functionality: - Configure the dynamic DNS client co-located with the service, - Configure the STUN client co-located with the service, - Check if the device hosting the service is reachable from the internet.
- Standard14 pagesEnglish languagesale 15% off
- 29-Aug-2011
- 29.060.10
- 35.200
- ISO/IEC JTC 1
IEC TR 61169-1-8:2025 provides a test method for voltage standing wave ratio (VSWR, hereinafter) of single RF connector by double-connector method. This document is applicable to single RF cable connectors and single microstrip RF connectors as well as single adapters if an estimation of the VSWR of a single completely installed RF-connector is used and a time domain feature is not available on the vector network analyzer.
- Technical report18 pagesEnglish languagesale 15% off
IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows:
• The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols.
• The Device Communication Model adds Network and Connection information elements so that communication topologies can be created.
• The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks.
This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are:
• Locking model – a generic AddIn to control concurrent access,
• Software update model – an AddIn to manage software in a Device.
This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType;
b the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added.
c) a new model for Software Update (Firmware Update) has been added;
d) a new entry point for documents where each document is represented by a FileType instance has been specified;
e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.
- Standard152 pagesEnglish languagesale 15% off
- Standard158 pagesFrench languagesale 15% off
- Standard310 pagesEnglish and French languagesale 15% off
IEC 62541-13:2025 is available as IEC 62541-13:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-13:2025 defines the information model associated with Aggregates. Programmatically produced aggregate examples are listed in Annex A. This third edition cancels and replaces the second edition published in 2020. This edition constitutes a technical revision.
This edition includes the following technical changes with respect to the previous edition:
a) Multiple fixes for the computation of aggregates
• The Raw status bit is always set for non-bad StatusCodes for the Start and End aggregates.
• Entries in the Interpolative examples Tables A2.2 Historian1, Historian2, and Historian3 have been changed from Good to Good, Raw status codes when the timestamp matches with the timestamp of the data source.
• Missing tables have been added for DurationInStateZero and DurationInStateNonZero.
• The value of zero has been removed for results with a StatusCode of bad.
• Data Type was listed as "Status Code" when it is "Double" for both Standard Deviation and both Variance Aggregates.
• Rounding Error in TimeAverage and TimeAverage2 have been corrected.
• The status codes have been corrected for the last two intervals and the value has been corrected in the last interval.
• The wording has been changed to be more consistent with the certification testing tool.
• UsedSlopedExtrapolation set to true for Historian2 and all examples locations needed new values or status' are modified.
• Values affected by percent good and percent bad have been updated.
• PercentGood/PercentBad are now accounted for in the calculation.
• TimeAverage uses SlopedInterpolation but the Time aggregate is incorrectly allowed to used Stepped Interpolation.
• Partial bit is now correctly calculated.
• Unclear sentence was removed.
• Examples have been moved to a CSV.
• The value and status code for Historian 3 have been updated.
• TimeAverage2 Historian1 now takes uncertain regions into account when calculating StatusCodes.
• TimeAverage2 Historian2 now takes uncertain regions into account when calculating StatusCodes.
• Total2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Total2 Historian2 now takes uncertain regions into account when calculating StatusCodes
• Maximum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MaximumActualTime2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Minimum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MinimumActualTime2 Historian1 now has the StatusCodes calculated while using the TreatUncertainAsBad flag.
• Range2 Historian1 now looks at TreatUncertainAsBad in the calculation of the StatusCodes.
• Clarifications have been made to the text defining how PercentGood/PercentBad are used. The table values and StatusCodes of the TimeAverage2 and Total2 aggregates have been corrected.
- Standard64 pagesEnglish languagesale 15% off
- Standard64 pagesFrench languagesale 15% off
- Standard128 pagesEnglish and French languagesale 15% off
IEC 62541-4:2025 is available as IEC 62541-4:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-4:2025 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541‑6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541‑6 is to UA-TCP UA-SC UA-Binary. In that case the Services described in this document appear as OPC UA Binary encoded payload, secured with OPC UA Secure Conversation and transported via OPC UA TCP. Not all OPC UA Servers implement all of the defined Services. IEC 62541‑7 defines the Profiles that dictate which Services must be implemented in order to be compliant with a particular Profile. A BNF (Backus-Naur form) for browse path names is described in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of new definitions to Method Call Service to allow optional Method arguments;
b)addition of reference to SystemStatusChangeEventType for event monitored item error scenarios;
c) enhancement of the general description of how determining if a Certificate is trusted;
d) addition of support for ECC;
e) addition of revisedAggregateConfiguration to AggregateFilterResult structure;
f) addition of INVALID to the BrowseDirection enumeration data type;
g) addition of INVALID to the TimestampsToReturn enumeration data type;
h) addition of definitions that make sure the subscription functionality works if retransmission queues are optional;
i) addition of client checks has been added to be symmetric to the Server Certificate check has been added;
j) clarification that ‘local’ top level domain is not appended by server into certificate and not checked by client when returned from LDS-ME;
k) addition of a definition for expiration behaviour of IssuedIdentityTokens;
l) addition of status code Good_PasswordChangeRequired to ActivateSession;
m) restriction of AdditionalInfo to servers in debug mode;
n) addition of new status code Bad_ServerTooBusy;
o) addition of definition for cases where server certificate must be contained in GetEndpoints response.
- Standard245 pagesEnglish languagesale 15% off
- Standard257 pagesFrench languagesale 15% off
- Standard502 pagesEnglish and French languagesale 15% off
IEC 61757-1-4:2025 defines the terminology, structure, and measurement methods of distributed fibre optic sensors for absolute strain measurements based on spectral correlation analysis of Rayleigh backscattering signatures in single-mode fibres, where the fibre is the distributed strain measurement element in a measurement range from about 10 m to tens of km. This document also applies to hybrid sensor systems that combine the advantages of Brillouin and Rayleigh backscattering effects to obtain optimal measurement quality. This document also specifies the most important features and performance parameters of these distributed fibre optic strain sensors defines procedures for measuring these features and parameters. This part of IEC 61757 does not apply to point measurements or to dynamic strain measurements. Distributed strain measurements using Brillouin scattering in single-mode fibres are covered in IEC 61757-1-2. The most relevant applications of this strain measurement technique are listed in Annex A, while Annex B provides a short description of the underlying measurement principle.
- Standard27 pagesEnglish languagesale 15% off
- Standard29 pagesFrench languagesale 15% off
- Standard56 pagesEnglish and French languagesale 15% off
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...