Schneider Electric Premium and Atrium Using EcoStruxure™ Control Expert - Fipio Bus User Guide
광고
광고
Premium and Atrium Using EcoStruxure™ Control Expert
35008155 12/2018
Premium and Atrium Using
EcoStruxure™
Control Expert
Fipio Bus
Setup Manual
(Original Document)
12/2018 www.schneider-electric.com
2
The information provided in this documentation contains general descriptions and/or technical characteristics of the performance of the products contained herein. This documentation is not intended as a substitute for and is not to be used for determining suitability or reliability of these products for specific user applications. It is the duty of any such user or integrator to perform the appropriate and complete risk analysis, evaluation and testing of the products with respect to the relevant specific application or use thereof. Neither Schneider Electric nor any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information contained herein. If you have any suggestions for improvements or amendments or have found errors in this publication, please notify us.
You agree not to reproduce, other than for your own personal, noncommercial use, all or part of this document on any medium whatsoever without permission of Schneider Electric, given in writing. You also agree not to establish any hypertext links to this document or its content.
Schneider Electric does not grant any right or license for the personal and noncommercial use of the document or its content, except for a non-exclusive license to consult it on an "as is" basis, at your own risk. All other rights are reserved.
All pertinent state, regional, and local safety regulations must be observed when installing and using this product. For reasons of safety and to help ensure compliance with documented system data, only the manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant instructions must be followed.
Failure to use Schneider Electric software or approved software with our hardware products may result in injury, harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
© 2018 Schneider Electric. All rights reserved.
35008155 12/2018
Table of Contents
Safety Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Part I Introduction to Communication by Fipio Bus . . . . . .
Chapter 1 Communication by Fipio bus . . . . . . . . . . . . . . . . . . . . .
The Fipio Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples of architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Part II Hardware Implementation for Fipio Bus . . . . . . . . . .
Chapter 2 Introduction to and implementation of Fipio bus devices
2.1 Introduction to Fipio bus architectures. . . . . . . . . . . . . . . . . . . . . . . . .
Architecture of Fipio bus with connection auxiliaries (IP20) . . . . . . . .
Architecture of Fipio Bus with Connection Auxiliaries (IP65). . . . . . . .
Architecture of Fipio bus with Connection Auxiliaries (IP67) . . . . . . . .
Fipio Architecture with OZD FIP G3 . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Master Fipio communication built into processors. . . . . . . . . . . . . . . .
Built-in Fipio Link on Premium/Atrium Processors . . . . . . . . . . . . . . .
2.3 TSX FPP 10 PCMCIA card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connection of the TSX FPP 10 card . . . . . . . . . . . . . . . . . . . . . . . . . .
Precautions to be taken when connecting PCMCIA card . . . . . . . . . .
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mounting Cards and Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying operating state of PCMCIA cards . . . . . . . . . . . . . . . . . . .
Visual Diagnostics for TSX FPP 10 PCMCIA Card . . . . . . . . . . . . . . .
Consumption of PCMCIA card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 TSX FPC 10 module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 TSX FPP 20 PCMCIA card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Part III Software Implementation for Fipio Bus. . . . . . . . . . .
Chapter 3 Presentation and Specifications of the Fipio Bus . . . . . .
3.1 Introduction to Fipio communication . . . . . . . . . . . . . . . . . . . . . . . . . .
Addressing of Remote Module Language Objects on a FIPIO Bus . .
46
47
49
50
50
44
45
45
46
38
39
42
43
33
35
36
37
29
30
30
32
22
23
24
26
14
16
19
21
11
13
7
9
35008155 12/2018
3
4
3.2 Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware Compatibilities relating to the Bus Manager . . . . . . . . . . . .
Software Compatibilities relating to the Bus Manager . . . . . . . . . . . . .
Software Compatibility: Network Transparency . . . . . . . . . . . . . . . . . .
Software Compatibility: Outside Communication . . . . . . . . . . . . . . . . .
TBX Device Compatibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Momentum Device Compatibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Programming Terminal Compatibilities . . . . . . . . . . . . . . . . . . . . . . . .
Miscellaneous Device Compatibilities . . . . . . . . . . . . . . . . . . . . . . . . .
Fipio Bus Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saturation of Fipio Messaging Service. . . . . . . . . . . . . . . . . . . . . . . . .
Network Cycle Time: Mono Task Application. . . . . . . . . . . . . . . . . . . .
Network Cycle Time: Multitasking Application . . . . . . . . . . . . . . . . . . .
Example of calculating the network cycle times of a multitasking application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4 Installation methodology. . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5 Configuring Fipio communication . . . . . . . . . . . . . . . . . . .
5.1 General information on configuration . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Fipio bus configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access the Fipio Bus Configuration Screen. . . . . . . . . . . . . . .
Fipio Bus Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Add a Device on the Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Add an Extension Module on the Bus . . . . . . . . . . . . . . . . . . .
How to Delete/Move/ Duplicate a Bus Device . . . . . . . . . . . . . . . . . . .
Changing the Fipio Communicator Type . . . . . . . . . . . . . . . . . . . . . . .
Fipio Bus Displayed in the Project Browser . . . . . . . . . . . . . . . . . . . . .
How to Access the Properties Screen of the Fipio Bus . . . . . . . . . . . .
Properties of the Fipio Bus: General Tab. . . . . . . . . . . . . . . . . . . . . . .
Properties of the Fipio Bus: Expert tab . . . . . . . . . . . . . . . . . . . . . . . .
Expert Tab: Manual Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 Configuration of devices on the Fipio bus . . . . . . . . . . . . . . . . . . . . . .
How to Access the Configuration Screen for a Fipio Device . . . . . . . .
Configuration Screen of a Fipio Device . . . . . . . . . . . . . . . . . . . . . . . .
How to Access Different Parameters Depending on the Type of Device
95
96
97
99
85
87
89
91
82
82
83
84
77
79
79
81
100
101
103
104
105
107
59
61
63
65
53
54
55
56
66
69
71
72
74
35008155 12/2018
5.4 Management of Inputs/Outputs by Control Expert Tasks: . . . . . . . . .
How to Access the Configuration of Control Expert Tasks in Fipio Mode
Management of Inputs/Outputs by Control Expert Tasks . . . . . . . . . .
5.5 Confirmation of the Fipio bus configuration . . . . . . . . . . . . . . . . . . . . .
Refused Build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples of Validation Refusals . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 6 Programming Fipio communication . . . . . . . . . . . . . . . .
Fipio Fault Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples of Detection of Explicit Exchange Saturation . . . . . . . . . . .
Chapter 7 Debugging a Fipio communication . . . . . . . . . . . . . . . . .
Debug Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access the Debug Screens of Remote Devices . . . . . . . . . . .
Debug Screen for a Device on the Fipio Bus . . . . . . . . . . . . . . . . . . .
Chapter 8 Fipio communication diagnostics . . . . . . . . . . . . . . . . . .
Diagnostics Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access the Fipio Bus Monitoring Screen. . . . . . . . . . . . . . . . .
Diagnostics Screen: Fipio Bus Monitoring. . . . . . . . . . . . . . . . . . . . . .
How to Access the Device Monitoring Screen. . . . . . . . . . . . . . . . . . .
Diagnostics Screen: Device Monitoring. . . . . . . . . . . . . . . . . . . . . . . .
How to Access the Device Monitoring Screen for a Single Device . . .
Diagnostics Screen: Device Monitoring. . . . . . . . . . . . . . . . . . . . . . . .
How to Access the Communication Faults History Screen . . . . . . . . .
Diagnostics Screen: Communication Errors History . . . . . . . . . . . . . .
Chapter 9 Language objects associated with Fipio communication
9.1 Language Objects and IODDTs for Fipio Communication . . . . . . . . .
Presentation of Language Objects for Fipio Communication . . . . . . .
Implicit Exchange Language Objects Associated with the Application-
Specific Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Explicit Exchange Language Objects Associated with the Application-
Specific Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Management of Exchanges and Reports with Explicit Objects . . . . . .
Details of Implicit Exchange Objects for Fipio Communication . . . . . .
9.2 The IODDT Type T_GEN_MOD Applicable to All Modules . . . . . . . . .
Details of the Language Objects for the IODDT of Type T_GEN_MOD
Chapter 10 Fipio communication standard profiles . . . . . . . . . . . . . .
10.1 Introduction to standard Fipio communication profiles . . . . . . . . . . . .
Standard profiles: general . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Designation of a Standard Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Catalog Standard Profiles Proposed by Control Expert . . . . . .
35008155 12/2018
151
152
154
158
159
159
161
162
163
164
165
119
125
126
127
128
131
132
133
108
109
110
112
113
114
117
118
134
136
137
139
140
142
143
147
148
149
5
6
10.2 Configuration of the Fipio bus standard profiles. . . . . . . . . . . . . . . . . .
Configuration Screen for a Standard Profile . . . . . . . . . . . . . . . . . . . .
How to Modify the Parameters of a Standard Profile . . . . . . . . . . . . . .
Adjustment Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Debugging the Fipio bus standard profiles. . . . . . . . . . . . . . . . . . . . . .
Debug Screen for a Standard Profile . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Modify the Debug Parameters for a Standard Profile . . . . . . .
10.4 Language objects associated with the Fipio bus standard profiles . . .
Details of the Language Objects for the IODDT of Type T_STDP_GEN
Objects Accessible by Standard Profiles . . . . . . . . . . . . . . . . . . . . . . .
Implicit Exchange Language Objects. . . . . . . . . . . . . . . . . . . . . . . . . .
Explicit Exchange Language Objects. . . . . . . . . . . . . . . . . . . . . . . . . .
Language Objects Associated with Configuration . . . . . . . . . . . . . . . .
186
Chapter 11 Fipio Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
187
11.1 Introduction to Fipio Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
179
181
183
184
Fipio Agent: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Periodic Data Exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Special Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communication from a Fipio Agent . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Configuration of Fipio Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Fipio Agent Parameters Using PCMCIA Cards . . . . . . . . . . . .
Configuration Screen of a Fipio Agent . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 Debugging Fipio Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Debug Screen of a Fipio Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4 Language objects associated with the Fipio Agents . . . . . . . . . . . . . .
Implicit Exchange Language Objects. . . . . . . . . . . . . . . . . . . . . . . . . .
Explicit Exchange Language Objects. . . . . . . . . . . . . . . . . . . . . . . . . .
Explicit Exchange Management and Report . . . . . . . . . . . . . . . . . . . .
Language Objects Associated with Configuration . . . . . . . . . . . . . . . .
167
168
170
172
173
174
176
178
199
199
201
202
203
204
205
188
189
190
191
192
194
195
197
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
207
35008155 12/2018
Safety Information
Important Information
NOTICE
Read these instructions carefully, and look at the equipment to become familiar with the device before trying to install, operate, service, or maintain it. The following special messages may appear throughout this documentation or on the equipment to warn of potential hazards or to call attention to information that clarifies or simplifies a procedure.
35008155 12/2018
7
PLEASE NOTE
Electrical equipment should be installed, operated, serviced, and maintained only by qualified personnel. No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction and operation of electrical equipment and its installation, and has received safety training to recognize and avoid the hazards involved.
8
35008155 12/2018
About the Book
At a Glance
Document Scope
This manual describes the implementation of hardware and software for Fipio communication with
Premium and Atrium PLCs.
Validity Note
This documentation is valid for EcoStruxure™ Control Expert 14.0 or later.
The technical characteristics of the devices described in the present document also appear online.
To access the information online:
Step
1
2
3
4
5
6
Action
Go to the Schneider Electric home page www.schneider-electric.com
.
In the Search box type the reference of a product or the name of a product range.
Do not include blank spaces in the reference or product range.
To get information on grouping similar modules, use asterisks ( * ).
If you entered a reference, go to the Product Datasheets search results and click on the reference that interests you.
If you entered the name of a product range, go to the Product Ranges search results and click on the product range that interests you.
If more than one reference appears in the Products search results, click on the reference that interests you.
Depending on the size of your screen, you may need to scroll down to see the data sheet.
To save or print a data sheet as a .pdf file, click Download XXX product datasheet.
The characteristics that are presented in the present document should be the same as those characteristics that appear online. In line with our policy of constant improvement, we may revise content over time to improve clarity and accuracy. If you see a difference between the document and online information, use the online information as your reference.
35008155 12/2018
9
Related Documents
Title of Documentation
Communication Services and Architectures, Reference Manual
EcoStruxure™ Control Expert, System Bits and Words, Reference
Manual
Reference Number
35010500 (English),
35010501 (French),
35006176 (German),
35013966 (Italian),
35006177 (Spanish),
35012196 (Chinese)
EIO0000002135 (English),
EIO0000002136 (French),
EIO0000002137 (German),
EIO0000002138 (Italian),
EIO0000002139 (Spanish),
EIO0000002140 (Chinese)
You can download these technical publications and other technical information from our website at https://www.schneider-electric.com/en/download
Product Related Information
WARNING
UNINTENDED EQUIPMENT OPERATION
The application of this product requires expertise in the design and programming of control systems. Only persons with such expertise should be allowed to program, install, alter, and apply this product.
Follow all local and national safety codes and standards.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
10
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Introduction to Fipio Bus
35008155 12/2018
Introduction to Communication by Fipio Bus Part I
Introduction to Communication by Fipio Bus
35008155 12/2018
11
Introduction to Fipio Bus
12
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
General points concerning Fipio bus
35008155 12/2018
Communication by Fipio bus Chapter 1
Communication by Fipio bus
Subject of this Chapter
This Chapter introduces some general points concerning communication by Fipio bus.
What Is in This Chapter?
This chapter contains the following topics:
Topic
The Fipio Bus
Examples of architecture
Page
35008155 12/2018
13
General points concerning Fipio bus
The Fipio Bus
General
Fipio is a field bus which allows the decentralization of the inputs/outputs of a PLC station and its industrial peripheral devices nearest to the operational part.
Fipio bus is part of the WorldFIP product range from Schneider Automation S.A.S.
From a PLC station whose processor has a built-in Fipio link, the Fipio bus is used to connect 1 to
127 devices such as:
Momentum remote input/output modules (discrete, analog and counting modules),
TBX IP20 remote input/output modules (discrete and analog modules),
TBX IP65 and IP67 remote input/output modules (discrete modules),
XBT-F terminals,
Lexium, ATV 58 variable speed controllers,
Devices which conform to standard profiles,
Agent PLCs, PCs,
Inductel stations,
An AS-i gateway.
The Fipio field bus can be used in a single architecture (mono-station) or in a more complex architecture (multi-station) where several Fipio segments can be brought together by a local network at a higher level such as Fipway or Ethernet TCP_IP for example.
The Fipio protocol uses producer/consumer type exchanges and the bus is managed by a bus arbiter.
Manager PLC
A PLC station which has a built-in Fipio link is called a manager PLC
see page 30
.
Agent PLC
A PLC station with a PCMCIA card installed in a host slot is called an agent PLC
see page 32
14
35008155 12/2018
General points concerning Fipio bus
Main Characteristics
Structure
Nature
Topology
Access method
Communication
Privileged exchanges
Open field bus, conforming to World FIP and FIP standards.
Devices linked by chaining or branching.
Managed by a bus arbiter
By exchange of variables which can be accessed by the user in the form of Control Expert objects and X-Way datagrams.
Cyclical exchange of status variables and remote input/output commands
Transmission
Binary rate
Medium
1 Mb/s.
Shielded twisted pair (150 Ohms of characteristic impedance) or fiber optic.
Configuration
Number of connection points
Number of segments
128 logic connection points for whole architecture
15 maximum (in cascade format) using electrical or optical repeaters (14 maximum in cascade format).
Number of repeaters
PLC
Length
An electrical or optical repeater is required every 1000 meters or every 32 devices.
One manager PLC (connection point address 0).
Programming terminal One programming terminal (must be connected to connection point
63).
The length of a segment depends on its type of branches:
1000 meters maximum without repeater.
1500 meters maximum between the devices which are the furthest apart.
WARNING
UNEXPECTED EQUIPMENT OPERATION
You are advised against connecting/disconnecting elements from the Fipio bus while powered up as certain devices may then not restart.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
35008155 12/2018
15
General points concerning Fipio bus
Examples of architecture
Premium station
Illustration:
16
35008155 12/2018
Atrium station
Illustration:
General points concerning Fipio bus
35008155 12/2018
17
General points concerning Fipio bus
18
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Fipio Hardware Implementation
35008155 12/2018
Hardware Implementation for Fipio Bus Part II
Hardware Implementation for Fipio Bus
35008155 12/2018
19
Fipio Hardware Implementation
20
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Fipio hardware implementation
35008155 12/2018
Introduction to and implementation of Fipio bus devices Chapter 2
Introduction to and implementation of Fipio bus devices
Subject of this Chapter
This Chapter introduces the different Fipio bus architectures and the implementation of devices.
What Is in This Chapter?
This chapter contains the following sections:
Section
2.1
2.2
2.3
2.4
2.5
Topic
Introduction to Fipio bus architectures
Master Fipio communication built into processors
TSX FPP 10 PCMCIA card
TSX FPC 10 module
TSX FPP 20 PCMCIA card
Page
35008155 12/2018
21
Fipio hardware implementation
Introduction to Fipio bus architectures Section 2.1
Introduction to Fipio bus architectures
Subject of this Section
This Section introduces some different Fipio bus architectures.
What Is in This Section?
This section contains the following topics:
Topic
Architecture of Fipio bus with connection auxiliaries (IP20)
Architecture of Fipio Bus with Connection Auxiliaries (IP65)
Architecture of Fipio bus with Connection Auxiliaries (IP67)
Fipio Architecture with OZD FIP G3
Page
22
35008155 12/2018
Fipio hardware implementation
Architecture of Fipio bus with connection auxiliaries (IP20)
At a Glance
The architecture below shows the Fipio bus and the different devices (IP20) of which it is composed.
Description
The following table shows the devices on the bus:
6
7
8
4
5
2
3
Number Product reference
1 TSX FP CA/CRxxx
TSX FP CCxxx
TSX FP CE030
TSX FP ACC7
TSX FP ACC3 or TSX FP ACC4 or TSX FP ACC14
9
TSX FP ACC2
TSX FP ACC12
TSX FP ACC6
TSX FP ACC8
TBX BLP 01
Description
Trunk cable
Drop cable
Connection cable for terminals and PCs
Line terminator
Branching devices
Connector for daisy-chaining or branching
Connector for Premium PLC
Electrical repeater or fiber optic repeater if fiber optic link used
Connector for connecting TBXs
The Fipio reference manual (TSX DR FIP) specifies the characteristics of each device.
35008155 12/2018
23
Fipio hardware implementation
Architecture of Fipio Bus with Connection Auxiliaries (IP65)
At a Glance
The architecture below shows the Fipio bus and the different devices (IP65) of which it is composed.
24
35008155 12/2018
Fipio hardware implementation
Description
The following table shows the devices on the bus:
9
10
11
6
7
4
5
8
2
3
Number
1
Reference Description
TSX FP CA/CR••• Trunk cable
TSX FP CC•••
TSX FP CE030
Branch cable
Connection cable for terminals and PCs
TSX FP ACC7
TSX FP ACC4
TSX FP ACC2
TSX FP ACC12
TSX FP ACC6
TSX FP ACC8
Line terminator
Branching device
Connector for daisy-chaining or branching
Connector for Premium PLC
Electrical repeater or fiber optic repeater if fiber optic link used
TBX BLP 10
TBX FP ACC10
TSX FP CF•••
Connector for connecting IP 65 TBXs
Branching device
Remote power supply cable
The Fipio reference manual (TSX DR FIP) specifies the characteristics of each device.
35008155 12/2018
25
Fipio hardware implementation
Architecture of Fipio bus with Connection Auxiliaries (IP67)
Illustration
The diagram below shows the possible architectures which may be used to connect IP67 sealed
I/O modules, as well as the accessories used, to the Fipio bus.
26
A Branch head.
B IP67 branch.
35008155 12/2018
Fipio hardware implementation
Description
The following table presents the various accessories that make it possible to assemble the desired configuration whilst observing all the operating constraints of the Fipio bus.
Number Part Number
1 TSX EF ACC 99
2
3
4
5
6
7
8
9
TSX EF CF 01
TSX EF CM 01
TSX EF CF 03
TSX EF CM 03
TSX EF CT 03
TSX EF CF 02
TSX FP ACC 2 or
TSX FP ACC 12
TSX EF ACC 2••• and
TSX EF ACC 2••••
Type of connection Description
Branch box.
This IP65 branch box can be used to perform 3 functions:
Connection of a 24 VDC power supply,
Creation of an IP67 branch,
Connection of a programming terminal.
IP67 female connector, type
M23.
IP67 male connector, type
M23.
IP67 female connector, type 7/8"
(24 VDC power supply).
IP67 female solder connector with M23-type ring,
6 contacts for Fipio bus connection and 24 VDC power supply. This type of independent connector is designed to be fitted to one end of TSX FP CA/CC/CP•00/CR cables.
IP67 male solder connector with M23-type ring, 6 contacts for Fipio bus connection and 24 VDC power supply. This type of independent connector is designed to be fitted to one end of TSX FP CA/CC/CP•00/CR cables.
7/8" type IP67 female screw connector, 5 contacts for Fipio bus connection and 24 VDC power supply. This type of connector is designed to be used for connecting the
24 VDC power supply of TSX ESF/EMF output or mixed modules and/or of the TSX EF ACC 99 branch box. The maximum authorized current in each contact on the connector is 8 A.
7/8" type IP67 male screw connector, 5 contacts for linked connection using the TSX EF CT 03 T connector, designed to supply the preactuators with 24 VDC.
IP67 male connector, type 7/8"
(24 VDC power supply).
T connector (for linking 24 VDC power supply).
IP67 female connector, type
M23.
SUB-D 9 type female connector.
IP67 compoundfilled Fipio cable for linking of modules.
7/8" type IP67 T connector, 5 contacts for linking the 24 V power supply of the preactuators. The maximum authorized current for each contact on this connector is 8 A.
M23, type IP67 female threaded solder connector,
6 contacts for extending Fipio TSX FP CA/CC/CP•00/CR cables.
SUB-D type connectors with 9 contacts for Fipio/Fipway connection to PLCs. Can be used for linked or branched connection (90° high or low output, 45° high or low output).
Main compound-filled cable of a predefined length, 150 Ω twisted shielded pair, and a 1.5 mm female/female connector.
2
power supply pair.
Equipped with an M23 male connector and an M23 double
35008155 12/2018
27
Fipio hardware implementation
Number Part Number
10 TSX FP CP •00
11
12
13
14
15
TSX FP CC •00
TSX FP CA •00
TSX EF ACC 7
TSX FP ACC 7
TSX FP CG 0•0
Type of connection Description
IP67 Fipio cable
(1 cable pair,
2 1.5 mm 2 power supply conductors, in 100 m or 500 m).
Main IP67, Fipio cable, 150 Ω twisted shielded pair, and a
1.5 mm 2 power supply pair (Ø 9.5 mm). Free wire ends to be fitted with IP 67 M23 type TSX EF CF 01/02 and
TSX EF CM 01 solder connectors.
Fipio branch cable
(2 pairs, in 100 m or
500 m).
Fipio link cable
(1 pair, in 100 m,
200 m or 500 m).
Branch cable, 150 Ω double shielded twisted pair (Ø 8 mm) for standard environments and building interiors. Free wire ends to be fitted with IP67 M23 type TSX CF 01/02 and
TSX CM 01 soldered connectors.
Main cable, one 150 Ω shielded twisted pair (Ø 8 mm) for standard environments and building interiors. Free wire ends to be fitted with IP 67 M23 type TSX EF CF 01/02 and
TSX EF CM 01 solder connectors.
IP67 M23 type line terminator.
Line terminator
PLC or programming terminal link cable
IP67 M23 type line terminator, to be positioned, depending on use, at one or both ends of the section (male type for direct connection).
IP20 line terminator (batch of 2), to be positioned, depending on use, at one or both ends of the section.
Branch connection cable for TSX FP 10/20 PCMCIA interface card for Premium, FT 2000 terminal and PCcompatible PLCs. This cable allows a PLC or a programming terminal to be connected to a
TSX EF ACC 99 branch box.
Other Accessories
The following table shows the other accessories available.
Part Number
XZ-LG 101
XZ-LG 102
170 XTS 050 00
Type of connection
Identification labels.
IP67 sealing plugs.
IP67 sealing plug.
Description
Strip of 10 additional identification labels (a strip is already supplied with each module).
Batch of 10 M12 sealing plugs for unused I/O connectors. Each module is supplied with two plugs.
Sealing plug for M23 connector.
28
35008155 12/2018
Fipio Architecture with OZD FIP G3
Description
Example of a Fipio architecture:
Fipio hardware implementation
Most Schneider products which operate on the Fipio bus can be connected to the OZD FIP G3 transceiver:
As Fipio manager devices:
Premium: processors with an integrated FIPIO link: TSX P57•54 and TSX PCXI57 354 programmed with Control Expert (version V1.1 or later).
As Fipio bus agent devices:
TBX equipped with an LEP 030 communication module
Magelis XBT equipped with a TSX FPP 10 card
PC equipped with a TSX FPC 10 or PCMCIA FPP20 ISA card
Momentum
TSX Micro TSX 372• and TSX Premium TSX/PMX/PCX 57 equipped with a TSX FPP 010
card
Third-party devices which conform to the standard Fipio profiles defined in the FipConnect connection program.
NOTE: TSX FP ACC6 and TSX FP ACC8M repeaters are not compatible with architectures using
OZD FIP G3 transceivers.
NOTE: Fipio configurations in WorldFip mode are excluded from these architectures.
NOTE: The TSX DM OZD 01 manual gives all the characteristics of HIRSCHMANN OZD FIP G3 transceivers.
35008155 12/2018
29
Fipio hardware implementation
Master Fipio communication built into processors Section 2.2
Master Fipio communication built into processors
Built-in Fipio Link on Premium/Atrium Processors
General
Some Premium (see Premium and Atrium using EcoStruxure™ Control Expert, Processors, racks and power supply modules, Implementation Manual) and Atrium (see Premium and Atrium using
EcoStruxure™ Control Expert, Processors, racks and power supply modules, Implementation
Manual) processors have a built-in master Fipio link which makes it possible to connect the PLC station to a Fipio bus.
Illustration:
30
35008155 12/2018
Fipio hardware implementation
Connecting to Fipio Bus
The processor has a SUB-D 9-pin connector which is used to connect it to the Fipio bus using a
TSX FP ACC12 connector.
Illustration:
NOTE: The master Fipio link built into processors should not be taken into account when counting the station channels.
35008155 12/2018
31
Fipio hardware implementation
TSX FPP 10 PCMCIA card Section 2.3
TSX FPP 10 PCMCIA card
Subject of this Section
This Section deals with the installation of a TSX FPP 10 PCMCIA card.
What Is in This Section?
This section contains the following topics:
Topic
Introduction
Description
Connection of the TSX FPP 10 card
Precautions to be taken when connecting PCMCIA card
Installation
Mounting Cards and Cables
Displaying operating state of PCMCIA cards
Visual Diagnostics for TSX FPP 10 PCMCIA Card
Consumption of PCMCIA card
Page
32
35008155 12/2018
Fipio hardware implementation
Introduction
General
Premium/Atrium PLC stations connect to communication networks, buses and links via PCMCIA communication cards.
The card to be connected is a metal unit whose dimensions comply with PCMCIA extended type
III format.
The PCMCIA card is installed in the host slot of the processor of Premium PLCs.
The PCMCIA card can also be used in devices which have a type III host slot, such as XBT terminals or third-party devices, such as PC compatible devices, for example.
Illustration:
NOTE: It is prohibited to connect PCMCIA cards when the power is switched on.
Definition
An agent PLC is a PLC with a connected PCMCIA card.
35008155 12/2018
33
Fipio hardware implementation
TSX FPP 10 card
The PCMCIA card used to connect a Premium/Atrium PLC station to a Fipio bus is the TSX FPP
10.
The PCMCIA card is installed, operated and maintained using Control Expert programming and operation software for all PLCs in the Premium/Atrium family.
34
35008155 12/2018
Fipio hardware implementation
Description
General
PCMCIA type III (extended) communication cards are built into a metal unit with the following dimensions:
Length: 85.5 mm
Width: 51 mm
Height: 10 mm
The front of the card is designed to display the operating status of communications as well as the physical connection to the network.
Mechanical configuration
The mechanical configuration of the card must be adapted by mounting a removable cover, depending on the type of installation desired:
Type of installation
Installation on a
Premium type processor.
Installation on an Atrium type processor.
Installation on a PC compatible device.
Configuration
Removable cover with wings. Screws are provided to fix it to the host module (marked 3 on illustration)
Removable cover with wings. Screws are provided to fix it to the
Atrium processor
(marked 2 on illustration).
Removable cover
(marked 1 on illustration).
Illustration
NOTE: The covers with wings, mounted on PCMCIA cards, prevent any accidental removal when switched on and guarantee that the card remains in good working order.
The two covers (1) and (3) are provided with the PCMCIA card. The cover (2) is provided with the
Atrium processor.
Connection to the network is achieved by connecting the link cable to the front of the card. A guidance system is used to prevent anything being mounted incorrectly.
The product reference label informs the user of the type of physical layer supported by the card.
35008155 12/2018
35
Fipio hardware implementation
Connection of the TSX FPP 10 card
General
The TSX FPP 10 PCMCIA card is connected to the Fipway bus using a connector such as a TSX
FP ACC 3 or TSX FP ACC 4.
To connect the PCMCIA card to the ACC3/ACC4 connector the user may use:
Either a 1 m cable, product reference TSX FP CG 010.
Or a 3 m cable, product reference TSX FP CG 030.
Items required for connecting a Premium/Atrium PLC to the remote inputs/outputs Fipio bus:
36
35008155 12/2018
Fipio hardware implementation
Precautions to be taken when connecting PCMCIA card
General
NOTICE
PCMCIA CARD DESTRUCTION
Cables (TSX FP CG 010/030) are to be connected and disconnected from the PCMCIA card only when the power is switched off
Failure to follow these instructions can result in equipment damage.
CAUTION
PCMCIA CARD DESTRUCTION
Power off the module before inserting or removing the PCMCIA card.
Failure to follow these instructions can result in injury or equipment damage.
When removing or inserting the card, the unit is not guaranteed to be operational.
The PCMCIA card must be equipped with a PLC version cover and be screwed into the reception
module before the power is switched on (see Mechanical configuration,
page 35
The ferrule, placed in direct contact with the PCMCIA card device, is used to drain electrical interference carried by the link cable braids.
35008155 12/2018
37
Fipio hardware implementation
Installation
Installation
The TSX FPP 10 card can only be installed in the host slot of processors. It cannot be installed in the module TSX SCM 21601
Application-specific channel and network connection
The installation of the card in the processor does not count as an application-specific channel or as a network connection.
38
35008155 12/2018
Fipio hardware implementation
Mounting Cards and Cables
PCMCIA Card Details
Illustration:
PCMCIA cards are made up of the following elements:
2
3
Number Designation
1 Equipped card
4
Body made of zamac
PCMCIA connector
Upper cover
5
6
Removable cover
Link cable with ferrule
Comments
Receives electronic components.
-
Connector with 20 connection points.
Houses the product reference label which shows the type of PCMCIA card
Ensures the card is displayed in its slot. The names of the two LEDs are printed on the front of the removable cover. This cover also allows the
PCMCIA card to be fastened to the processor.
The ferrule placed on the end of the cable nearest to the PCMCIA card prevents the cable being pinched by the removable cover. This ferule also eliminates the risk of causing a bending radius which can damage the quality of the link.
35008155 12/2018
39
Fipio hardware implementation
Assembly for TSX P57 1•4 to TSX P57 5•4 Processors
To assemble the transmission card for the processor or the TSX SCY 21601, first remove the cover which is screwed on the device and then follow the instructions below:
Step
1
2
3
4
5
Action
Connect the cable
Place the appropriate cover on the device, taking care to insert the ferrule in the slot provided in order to fix the cable to the card.
Screw on the cover.
Insert the card in the slot provided in the host device.
Screw in the card to stop it being moved when switched on, and to ensure it functions effectively.
Illustration
Assembly for TSX P57 5•4 Processors
To assemble the card in TSX P57 5•4 type processors, follow the instructions below:
Step
1
2
3
Action
Connect the cable.
Place the appropriate cover on the device, taking care to insert the ferrule in the slot provided in order to fix the cable to the card.
Screw on the cover.
Illustration
40
35008155 12/2018
Step
4
Action
Remove the plastic cover from the caddy.
Illustration
5 Guide the card into the caddy from an oblique angle using the 2 locating devices.
6 Slide the card into the caddy until it stops. The card is now firmly attached to the caddy.
7
8
Insert the assembly
(caddy and card) in the slot provided in the host device.
Screw in the card to stop it being moved when switched on, and to ensure it functions effectively.
35008155 12/2018
Fipio hardware implementation
41
Fipio hardware implementation
Displaying operating state of PCMCIA cards
General
Two diagnostics LEDs are located on the front of the card. They inform the user on the status of exchanges between the device supporting the PCMCIA card and related devices.
Illustration
Number Description
1 "ERR" Error LED (normally off) displays errors.
It is red
2 The "COM" communication LED displays line activity.
This LED is yellow
Diagram
42
35008155 12/2018
Fipio hardware implementation
Visual Diagnostics for TSX FPP 10 PCMCIA Card
General
Depending on their state, the LEDs of the PCMCIA card indicate the operating mode for communication, as well as the card diagnostics.
TSX FPP 10 card
State of LEDs:
ERR COM Meaning
Device switched off No dialog
Corrective actions
Check supply, card inoperational
Normal operation -
(1) Serious fault
Functional fault
Functional fault
Change the card
Check the configuration and the connection to the communication bus
Check the configuration
Key:
Off
On
Flashing
(1) = Indifferent state
35008155 12/2018
43
Fipio hardware implementation
Consumption of PCMCIA card
TSX FPP 10
Table of consumption:
Voltage
5 volts
Typical Current
280 mA
Maximum Current
330 mA
Power dissipation
1.65 W max.
44
35008155 12/2018
Fipio hardware implementation
TSX FPC 10 module Section 2.4
TSX FPC 10 module
Description
General
The TSX FPC 10 module can be used for connecting the following devices to the Fipio bus:
FTX 517 workstations
CCX 77/87 supervision terminals any machine fitted with an ISA bus
The module is the same shape as a half-format PC extension card.
It is connected to the Fipio bus via a TSX FP CE030 cable and a TSX FP ACC3, TSX FP ACC4 or TBX FP ACC10 branching device
35008155 12/2018
45
Fipio hardware implementation
TSX FPP 20 PCMCIA card Section 2.5
TSX FPP 20 PCMCIA card
Description
General
The TSX FPP 20 card is used to connect a programming terminal to a PLC station via the Fipio bus.
The card can also be used to connect a Premium/Atrium PLC station to a Fipway network.
The programming terminal must have a type III (extended) PCMCIA slot.
To install the card, see the manual entitled Fipway Communication.
46
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Fipio Software Implementation
35008155 12/2018
Software Implementation for Fipio Bus Part III
Software Implementation for Fipio Bus
Subject of this Part
This part presents the principles for configuring and using Fipio bus communication using Control
Expert software.
What Is in This Part?
This part contains the following chapters:
10
11
8
9
6
7
Chapter
3
4
5
Chapter Name
Presentation and Specifications of the Fipio Bus
Installation methodology
Configuring Fipio communication
Programming Fipio communication
Debugging a Fipio communication
Fipio communication diagnostics
Language objects associated with Fipio communication
Fipio communication standard profiles
Fipio Agent
Page
35008155 12/2018
47
Fipio Software Implementation
48
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
General
35008155 12/2018
Presentation and Specifications of the Fipio Bus Chapter 3
Presentation and Specifications of the Fipio Bus
Subject of this Chapter
This chapter presents communication by Fipio bus and its specifications.
What Is in This Chapter?
This chapter contains the following sections:
Section
3.1
3.2
Introduction to Fipio communication
Characteristics
Topic Page
35008155 12/2018
49
General
Introduction to Fipio communication Section 3.1
Introduction to Fipio communication
Addressing of Remote Module Language Objects on a FIPIO Bus
At a Glance
The addressing of the main bit and word objects of remote modules on the Fipio bus is performed on a geographical basis. That means that it depends on:
The connection point,
The type of module (base or extended),
The channel number.
Illustration
Addressing is defined in the following way:
Syntax
The table below describes the different elements that make up addressing.
Family
Symbol
Object type I
Q
Element Values
% -
-
-
M
K -
-
-
Meaning
Image of the physical input of the module.
Image of the physical output of the module.
This information is exchanged automatically for each cycle of the task to which they are attached.
Internal variable
This read or write information is exchanged at the request of the project.
Internal constant
This configuration information is available as read only.
50
35008155 12/2018
General
Family
Format (size)
Module/channel address and connection point
Rack No.
Module No.
Channel No.
r m c
Element Values
X b e
W
D
F
-
16 Bit
32 Bit
32 Bit
Meaning
Boolean
For Boolean objects the X can be omitted.
Single length.
Double length.
Floating point. The floating point format used is the IEEE Std 754-1985 standard (equivalent to IEC 559).
2 Bus number.
1 to 127 Connection point number.
Channel data No. d
0
0 or 1
0 to 999 or MOD
0 to 999 or ERR
Virtual rack number:
0: base module, 1: extension module.
MOD: channel reserved for managing the module and parameters common to all the channels.
ERR: Used to read a module or channel fault.
35008155 12/2018
51
General
Examples
The table below shows some examples of addressing objects.
Object
%MW\2.1\0.0.5.2
%I\2.1\0.0.7
%Q\2.1\0.1.2
Meaning
Status word at rank 2 of the image bit of input 5 of the remote input base module situated at connection point 1 on the Fipio bus.
Image bit of input 7 of remote input base module situated at connection point 1 on the Fipio bus.
Image bit of output 2 of the remote output extension module situated at connection point 1 on the Fipio bus.
%I\2.2\0.0.MOD.ERR Fault information for Momentum module situated at connection point 2 on the Fipio bus.
%I\2.3\0.0.0.ERR
Fault information for channel 0 of Magelis module situated at connection point 3 on the Fipio bus.
52
35008155 12/2018
General
Characteristics Section 3.2
Characteristics
Aim of this Section
This Section introduces the characteristics and constraints of using Fipio communication.
What Is in This Section?
This section contains the following topics:
Topic
Hardware Compatibilities relating to the Bus Manager
Software Compatibilities relating to the Bus Manager
Software Compatibility: Network Transparency
Software Compatibility: Outside Communication
TBX Device Compatibilities
Momentum Device Compatibilities
Programming Terminal Compatibilities
Miscellaneous Device Compatibilities
Fipio Bus Operating Mode
Saturation of Fipio Messaging Service
Network Cycle Time: Mono Task Application
Network Cycle Time: Multitasking Application
Example of calculating the network cycle times of a multitasking application
Page
35008155 12/2018
53
General
Hardware Compatibilities relating to the Bus Manager
General
The binary rate of the bus is 1 Mbits/s, with a length that can reach 15 Km with optical or electric repeaters.
The Fipio bus is linked to the Hirschmann optical transmitters, which is used to create medium hotstandby architectures.
Availability
This type of communication is available using built-in links to the Premium PLCs.
Capacity
Processors with a built-in Fipio link capable of managing 128 connection points (limited to 64 for
TSX P57 154) on the bus (maximum addresses 0 to 127).
The bus manager is connected to address 0, with address 63 reserved for the programming and diagnostics terminal.
These processors feature a RAM that enables them to save the configuration of the devices linked to the bus.
54
35008155 12/2018
General
Software Compatibilities relating to the Bus Manager
Explicit Exchanges Limits
Processors with a built-in Fipio link can be used to simultaneously activate 24 explicit exchange functions.
An exchange request sent to a Fipio device can take several MAST task cycles. It is therefore essential to manage the words of the exchange management parameters for every explicit variable exchange, including READ_STS(IODDT_VAR1) and READ_STS(IODDT_VAR2) . This requires
IODDT-type IODDT_VAR1 and IODDT_VAR2.
If for example 24 functions are being processed simultaneously, or if 25 functions are triggered in a same task cycle, then all new functions (or the 25th) will not be served and will end in error.
For a READ_STS exchange, given that the 25th exchange is not possible, the report raises a communication fault in word %MW\2.e\0.m.c.2
For exchanges WRITE_CMD , READ_PARAM , WRITE_PARAM , RESTORE_PARAM , the report raises a communication fault in word %MW\2.e\0.m.c.1. A probable cause is the lack of system resources to provide the service.
Reminders
System word %SW155 contains the number of explicit exchanges in progress. Bit %SW116 .2 switches to 1 if the maximum number of simultaneous explicit exchanges is reached or exceeded.
35008155 12/2018
55
General
Software Compatibility: Network Transparency
At a Glance
Message exchanges from a remote station to the Fipio bus, or vice-versa, are possible as long as certain conditions are met.
Transparency Restrictions
Inter-station communication to Fipio is only available if the bus arbiter is a Premium-type PLC.
Exchanges from a third-party device to a PLC connected as a Fipio agent are only possible if the
PLC is Premium. There is no communication to a Micro-type PLC.
Connection point 63 is a privileged connection point, which does not need to be declared in Control
Expert configuration.
The programming terminal can only be physically connected to connection point 63.
It is impossible to download a project from the programming terminal connected to address 63 in the bus arbiter from the Fipio bus. In fact, downloading causes the PLC to switch to STOP, which makes Fipio communication no longer managed by the bus arbiter.
NOTE: You must not configure managing Fipio communication (built-in link) and Fipio agent communication (PCMCIA TSX FPP 10 card) on the same PLC
56
35008155 12/2018
General
Illustration
The following illustration shows the different possible exchanges between a Fipio bus, a network or another bus.
In the above example, the micro PLC cannot communicate with the third-party device. Here, you
see page 59
PLC. The programming terminal can access the master and
Fipio Agents as well as third-party devices via the master.
35008155 12/2018
57
General
Illustration
The following illustration shows the restrictions on exchanges between a terminal connected to the terminal port of a Premium agent.
58
In the above example, the programming terminal cannot communicate with the managing PLC and the other PLC agents present on the Fipio bus.
35008155 12/2018
General
Software Compatibility: Outside Communication
At a Glance
To communicate from one station connected to the Fipio bus to an outside device, the transmitter station must send to the master PLC and not the destination device (requests are not sent directly).
NOTE: The master PLC project transfers requests to the destination device.
Example
The following example shows an exchange from the Fipio bus to the Uni-Telway bus. Exchanges in the other direction use an identical procedure.
Step 1
The transmitter station, connected to Fipio connection point 6, sends the request to the master
PLC. The destination address is the address of the master PLC.
WRITE_VAR (ADDR('\2.0\SYS'), '%MW',0,10, %MW10:10, %MW100:4)
The report is provided by the master PLC.
35008155 12/2018
59
General
Step 2
When the master PLC project receives the request from the transmitter station, it sends it to the destination device according to the Uni-Telway protocol.
WRITE_VAR (ADDR('0.0.0.1'), '%MW',100,10, %MW10:10, %MW40:4)
The report is addressed to the master PLC.
60
35008155 12/2018
General
TBX Device Compatibilities
At a Glance
The following compatibility information concerns:
The address settings supported by the different connectable devices,
The memory size these devices occupy in the configuration RAM.
Rules of Use
The device connected to a connection point, if it is modular, must have a uniform application:
Discrete base and extension, or analog base and extension (no Discrete/analog mix).
The device (base and extension) is controlled by a single FAST or MAST Control Expert task (no group assigning of channel groups of a single TBX to different tasks).
Address Settings
Fipio address settings depend on the type of device:
Type of Device
Compact TSXs
FIPIO addresses
1...31
Dust and damp proof TBXs 1...62, 64...127
Modular TBXs 1...62, 64...127
AS-i gateway 1...62, 64...127
Comments
TBX C•
TBX E•
TBX LEP •••
TBX SAP 10
35008155 12/2018
61
General
Memory Space
Each processor
see page 97
SX P57 454/554 processors.
) has a memory space available for Fipio devices. This memory
space equals 95744 bytes for TSX P57 154/254/354 processors and 214528 bytes for
Each Fipio device connected to the bus uses part of this memory space. The memory used by the devices connected to the Fipio bus must be less than the processor’s available memory. When calculating the memory used, you must add an offset of 1424 bytes.
The following table lists the memory values used in bytes for each TBX module.
Module
AES 400, ASS 200
AMS 620
CEP 1622, CSP 1622, CSP 1625
DES 16••, DMS 16••, DSS 16••
DSS 1235
DMS 1025
EEP/ESP 08C22/1622
TBX SAP 10
Base
1332
1584
1152
1152
1152
1152
1152
1808
-
Extended
-
272
-
272
528
-
-
-
144
144
144
62
62
62
52
Maximum number of connection points
TSX P57 154 TSX P57
254/354
TSX P57
454/554
62
2 or 4 channels
70 126
59
59
2 channels
50
59
59
50
126
126
100
4 channels
50
8 channels
44
10 or 12 channels
31
62
62
50
44
31
81
64
72
72
64
52
84
63
31
126
64
85
102
126
117
Example:
For a TSX P57 154 processor:
Two TBX AES 200 (base and extension) and a TBX AMS 620 (base) are connected to the Fipio bus.
The memory used equals 4612, i.e.: 1332+272+1584+1424 (offset).
In this case, the memory used by the devices (4612) is less than the processor’s memory (95744).
62
35008155 12/2018
General
Momentum Device Compatibilities
At a Glance
The following compatibility information concerns:
The address settings supported by the different connectable devices,
The memory size these devices occupy in the configuration RAM.
Rules of Use
The implementation of Momentum devices on Fipio is only possible using the communication module: 170 FNT 110 01.
Address Range
The address ranges for Momentum devices vary depending on the type of processor used. The address range is:
[1..62] for TSX P57 154 processors,
[1..62] and [64..99] for the other processors (TSX P57 254/354/454/554).
Memory Space
Each processor
see page 97
SX P57 454/554 processors.
) has a memory space available for Fipio devices. This memory
space equals 95744 bytes for TSX P57 154/254/354 processors and 214528 bytes for
Each Fipio device connected to the bus uses part of this memory space. The memory used by the devices connected to the Fipio bus must be less than the processor’s available memory. When calculating the memory used, you must add an offset of 1424 bytes.
The following table lists the memory values used in bytes for each Momentum module.
Module
ADI, ADM, ADO
ARM 370 30
AAI 520 40 00
AMM 090 00, AAI 030 00,
AAO 120 00, AAO 921 00
AAI 140 00
AEC 920 00
OTHER_FED
OTHER_FED_P
Base
832
832
1808
1808
2304
1808
1280
2304
40
52
62
40
Maximum number of connections
TSX P57 154 TSX P57
254/354
TSX P57
454/554
62
62
98
98
98
98
52
52
52
52
98
98
40
52
62
40
92
98
99
92
35008155 12/2018
63
General
Module
OTHER_FRD
OTHER_FRD_P
OTHER_FSD
OTHER_FSD_P
Base
832
1744
896
1808
Maximum number of connections
62
54
98
54
98
99
62
52
98
52
98
98
Example:
Or a TSX P57 154 processor.
Two momentums of type ADI and one momentum of type standard profile OTHER_FSD are connected to the Fipio bus.
The memory used equals 3984, i.e.: 832+832+896+1424 (offset).
In this case, the memory used by the devices (3984) is less than the processor’s memory (95744).
64
35008155 12/2018
General
Programming Terminal Compatibilities
At a Glance
The following compatibility information concerns the address settings supported by the different connectable devices.
Rules of Use
A programming terminal equipped with a TSX FPC 10 card or PCMCIA card TSX FPP 20 must be connected to Fipio address 63.
Control Expert operates in online mode with the Fipio manager PLC.
If the manager PLC has a project in which one or more agent devices are configured, Control
Expert communicates with the Premium agent Fipio PLCs.
Exchanges from a third-party device to a PLC connected as a Fipio agent are only possible if the
PLC is Premium. There is no communication to a Micro-type PLC.
It is impossible to download a Control Expert project to the manager from a programming terminal.
In fact, downloading causes the PLC to switch to STOP, which makes Fipio communication no longer managed by the bus arbiter. However, it is possible to download a Control Expert project to a Fipio agent PLC.
35008155 12/2018
65
General
Miscellaneous Device Compatibilities
At a Glance
The following compatibility information concerns:
The address settings supported by the different connectable devices,
The memory size these devices occupy in the configuration RAM.
Address Range
The table below shows the Fipio address range a device can use depending on the type of processor used:
Type of device
Analog TBX (AES, AMS,
ASS)
Type of processor
TSX P57 154 TSX P57 254/354 TSX P57 454/554
Advantys STB 1...62
Altivar (ATV-38/58/58F/68) 1...62
1...62
1...62, 64...127
1...62
1...62, 64...127
1...62, 64...127
1...62
1...62, 64...127
Gateway (TBX SAP 10)
Inductel
Lexium
Magelis
1...62
1...62
1...62
1...62
1...62, 64...127
1...62
1...62
1...62
1...62, 64...127
1...62
1...62
1...62
1...62
1...62
1...62, 64...99
1...62, 64...127
1...62, 64...99
1...62, 64...127
Momentum
Standard profiles (FED,
FDR, FSD)
Discrete TBX (DES, DMS,
DSS)
Discrete TBX compact
(CEP and CSP)
TSX (37 and 57)
Waterproof IP65 (EEP,
ESP)
Waterproof IP67 (EEF,
ESF, EMF)
1...62
1...31
1...62
1...62
1...62
1...62, 64...127
1...31
1...62
1...62, 64...127
1...62, 64...99
1...62, 64...127
1...31
1...62
1...62, 64...127
1...62, 64...99
66
35008155 12/2018
General
Memory Space
Each processor
see page 97
TSX P57 454/554 processors.
) has a memory space available for Fipio devices. This memory
space equals 95744 bytes for TSX P57 154/254/354 processors and 214528 bytes for
Each Fipio device connected to the bus uses part of this memory space. The memory used by the devices connected to the Fipio bus must be less than the processor’s available memory. When calculating the memory used, you must add an offset of 1424 bytes.
The following table lists the memory values used in bytes for each device.
Module
ATV38 with VW58311 card
ATV58/58F with VW-A58301 card
ATV58/58F PKW with VW58311 card
ATV 68
Magelis
EEF 08D2, EEF 16D2
ESF 08T22 EMF 16DT2
FED C32
FED C32P
FED M32
FED M32P
FRD C2
FSD C8
FSD C8P
FSD M8
FSD M8P
Premium/Micro Agent
Lexium
Inductel
Advantys STB 2 words
Advantys STB 8 words
Advantys STB 32 words
1280
2304
1424
2448
832
896
1808
1040
Base
1280
1808
1280
1280
1424
832
1808
1952
1424
1424
1808
832
896
1280
35008155 12/2018
67
General
Example:
Or a TSX P57 154 processor.
Two Magelis and a standard profile FSD C8P are connected to the Fipio bus.
The memory used equals 6080, i.e.: 1424+1424+1808+1424 (offset).
In this case, the memory used by the devices (6080) is less than the processor’s memory (95744).
68
35008155 12/2018
General
Fipio Bus Operating Mode
At a Glance
Fipio bus operating mode is linked to the processor's operating mode and to the physical state of the bus.
If the number of physical errors detected by the processors endangers the nominal operation of the devices connected to the bus, then the processor stops all bus activity. In this case, certain connected devices apply fallback values to the inputs.
Operating Mode
The operating mode is as follows:
Situation Description
1 Cold start of the processor with a Fipio project: the bus is automatically started, the inputs/outputs are checked and controlled.
2 Downloading a Fipio project: the bus is automatically started, the inputs/outputs are checked and controlled.
3 When a communication issue is detected by the processor (equipment powered off, Fipio cable disconnected, ...) the status bit corresponding to the equipement in the system words %SW128 to %SW143 (see EcoStruxure™
Control Expert, System Bits and Words, Reference Manual) is reset.The equipment status bits should be tested before their input/output values are used.
4
5
If the processor detects serious physical errors, the Fipio bus is automatically stopped. The connected devices apply the fallback values and the processor no longer checks inputs/outputs. An example of a serious physical error is disconnection of the line end jack, disconnection of the Fipio terminal block from the processor, etc.
Following an automatic stopping (serious errors detected by the processor):
The %SW144.2
bit is set to 1: the processor periodically executes an
attempt to restart by trying to check and control the inputs/outputs of the connected devices. This is automatic mode.
The %SW144.2
bit is set to 0: to restart the bus, a user action must be carried out by program or in the programming terminal. Set the %SW144.0
and %SW144.1
bits to 1. This is manual mode.
6
7
Warm restart: The bus is automatically restarted if it was not intentionally stopped though an action on the %SW144 system word 0 and 1 bits. The bus is set to the previous power outage state.
If %S0 = 1 the system words are initialized, and if the bus was stopped, it is restarted.
35008155 12/2018
69
General
Additional Information Concerning Manual Mode
If %SW144.0
is set to 0 (in the programming terminal or by program), then the producer/consumer
(PC) function stops. No further variables or messages are exchanged on the bus.
If %SW144.1
is set to 0 (in the programming terminal or by program), then the bus arbiter (BA) function stops. No further variable or message scanning is carried out on the bus.
To completely and intentionally stop Fipio bus activity, the %SW144 system word 0 and 1 bits must be set to 0 simultaneously in the programming terminal or by the program.
Additional Information Concerning Automatic Mode
If the Fipio bus is stopped without intentional action on the %SW144 system word, this means that the processor has detected physical errors that inhibit nominal operation of the bus and of the connected devices.
In this case and only in this case, if the %SW144.2
bit is set to 1 (automatic start), then the processor will periodically and automatically attempt to restart exchanges on the bus.
If the %SW144.2
bit is set to 0 following a stop of the bus due to physical errors, then the %SW144.0
and %SW144.1
bits must be reset to 1 by the program or in the programming terminal in order to restart the Fipio bus. In this case, the bus will restart if and only if the physical error that caused the stop has disappeared.
Example
If the %SW144.2
bit is set to 1, when the Fipio terminal block is disconnected/reconnected from/to the processor, the bus will be restarted automatically.
The devices will be checked again and will be able to apply program values.
If the %SW144.2
bit is set to 0, when the Fipio bus is disconnected/reconnected from/to the processor, the devices connected to the bus will not be checked and will be unable to apply program values.
The devices will be checked again if the user sets the %SW144.0
and %SW144.1
bits to 1.
70
35008155 12/2018
General
Saturation of Fipio Messaging Service
Messaging
The Fipio messaging service is used for communication between:
the bus arbiter and a Premium or Micro PLC agent (equipped with a TSX FPP 10 card) or between agents,
Control Expert and Fipio agents (Premium or Micro PLC), the bus arbiter with devices such as the HMI terminal (XBT), variable speed controllers (Altivar) or Lexium drives.
If the messaging service is saturated, the system returns an increasing number of time-out errors.
Start by increasing the bandwidth allocated to the messaging service. If the problem persists, decrease
see page 101
the message rate.
This problem mainly occurs on TSX P57 554 processors which have a very short cycle time.
35008155 12/2018
71
General
Network Cycle Time: Mono Task Application
At a Glance
The network cycle time for a mono task application is calculated for the following configuration:
the bus length is 1 Km, the values corresponding to silence time, slot time and bandwidth are the default values
(automatic mode).
Calculation of Network Cycle Time
For an application where all devices are configured in the same task, the value of the network cycle time of the task, in milliseconds, is obtained using the following formula (provided for information purposes):
Value of Coefficient K
Coefficient K will be defined as follows:
1.5
0.4
0.6
1.5
0.6
0.6
1.5
0.6
Coefficient K
0.5
0.9
0.4
Family
TBX
TBX
Momentum
Momentum
ATV-58
TSX 37/57
AS-i gateway
Magelis
STD_P
STD_P
STD_P
Device
Discrete
Analog
Discrete
Analog
All
All
TSX SAP 10
All
FRD
FSP
FED
72
35008155 12/2018
Example
The example is configured as follows:
All the elements are configured in the application's MAST task.
The configuration consists of:
10 discrete TBXs,
11 analog TBXs,
12 discrete Momentums.
The MAST task cycle time is calculated as follows:
TCR_MAST = 1.45 + ((0.5 x 10) + (0.9 x 11) + (0.4 x 12)) = 21.15 ms
The resulting network cycle time value is 21 ms.
General
35008155 12/2018
73
General
Network Cycle Time: Multitasking Application
At a Glance
For a multitasking application with two periodic tasks, and if the devices are configured in each of the tasks, the value of the network cycle times depends on the configuration of the different tasks.
The cycle time values calculated with the following algorithm are the maximum values. The actual values are less than or equal to these values.
Convention
The following table shows all the parameters involved in the calculation of the network cycle time.
Parameter
P max
P min
T max
T min
R
NE max
NE min
NE_Equip
TCR_T max
TCR_T min
Definition
Value of the largest task period (MAST or FAST)
Value of the smallest task period (MAST or FAST)
Task with period P max
Task with period P min
Ratio between the periods (This ratio must be a whole number; it will be rounded off to the nearest whole number if necessary).
Number of devices from the same family configured in T max
Number of devices from the same family configured in T min
Equivalent number of devices from the same family
Network cycle time for the task T max
Network cycle time for the task T min
Calculation Algorithm
To calculate the network cycle time, the algorithm is as follows:
Phase
1
Description
Calculation of R
2 Calculation of NE_Equip (for each device family)
3 Calculation of TCR_T max
74
35008155 12/2018
Phase
4
Description
Calculation of TCR_T min
Value of Coefficient K
Coefficient K will be defined as follows:
1.5
0.4
0.6
1.5
0.6
0.6
1.5
0.6
1.5
0.6
0.4
0.6
1.5
0.5
0.4
0.4
0.6
Coefficient K
0.5
0.5
0.9
Family
TBX
TBX
TBX
TBX IP65
TBX IP67
Momentum
Momentum
Momentum expert
Altivar
TSX 37/57
AS-i gateway
Magelis
STD_P
STD_P
STD_P
Lexium
Inductel
Advantys
Advantys
Advantys
All
All
2W
8W
32W
Device
Discrete
Discrete Compact
Analog
All
All
Discrete
Analog
170 AEC 920
All
All
TSX SAP 10
All
FRD
FSP
FED
35008155 12/2018
General
75
General
Interpretation of the Results
To refresh the inputs/outputs on the bus, the following constraints are imposed:
For the periodic tasks in controlled mode, the network cycle time of the task must be less than the task period.
For the periodic tasks in free mode, the network cycle time of the task must be less than the task watchdog.
76
35008155 12/2018
General
Example of calculating the network cycle times of a multitasking application
Introduction
The configuration of the example is as follows:
Task periods:
MAST: 60 ms
FAST: 15 ms
The configuration comprises:
6 discrete TBXs configured in the MAST task and 4 discrete TBXs configured in the FAST
task,
6 analog TBXs configured in the MAST task and 4 analog TBXs configured in the FAST task,
6 discrete Momentums configured in the MAST task and 4 discrete Momentums configured in the FAST task,
6 analog Momentums configured in the MAST task and 4 analog Momentums configured in the FAST task,
Convention
Depending on the configuration, the application of conventions involves:
P
T max max
= 60 and P min
= T
MAST
TCR_T max
and T
= 15 min
= T
= TCR_T
MAST
FAST
and TCR_T min
= TCR_T
FAST
Algorithm
The following table shows the algorithm:
Stage
1
2
3
4
Description
Calculation of R
R = 60 / 15 = 4
Calculation of the equivalent number of devices
NE_TBX_TOR = (R * 4 + 6) = 22
NE_TBX_ANA = (R * 4 + 6) = 22
NE_MOMENTUM_TOR = (R * 4 + 6) = 22
NE_MOMENTUM_ANA = (R * 4 + 6) = 22
Calculation of the network cycle times TCR_T
MAST
TCR_T
MAST
TCR_T
MAST
= 1.45 + ((0.5 * 22) + (0.9 * 22) + (0.4 * 22) + (0.6 * 22))
= 54.25 ms
Calculation of the network cycle times TCR_T
FAST
TCR_T
FAST
TCR_T
FAST
= 54.25 / 4
= 13.56 ms
35008155 12/2018
77
General
Conclusions
The network cycle times of each equal:
TCR_T
MAST
TCR_T
FAST
= 55 ms,
= 14 ms.
The time period for MAST and FAST tasks are sufficient to refresh the inputs/outputs.
78
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Methodology
35008155 12/2018
Installation methodology Chapter 4
Installation methodology
Overview
Introduction
The software installation for the modules is carried out from the various Control Expert editors:
In offline mode,
In online mode.
The following order of installation phases is recommended but it is possible to change the order of certain phases (for example, starting with the configuration phase).
Installation Phases with Processor
The following table shows the various phases of installation with the processor.
Phase
Declaration of variables
Programming
Configuration
Association
Description
Declaration of IODDT-type variables for the applicationspecific modules and variables of the project.
Project programming.
Declaration of modules.
Module channel configuration.
Entry of configuration parameters.
Association of IODDTs with the channels configured
(variable editor).
Generation
Transfer
Adjustment /
Debugging
Project generation (analysis and editing of links).
Transfer project to PLC.
Project debugging from debug screens, animation tables.
Modifying the program and adjustment parameters.
Documentation Building documentation file and printing miscellaneous information relating to the project.
Operation/Diagnostic Displaying miscellaneous information necessary for supervisory control of the project.
Diagnostic of project and modules.
Mode
Offline (1)
Offline (1)
Offline
Offline (1)
Offline
Online
Online
Online (1)
Online
Key:
(1)
35008155 12/2018
These various phases can also be performed in the other mode.
79
Methodology
80
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Fipio Configuration
35008155 12/2018
Configuring Fipio communication Chapter 5
Configuring Fipio communication
Subject of this Chapter
This chapter describes the Configuration process during set-up of Fipio communication.
What Is in This Chapter?
This chapter contains the following sections:
Section
5.1
5.2
5.3
5.4
5.5
General information on configuration
Topic
Fipio bus configuration
Configuration of devices on the Fipio bus
Management of Inputs/Outputs by Control Expert Tasks:
Confirmation of the Fipio bus configuration
Page
35008155 12/2018
81
Fipio Configuration
General information on configuration Section 5.1
General information on configuration
Configuration Mode
At a Glance
The creation of a project implementing a Fipio bus requires the configuration of several elements from the Control Expert software.
Methodology
The following methodology describes the different configuration phases of the Fipio bus and devices:
82
35008155 12/2018
Fipio bus configuration Section 5.2
Fipio bus configuration
Aim of this Section
This section introduces the Fipio bus configuration principles.
What Is in This Section?
This section contains the following topics:
Topic
How to Access the Fipio Bus Configuration Screen
Fipio Bus Configuration Screen
How to Add a Device on the Bus
How to Add an Extension Module on the Bus
How to Delete/Move/ Duplicate a Bus Device
Changing the Fipio Communicator Type
Fipio Bus Displayed in the Project Browser
How to Access the Properties Screen of the Fipio Bus
Properties of the Fipio Bus: General Tab
Properties of the Fipio Bus: Expert tab
Expert Tab: Manual Mode
Fipio Configuration
Page
35008155 12/2018
83
Fipio Configuration
How to Access the Fipio Bus Configuration Screen
At a Glance
This describes how to access the configuration screen of the Fipio bus for a Premium or Atrium
PLC with a built-in Fipio link.
Procedure
To access the Fipio field bus, perform the following actions:
Step
1
Action
From the project navigator, deploy the Configuration directory.
Result: the following screen appears
2 Select the Fipio sub-directory and select the Opencommand using the contextual menu.
Result: the Fipio window appears
84
35008155 12/2018
Fipio Bus Configuration Screen
At a Glance
This screen is used to declare devices which are connected to the bus.
Illustration
The Fipio communication screen looks like this:
Fipio Configuration
35008155 12/2018
85
Fipio Configuration
Elements and Functions
This table describes the different areas that make up the configuration screen:
Number Element
1 Bus
2
Connections configured
Logical address area
Function
Bus number.
Indicates the number of connection points configured (0 and 63 are not counted).
This area consists of:
slot 0 (manager),
the addresses of each device, free addresses between 0 and 63 and over 63, address 63 is reserved for the programming terminal.
3 Module area This area contains the devices (base and extension modules, and the communicator if necessary) which are connected to the bus.
Gray squares on the bus indicates the two reserved addresses:
0 for the bus manager,
63 for the privileged terminal.
Available connection points are indicated by a white square with rounded edges.
86
35008155 12/2018
Fipio Configuration
How to Add a Device on the Bus
Procedure
This operation is used to add, via the software, a device connected to the Fipio bus.
Step
1
2
Action
Access the Fipio
configuration screen.
Right-click on the logical address of the connection point, at the location where the module has to be connected (available addresses from 1 to 62 and 64 to 127, addresses 0 and 63 being reserved by the system).
Result: the New Device screen appears.
3
4
35008155 12/2018
Enter the number of the connection point corresponding to the address.
By default, the Control Expert software offers the first free consecutive address.
In the Reference field, enter the type of device to connect to the bus.
87
Fipio Configuration
Step
5
6
Action
In the Communicator field, select the element type enabling communication on the Fipio bus.
For modules with built-in communicators, this window does not appear.
Validate with Ok.
Result: the module is declared.
88
35008155 12/2018
Fipio Configuration
How to Add an Extension Module on the Bus
Procedure
This operation is used to add, via the software, an extension module to a base module which is connected to the Fipio bus.
Step
1
2
Action
Access the Fipio
configuration screen.
3
On the base module, select the connection point which is shown as
From the contextual menu, select New Device.
Result: the New Device screen appears.
.
4 In the Reference field, select the type of device to connect to the base module.
35008155 12/2018
89
Fipio Configuration
Step
5
Action
Validate with Ok.
Result: the module is declared.
90
35008155 12/2018
Fipio Configuration
How to Delete/Move/ Duplicate a Bus Device
Procedure for Deleting a Device
This operation is used to delete, via the software, a device connected to the Fipio bus.
Step
1
2
3
Action
Access the Fipio
( see page 84 ) configuration screen.
Select the connection point to be deleted.
A dotted frame surrounds the selected connection point.
Select the Edit → Delete command.
Procedure to Follow to Delete an Extension Module
This operation is used to delete, via the software, an extension module connected to a base module.
Step
1
2
3
Action
Access the Fipio
( see page 84 ) configuration screen.
Select the extension module to be deleted.
A dotted frame surrounds the selected module.
Select the Edit → Delete command.
Procedure for Moving a Device
Moving a device does not involve a physical move on the bus, but rather a change in the device address logic. This triggers modification of the address of I/O objects in the program and movement of the variables associated with these objects.
Step
1
2
Action
Access the Fipio
( see page 84 ) configuration screen.
Select the connection point to be moved.
A dotted frame surrounds the selected connection point.
35008155 12/2018
91
Fipio Configuration
Step
3
Action
Drag and Drop the connection point to be moved to an empty connection point.
Result: the Move Device screen appears.
4
5
Enter the number of the destination connection point.
Confirm the new connection point by pressing OK.
Result: the Move Device screen appears.
6 Confirm the modification by pressing Yes to modify the addresses of the I/O objects in the program and move the variables associated with these objects.
Procedure to Follow to Move an Extension Module
Moving an extension module does not involve a physical move on the bus, but rather a change in the device address logic. This triggers modification of the address of I/O objects in the program and movement of the variables associated with these objects.
Step
1
2
Action
Access the Fipio
( see page 84 ) configuration screen.
Select the extension module to be moved.
A dotted frame surrounds the selected connection point.
92
35008155 12/2018
Step
3
Fipio Configuration
Action
Drag and Drop the connection point to be moved to an empty connection point in the base module.
Result: the Move Device screen appears.
4 Confirm the modification by pressing Yes to modify the addresses of the I/O objects in the program and move the variables associated with these objects.
Procedure for Duplicating a Device
This feature is similar to the function for moving a device.
Step
1
2
3
4
5
Action
Access the Fipio
( see page 84 ) configuration screen.
Select the connection point to be duplicated.
A dotted frame surrounds the selected connection point.
Select the Edit → Copy command.
Select the destination connection point.
Select the Edit → Paste command.
Result: the New Device screen appears.
35008155 12/2018
6
7
Enter the number of the destination connection point.
Confirm the new connection point by pressing OK.
93
Fipio Configuration
Procedure to Follow to Duplicate an Extension Module
The following table shows the procedure for duplicating an extension module.
Step
1
2
3
4
5
Action
Access the Fipio
( see page 84 ) configuration screen.
Select the extension module to be duplicated.
A dotted frame surrounds the selected connection point.
Select the Edit → Copy command.
Select the connection point of the destination base module.
Select the Edit → Paste command.
Result: the New Device screen appears.
94
35008155 12/2018
Fipio Configuration
Changing the Fipio Communicator Type
At a Glance
You can change the type of Fipio communicator for TBX IP20 discrete input/output modules.
Procedure
The following table shows the procedure for changing the Fipio communicator:
Step
1
2
3
Action
Access the Fipio
( see page 104 ) configuration screen.
Select the Fipio communicator to be changed.
From the contextual menu, select the product reference of the new communicator (TBX LEP 020 or TBX LEP 030).
35008155 12/2018
95
Fipio Configuration
Fipio Bus Displayed in the Project Browser
At a Glance
If the processor has a built-in Fipio link, the Fipio bus is shown in the configuration directory of the project browser with the number 2. This value cannot be modified.
The project browser displays all the Fipio devices in the Fipio configuration screen following items may be displayed below the device:
see page 85
.
Each device is displayed with its address number. Depending on the type of device configured, the
a communicator, a base module, an extension module.
Whenever a Fipio device is added/removed to/from the Fipio bus, it also appears/disappears on/from the Fipio bus in the project browser.
The following illustration shows the Fipio bus with its devices in the project browser:
96
35008155 12/2018
Fipio Configuration
How to Access the Properties Screen of the Fipio Bus
At a Glance
In a Fipio bus, the input/output exchange manager is the bus arbiter. This is in charge of managing access to the bus of each connected device.
The screen showing the properties of the bus lets you adapt the management parameters according to the devices connected.
How to Access the Properties
The following table shows the procedure for accessing the bus properties screen:
Step
1
2
3
Action
From the project navigator, deploy the Configuration directory.
Select the Fipio sub-directory.
Select the Properties command of the contextual menu.
Result: the Properties screen appears.
NOTE: Where a OZD FIP G3 is used, it is essential to set this value to 7km, whatever the actual length of the fiber optic.
35008155 12/2018
97
Fipio Configuration
Description of the Tabs
This table describes the different tabs which make up the properties screen:
Tab
General
Expert
Function
This tab is used to:
Select the type of profile managed by the bus arbiter,
View the RAM occupation of the devices,
Adjust the length of the bus.
This tab is used to select the management mode. For manual management, it is used to adjust the management parameters depending on the connected devices.
98
35008155 12/2018
Fipio Configuration
Properties of the Fipio Bus: General Tab
At a Glance
With this tab, you can access three types of information:
The profile,
The RAM Fip,
The bus length.
The Profile
The profile is chosen according to the devices which are connected to the Fipio bus. It can be in either of two versions:
FIP:
This profile is chosen by default.
It is compatible with all the devices of Schneider and partners.
WorldFip:
The selection of this mode allows you to operate the Fipio bus in accordance with the EN
50170 standard.
NOTE: The WorldFip profile mode can be used with the following restrictions:
No TSX FP ACC6 or TSX FP ACC8 repeaters,
Use of TBX LEP 020 version 1.4 minimum and TBX LEP 030 version 1.2 minimum,
Use of the PCMCIA TSX FPP 10 card, version 1.8 minimum.
RAM Fip
This is the memory used by the configured Fipio devices in relation to the memory available in the processor.
The bus length
With this cursor you can increase or decrease the bus length. The default value is 1 Km and the adjustment increment is 1 Km.
This length must be adjusted because it is taken into account in the calculation of the propagation time for the variables and messages on the bus and consequently in the calculation of the network cycle times.
NOTE: At each modification of the length of the Fipio bus, all the connected devices must be powered off, then on after the new project has been downloaded (in the PLC).
35008155 12/2018
99
Fipio Configuration
Properties of the Fipio Bus: Expert tab
At a Glance
With this tab, you have access to the management mode concerning the calculation of:
reversal and silence time, aperiodic bandwidths.
NOTE: At each modification of the parameters below, all the connected devices must be powered off, then on after the new project has been downloaded (to the PLC).
Automatic Mode
NOTE: This mode is the recommended mode.
The reversal and silence times and the bandwidths cannot be modified. They are calculated according to the bus parameters and device configuration data.
Manual Mode
No monitoring is carried out in manual mode. Modifying these parameters can cause the device connected to the bus not to work.
This mode is used to enter the reversal and silence times and the bandwidths.
It is mainly reserved for specific projects which require these values to be modified (example: use of Hirschmann transceivers).
100
35008155 12/2018
Expert Tab: Manual Mode
At a Glance
By selecting the manual mode, you have access to the following information:
The reversal and silence times,
The aperiodic bandwidths.
Illustration:
Fipio Configuration
Aperiodic variables
The following table gives a description of the times:
Reference Description
Silence time delay T0 This defines the maximum time between the transmission of the last byte of a frame and the transmission of the first byte of the following frame.
This time is expressed in micro-seconds.
Its value must be greater than the reversal time TR and less than 255.
Reversal time TR This defines the minimum time between the transmission of the last byte of a frame and the transmission of the first byte of the following frame.
This time is expressed in micro-seconds.
Its value must be greater than or equal to 1 and less than the silence time T0.
NOTE: In the case of using an OZD FIP G3, it is essential to adjust the value of T0 = 255µs and
TR = 30µs for all configurations.
35008155 12/2018
101
Fipio Configuration
Aperiodic Bandwidths
There are two types of exchange on a Fipio bus:
Exchanges of cyclic variables which are reserved for the process data,
Exchanges of aperiodic variables which concern the configuration of connected devices, the adjustment and the messaging.
A decrease or increase of the bandwidth of the aperiodic exchanges (Variables and Messages) slows down or accelerates the output of the configuration or adjustment variables which can circulate on the bus. The same applies to a decrease or increase of the aperiodic bandwidth of the messaging facility.
The following table gives a description of the aperiodic bandwidths:
Reference
Aperiodic variables
Messaging
Description
This defines the output of the aperiodic variables which can circulate on the bus.
This bandwidth is expressed in Kbits/s.
Its value can be adjusted from 1 to 200 Kbits/s.
This defines the output of the aperiodic messages which can circulate on the bus.
This bandwidth is expressed in Kbits/s.
Its value can be adjusted from 1 to 200 Kbits/s.
NOTE: An increase in the aperiodic bandwidth increases the network cycle time.
102
35008155 12/2018
Configuration of devices on the Fipio bus Section 5.3
Configuration of devices on the Fipio bus
Aim of this Section
This section introduces the configuration principles for Fipio bus devices.
What Is in This Section?
This section contains the following topics:
Topic
How to Access the Configuration Screen for a Fipio Device
Configuration Screen of a Fipio Device
How to Access Different Parameters Depending on the Type of Device
Fipio Configuration
Page
35008155 12/2018
103
Fipio Configuration
How to Access the Configuration Screen for a Fipio Device
At a Glance
When a device has been declared, its configuration can be accessed in the same way as for an inrack module.
This screen is used to select the task which exchanges the inputs/outputs: FAST or MAST. It can also be used to modify the configuration or adjustment parameters specific to the module.
Procedure
The following table describes the procedure for accessing the configuration of a device on the Fipio bus.
Step
1
2
3
Action
Access the Fipio
( see page 84 ) configuration screen.
Select the module to be configured.
Using the contextual menu, click Open Module.
104
35008155 12/2018
Fipio Configuration
Configuration Screen of a Fipio Device
At a Glance
This screen, featuring several zones, is used to declare the communication channel and configure the parameters of the selected device for Fipio communication.
Illustration
The following figure shows an example of a configuration screen.
35008155 12/2018
105
Fipio Configuration
Description
The next table shows the various elements of the configuration screen and their functions.
2
3
Number Element
1 Tabs
4
5
Function
The tab in the foreground indicates the mode in progress
(Configuration in this example). Every mode can be selected using the respective tab. The available modes are:
Configuration,
Adjust,
Debug which can be accessed only in online mode,
Calibration which can be accessed only in online mode,
Fault which can be accessed only in online mode.
Module area Gives a reminder of the device’s shortened name.
Channel area Is used:
By clicking on the reference number, to display the tabs:
Description which gives the characteristics of the device.
I/O Objects (see EcoStruxure™ Control Expert, Operating
Modes) which is used to presymbolize the input/output objects.
Fault which shows the device faults (in online mode).
General parameters area
To select the channel or group of channels to be configured,
To display the Symbol, name of the channel defined by the user (using the variable editor).
This area is used to define:
The type of task (MAST or FAST),
The channel filtering,
The fallback mode,
The reactivation, etc.
Configuration area
This area is used to set up the channels of the devices. For certain types of devices, this area is not accessible.
NOTE: Refer to the documentation of each device for information on general, configuration, adjustment and debugging parameters.
106
35008155 12/2018
Fipio Configuration
How to Access Different Parameters Depending on the Type of Device
How to Access Inputs/Outputs
The following procedure shows how to access the input or output parameters of a module. It can be used in both offline and online mode.
Step
1
2
3
Action
Access the configuration screen of the Fipio ( see page 104 )
device.
Select the Configuration tab.
Select the channel which corresponds to the inputs or the outputs or the inputs/outputs in the module area
Result: the configuration screen corresponding to the input/output type is displayed in the configuration area.
How to Set the Configuration Parameters
The following procedure describes how to modify the configuration parameters of a module. It can be used in both offline and online mode.
Step
1
2
3
4
5
Action
Access the configuration screen of a Fipio ( see page 104 )
device.
Select the Configuration tab.
Select the channel in the module area.
Depending on the type of device, you can do the following in the configuration area:
check or uncheck a box and/or, select a value from a drop-down list and/or, modify a value directly.
Confirm by pressing Enter.
How to Assign a Module to a Control Expert Task
The following procedure shows how to assign a module to a Control Expert task. It can be used in offline mode only.
Step
1
2
3
4
Action
Access the configuration screen of a Fipio ( see page 104 )
device.
Select the Configuration tab.
Select the channel in the module area.
In the General parameters area, select Task → MAST or FAST.
35008155 12/2018
107
Fipio Configuration
Management of Inputs/Outputs by Control Expert Tasks: Section 5.4
Management of Inputs/Outputs by Control Expert Tasks:
Aim of this Section
This section introduces the configuration principles for Control Expert tasks in Fipio mode.
What Is in This Section?
This section contains the following topics:
Topic
How to Access the Configuration of Control Expert Tasks in Fipio Mode
Management of Inputs/Outputs by Control Expert Tasks
Page
108
35008155 12/2018
How to Access the Configuration of Control Expert Tasks in Fipio Mode
Fipio Configuration
At a Glance
The following elements are configured in the Properties window of the MAST or FAST task:
the type of task (cyclic or periodic), as well as its watchdog and execution time, processing of Fipio inputs/outputs in relation to the task cycle (controlled or free).
The network cycle time is calculated using the elements provided above and the bus and Fipio device configuration.
NOTE: The Network Cycle Time is only significant where the project was generated after all modifications to the bus.
Procedure
The following table describes the procedure for accessing the MAST or FAST task configuration in
Fipio mode:
Step
1
2
Action
From the project browser select the MAST or FAST sub-directory of the
Program directory.
Select Properties from the contextual menu.
Result: the MAST Properties or FAST Properties window is displayed.
35008155 12/2018
109
Fipio Configuration
Management of Inputs/Outputs by Control Expert Tasks
At a Glance
The MAST or FAST task screen is divided into several areas. It allows you to manage Fipio inputs/outputs according to:
the task type (MAST or FAST), the execution type (cyclic or periodic) and period, the watchdog,
Controlled Fipio Mode
This mode can only be accessed for a Control Expert task declared as periodic.
110
In this mode, the refreshing of inputs/outputs is correlated with the task period. The system guarantees that inputs/outputs are updated in a single period. Only the inputs/outputs associated with this task are refreshed.
The calculated network cycle time is used to adjust the PLC (MAST or FAST) task period.
This period must be greater than or equal to the calculated network cycle time.
35008155 12/2018
Free Fipio Mode
This mode can be accessed for a Control Expert task declared as periodic.
Fipio Configuration
In this mode, no restriction is imposed on the task period. The period of the PLC task (MAST or
FAST) can be less than the network cycle time.
If a refresh is performed in a network cycle, the task can be executed without updating the inputs/outputs.
Selecting this mode gives you the possibility of having the lowest possible task times for projects where speed is critical.
Network Cycle Time
Network cycle time (calculated): this time is the network cycle time associated with a task. It is only displayed in the window if project generation is executed.
35008155 12/2018
111
Fipio Configuration
Confirmation of the Fipio bus configuration Section 5.5
Confirmation of the Fipio bus configuration
Aim of this Section
This Section introduces the main instances of Fipio bus configuration refusal.
What Is in This Section?
This section contains the following topics:
Topic
Refused Build
Examples of Validation Refusals
Page
112
35008155 12/2018
Fipio Configuration
Refused Build
At a Glance
When you use the Build Project or Rebuild All Project command, Control Expert checks the constraints relating to the project. If the constraints relating to task data for the devices configured and the bus parameters are not observed, the scan table is not generated.
In this case, a message is displayed in the output window
The configuration as a whole remains invalid until the problem is corrected by the user. This configuration cannot be transferred to the PLC.
If the task constraints are not observed, the cause of the failure and the recommendations on how to correct it, are provided in the properties.
Depending on the recommendations, you have two possible ways of correcting the configuration:
Access the task properties screen to modify the Control Expert task management parameters.
Access the Fipio configuration screen to modify the distribution of devices in the MAST or FAST tasks.
35008155 12/2018
113
Fipio Configuration
Examples of Validation Refusals
At a Glance
The following examples cover the main reasons for refusal that you are likely to encounter.
Example 1
The MAST task is configured in cyclic mode.
This network cycle time is greater than the watchdog time.
Example 2
The MAST or FAST task is configured in free periodic mode.
This network cycle time is greater than the watchdog time.
114
35008155 12/2018
Example 3
The MAST or FAST task is configured in controlled periodic mode.
This network cycle time is greater than the period.
Fipio Configuration
35008155 12/2018
115
Fipio Configuration
116
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Fipio Programming
35008155 12/2018
Programming Fipio communication Chapter 6
Programming Fipio communication
Subject of this Chapter
This Chapter describes the Programming process during set-up Fipio communication.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Fipio Fault Processing
Examples of Detection of Explicit Exchange Saturation
Page
35008155 12/2018
117
Fipio Programming
Fipio Fault Processing
At a Glance
Fipio faults can be processed from the debug and diagnostics screens. It can be advantageous to use the program to perform this processing.
Algorithm
The algorithm below is an example of an application algorithm that can be used to detect and manage faults on the Fipio bus
118
35008155 12/2018
Fipio Programming
Examples of Detection of Explicit Exchange Saturation
At a Glance
The examples provided below are in Structured Text language, but they are transposable to any of the languages available in Control Expert.
They should only be used if the Control Expert project is likely to activate more than 24 explicit functions simultaneously and if you wish to relaunch a request in the event of explicit exchange saturation.
Management of READ_STS for Module
35008155 12/2018
119
Fipio Programming
Management of READ_STS for Channel
120
35008155 12/2018
READ_PARAM at Connection Point 2
Fipio Programming
35008155 12/2018
121
Fipio Programming
WRITE_PARAM at Connection Point 2
122
35008155 12/2018
WRITE_CMD at Connection Point 2
Fipio Programming
35008155 12/2018
123
Fipio Programming
124
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Fipio Debugging
35008155 12/2018
Debugging a Fipio communication Chapter 7
Debugging a Fipio communication
Subject of this Chapter
This Chapter describes the Debugging process during set-up of Fipio communication.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Debug Mode
How to Access the Debug Screens of Remote Devices
Debug Screen for a Device on the Fipio Bus
Page
35008155 12/2018
125
Fipio Debugging
Debug Mode
At a Glance
The Debug mode is only accessible in online mode.
This mode is used:
to see if a device is faulty by checking whether a red square is displayed in the Fipio configuration screen, to adjust and debug devices connected to the Fipio bus from their application screen.
Unavailable Functions
The following functions are not available from the Fipio configuration screen in online mode:
addition of a new device in online mode, duplication or movement of a device, modification of a device, modification of the communication adapter, deletion of a device, addition of an extension module, deletion of an extension module, duplication or movement of an extension module.
A message indicating the reason why the function cannot be accessed is displayed in the Control
Expert status bar.
126
35008155 12/2018
Fipio Debugging
How to Access the Debug Screens of Remote Devices
At a Glance
This describes how to access the debug screen of a device connected to the Fipio bus.
Procedure
The following table shows the procedure to follow:
Step
1
2
3
4
Action
Connect to the manager PLC.
Access the Fipio
( see page 84 ) bus configuration screen.
Double-click on the module to debug.
Select the Debug tab.
35008155 12/2018
127
Fipio Debugging
Debug Screen for a Device on the Fipio Bus
At a Glance
In debug mode the following functions can be accessed by opening the application screen of a device:
viewing of the module configuration parameters, modification of the configuration, reading, writing and saving of adjustment parameters, reading, writing and forcing of inputs/outputs, aperiodic reading of status data, writing of command words.
Illustration
The figure below represents a debug screen.
128
35008155 12/2018
Fipio Debugging
Description
The following table shows the different elements of the debug screen and their functions.
Number Element
1 Tabs
2
3
4
5
Module area Specifies the abbreviated heading of the module.
In the same area there are 3 LEDs which indicate the module’s operating mode:
RUN indicates the operating status of the module,
ERR indicates an internal fault in the module,
I/O indicates a fault from outside the module or an application fault.
Channel area Is used:
By clicking on the reference number, to display the tabs:
Description which gives the characteristics of the device.
I/O Objects (see EcoStruxure™ Control Expert, Operating
Modes) which is used to presymbolize the input/output objects.
Fault which shows the device faults (in online mode).
General parameters area
Parameters in progress area
Function
The tab in the foreground indicates the mode in progress (Debug in this example). Each mode can be selected using the respective tab.
Debug which can be accessed only in online mode,
Calibration which can be accessed only in online mode,
Configuration,
Adjust.
To select the required channel or channel group; to the left of the symbol there is a copy of theCHx channel LED.
Provides a reminder of the channel settings (Task type) and gives access to various functions (Global Unforce, etc.).
This area displays the state of the inputs and outputs, and the different parameters in progress.
Specific Parameters
Refer to the documentation of each device for information on the general, configuration, adjustment and debugging parameters available.
For input/output modules, the specific parameters area shows the value and state of each of the module channels and gives access to the channel commands.
35008155 12/2018
129
Fipio Debugging
130
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Fipio Diagnostics
35008155 12/2018
Fipio communication diagnostics Chapter 8
Fipio communication diagnostics
Subject of this Chapter
This Chapter describes the Diagnostics process during set-up of Fipio communication.
What Is in This Chapter?
This chapter contains the following topics:
Topic
Diagnostics Mode
How to Access the Fipio Bus Monitoring Screen
Diagnostics Screen: Fipio Bus Monitoring
How to Access the Device Monitoring Screen
Diagnostics Screen: Device Monitoring
How to Access the Device Monitoring Screen for a Single Device
Diagnostics Screen: Device Monitoring
How to Access the Communication Faults History Screen
Diagnostics Screen: Communication Errors History
Page
35008155 12/2018
131
Fipio Diagnostics
Diagnostics Mode
At a Glance
In online mode it is possible to perform general diagnostics of bus errors and device faults.
These diagnostics can be performed using the screens available in Control Expert or by using the system bits and words managed by the application.
Two modes are available:
Fipio bus monitoring, device monitoring with or without fault history.
Communication Counters
Each connection point configured (including connection points 0 and 63) has a report variable. This variable contains the communication and performance counter values.
This variable contains:
the activity counters numbered from 16#00 to 16#20 compliant with the WORLDFIP standard, the fault counters numbered from 16#21 to 16#7F compliant with the WORLDFIP standard, the manufacturer-specific counters numbered from 16#80 to 16#FF; these counters are not compliant with the WORLDFIP standard.
The fault counters change value when communication faults occur on the Fipio bus.
Diagnostic Screens.
Four types of screen are used to view changes in the value of these various counters and so to view communication faults:
The Fipio Bus Monitoring screen provides a global view of the Fipio bus. It displays the communication faults for the whole bus.
The Device Monitoring screen provides a summary for each connection point. It shows all the connection points and signals any change in the value of the fault counters for each connection point.
The Device Monitoring at Connection Point screen shows all counters with any change in their value for a given connection point.
The Communication Errors History screen provides a fault history. It is used to keep a dated trace of changes in the fault counters.
Only one single screen of each type can be opened (one per connection point for the third type). If you try to open a screen that is already open it will be displayed instantly.
132
35008155 12/2018
Fipio Diagnostics
How to Access the Fipio Bus Monitoring Screen
At a Glance
This describes how to access the Fipio bus monitoring screen. It can be used in online mode only.
Procedure
The following table shows the procedure to follow:
Step
1
2
3
4
Action
Connect to the manager PLC.
From the Configuration directory in the project browser, select the Fipio bus.
Select the Open command.
Result: the Fipio bus window is displayed
Right click on the background.
Result: the contextual menu appears.
5 Select the Fipio Bus Monitoring command.
35008155 12/2018
133
Fipio Diagnostics
Diagnostics Screen: Fipio Bus Monitoring
At a Glance
This screen provides the user with a global view of the bus and signals communication faults occurring on the bus.
The screen lists all the communication fault counters and signals any change in their value.
Illustration
The device screen looks like this:
Elements and functions
Each line contains:
an icon showing the state of the fault counters (the reference state being the state they were in when the screen was opened):
white for normal, red for a counter showing a fault,
the counter number in hexadecimal, the counter label (as specified by the WORLDFIP standard).
134
35008155 12/2018
Fipio Diagnostics
Diagnostics
While the screen is open, the report variables of all connection points are read cyclically.
When the screen is opened or upon reset, the values of the counters for each report variable are stored to constitute a reference state. The time between two reads of the same variable is equal to the number of devices configured + 2 (0 and 63) in seconds.
As soon as a fault counter changes its value from its reference value, for any connection point, the counter icon changes to red. Reading the counter label provides details of the type of fault detected.
Example
Counter 21 changes to red. This means that at least one counter 21 of all the counters 21 has changed its value.
How to Reset the Reference State
The following procedure describes how to reset the reference state.
Step
1
Action
Right click on the background.
Result: a shortcut menu appears.
2 Select the Reset command.
Bus Monitoring by the Application
In Control Expert, the system words %SW150 and %SW151 indicate the number of frames sent and received by the channel manager.
If these two counters have stopped this indicates the Fipio channel manager function has stopped.
This is signaled to the user in the configuration screen in online mode by the connection point 0 shown in red.
35008155 12/2018
135
Fipio Diagnostics
How to Access the Device Monitoring Screen
At a Glance
This describes how to access the Fipio bus device monitoring screen. It can be used in online mode only.
Procedure
The following table shows the procedure to follow:
Step
1
2
3
4
Action
Connect to the manager PLC.
From the Configuration directory in the project browser, select the Fipio bus.
Select the Open command.
Result: the Fipio bus window is displayed
Right click on the background.
Result: the contextual menu appears.
5 Select the Device Monitoring command.
136
35008155 12/2018
Diagnostics Screen: Device Monitoring
At a Glance
This screen is used to access monitoring of all configured devices.
The screen lists the configured connection points as well as points 0 and 63.
Illustration
The device screen looks like this:
Fipio Diagnostics
Elements and Functions
The following elements are associated to each connection point:
an icon specifying:
if the connection point must be monitored. If the box is checked, the device is monitored.
if the connection point is faulty. The icon changes to red if a fault is detected.
the connection point number.
Diagnostics
While the screen is open, the report variables of all connection points are read cyclically.
When the screen is opened or upon reset, the values of the counters for each report variable are stored to constitute a reference state. The time between two reads of the same variable is equal to the number of devices configured + 2 (0 and 63) in seconds.
A connection point is considered to be faulty if the value of one of its fault counters has changed from the reference state. When the point is faulty, the icon is shown in red.
Diagnostics are only sent back if a communication is established between the bus manager and the faulty connection point. The faults are signaled for fault counters defined by the WORLDFIP standard.
35008155 12/2018
137
Fipio Diagnostics
How to Deactivate Device Monitoring
The following procedure describes how to deactivate monitoring of a device on the bus.
Step
1
Action
Click on the check box of the connection point to be deactivated.
Result:
The box is unchecked In this case, the report variable of this connection point is no longer read and its reference state is reset.
How to Reset the Reference State
The following procedure describes how to reset the reference state.
Step
1
Action
Right click on the background.
Result: a shortcut menu appears.
2 Select the Reset command.
138
35008155 12/2018
Fipio Diagnostics
How to Access the Device Monitoring Screen for a Single Device
At a Glance
This describes how to access the monitoring screen for a single device connected to the Fipio bus and how to view its fault counters.
It can be used in online mode only.
Procedure
The following table shows the procedure to follow:
Step
1
2
3
Action
Access the Device Monitoring screen.
Select the connection point number you wish to access.
Result: the number is displayed in reverse video.
Right click on the background.
Result: a shortcut menu appears.
4 Select the Device Monitoring command.
35008155 12/2018
139
Fipio Diagnostics
Diagnostics Screen: Device Monitoring
At a Glance
This screen is used to display the details of changes in the value of all counters for the selected connection point.
It is made up of three areas corresponding to each type of counter:
activity, fault, manufacturer-specific.
Illustration
The device screen looks like this:
140
35008155 12/2018
Fipio Diagnostics
Elements and Functions
The following elements are associated to each counter:
an icon indicating any change in the counter from its reference state:
white: no change,
green: change in the activity or manufacturer-specific counters, red: change in the fault counters (the current value is different to the reference state).
the counter number in hexadecimal, its reference value in hexadecimal, its value in hexadecimal from the last read operation, its current value in hexadecimal, its label in accordance with the WORLDFIP standard or the label Counter not listed for the manufacturer-specific part.
Diagnostics
While the screen is open, the report variables of all connection points are read cyclically.
When the screen is opened or upon reset, the values of the counters for each report variable are stored to constitute a reference state.
A connection point is considered to be faulty if the value of one of its fault counters has changed from the reference state. When the point is faulty, the icon is shown in red.
Diagnostics are only sent back if a communication is established between the bus manager and the faulty connection point. The faults are signaled for fault counters defined by the WORLDFIP standard.
How to Reset the Reference State
The following procedure describes how to reset the reference state.
Step
1
Action
Right click on the background.
Result: a shortcut menu appears.
2 Select the Reset command.
35008155 12/2018
141
Fipio Diagnostics
How to Access the Communication Faults History Screen
At a Glance
This describes how to access the Fipio bus communication faults history screen.
It can be used in online mode only.
Procedure
The following table shows the procedure to follow:
Step
1
2
Action
Access the Device Monitoring screen.
Right click on the background.
Result: a shortcut menu appears.
3 Select the Communication Errors History command.
142
35008155 12/2018
Fipio Diagnostics
Diagnostics Screen: Communication Errors History
At a Glance
This screen lists the communication faults for the connection points configured (plus 0 and 63) and declared as monitored in the Device Monitoringscreen.
Illustration
The history looks like this:
Elements and Functions
Every time a counter for a connection point changes, a line is added. It contains:
the current date and time on the programming terminal.
the connection point number in decimal.
the fault counter number in hexadecimal, the counter value in hexadecimal, the counter label in accordance with the WORLDFIP standard.
How to Pause/Resume the History Function
This command is used to stop or resume updating of the screen.
Step
1
Action
Right click on the background.
Result: a contextual menu appears.
35008155 12/2018
2 Select the Pause History or Resume History command.
143
Fipio Diagnostics
How to Clear the History
This command can be accessed if the Pause History function has been activated. It can be used to delete all the lines on the screen.
Step
1
2
Action
Access the contextual menu.
Select the Clear History command.
How to Sort the History
This command can be accessed if the Pause History function has been activated. It can be used to sort all the lines of the history by date and time, or by connection point, or by counter.
Step
1
2
3
Action
Right click on the background.
Access the contextual menu.
Select the desired command:
Sort → By Date and Time
Sort → By Connection Point
Sort → By Counter
How to Copy the History
This command can be accessed if the Pause History function has been activated. It is used to copy the selected lines to the clipboard in text format.
Step
1
2
3
Action
Right click on the background.
Access the contextual menu.
Select the Copy command.
How to Stop the History Automatically
This function, when selected, allows you to stop the history when it reaches the maximum number of lines (4000 lines). A message informs you that the history has stopped. When the function has not been selected, and when the maximum number is reached, the newly added lines replace the first lines recorded (rotational mode).
Step
1
2
Action
Access the contextual menu.
Select the Automatic History Stop.
Result: selecting the command checks the function.
144
35008155 12/2018
How to Reset the Reference State
The following procedure describes how to reset the reference state.
Step
1
2
Action
Access the contextual menu.
Select the Reset command.
Fipio Diagnostics
35008155 12/2018
145
Fipio Diagnostics
146
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Fipio language objects
35008155 12/2018
Language objects associated with Fipio communication Chapter 9
Language objects associated with Fipio communication
Subject of this Section
This Chapter introduces language objects associated with Fipio communication.
What Is in This Chapter?
This chapter contains the following sections:
Section
9.1
9.2
Topic
Language Objects and IODDTs for Fipio Communication
The IODDT Type T_GEN_MOD Applicable to All Modules
Page
35008155 12/2018
147
Fipio language objects
Language Objects and IODDTs for Fipio Communication Section 9.1
Language Objects and IODDTs for Fipio Communication
Subject of this Section
This section presents general information about language objects and IODDTs associated with the
Fipio bus.
What Is in This Section?
This section contains the following topics:
Topic
Presentation of Language Objects for Fipio Communication
Implicit Exchange Language Objects Associated with the Application-Specific Function
Explicit Exchange Language Objects Associated with the Application-Specific Function
Management of Exchanges and Reports with Explicit Objects
Details of Implicit Exchange Objects for Fipio Communication
Page
148
35008155 12/2018
Fipio language objects
Presentation of Language Objects for Fipio Communication
General
Fipio communication does not have any specific associated IODDT. The IODDTs that you can use are those IODDTs defined for devices associated with Fipio communication.
All these IODDTs are described in detail in the specific manuals for Fipio devices. The T_GEN_MOD
IODDT is presented in this manual as it can be used by all devices.
NOTE: IODDT variables can be created in two different ways:
Using the I/O objects
Data Editor.
(see EcoStruxure™ Control Expert, Operating Modes) tab,
The following table shows the different IODDTs that are available depending on the Fipio device used:
IODDT
T_DIS_IN_STD
T_DIS_IN_FIP_STD
T_DIS_OUT_STD
T_DIS_IN_GEN
T_DIS_OUT_GEN
T_ANA_IN_STD
T_ANA_OUT_STD
T_ANA_IN_GEN
T_ANA_OUT_GEN
T_DIS_IN_MOM
T_DIS_OUT_MOM
T_ANA_IN_MOM4
T_ANA_IN_MOM8
T_ANA_IN_MOM16
T_ANA_OUT_MOM4
T_ANA_DIS_IN_OUT_AMM
T_STDP_GEN
T_LEXIUM_FIPIO
T_ATV58F_STD
T_ATV58_STD
T_DIS_ESF_IP67_x_STD (1)
Device
Standard profiles
X
X
X
X
X
X
X
X
X
TBX Waterproof
IP65
X
X
X
X
X
X
X
X
X
X
Waterproof
IP67
Fipio/AS-i gateway
Momentum Lexium Altivar
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
35008155 12/2018
149
Fipio language objects
IODDT Device
Standard profiles
T_DIS_EMF_IP67_x_STD (2)
T_DIS_OUT_IP67_STD
T_SAP10_STD
Legend:
(1) : x represents number from 0 to 7
(2) : x represents numbers 8, 10 to 13
TBX Waterproof
IP65
X
X
Waterproof
IP67
Fipio/AS-i gateway
Momentum Lexium Altivar
X
Language Object Types
Each IODDT contains a group of language objects which are used to control them and check their operation.
There are two types of language object:
Implicit exchange objects, which are automatically exchanged on each cycle of the task associated with the module,
Explicit exchange objects, which are exchanged when requested to do so by the project, using explicit exchange instructions.
Implicit exchanges concern the states of modules and slaves, etc.
Explicit exchanges are used to set up the module's parameters and for module diagnostics.
150
35008155 12/2018
Fipio language objects
Implicit Exchange Language Objects Associated with the Application-Specific Function
At a Glance
An integrated application-specific interface or the addition of a module automatically enhances the language objects application used to program this interface or module.
These objects correspond to the input/output images and software data of the module or integrated application-specific interface.
Reminders
The module inputs ( %I and %IW ) are updated in the PLC memory at the start of the task, the PLC being in RUN or STOP mode.
The outputs ( %Q and %QW ) are updated at the end of the task, only when the PLC is in RUN mode.
NOTE: When the task occurs in STOP mode, either of the following are possible, depending on the configuration selected:
outputs are set to fallback position (fallback mode) outputs are maintained at their last value (maintain mode)
Figure
The following diagram shows the operating cycle of a PLC task (cyclical execution).
35008155 12/2018
151
Fipio language objects
Explicit Exchange Language Objects Associated with the Application-Specific Function
At a Glance
Explicit exchanges are exchanges performed at the user program's request, and using instructions:
READ_STS words)
(see EcoStruxure™ Control Expert, I/O Management, Block Library)
WRITE_CMD
SAVE_PARAM adjustment parameters)
RESTORE_PARAM
(restore adjustment parameters)
(read status
(see EcoStruxure™ Control Expert, I/O Management, Block Library) command words)
WRITE_PARAM adjustment parameters)
READ_PARAM
(write
(see EcoStruxure™ Control Expert, I/O Management, Block Library)
(see EcoStruxure™ Control Expert, I/O Management, Block Library) adjustment parameters)
(see EcoStruxure™ Control Expert, I/O Management, Block Library)
(write
(read
(save
(see EcoStruxure™ Control Expert, I/O Management, Block Library)
These exchanges apply to a set of %MW objects of the same type (status, commands or parameters) that belong to a channel.
NOTE: These objects provide information about the module (e.g., type of channel fault, etc.), and are used to control the modules and to define their operating modes (saving and restoring currently applied adjustment parameters).
152
35008155 12/2018
Fipio language objects
General Principle For Using Explicit Instructions
The diagram below shows the different types of explicit exchanges that can be made between the processor and module.
Managing exchanges
During an explicit exchange, it is necessary to check its performance in order that data is only taken into account when the exchange has been correctly executed.
To do this, two types of information are available:
information concerning the exchange in progress
see page 157
see page 156
The following diagram describes the management principle for an exchange:
NOTE: In order to avoid several simultaneous explicit exchanges for the same channel, it is necessary to test the value of the word EXCH_STS ( %MWr.m.c.0
) of the IODDT associated to the channel before to call any EF using this channel.
35008155 12/2018
153
Fipio language objects
Management of Exchanges and Reports with Explicit Objects
At a Glance
When data is exchanged between the PCL memory and the module, the module may require several task cycles to acknowledge this information. All IODDTs use two words to manage exchanges:
EXCH_STS (%MW\2.e\0.m.c.0): exchange in progress
EXCH_RPT (%MW\2.e\0.m.c.1): report
NOTE: Depending on the localization of the module, the management of the explicit exchanges
(%MW0.0.MOD.0.0 for example)will not be detected by the application:
For in-rack modules, explicit exchanges are done immediately on the local PLC Bus and are finished before the end of the execution task. So, the READ_STS , for example, is always finished
when the %MW0.0.MOD.0.0 bit is checked by the application.
For remote bus (Fipio for example), explicit exchanges are not synchronous with the execution task. So, the detection is possible by the application.
Illustration
The illustration below shows the different significant bits for managing exchanges:
154
35008155 12/2018
Fipio language objects
Description of the Significant Bits
Each bit of the words EXCH_STS (%MW\2.e\0.m.c.0) and EXCH_RPT (%MW\2.e\0.m.c.1) is associated with a type of parameter:
Rank 0 bits are associated with the status parameters:
The STS_IN_PROGR bit (%MW\2.e\0.m.c.0.0) indicates whether a read request for the status
words is in progress.
The STS_ERR bit (%MW\2.e\0.m.c.1.0) specifies whether a read request for the status words is refused by the module channel.
Rank 1 bits are associated with the command parameters:
The CMD_IN_PROGR bit (%MW\2.e\0.m.c.0.1) indicates whether command parameters are
being sent to the module channel.
The CMD_ERR bit (%MW\2.e\0.m.c.1.1) specifies whether the command parameters are refused by the module channel.
Rank 2 bits are associated with the adjustment parameters:
The ADJ_IN_PROGR bit (%MW\2.e\0.m.c.0.2) indicates whether the adjustment parameters are being exchanged with the module channel (via WRITE_PARAM, READ_PARAM,
SAVE_PARAM, RESTORE_PARAM ).
The ADJ_ERR bit (%MW\2.e\0.m.c.1.2) specifies whether the adjustment parameters are refused by the module.
If the exchange is correctly executed, the bit is set to 0.
Rank 15 bits indicate a reconfiguration on channel c of the module from the console
(modification of the configuration parameters + cold start-up of the channel).
NOTE: m stands for the position of the module; c stands for the channel number in the module.
NOTE: Exchange and report words also exist at module level EXCH_STS (%MW\2.e\0.m.MOD) and EXCH_RPT (%MW\2.e\0.m.MOD.1) in the IODDT type T_GEN_MOD .
Example
Phase 1: Sending data by using the WRITE_PARAM instruction.
When the instruction is scanned by the PLC processor, the Exchange in progress bit is set to 1 in
%MW\2.e\0.m.c.
35008155 12/2018
155
Fipio language objects
Phase 2: Analysis of the data by the I/O module and report
When the data is exchanged between the PLC memory and the module, processing by the module is managed by the ADJ_ERR bit (%MW\2.e\0.m.c.1.2): Report (0 = correct exchange, 1 = faulty exchange).
NOTE: There is no adjustment parameter at module level.
Execution Indicators for an Explicit Exchange: EXCH_STS
The table below shows the control bits of the explicit exchanges: EXCH_STS (%MW\2.e\0.m.c.0).
Standard symbol
STS_IN_PROGR
CMD_IN_PROGR
ADJ_IN_PROGR
RECONF_IN_PROGR
Type Access Meaning
BOOL R Reading of channel status words in progress
BOOL R
BOOL R
Command parameters exchange in progress
Adjust parameters exchange in progress
BOOL R Reconfiguration of the module in progress
Address
%MW\2.e\0m.c.0.0
%MW\2.e\0m.c.0.1
%MW\2.e\0m.c.0.2
%MW\2.e\0.m.c.0.15
NOTE: If the module is not present or is disconnected, explicit exchange objects (Read_Sts for example) are not sent to the module (STS_IN_PROG (%MWr.m.c.0.0) = 0), but the words are refreshed.
156
35008155 12/2018
Fipio language objects
Explicit Exchange Report: EXCH_RPT
The table below shows the report bits: EXCH_RPT (%MW\2.e\0.m.c.1).
Standard symbol
STS_ERR
CMD_ERR
ADJ_ERR
RECONF_ERR
Type Access Meaning
BOOL R Error in reading status words of the channel
(1 = failure)
BOOL R
BOOL R
Error when exchanging command parameters
(1 = failure)
Error when exchanging adjustment parameters
(1 = failure)
BOOL R Fault when reconfiguring the channel
(1 = failure)
Address
%MW\2.e\0.m.c.1.0
%MW\2.e\0.m.c.1.1
%MW\2.e\0.m.c.1.2
%MW\2.e\0.m.c.1.15
35008155 12/2018
157
Fipio language objects
Details of Implicit Exchange Objects for Fipio Communication
At a Glance
The following table presents all the implicit exchange objects for Fipio communication that can be displayed or modified by the application program.
Bit Objects
The table below shows the different bit objects:
Symbol
At user's initiative
At user's initiative
Type
EBOOL R
EBOOL
Access Meaning
R
Image of physical inputs of module (acquisition of inputs).
Image of physical outputs of the module (output commands).
Address
%I\2.e\0.m.c.d
%Q\2.e\0.m.c.d
Word Objects
The table below shows the different word objects:
Symbol
At user's initiative
At user's initiative
Type
INT
INT
Access Meaning
R Image of physical inputs of module (acquisition of inputs).
R Image of physical outputs of the module (output commands).
Address
%IW\2.e\0.m.c.d
%QW\2.e\0.m.c.d
158
35008155 12/2018
Fipio language objects
The IODDT Type T_GEN_MOD Applicable to All Modules Section 9.2
The IODDT Type T_GEN_MOD Applicable to All Modules
Details of the Language Objects for the IODDT of Type T_GEN_MOD
At a Glance
All Premium PLC modules have an associated IODDT of type T_GEN_MOD .
Observations
In general, the meaning of the bits is given for bit status 1. In specific cases an explanation is given for each status of the bit.
Not all bits are used.
List of Objects
The table below presents the objects of the IODDT:
Standard symbol
MOD_ERROR
EXCH_STS
STS_IN_PROGR
EXCH_RPT
STS_ERR
MOD_FLT
MOD_FAIL
CH_FLT
BLK
CONF_FLT
NO_MOD
EXT_MOD_FLT
MOD_FAIL_EXT
CH_FLT_EXT
BLK_EXT
Type
BOOL
INT
BOOL
INT
BOOL
INT
BOOL
BOOL
BOOL
BOOL
BOOL
BOOL
BOOL
BOOL
BOOL
R
R
R
R
R
R
R
R
R
R
R
R
R
R
Access Meaning
R Module error bit.
Module exchange control word.
Reading of module status words in progress.
Exchange report word.
Error when reading status words of the module.
Module internal error word.
Internal fault, module unserviceable.
Faulty channel(s).
Terminal block fault.
Address
%I\2.e\0.m.MOD.ERR
%MW\2.e\0.m.MOD.0
%MW\2.e\0.m.MOD.0.0
%MW\2.e\0.m.MOD.1
%MW\2.e\0.m.MOD.1.0
%MW\2.e\0.m.MOD.2
%MW\2.e\0.m.MOD.2.0
%MW\2.e\0.m.MOD.2.0
%MW\2.e\0.m.MOD.2.2
Hardware or software configuration error.
%MW\2.e\0.m.MOD.2.5
Module missing or inoperative.
%MW\2.e\0.m.MOD.2.6
%MW\2.e\0.m.MOD.2.7
Internal error word of the module (Fipio extension only).
Internal fault, module unserviceable (Fipio extension only).
%MW\2.e\0.m.MOD.2.8
Faulty channel(s) (Fipio extension only).
%MW\2.e\0.m.MOD.2.9
Terminal block fault (Fipio extension only). %MW\2.e\0.m.MOD.2.10
35008155 12/2018
159
Fipio language objects
Standard symbol
CONF_FLT_EXT
NO_MOD_EXT
Type
BOOL
BOOL
Access Meaning
R Hardware or software configuration fault
(Fipio extension only).
R Module missing or inoperative (Fipio extension only).
Address
%MW\2.e\0.m.MOD.2.13
%MW\2.e\0.m.MOD.2.14
160
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Standard profiles
35008155 12/2018
Fipio communication standard profiles Chapter 10
Fipio communication standard profiles
Subject of this Chapter
This chapter introduces devices compatible with the standard communication profiles for use with the Fipio bus and its services.
What Is in This Chapter?
This chapter contains the following sections:
Section
10.1
10.2
10.3
10.4
Topic
Introduction to standard Fipio communication profiles
Configuration of the Fipio bus standard profiles
Debugging the Fipio bus standard profiles
Language objects associated with the Fipio bus standard profiles
Page
35008155 12/2018
161
Standard profiles
Introduction to standard Fipio communication profiles Section 10.1
Introduction to standard Fipio communication profiles
Aim of this Section
This Section provides a summary description of the standard profiles of the Fipio bus and its associated services.
What Is in This Section?
This section contains the following topics:
Topic
Standard profiles: general
Designation of a Standard Profile
List of Catalog Standard Profiles Proposed by Control Expert
Page
162
35008155 12/2018
Standard profiles
Standard profiles: general
Introduction
A device conforming to the standard Fipio communication profiles can be linked to a Fipio bus, to exchange the input/output variables.
Data exchanges with devices are used to:
exchange inputs/outputs, write configuration or adjustment parameters, diagnose a connected device.
There are three types of standard profile:
FRDP: Fipio Reduced Device Profile
FSDP: Fipio Simple Device Profile
FEDP: Fipio Extended Device Profile
Volume of data exchanged
The device profiles, which conform to a standard profile are a function of the number of inputs and outputs to be exchanged.
The table below describes the words managed by the different standard profiles:
FRD FSD FED Profile
Process data input acquisition output control
Configuration (optional)
Adjust (optional)
Commands specific command
Diagnostics input validity specific status
-
-
-
2 words
2 words
-
1 byte
-
8 words
8 words
16 words
32 words
-
1 byte
32 words
32 words
30 words
30 words
8 words
1 byte
8 words
35008155 12/2018
163
Standard profiles
Designation of a Standard Profile
At a Glance
A device conforming to the standard Fipio communication profiles is defined by assigning one of the standard profiles from the Standard Profiles family to it at the Fipio connection point.
The family consists of a list of standard profile references.
Composition of a Reference
Each reference is made up of several significant codes:
the standard profile used:
FRD
FSD
FED the connected device structure:
C: Compact
M: Modular
the number and type of objects exchanged with the manager: corresponds to the input/output exchange volume in 16 bit words
2 words
8 words
32 words
P: corresponds to the presence of configuration or adjustment parameters (optional).
Example of a compact standard profile reference: FED C32 P.
164
35008155 12/2018
Standard profiles
List of Catalog Standard Profiles Proposed by Control Expert
At a Glance
When configuring the Fipio bus, you can connect standard profiles according to the type of device.
Compact Devices
The following table lists the compact standard profiles:
Reference
FRD C2
FRD C2 P
FSD C8
FSD C8 P
FED C32
FED C32 P
Designation
EQP RED CMPCT 2M
EQP STD CMPCT 2M P
STD DEV CMPCT 2W P
EQP STD CMPCT 8M
STD DEV CMPCT 8W
EQP STD CMPCT 8M P
STD DEV CMPCT 8W P
EQP STD CMPCT 32M
STD DEV CMPCT 32W
EQP STD CMPCT 32M P
STD DEV CMPCT 328W P
Language interface
32 bits %I, 32 bits %Q
32 %I bits, 32 %Q bits
16 configuration words, 32 adjustment words
8 %IW words, 8 %QW words
8 %IW words, 8 %QW words
16 configuration words, 32 adjustment words
32 %IW words, 32 %QW words
32 %IW words, 32 %QW words
30 configuration words, 30 adjustment words
Modular Devices
The following table lists the modular standard profiles:
Reference
FSD M8
FSD M8 P
FED M32
FED M32 P
Designation
EQP STD MOD 8M
STD DEV MOD 8W
EQP STD MOD 8M P
Language interface
8 %IW words, 8 %QW words
STD DEV MOD 8W P
EQP STD MOD 32M
8 %IW words, 8 %QW words
16 configuration words, 32 adjustment words
32 %IW words, 32 %QW words
EXTENDED DEV MOD 32W
EQP STD MOD 32M P 32 %IW words, 32 %QW words
EXTENDED DEV MOD 328W P 30 configuration words, 30 adjustment words
35008155 12/2018
165
Standard profiles
Momentum Devices
With the Momentum product family, an analog input/output module is not available in the catalog.
In this case, you need to select one of the OTHER_FxD_[P] standard profile references.
The selection criteria are as follows:
Language interface
32 %I bits, 32 %Q bits
Reference
OTHER_FRD
OTHER_FRDP
OTHER_FSD
OTHER_FSDP
OTHER_FED
OTHER_FEDP
8 %IW words, 8 %QW words
32 %IW words, 32 %QW words
Communicator
The following communicators are available:
Family
STD-P
Reference
TSX FPP10
Language interface
TSX Fipio communication module
Momentum 170 FNT 110 01 TSX Fipio communication module for Momentums
166
35008155 12/2018
Standard profiles
Configuration of the Fipio bus standard profiles Section 10.2
Configuration of the Fipio bus standard profiles
Aim of this Section
This Section introduces the configuration principles for the Fipio bus standard profiles.
What Is in This Section?
This section contains the following topics:
Topic
Configuration Screen for a Standard Profile
How to Modify the Parameters of a Standard Profile
Adjustment Mode
Page
35008155 12/2018
167
Standard profiles
Configuration Screen for a Standard Profile
At a Glance
The configuration screen for a standard profile reuses the elements of the devices on the Fipio bus
see page 105
However, certain parameters are specific to this screen. The remainder of this document only covers the part specific to standard profiles.
Illustration
The figure below represents a configuration screen.
168
35008155 12/2018
Standard profiles
Description
The following table presents the various elements of the configuration screen and their functions.
2
3
Number Element
1 Tabs
4
5
General parameters area
Configuration area
Function
The tab in the foreground indicates the mode in progress
(Configuration in this example). Every mode can be selected using the respective tab. The available modes are:
Configuration,
Adjust,
Debug which can be accessed only in online mode,
Fault (channel level) accessible only in online mode.
Module area Gives a reminder of the device’s shortened name.
Channel area Is used:
By clicking on the device reference number, to display the tabs:
Description which gives the characteristics of the device.
I/O Objects (see EcoStruxure™ Control Expert,
Operating Modes) which is used to presymbolize the input/output objects,
Fault which shows the device faults (in online mode).
Channel: single channel for a standard profile.
Symbol: name of the channel defined by the user (using the variable editor).
This area is used to define the task (MAST or FAST) in which the channel implicit exchange objects will be exchanged.
The Local configuration checkbox is only available for the profiles FSD C8 P and FSD M8 P.
If the box is checked, the configuration and adjustment parameters are not sent to the device connected to the bus. In this case, the device starts up or initializes itself using its own parameters.
If the box is checked in the configuration screen, the channel parameters cannot be accessed from the configuration area.
The Default configuration button is used to return to the initial configuration.
In cases where the standard profile of %KW configuration words or the %MW adjustment words exist, this area displays them.
A Symbol and a Value are associated to each word.
For each value the contextual menu can be used to select the display base for the value of the selected word.
Three types are available:
Decimal,
Hexadecimal,
Binary.
35008155 12/2018
169
Standard profiles
How to Modify the Parameters of a Standard Profile
At a Glance
The following procedures are applicable for configuration or adjustment parameters.
How to Modify the Display Base
The following procedure describes how to select the display base. In the example, the chosen base is binary.
Step
1
2
Action
In the Configuration area, select the Value cell of the word to be modified.
Select Binary from the contextual menu (right-click).
Result: the cell displays 2#1011 0000 0000 0000 .
How to Enter a Value Using the Keyboard
The following procedure describes how to enter a value in a cell.
Step
1
2
Action
In the Configuration area, select the Value cell of the word to be modified.
Enter the value using the keyboard.
Note: keyboard entry depends on the display base.
170
35008155 12/2018
How to Enter a Value in Binary Format
The following procedure describes how to enter a value in binary format.
Step
1
Action
Double click on the Value cell in the Configuration area of the word to be modified.
Result: the following window appears.
Standard profiles
2
3
Select the bits to be set to 1.
Close the Properties ... window by clicking on the cross in the top right-hand corner of the window.
Result: Closing the window confirms the entered value and it is displayed in the cell format.
35008155 12/2018
171
Standard profiles
Adjustment Mode
At a Glance
Adjustment mode can be accessed from the Adjust tab. The principle is the same as for configuration mode; the adjustment words are %MW words.
There are 32 possible words for FSD and FRD profiles and 30 words for FED profiles.
Illustration p
The adjust screen for devices looks like this:
172
35008155 12/2018
Debugging the Fipio bus standard profiles Section 10.3
Debugging the Fipio bus standard profiles
Aim of this Section
This Section introduces the debugging principles Fipio bus standard profiles.
What Is in This Section?
This section contains the following topics:
Topic
Debug Screen for a Standard Profile
How to Modify the Debug Parameters for a Standard Profile
Standard profiles
Page
35008155 12/2018
173
Standard profiles
Debug Screen for a Standard Profile
At a Glance
The debug screen for a standard profile reuses the elements of the other devices available on the Fipio bus.
see page 128
However, certain elements are specific to this screen. The remainder of this document only covers the part specific to standard profiles.
Illustration
The figure below represents a debug screen.
174
35008155 12/2018
Standard profiles
Description
The following table shows the different elements of the debug screen and their functions.
Number Element
1 Tabs
2
3
4
5
Module area
Function
The tab in the foreground indicates the mode in progress (Debug in this example). Each mode can be selected using the respective tab. The available modes are:
Debug which can be accessed only in online mode,
Fault (channel level) accessible only in online mode,
Configuration,
Adjust.
Gives a reminder of the device’s shortened name.
In the same area there are 3 LEDs which indicate the module’s operating mode:
RUN indicates the operating status of the module,
ERR indicates an internal fault in the module,
I/O indicates a fault from outside the module or an application fault.
Channel area Is used:
By clicking on the reference number, to display the tabs:
Description which gives the characteristics of the device.
I/O Objects (see EcoStruxure™ Control Expert, Operating Modes) which is used to presymbolize the input/output objects,
Fault which shows the device faults (in online mode).
General parameters area
Parameters in progress area
Channel: single channel for a standard profile.
Symbol: name of the channel defined by the user (using the variable editor).
This area is used to display the type of task (MAST or FAST) in which the channel implicit exchange objects are exchanged.
In cases where for the standard profile the input bits, the %IW input words or the %QW output words exist, this area displays them.
A Reference, a Symbol and a Value are associated to each word.
For each value the contextual menu can be used to select the display base for the value of the selected word.
Three types are available:
Decimal,
Hexadecimal,
Binary.
For FRD ••• standard profile, the Error column provides direct access to the diagnostics for each channel when these are faulty (indicated by the indicator lamp built into the diagnostics access button, which turns red).
35008155 12/2018
175
Standard profiles
How to Modify the Debug Parameters for a Standard Profile
At a Glance
The following procedures are applicable for debug parameters.
How to Modify the Display Base
The following procedure describes how to select the display base. In the example, the chosen base is binary.
Step
1
2
Action
In the Parameters in progress area, select the Value cell of the word to be modified.
Select Binary from the contextual menu (right-click).
Result: the cell displays 2#1011 0000 0000 0000 .
How to Enter a Value Using the Keyboard
The following procedure describes how to enter a value in a cell using the keyboard.
Step
1
2
Action
In the Parameters in progress area, select the Value cell of the word to be modified.
Enter the value using the keyboard.
Note: keyboard entry depends on the display base.
176
35008155 12/2018
Standard profiles
How to Enter a Value in Binary Format
The following procedure describes how to enter a value in binary format. It is only valid for outputs.
Step
1
Action
Double click on the Value cell in the Parameters in progress area of the word to be modified.
Result: the following window appears.
2
3
Select the bits to be set to 1.
Close the Properties ... window by clicking on the cross in the top right-hand corner of the window.
Result: Closing the window confirms the entered value and it is displayed in the cell format.
35008155 12/2018
177
Standard profiles
Language objects associated with the Fipio bus standard profiles Section 10.4
Language objects associated with the Fipio bus standard profiles
Aim of this Section
This section introduces the language objects associated with the Fipio bus standard profiles.
What Is in This Section?
This section contains the following topics:
Topic
Details of the Language Objects for the IODDT of Type T_STDP_GEN
Objects Accessible by Standard Profiles
Implicit Exchange Language Objects
Explicit Exchange Language Objects
Language Objects Associated with Configuration
Page
178
35008155 12/2018
Standard profiles
Details of the Language Objects for the IODDT of Type T_STDP_GEN
At a Glance
The tables below present the objects for the T_STDP_GEN -type IODDT that are applicable to all
Fipio standard profiles.
Error Bit %I\2.e\0.m.c.ERR
The table below presents the error bit %I\2.e\0.m.c.ERR..
Standard Symbol
CH_ERROR
Type
BOOL
Access
R
Meaning
Channel c error bit
Address
%I\2.e\0.m.c.ERR
Execution Indicators of an Explicit Exchange: EXCH_STS
The table below presents the meanings of the exchange control bits of the channel EXCH_STS
(%MW\2.e\0.m.c.0).
Standard Symbol
STS_IN_PROGR
CMD_IN_PROGR
ADJ_IN_PROGR
RECONF_IN_PROGR
Type
BOOL
BOOL
BOOL
BOOL
Access Meaning
R
Address
Reading of channel status words in progress %MW\2.e\0.m.c.0.0
R %MW\2.e\0.m.c.0.1
R
R
Current command parameters exchange in progress
Adjustment parameters exchange in progress
Reconfiguration in progress
%MW\2.e\0.m.c.0.2
%MW\2.e\0.m.c.0.15
Explicit Exchange Report: EXCH_RPT
The table below presents the meaning of the exchange report bits EXCH_RPT (%MW\2.e\0.m.c.1).
Standard Symbol
STS_ERR
CMD_ERR
ADJ_ERR
RECONF_ERR
Type
BOOL
BOOL
BOOL
BOOL
R
R
Access
R
R
Meaning
Reading error for channel status words
Address
%MW\2.e\0.m.c.1.0
Error during command parameter exchange %MW\2.e\0.m.c.1.1
Error during adjustment parameters exchange
%MW\2.e\0.m.c.1.2
Error when configuring the channel %MW\2.e\0..m.c.1.15
35008155 12/2018
179
Standard profiles
Standard Channel Faults, CH_FLT
The following table presents the meanings of the bits of the CH_FLT status word
(%MW\2.e\0.m.c.2). The reading is performed by a READ_STS ( IODDT_VAR1 ).
Standard Symbol
INTERNAL_FLT
CONF_FLT
COM_FLT
APPLI_FLT
Type
BOOL
BOOL
BOOL
BOOL
R
R
Access
R
R
Meaning
Internal error or channel self-testing
Hardware or software configuration error
Bus communication fault
Application fault (adjustment or configuration error)
Address
%MW\2.e\0.m.c.2.4
%MW\2.e\0.m.c.2.5
%MW\2.e\0.m.c.2.6
%MW\2.e\0.m.c.2.7
180
35008155 12/2018
Standard profiles
Objects Accessible by Standard Profiles
At a Glance
The following tables list the language objects associated with each profile in the Control Expert catalog.
FRD Profile
The following table relates to FRD profiles
Acquisition of inputs
Output command
Configuration words
FRD C2
-
%I\2.e\0.0.0 to
%I\2.e\0.0.31
%Q\2.e\0.0.0 to
%Q\2.e\0.0.31
Status: exchange management
Exchange report
%MW\2.e\0.0.c.0
%MW\2.e\0.0.c.1
Status: standard to channel %MW\2.e\0.0.c.2
Input validity
Status: specific to channel
Command words
Adjustment words
-
-
-
%MW\2.e\0.0.c.3
FRD C2 P
%I\2.e\0.0.0 to
%I\2.e\0.0.31
%Q\2.e\0.0.0 to
%Q\2.e\0.0.31
%KW\2.e\0.0.c.0 to
%KW\2.e\0.0.c.15
%MW\2.e\0.0.c.0
%MW\2.e\0.0.c.1
%MW\2.e\0.0.c.2
-
%MW\2.e\0.0.c.3
-
%MW\2.e\0.0.c.4 to
%MW\2.e\0.0.c.35
Standard profiles only have channel 0 (c =0).
FSD Profile
The following table relates to FSD profiles
Acquisition of inputs
Output command
Configuration words
FSD C/M8
%IW\2.e\0.0.0 to
%IW\2.e\0.0.7
-
%QW\2.e\0.0.0 to
%QW\2.e\0.0.7
%MW\2.e\0.0.c.0
Status: exchange management
35008155 12/2018
FSD C/M8 P
%IW\2.e\0.0.0 to
%IW\2.e\0.0.7
%QW\2.e\0.0.0 to
%QW\2.e\0.0.7
%KW\2.e\0.0.c.0 to
%KW\2.e\0.0.c.15
%MW\2.e\0.0.c.0
181
Standard profiles
FSD C/M8
Exchange report %MW\2.e\0.0.c.1
Status: standard to channel %MW\2.e\0.0.c.2
Input validity
Status: specific to channel
Command words
Adjustment words
-
-
-
%MW\2.e\0.0.c.3
Standard profiles only have channel 0 (c =0).
FED profile
The following table relates to FED profiles
Acquisition of inputs
Output command
Configuration words
FED C/M32
-
%IW\2.e\0.0.0 to
%IW\2.e\0.0.31
%QW\2.e\0.0.0 to
%QW\2.e\0.0.31
Status: exchange management
%MW\2.e\0.0.c.0
Exchange report %MW\2.e\0.0.c.1
Status: standard to channel %MW\2.e\0.0.c.2
Input validity
Status: specific to channel
Command words
Adjustment words
%MW\2.e\0.0.c.3
%MW\2.e\0.0.c.4 to
%MW\2.e\0.0.c.11
-
%MW\2.e\0.0.c.12 to
%MW\2.e\0.0.c.19
Standard profiles only have channel 0 (c =0).
FSD C/M8 P
%MW\2.e\0.0.c.1
%MW\2.e\0.0.c.2
-
%MW\2.e\0.0.c.3
-
%MW\2.e\0.0.c.4 to
%MW\2.e\0.0.c.35
FED C/M32 P
%IW\2.e\0.0.0 to
%IW\2.e\0.0.31
%QW\2.e\0.0.0 to
%QW\2.e\0.0.31
%KW\2.e\0.0.c.0 to
%KW\2.e\0.0.c.29
%MW\2.e\0.0.c.0
%MW\2.e\0.0.c.1
%MW\2.e\0.0.c.2
%MW\2.e\0.0.c.3
%MW\2.e\0.0.c.4 to
%MW\2.e\0.0.c.11
%MW\2.e\0.0.c.12 to
%MW\2.e\0.0.c.19
%MW\2.e\0.0.c.20 to
%MW\2.e\0.0.c.49
182
35008155 12/2018
Standard profiles
Implicit Exchange Language Objects
At a Glance
This page describes all the implicit exchange language objects associated with standard profiles for Fipio communication that can be displayed or modified by the application program.
Bit Objects
The table below shows the different bit objects for implicit exchange.
Object (1) Function
%I\2.e\0.0.MOD.ERR
Module error bit
%I\2.e\0.m.c.ERR
Channel error bit
Bit exchange
Meaning
This bit set to 1 indicates a module error (at least one of the channels has an error, for instance)
This bit set to 1 indicates that a channel is faulty.
Acquisition of input bits for FRD profiles %I\2.e\0.0.0 to
%I\2.e\0.0.31
%Q\2.e\0.0.0 to
%Q\2.e\0.0.31
Bit exchange Acquisition of output bits for FRD profiles
Word Objects
The following table shows the various implicit exchange word objects.
Object (1)
%IW\2.e\0.0.0.0 to
%IW\2.e\0.0.0.7
%QW\2.e\0.0.0.0 to
%QW\2.e\0.0.0.7
%IW\2.e\0.0.0.0 to
%IW\2.e\0.0.0.31
%QW\2.e\0.0.0.0 to
%QW\2.e\0.0.0.31
Function Meaning
FSD word exchange Acquisition of input words for FSD profiles
FSD word exchange Acquisition of output words for FSD profiles
FED word exchange Acquisition of input words for FED profiles
FED word exchange Acquisition of output words for FED profiles
35008155 12/2018
183
Standard profiles
Explicit Exchange Language Objects
At a Glance
This page describes all the explicit exchange language objects associated with standard profiles for Fipio communication that can be displayed or modified by the application program.
Word Objects Common to All Profiles
The table below shows the different explicit exchange word objects.
Object Function
%MW\2.e\0.0.MOD.2
Module status
%MW\2.e\0.0.c.2
%MW\2.e\0.0.c.3
Base module channel status
Input validity
Meaning
Least significant byte: corresponds to the base.
bit 0 = 1: internal fault
bit 1 = 1: functional fault bit 2 = 1: terminal block fault bit 3 = 1: base module in self-test phase bit 4 = 1: reserved (= 0)
bit 5 = 1: configuration error bit 6 = 1: module missing bit 7 = 1: extension module fault
Most significant byte: corresponds to the extension.
bit 8 = 1: internal fault
bit 9 = 1: functional fault bit 10 = 1: terminal block fault
bit 11 = 1: extension module in self-test phase bit 12 = 1: reserved (= 0) bit 13 = 1: configuration error bit 14 = 1: module missing bit 15 = 1: reserved (= 0)
Least significant byte: corresponding to the base
bit 0 = 1: external fault 4
bit 1 = 1: external fault 3 bit 2 = 1: external fault 2 bit 3 = 1: external fault 1 bit 4 = 1: internal fault bit 5 = 1: hardware configuration fault
bit 6 = 1: communication fault bit 7 = 1: application fault
For FRD, FSD and FED profiles, the least significant byte is specific to the connected device.
Refer to the device documentation.
NOTE: For each connected device, please refer to the corresponding documentation for details of the application-specific status words.
184
35008155 12/2018
Internal Words for FRD and FSD Profiles
The following table describes the internal words specific to FRD and FSD profiles:
Object
%MW\2.e\0.0.c.4
to
%MW\2.e\0.0.c.35
Function
Adjustment parameters
Meaning
32 specific adjustment words.
Parameters accessible in read and write using the
WRITE_PARAM , READ_PARAM , SAVE_PARAM , and
RESTORE_PARAM functions.
Standard profiles
Internal Words for FED Profiles
The following table describes the internal words specific to FED profiles:
Object
%MW\2.e\0.0.c.4
to
%MW\2.e\0.0.c.11
%MW\2.e\0.0.c.12
to
%MW\2.e\0.0.c.19
%MW\2.e\0.0.c.20
to
%MW\2.e\0.0.c.49
Function Meaning
Specific status 8 specific status words.
Parameters accessible in read using the
READ_STATUS function.
Specific channel level command
Adjustment parameters
32 specific command words.
Parameters accessible in write using the WRITE_CMD function.
32 specific adjustment words.
Parameters accessible in read and write using the
WRITE_PARAM , READ_PARAM , SAVE_PARAM , and
RESTORE_PARAM functions.
35008155 12/2018
185
Standard profiles
Language Objects Associated with Configuration
At a Glance
This page describes the configuration words associated with devices used for Fipio communication.
Internal Constants
The following table describes the internal constants:
Object
%KW\2.e\0.0.0.0 to
%KW\2.e\0.0.0.15
%KW\2.e\0.0.0.0 to
%KW\2.e\0.0.0.29
Function
Channel level configuration words
Channel level configuration words
Meaning
Contain the parameters of channels defined using the configuration editor for FRD and FSD profiles.
Contain the parameters of channels defined using the configuration editor for FED profiles.
186
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Fipio Agent
35008155 12/2018
Fipio Agent Chapter 11
Fipio Agent
Subject of this Chapter
This Chapter introduces the Agent devices on the Fipio bus and its services.
What Is in This Chapter?
This chapter contains the following sections:
Section
11.1
11.2
11.3
11.4
Topic
Introduction to Fipio Agents
Configuration of Fipio Agents
Debugging Fipio Agents
Language objects associated with the Fipio Agents
Page
35008155 12/2018
187
Fipio Agent
Introduction to Fipio Agents Section 11.1
Introduction to Fipio Agents
Aim of this Section
This section provides a summary description of the agents on the Fipio bus and their associated services.
What Is in This Section?
This section contains the following topics:
Topic
Fipio Agent: General
Periodic Data Exchange
Special Cases
Communication from a Fipio Agent
Page
188
35008155 12/2018
Fipio Agent
Fipio Agent: General
At a Glance
Micro or Premium PLCs, equipped with a TSX FPP 10 PCMCIA card on their built-in communication channel act as agents on the Fipio bus.
The Fipio Agent function can be used for two types of data exchange:
periodic exchanges of information with the manager (of shared variable type), aperiodic message exchanges with the manager or with other agents.
NOTE: This function is available with version V1.9 or later of the TSX FPP 10 card.
NOTE: The periodic cycle time of Fipio agents must be at least 5ms but the value depends on the configuration.
35008155 12/2018
189
Fipio Agent
Periodic Data Exchange
At a Glance
Each Fipio Agent PLC uses 64 consecutive %MW words to exchange periodic data.
The first 32 words are reserved for sending the information to the manager.
The next 32 words are reserved for receiving information.
NOTE: The %MW status words and the %MW command words are not significant.
View of Exchanges
The following diagram shows the exchanges between a Fipio Agent and a Premium manager.
190
35008155 12/2018
Fipio Agent
Special Cases
At a Glance
A Premium PLC declared as a Fipio Agent can communicate with a TSX 47-107 or APRIL 5000 manager.
When used in this way, the Fipio Agent is declared on the bus as a standard profile at the connection point.
The standard profile to be declared is as follows:
Device family: STD_P.
Base: FED M32.
Communicator: TSX FPP 10.
Exchanges with a TSX 47-107
The following diagram shows the exchanges between a Fipio Agent and a TSX 47-107 manager.
35008155 12/2018
191
Fipio Agent
Communication from a Fipio Agent
At a Glance
A PLC declared as a Fipio Agent can communicate:
with the bus manager server, with the server of another Fipio Agent.
Address Settings
The syntax of an address is as follows:
ADDR('\2.4\SYS')
The following table describes the address parameters:
Parameter
2.4
SYS
Description
2 : corresponds to the Fipio bus number
4 : corresponds to the destination connection point
Corresponds to the server address.
192
35008155 12/2018
Example
Example of How Different PLCs Access the System
Fipio Agent
The Fipio Agent PLC at address 1 reads 10 words from the Fipio Agent at address 4.
READ_VAR(ADDR('\2.4\SYS'), '%MW',0,10, %MW100:4,%MW10:10)
35008155 12/2018
193
Fipio Agent
Configuration of Fipio Agents Section 11.2
Configuration of Fipio Agents
Aim of this Section
This Section introduces the configuration principles for Fipio Agents.
What Is in This Section?
This section contains the following topics:
Topic
How to Fipio Agent Parameters Using PCMCIA Cards
Configuration Screen of a Fipio Agent
Page
194
35008155 12/2018
Fipio Agent
How to Fipio Agent Parameters Using PCMCIA Cards
At a Glance
The creation of a project implementing Fipio Agents requires you to configure the communication channel of the PLC declared as a Fipio Agent.
This part describes how to access the configuration parameters of the Fipio Agent link using the
TSX FPP 10 PCMCIA card for Micro/Premium PLCs.
How to Declare the Fipio PCMCIA Card
The following table shows the procedure for physically declaring the Fipio PCMCIA card on the
PLC:
Step
1
2
Action
Open the hardware configuration editor.
Double-click the PCMCIA communication card slot (bottom slot).
Result: The card type selection window appears
3 Expand the Communication line by clicking on the + sign.
Result:
35008155 12/2018
4 Select the TSX FPP 10 Fipio card and then confirm with OK.
Result: the hardware configuration editor is displayed with the configured card.
195
Fipio Agent
Step
5
Action
Double click on the processor's PCMCIA communication card.
Result:
196
6 Select the channel and choose the Fipio AGENT function.
Result:
35008155 12/2018
Fipio Agent
Configuration Screen of a Fipio Agent
At a Glance
This screen, separated into two areas, is used to declare the communication channel and to configure the necessary parameters for a Fipio Agent link.
Illustration
The following figure shows an example of a Fipio Agent configuration screen.
35008155 12/2018
197
Fipio Agent
Description
The following table shows the various elements of the configuration screen and their functions.
2
3
Number Element
1 Tabs
4
5
General parameters area
Configuration area
Function
The tab in the foreground indicates the mode in progress
(Configuration in this example). Every mode can be selected using the respective tab. The available modes are:
Configuration,
Debug which can be accessed only in online mode.
Fault (channel level) accessible only in online mode.
Module area Gives a reminder of the device’s shortened name.
Channel area Is used:
By clicking on the device reference number, to display the tabs:
Description which gives the characteristics of the device.
I/O Objects (see EcoStruxure™ Control Expert, Operating
Modes) which is used to presymbolize the input/output objects.
Fault which shows the device faults (in online mode).
By clicking on the Channel, to select the channel to be debugged. To the left of the symbol there is a copy of the CHx channel LED.
This area displays the task (MAST or FAST) in which the channel's implicit exchange objects will be exchanged.
The function menu is used to select the Fipio Agent function.
None is selected by default.
Used to select and enter the following parameters:
the address of the connection point on the Fipio bus,
the address of the start of the table.
Table Start Address
This parameter indicates the table address to be reserved for periodic data exchanges between the bus manager and the Fipio Agent.
The table contains 64 words:
32 words for the inputs (%IW\2.e\0.0.1.d),
32 words for the outputs (%QW\2.e\0.0.1.d).
198
35008155 12/2018
Debugging Fipio Agents Section 11.3
Debugging Fipio Agents
Debug Screen of a Fipio Agent
At a Glance
This screen, separated into two areas, allows you to debug a Fipio Agent.
Illustration
The figure below represents a debug screen.
Fipio Agent
35008155 12/2018
199
Fipio Agent
Description
The following table shows the different elements of the debug screen and their functions.
2
3
Number
1
4
5
Element
Tabs
Module area Gives a reminder of the device’s shortened name.
Channel area Is used:
By clicking on the device reference number, to display the tabs:
Description which gives the characteristics of the device.
I/O Objects (see EcoStruxure™ Control Expert, Operating
Modes) which is used to presymbolize the input/output objects.
Fault which shows the device faults (in online mode).
General parameters area
Debug area
Function
The tab in the foreground indicates the mode in progress (Debug in this example). Each mode can be selected using the respective tab. The available modes are:
Debug which can be accessed only in online mode.
Fault (channel level) accessible only in online mode,
Configuration.
By clicking on the Channel, to select the channel to be debugged. To the left of the symbol there is a copy of the CHx channel LED.
This area displays the task (MAST or FAST) in which the channel's implicit exchange objects will be exchanged.
Gives access to the debug parameters of a Fipio Agent.
No data can be accessed from this screen.
200
35008155 12/2018
Fipio Agent
Language objects associated with the Fipio Agents Section 11.4
Language objects associated with the Fipio Agents
Aim of this Section
This Section introduces the language objects associated with Fipio Agents.
What Is in This Section?
This section contains the following topics:
Topic
Implicit Exchange Language Objects
Explicit Exchange Language Objects
Explicit Exchange Management and Report
Language Objects Associated with Configuration
Page
35008155 12/2018
201
Fipio Agent
Implicit Exchange Language Objects
At a Glance
This page describes all the implicit exchange language objects associated with agent for Fipio communication that can be displayed or modified by the agent application program.
Bit Objects
The table below shows the different bit objects for implicit exchange.
Object (1)
%I\2.e\0.0.1.ERR
Function
%I\2.e\0.0.MOD.ERR Module error bit
Meaning
This bit set to 1 indicates a module error (at least one of the channels has an error, for instance)
Channel error bit This bit set to 1 indicates a line fault.
Word Objects
The table below shows the various implicit exchange word objects.
Object (1)
%IW\2.e\0.0.1.0
Function
Agent function
Status
Strategy to apply to outputs
Meaning
Byte 0:
= 16#01: IDLE Function
= 16#02: RUN Function
= 16#03: STOP Function
Byte 1:
= 16#01: security
= 16#02: valid %MW value
= 16#03: fallback
Key
(1) Address 2.e\0.m.c.d
2: corresponds to the bus number
e: corresponds to the connection point number
0: corresponds to the (virtual) rack number
0: corresponds to the module position number
1: corresponds to the channel number d: corresponds to the channel data
202
35008155 12/2018
Fipio Agent
Explicit Exchange Language Objects
At a Glance
This page describes all the explicit exchange language objects associated with agent for Fipio communication that can be displayed or modified by the agent application program.
Word Objects
The table below shows the different explicit exchange word objects.
Object (1)
%MW\2.e\0.m.c.2
Function
%MW\2.e\0.m.MOD.2 Module status
Channel standard status
Meaning bit 0 = 1: defective module bit 1 = 1: functional error (error between the processor and the module, adjustment or configuration error, etc.) bit 2 = 1: terminal block fault (not connected) bit 3 = 1: self-tests running bit 4 = 1: reserved bit 5 = 1: error in hardware or software configuration (the module present is not that declared in the configuration, the sub-modules are not compatible) bit 6 = 1: module missing bit 7 = 1: error in one of the sub-modules
Byte 0:
bit 0 = 1: the inputs words are not valid if the manager is in
RUN bit 1 = 1: the output words are not valid if the agent is in
RUN bit 4 = 1: internal fault on the TSX FPP 10 card or card not
yet started by the manager bit 5 = 1: configuration fault (the configured module is different from the one connected) bit 6 = 1: Fipio communication fault bit 7 = 1: application fault (%MW table overflow)
Byte 1: reserved
Key
(1) Address 2.e\0.m.c.d
2 : corresponds to the bus number
e: corresponds to the connection point number
0 : corresponds to the (virtual) rack number m: corresponds to the module position number c: corresponds to the channel number d: corresponds to the channel data
35008155 12/2018
203
Fipio Agent
Explicit Exchange Management and Report
At a Glance
This page describes all language objects which manage explicit exchanges.
Word objects
The table below shows the different word objects for the management of explicit exchanges.
Object (1) Function
%MW\2.e\0.m.MOD.0 Module exchanges in progress
%MW\2.e\0.m.MOD.1 Module report
%MW\2.e\0.m.c.0
%MW\2.e\0.m.c.1
Channel exchanges in progress
Channel report
Meaning
bit 0 = 1: status reading in progress bit 1 = 1: sending of command parameters to the communication module bit 2 = 1: sending of adjustment parameters to the communication module
bit 1 = 0: command parameters received and accepted by the module bit 2 = 0: adjustment parameters received and accepted by the module bit 0 = 1: status reading in progress bit 1 = 1: sending of command parameters to the communication channel bit 2 = 1: sending of adjustment parameters to the communication channel bit 1 = 0: command parameters received and accepted by the communication channel bit 2 = 0: adjustment parameters received and accepted by the communication channel
Key
(1) Address 2.e\0.m.c.d
2 : corresponds to the bus number
e: corresponds to the connection point number
0 : corresponds to the (virtual) rack number m: corresponds to the module position number c: corresponds to the channel number d: corresponds to the channel data
204
35008155 12/2018
Fipio Agent
Language Objects Associated with Configuration
At a Glance
This page describes all configuration language objects associated with Fipio communication agents which can be displayed by the agent application program.
Internal Constants
The following table describes the internal constants:
Object Function
%KW\2.e\0.m.c.0
Type
%KW\2.e\0.m.c.1
Reserved
%KW\2.e\0.m.c.2
Connection point address
%KW\2.e\0.m.c.3
Table start address
Meaning
Byte 0 = 16#09: for the Fipio Agent function
-
Byte 0 = 16#01 to 16#7F: corresponds to addresses
1 to 127
Byte 0: Least significant byte of address
Byte 1: Most significant byte of address
35008155 12/2018
205
Fipio Agent
206
35008155 12/2018
Premium and Atrium Using EcoStruxure™ Control Expert
Index
35008155 12/2018
Index
0-9
A
adjusting,
C
channel data structure for all modules
T_GEN_MOD,
configuring,
configuring Fipio Agent,
configuring standard profiles,
Connecting
TSXFPP10,
channel data structure for Fipio devices
D
Debug screen
Access,
debugging Fipio Agent,
Description
F
Fipio management,
35008155 12/2018
P
standard profiles,
S
T
T_STDP_GEN,
TBXBLP01,
TBXBLP10, topologie
IP65,
IP67, topologies
IP20,
TSXEFACC99,
TSXFPACC10,
TSXFPACC12,
TSXFPACC14,
TSXFPC10,
207
Index
TSXFPCAx00,
TSXFPCCx00,
TSXFPCE030,
consumption,
X
208
35008155 12/2018
다운로드
공개 링크 업데이트됨
문서 공개 링크
광고
