1.1 General

The Fieldbus Application Layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect, the FAL can be viewed as a “window between corresponding application programs”.

This standard provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to type 10 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life.

This standard defines in an abstract way the externally visible service provided by the Type 10 fieldbus Application Layer in terms of

an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service,
the primitive actions and events of the service;
the parameters associated with each primitive action and event, and the form which they take; and
the interrelationship between these actions and events, and their valid sequences.

The purpose of this standard is to define the services provided to

the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and
Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model.

This standard specifies the structure and services of the type 10 IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure (ISO/IEC 9545).

FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes.

Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this standard to provide access to the FAL to control certain aspects of its operation.

1.2 Specifications

The principal objective of this standard is to specify the characteristics of conceptual application layer services suitable for time-critical communications, and thus supplement the OSI Basic Reference Model in guiding the development of application layer protocols for time-critical communications.

A secondary objective is to provide migration paths from previously-existing industrial communications protocols. It is this latter objective which gives rise to the diversity of services standardized as the various Types of IEC 61158, and the corresponding protocols standardized in subparts of IEC 61158-6.

This standard may be used as the basis for formal Application Programming Interfaces. Nevertheless, it is not a formal programming interface, and any such interface will need to address implementation issues not covered by this standard, including

the sizes and octet ordering of various multi-octet service parameters, and
the correlation of paired request and confirm, or indication and response, primitives.

1.3 Conformance

This standard does not specify individual implementations or products, nor do they constrain the implementations of application layer entities within industrial automation systems.

There is conformance of equipment to this application layer service definition standard mainly achieved through implementation of the modeled behavior of an application layer user (e.g. see user state machines) accompanied by implementation of conforming application layer protocols that fulfill the application layer services as defined in this standard.

PDF Catalog

PDF Pages	PDF Title
8	English CONTENTS
19	INTRODUCTION
20	1 Scope 1.1 General
21	1.2 Specifications 1.3 Conformance 2 Normative references
23	3 Terms, definitions, abbreviations, symbols and conventions
24	3.1 Referenced terms and definitions 3.2 Additional terms and definitions for decentralized periphery
32	3.3 Additional terms and definitions for media redundancy
33	3.4 Abbreviations and symbols
35	3.5 Conventions
39	Tables Table 1 – State machine description elements Table 2 – Description of state machine elements Table 3 – Conventions used in state machines
40	Table 4 – Conventions for services used in state machines
41	4 Concepts
42	5 Data type ASE 5.1 General Figures Figure 1 – Data type class hierarchy example
45	Table 5 – Data type overview
47	5.2 Formal definition of data type objects
48	5.3 FAL defined data types
49	Table 6 – V2 octets Table 7 – L2 octets
52	Table 8 – E2 octets Table 9 – E2 value range Table 10 – Unipolar2.16 octets
53	Table 11 – Unipolar2.16 value range
54	Table 12 – N2 value range
55	Table 13 – N4 value range
56	Table 14 – X2 value range
57	Table 15 – X4 value range Table 16 – C4 value range
59	Table 17 – T2 value range
60	Table 18 – T2 value range Table 19 – D2 value range
61	Table 20 – R2 value range
62	Table 21 – UUID for decentralized peripherals
63	Figure 2 – NetworkTime date relation Table 22 – Status least significant Bit of the fractional portion (20)
64	Table 23 – Status value range
66	Table 24 – OctetString2+Unsigned8 Table 25 – Float32+Unsigned8 octets
67	Table 26 – Unsigned8+Unsigned8 octets Table 27 – Unsigned16_S octets Table 28 – Unsigned16_S meaning
68	Table 29 – Integer16_S octets Table 30 – Integer16_S meaning Table 31 – Unsigned8_S octets
69	Table 32 – Unsigned8_S meaning Table 33 – OctetString_S octets Table 34 – OctetString_S status bits
70	5.4 Data type ASE service specification 6 Communication model for common services 6.1 Concepts Table 35 – F message trailer with 4 octets Table 36 – F message trailer with 5 octets
71	6.2 ASE data types Figure 3 – FAL ASEs communication architecture
72	6.3 Application Service Elements
78	Table 37 – Get
81	Table 38 – Set
85	Table 39 – Local Set Command
87	Table 40 – Identify
89	Table 41 – Hello
91	Figure 4 – PTCP applications
97	Table 42 – Start bridge
98	Table 43 – Start slave
99	Table 44 – Start master
100	Table 45 – Stop bridge
101	Table 46 – Stop slave
102	Table 47 – Stop master
103	Table 48 – Sync state change Table 49 – Line Delay change
104	Figure 5 – Clock drift measurement
105	Figure 6 – Multiple synchronization
111	Figure 7 – Media redundancy diagnosis dependencies
117	Table 50 – PPM Set Prov Data Table 51 – PPM Set Prov Status
118	Table 52 – PPM Activate
121	Table 53 – PPM Close Table 54 – PPM Start Table 55 – PPM Error
122	Table 56 – Get Cons Data
123	Table 57 – CPM Get cons status
124	Table 58 – CPM Set RedRole Table 59 – CPM Activate
126	Table 60 – CPM NoData
127	Table 61 – CPM Stop
130	Table 62 – APMS Activate
132	Table 63 – APMR Activate
133	Table 64 – APMS A Data
134	Table 65 – APMR A Data Table 66 – APMR Ack
135	Table 67 – APMS Error
136	Table 68 – APMS Error ERRCLS/ERRCODE Table 69 – APMR Error Table 70 – APMR Error ERRCLS/ERRCODE
137	Table 71 – APMS_Close Table 72 – APMR_Close
139	Table 73 – Connect
141	Table 74 – Release
142	Table 75 – Read
143	Table 76 – Write
144	Table 77 – Control
149	Table 78 – System capabilities
151	Table 79 – Auto negotiation support and status Table 80 – MDI Power Support
152	Table 81 – Link aggregation status
155	Table 82 – Remote systems data change
158	Table 83 – Local Get Time Table 84 – Local Set Time
159	Table 85 – Local time changed event
162	Table 86 – Allowed values of Forwarding Mode
163	Table 87 – Allowed values of Fast Forwarding Multicast MAC Add
164	Table 88 – Allowed values of Reduction Ratio Table 89 – Frame ID
166	Table 90 – Tx Port Entry
169	Table 91 – Dependencies of RedOrangePeriodBegin, OrangePeriodBegin, and GreenPeriodBegin
173	Table 92 – Port state change Table 93 – Set port state
174	Table 94 – Flush filtering data base
177	Figure 8 – Example of periods at a local port
179	Table 95 – MAU Type change Table 96 – Set MAU Type
183	Table 97 – IP Multicast address Table 98 – Set ARP Cache
186	Table 99 – Enterprise number
187	Table 100 – Vendor OUI
188	Table 101 – P Data
190	Table 102 – N Data
191	Table 103 – A Data
192	Table 104 – C Data
193	7 Communication model for decentralized periphery 7.1 Concepts Table 105 – Requirements and features
194	Figure 9 – Example of communication between controlling devices and field devices
195	Figure 10 – Example of communication between an engineering station and several controlling and field devices Figure 11 – Example of communication between field devices and a server station Figure 12 – Example of communication between field devices
197	Figure 13 – Structural units of one arbitrary API of an IO device (general)
198	Figure 14 – Example 1 structural units for interfaces and ports within API 0
199	Figure 15 – Example 2 structural units for interfaces and ports within API 0
201	Figure 16 – Identification hierarchy
204	Figure 17 – Overview of application processes Figure 18 – IO device with APs, slots and subslots
207	Figure 19 – Application Process with application process objects (APOs)
208	Figure 20 – Access to a remote APO
209	Figure 21 – Access to a remote APO for provider/consumer association
210	Figure 22 – Example of one AR with two AREPs
211	7.2 ASE data types 7.3 ASEs Figure 23 – FAL ASEs communication architecture
212	Table 106 – Binding Record Data services
213	Figure 24 – Relation of a record data object to one real object Figure 25 – Relation of a record data object to two real objects
215	Table 107 – Persistence behavior for record data objects
218	Table 108 – Read
219	Table 109 – Read Services
222	Table 110 – Read Query
224	Table 111 – Write
226	Table 112 – Write Services
228	Table 113 – Data elements of Write Combined Object Container
229	Table 114 – Local Write Multiple
231	Table 115 – Local New Write Multiple
234	Figure 26 – Overview IO ASE service interactions
244	Table 116 – Local Set Input
245	Table 117 – Local Set Input IOCS
246	Table 118 – Local Get Input
247	Table 119 – Local Get Input IOCS
248	Table 120 – Local New Input Table 121 – Local Set Redundancy
249	Table 122 – Local Set State
250	Table 123 – Local Data State Changed
251	Table 124 – Data elements of Read Record Input Data Object Element
252	Table 125 – Local Set Output
253	Table 126 – Local Set Output IOCS
254	Table 127 – Local Get Output
255	Table 128 – Local Get Output IOCS
256	Table 129 – Local New Output
257	Table 130 – Local Set Provider State
258	Table 131 – Data elements of Read Record Output Data Object Element
260	Table 132 – Data elements of Read Substitute Value
261	Table 133 – Data elements of Write Substitute Value
263	Table 134 – Data elements of Read LogBook Data
264	Table 135 – Local Create LogBook Entry
265	Figure 27 – Severity classification of diagnosis and maintenance
271	Table 136 – Channel Error Type
272	Table 137 – Ext Channel Error type
276	Table 138 – Allowed combinations of Channel Error Type and Ext Channel Error Type
277	Table 139 – Ext Channel Add Value for Accumulative Info
278	Table 140 – Local Add Diagnosis Entry
280	Table 141 – Local Remove Diagnosis Entry
282	Table 142 – Local Diagnosis Event
283	Table 143 – General Data definition for Diagnosis services
299	Table 144 – Data elements of Read Nested Diagnosis Information
300	Figure 28 – State transition diagram DIAG_DIAG Table 145 – Remote primitives issued or received by DIAG_DIAG Table 146 – Local primitives issued or received by DIAG_DIAG
301	Table 147 – State table DIAG_DIAG
302	Table 148 – Functions, Macros, Timers and Variables used by DIAG_DIAG
303	Table 149 – Remote primitives issued or received by DIAG_MR Table 150 – Local primitives issued or received by DIAG_MR
304	Figure 29 – State transition diagram DIAG_MR Table 151 – State table DIAG_MR
306	Table 152 – Functions, Macros, Timers and Variables used by DIAG_MR
307	Table 153 – Remote primitives issued or received by DIAG_MD Table 154 – Local primitives issued or received by DIAG_MD
308	Figure 30 – State transition diagram DIAG_MD Table 155 – State table DIAG_MD
309	Table 156 – Functions, Macros, Timers and Variables used by the maintenance demanded entry
311	Figure 31 – State transition diagram DIAG_QUALIFIED Table 157 – Remote primitives issued or received by DIAG_QUALIFIED Table 158 – Local primitives issued or received by DIAG_QUALIFIED
312	Table 159 – State table DIAG_QUALIFIED Table 160 – Functions, Macros, Timers and Variables used by DIAG_QUALIFIED
315	Table 161 – Alarm type
318	Table 162 – Alarm Notification
321	Table 163 – Channel Diagnosis
322	Table 164 – Manufacturer Specific Diagnosis Table 165 – Submodule Diagnosis State Table 166 – AR Diagnosis State
324	Table 167 – User Structure Identifier
325	Table 168 – Semantics of Specifier
332	Figure 32 – Example of a resource model at the alarm source
340	Table 169 – Module State
341	Table 170 – Usage with respect to CR type
342	Table 171 – Detail
343	Table 172 – AR Info
344	Table 173 – Ident Info
355	Table 174 – Binding Context services
356	Table 175 – Connect
368	Table 176 – Connect Device Access
371	Table 177 – Release
372	Table 178 – Abort
373	Table 179 – Local AR Abort
374	Table 180 – Prm Begin
377	Table 181 – Prm End
378	Table 182 – Application Ready
381	Table 183 – General Data definition for identification services
385	Table 184 – Data elements of Read Module Diff Block
386	Table 185 – Data elements of Read API Data
387	Table 186 – Data elements of Read I&M0 Filter Data
389	Table 187 – Data elements of Read I&M0 Data
391	Table 188 – Data elements of Write I&M1 Data Table 189 – Data elements of Read I&M1 Data
392	Table 190 – Data elements of Write I&M2 Data Table 191 – Data elements of Read I&M2 Data
393	Table 192 – Data elements of Write I&M3 Data Table 193 – Data elements of Read I&M3 Data Table 194 – Data elements of Write I&M4 Data
394	Table 195 – Data elements of Read I&M4 Data Table 196 – Data elements of Read Autoconfiguration Data
397	Table 197 – Data elements of Write Expected Fast Startup Data
398	Table 198 – Data elements of Read Expected Fast Startup Data
399	Table 199 – Data elements of Read GSD Data
400	Table 200 – Data elements of Read GSD Data
401	Figure 33 – Basic model for isochronous applications
402	Figure 34 – General isochronous application model (example CACF == 1)
403	Figure 35 – General isochronous application model (example CACF == 2)
408	Table 201 – Data elements of Write Isochronous Mode Data Table 202 – Data elements of Read Isochronous Mode Data
409	Table 203 – Local SYNCH Event
410	Figure 36 – ASE relations in an IO device operating in isochronous mode for a submodule
412	Figure 37 – State transition diagram of ISOM_SYNC Table 204 – Remote primitives issued or received by ISOM_SYNC Table 205 – Local primitives issued or received by ISOM_SYNC
413	Table 206 – State table ISOM_SYNC Table 207 – Functions, Macros, Timers and Variables used by the ISOM_SYNC
414	Table 208 – Remote primitives issued or received for ISOM_OUT Table 209 – Local primitives issued or received for ISOM_OUT
415	Figure 38 – State transition diagram ISOM_OUT
416	Table 210 – State table ISOM_OUT
418	Table 211 – Functions, Macros, Timers and Variables used by the ISOM_OUT
419	Table 212 – Remote primitives issued or received for ISOM_IN Table 213 – Local primitives issued or received for ISOM_IN
420	Figure 39 – State transition diagram ISOM_IN
421	Table 214 – State table ISOM_IN
422	Table 215 – Functions, Macros, Timers and Variables used by the ISOM_IN
428	Table 216 – Subslot number for interface submodules
432	Table 217 – Sync Properties Role Table 218 – Sync Class
433	Table 219 – Distributed Watchdog Factor
434	Table 220 – Restart Factor For Distributed Watchdog Table 221 – DFP Mode Table 222 – SFIOCRProperties.DFPRedundantPathLayout
435	Table 223 – SFCRC16
438	Table 224 – Subslot number for port submodules Table 225 – Fiber Optic Types
439	Table 226 – Fiber Optic Cable Types
443	Table 227 – TimePLLWindow Table 228 – Data elements of Read PDev Data
450	Table 229 – Data elements of Read PD Real Data
454	Table 230 – Data elements of Read PD Expected Data
458	Table 231 – Read PD Interface Data Real
459	Table 232 – Data elements of Write PD Interface Adjust Table 233 – Data elements of Read PD Interface Adjust
460	Table 234 – Data elements of Write PD IR Data
464	Table 235 – Data elements of Read PD IR Data
468	Table 236 – Data elements of Write PD Sync Data
469	Table 237 – Data elements of Read PD Sync Data
471	Table 238 – Local Sync State Info
472	Table 239 – Data elements of Write PD IR Subframe Data
474	Table 240 – Data elements of Read PD IR Subframe Data
475	Table 241 – Data elements of Write PD Time Data Table 242 – Data elements of Read PD Time Data
476	Table 243 – Data elements of Read PD Interface MRP Data Real
477	Table 244 –Data elements of Write PD Interface MRP Data Check Table 245 – Data elements of Read PD Interface MRP Data Check
478	Table 246 – Data elements of Write PD Interface MRP Data Adjust
479	Table 247 – Data elements of Read PD Interface MRP Data Adjust Table 248 – Data elements of Write PD Interface FSU Data Adjust
480	Table 249 – Data elements of Read PD Interface FSU Data Adjust
481	Table 250 – Data elements of Write PD NC Data Check
482	Table 251 – Data elements of Read PD NC Data Check Table 252 – Data elements of Read PD Port Data Real
484	Table 253 – Data elements of Write PD Port Data Check
485	Table 254 – Data elements of Read PD Port Data Check
486	Table 255 – Data elements of Write PD Port Data Adjust Table 256 – Data elements of Read PD Port Data Adjust
487	Table 257 – Data elements of Read Port FO Data Real
488	Table 258 – Data elements of Write PD Port FO Data Check
489	Table 259 – Data elements of Read PD Port FO Data Check
490	Table 260 – Data elements of Write PD Port FO Data Adjust Table 261 – Data elements of Read PD Port FO Data Adjust
491	Table 262 – Data elements of Read PD Port MRP Data Real Table 263 – Data elements of Write PD Port MRP Data Adjust
492	Table 264 – Data elements of Read PD Port MRP Data Adjust Table 265 – Data elements of Read PD Port Statistic
495	Figure 40 – Assignment of communication relationship to application relationship
499	Figure 41 – Implicit application relationship
500	Figure 42 – Example IO application relationship (one-to-one)
501	Figure 43 – Example IO application relationship one-to-many
505	Table 266 – Device Access Table 267 – Companion AR Table 268 – Acknowledge Companion AR Table 269 – Startup Mode
506	Table 270 – Pull Module Alarm Allowed
509	Table 271 – Input Valid on Backup AR Table 272 – Activate Redundancy Alarm
510	Table 273 – APStructureIdentifier with API := 0 Table 274 – APStructureIdentifier with API != 0
514	Table 275 – Traffic Classes versus RT Class
515	Table 276 – Frame ID
516	Table 277 – Reduction Ratios
522	Table 278 – Data elements of Read AR Data
527	Table 279 – Local Set AR State Table 280 – Local AR In Data
528	7.4 Behavior of an IO device Figure 44 – Overview ASE state machines for IO device
529	Table 281 – Remote primitives issued or received by DEVSM Table 282 – Local primitives issued or received by DEVSM
531	Figure 45 – State transition diagram DEVSM
532	Table 283 – State table DEVSM
536	Table 284 – Functions, Macros, Timers and Variables by DEVSM
537	Table 285 – Remote primitives issued or received by REM_CHK
538	Figure 46 – State transition diagram REM_CHK Table 286 – Local primitives issued or received by REM_CHK
539	Table 287 – State table REM_CHK
544	Table 288 – Functions, Macros, Timers and Variables by REM_CHK Table 289 – Remote primitives issued or received LOC_LNK
545	Figure 47 – State transition diagram LOC_LNK Table 290 – Local primitives issued or received LOC_LNK
546	Table 291 – State table LOC_LNK
549	Table 292 – Functions, Macros, Timers and Variables used by LOC_LNK
550	Table 293 – Remote primitives issued or received by FOMR Table 294 – Local primitives issued or received by FOMR
551	Figure 48 – State transition diagram FOMR Table 295 – State table FOMR
552	Table 296 – Functions, Macros, Timers and Variables used by FOMR
553	Figure 49 – State transition diagram FOMD Table 297 – Remote primitives issued or received by FOMD Table 298 – Local primitives issued or received by FOMD
554	Table 299 – State table FOMD
555	Table 300 – Functions, Macros, Timers and Variables by FOMD Table 301 – Remote primitives issued or received by FODIAG Table 302 – Local primitives issued or received by FODIAG
556	Figure 50 – State transition diagram FODIAG Table 303 – State table FODIAG
557	Table 304 – Functions, Macros, Timers and Variables by FODIAG
559	Table 305 – Remote primitives issued or received by RSMSM
560	Figure 51 – State transition diagram RSMSM Table 306 – Local primitives issued or received by RSMSM Table 307 – State table RSMSM
561	Table 308 – Functions, Macros, Timers and Variables used by RSMSM
562	Table 309 – Rules for Submodule State.Ident Info
564	Figure 52 – Ownership handling
566	Table 310 – Remote primitives issued or received by OWNSM and ASSSM
567	Figure 53 – State transition diagram OWNSM Figure 54 – State transition diagram ASSSM Table 311 – Local primitives issued or received by OWNSM
568	Table 312 – State table OWNSM
574	Table 313 – State table ASSSM
575	Table 314 – Functions, Macros, Timers and Variables used by OWNSM
576	Table 315 – Functions, Macros, Timers and Variables used by ASSSM Table 316 – Rules for Submodule State.AR Info
577	Table 317 – Remote primitives issued or received by PLUGSM
578	Table 318 – Local primitives issued or received by PLUGSM
579	Figure 55 – State transition diagram PLUGSM
580	Table 319 – State table PLUGSM
581	Table 320 – Functions, Macros, Timers and Variables used by PLUGSM Table 321 – Remote primitives issued or received by PULLSM
582	Figure 56 – State transition diagram PULLSM Table 322 – Local primitives issued or received by PULLSM
583	Table 323 – State table PULLSM Table 324 – Functions, Macros, Timers and Variables used by PULLSM
584	Figure 57 – State transition diagram SYNC_DIAG Table 325 – Remote primitives issued or received by SYNC_DIAG Table 326 – Local primitives issued or received by SYNC_DIAG
585	Table 327 – State table SYNC_DIAG
586	Table 328 – Functions, Macros, Timers and Variables used by SYNC_DIAG
587	7.5 Behavior of an IO controller
588	Table 329 – Remote primitives issued or received by CTLSM Table 330 – Local primitives issued or received by CTLSM
589	Figure 58 – State diagram CTLSM
590	Table 331 – State table CTLSM
592	7.6 Application characteristics Table 332 – Functions, Macros, Timers and Variables used by CTLSM
593	7.7 Summary of FAL services Figure 59 – Example of network topology including slower wireless segments Figure 60 – Example of media redundancy including wireless segments
594	Table 333 – FAL services of the IO device Table 334 – FAL services of the IO controller
596	Annex A (informative)Device instances Figure A.1 – Instance model
598	Annex B (informative)Components of an Ethernet interface Figure B.1 – Scheme of an Ethernet interface
599	Figure B.2 – Scheme of an Ethernet interface with bridging ability
600	Figure B.3 – Scheme of an Ethernet interface with optical ports
601	Figure B.4 – Scheme of an Ethernet interface with bridging abilityusing radio communication Figure B.5 – Scheme of an Ethernet interface with radio communication
602	Annex C (informative)Scheme of MAC address assignment Figure C.1 – Scheme of MAC address assignment
603	Annex D (informative)Collection of objects Figure D.1 – Example for an intersection of IO device, slot, and AR
604	Annex E (informative)Measurement of the fast startup time Figure E.1 – Measurement of the fast startup time
605	Annex F (informative)Dynamic Frame Packing Figure F.1 – Frame Layout
606	Figure F.2 – Sub frame Layout
607	Figure F.3 – End to End Figure F.4 – Dynamic frame packing
608	Figure F.5 – Dynamic frame packing – Truncation of outputs Figure F.6 – Dynamic frame packing – Outbound Pack
609	Figure F.7 – Dynamic frame packing – Concatenation of inputs
610	Figure F.8 – Dynamic frame packing – Inbound Pack
611	Figure F.9 – Dynamic frame packing – Distributed watchdog
612	Figure F.10 – Interrelation between IO CR and dynamically packed frame
613	Annex G (informative)Building IR Data
614	Figure G.1 – Bridge- and LineDelay Figure G.2 – Sample Topology
615	Figure G.3 – Slip Stream Effect downstream
616	Figure G.4 – Using the slip stream effect in a comb topology downstream
618	Bibliography

Published By	Publication Date	Number of Pages
BSI	2014	620


PDF Format	Searchable	Printable	Preview Now

Status	Withdrawn
Title	Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 10 elements
Replaces	BS EN 61158-5-10:2012
Publisher	BSI
Committee	GEL/65/3
Pages	620
Publication Date	2014-10-31
Withdrawn Date	2022-07-29
Replaced By	BS EN IEC 61158-5-10:2019
ISBN	978 0 580 79457 5
Standard Number	BS EN 61158-5-10:2014
Identical National Standard Of	EN 60745-2-15:2009, IEC 61158-5-10:2014, EN 61158-5-10:2014
Descriptors	Communication procedures, Fieldbus, Communication networks, Computer networks, Industrial, Data transmission, Open systems interconnection, Bus networks, Interfaces (data processing), Process control, Automatic control systems, Application layer (OSI)
ICS Codes	35.110 - Networking

BS EN 61158-5-10:2014

PDF Catalog