没有合适的资源?快使用搜索试试~ 我知道了~
109747503_Library_Guideline_DOC_v10_en.pdf
需积分: 5 0 下载量 38 浏览量
2024-04-20
23:44:24
上传
评论
收藏 3.63MB PDF 举报
温馨提示
试读
79页
109747503_Library_Guideline_DOC_v10_en
资源推荐
资源详情
资源评论
Warranty and Liability
Guideline for library handling in TIA Portal
Entry ID: 109747503, V1.0, 11/2017
2
Siemens AG 2017 All rights reserved
Warranty and Liability
Note
The Application Examples are not binding and do not claim to be complete regarding the
circuits shown, equipping and any eventuality. The Application Examples do not represent
customer-specific solutions. They are only intended to provide support for typical
applications. You are responsible for ensuring that the described products are used
correctly. These Application Examples do not relieve you of the responsibility to use safe
practices in application, installation, operation and maintenance. When using these
Application Examples, you recognize that we cannot be made liable for any
damage/claims beyond the liability clause described. We reserve the right to make
changes to these Application Examples at any time without prior notice.
If there are any deviations between the recommendations provided in these Application
Examples and other Siemens publications – e.g. Catalogs – the contents of the other
documents have priority.
We do not accept any liability for the information contained in this document.
Any claims against us – based on whatever legal reason – resulting from the use of
the examples, information, programs, engineering and performance data etc.,
described in this Application Example shall be excluded. Such an exclusion shall
not apply in the case of mandatory liability, e.g. under the German Product Liability
Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life,
body or health, guarantee for the quality of a product, fraudulent concealment of a
deficiency or breach of a condition which goes to the root of the contract
(“wesentliche Vertragspflichten”). The damages for a breach of a substantial
contractual obligation are, however, limited to the foreseeable damage, typical for
the type of contract, except in the event of intent or gross negligence or injury to
life, body or health. The above provisions do not imply a change of the burden of
proof to your detriment.
Any form of duplication or distribution of these Application Examples or excerpts
hereof is prohibited without the expressed consent of the Siemens AG.
Security
informa-
tion
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is
necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial
security concept. Siemens’ products and solutions only form one element of such a
concept.
Customer is responsible to prevent unauthorized access to its plants, systems, machines
and networks. Systems, machines and components should only be connected to the
enterprise network or the internet if and to the extent necessary and with appropriate
security measures (e.g. use of firewalls and network segmentation) in place.
Additionally, Siemens’ guidance on appropriate security measures should be taken into
account. For more information about industrial security, please visit
http://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more
secure. Siemens strongly recommends to apply product updates as soon as available and
to always use the latest product versions. Use of product versions that are no longer
supported, and failure to apply latest updates may increase customer’s exposure to cyber
threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security
RSS Feed under http://www.siemens.com/industrialsecurity.
Table of Contents
Guideline for library handling in TIA Portal
Entry ID: 109747503, V1.0, 11/2017
3
Siemens AG 2017 All rights reserved
Table of Contents
Warranty and Liability ................................................................................................. 2
1 Introduction ........................................................................................................ 5
1.1 The type instance concept ................................................................... 5
1.1.1 Objective of the guideline ..................................................................... 5
1.1.2 Advantages of type instance concept .................................................. 5
1.1.3 Using the type instance concept .......................................................... 5
1.1.4 Topics not covered by this guideline .................................................... 6
1.2 Libraries and library elements in TIA Portal ......................................... 7
1.3 Handling of types and master copies ................................................... 8
1.3.1 Storing blocks as master copies in the project library .......................... 8
1.3.2 Adding blocks as master copy in the project ........................................ 9
1.3.3 Storing block as type in the project library ......................................... 10
1.3.4 Using typified blocks in project ........................................................... 11
1.3.5 Copying blocks as master copy/copying type in global library ........... 11
1.3.6 Editing type ......................................................................................... 12
1.3.7 Other basics ....................................................................................... 13
1.4 Central storage for global libraries ..................................................... 13
2 Creating a Corporate Library .......................................................................... 14
2.1 Programming guideline ...................................................................... 14
2.2 Workflow ............................................................................................. 14
2.3 "Creation/maintenance" process ........................................................ 15
2.3.1 "Integrator" role .................................................................................. 15
2.3.2 "Developer" role ................................................................................. 15
2.3.3 "Integrator project" (area of responsibility of integrator) ..................... 16
2.3.4 "Development library" (area of responsibility of integrator) ................ 16
2.3.5 "Developer project(s)" (area of responsibility of developer) ............... 16
2.3.6 "Transfer library/ies" (area of responsibility of developer) ................. 16
2.3.7 "Creation/maintenance" development cycle ....................................... 17
2.4 "Publication" process .......................................................................... 19
2.4.1 "Integrator" role .................................................................................. 19
2.4.2 Corporate library (area of responsibility of integrator) ........................ 19
2.5 "Application” process .......................................................................... 21
2.5.1 "User" role .......................................................................................... 21
2.5.2 Plant projects (area of responsibility of user) ..................................... 21
3 Application Cases in TIA Portal for the "Integrator" .................................... 22
3.1 Working with the "integrator project" .................................................. 22
3.1.1 Adding new library elements in the "integration project" from
"transfer libraries" ............................................................................... 22
3.1.2 Updating existing library elements in the "integrator project"
from the "transfer libraries" ................................................................. 26
3.1.3 Tips on structuring the container FBs ................................................ 31
3.2 Working with the global "development library" ................................... 32
3.2.1 Creating the global "development library" .......................................... 32
3.2.2 Updating blocks from the "integrator project" in the global
"development library" ......................................................................... 33
3.2.3 Deleting older type versions in the global "development library" ....... 34
3.3 Working with the global "corporate library" ........................................ 36
3.3.1 Creating and releasing the global "corporate library" ......................... 36
4 Application Cases in TIA Portal for the "Developer" ................................... 38
Table of Contents
Guideline for library handling in TIA Portal
Entry ID: 109747503, V1.0, 11/2017
4
Siemens AG 2017 All rights reserved
4.1 Working with the "developer project" ................................................. 38
4.1.1 Test environment in the "developer project" ...................................... 38
4.1.2 Updating the "developer project" using the global "development
library" ................................................................................................ 39
4.1.3 Creating new typified elements .......................................................... 45
4.1.4 Editing of typified elements ................................................................ 48
4.2 Working with the global "transfer library" ........................................... 50
4.2.1 Creating a global "transfer library" ..................................................... 50
4.2.2 Copying typified elements in global "transfer library" ......................... 50
5 Application Cases in TIA Portal for the "User" ............................................ 52
5.1 Working with the "plant project" ......................................................... 52
5.1.1 Opening archived global "corporate library" ....................................... 52
5.1.2 Adding typified library elements in "plant project" .............................. 53
5.1.3 Updating selected types in the "plant project" .................................... 54
5.1.4 Updating all types in the "plant project" .............................................. 56
6 Creating Individual Libraries .......................................................................... 58
7 Troubleshooting .............................................................................................. 60
7.1 Finding solutions for conflicts with same versions ............................. 60
7.2 Closing several versions .................................................................... 62
7.3 Accidental assignment of a later version ............................................ 66
7.4 Accidental separation of an instance from type ................................. 67
7.5 Accidental deleting of a type instance ................................................ 67
7.6 Deleted types in global libraries are not deleted from the project ...... 67
8 Valuable Information / Basics ........................................................................ 68
8.1 Terms ................................................................................................. 68
8.2 Overview of all library elements ......................................................... 69
8.3 Differences of the types for PLC and HMI .......................................... 69
8.4 Displaying type information in the project navigation ......................... 70
8.5 Library view and library management ................................................ 72
8.5.1 Overview............................................................................................. 72
8.5.2 Filter dialog in the library management .............................................. 72
8.5.3 Harmonizing project and libraries ....................................................... 74
8.6 Version numbers ................................................................................ 76
8.7 Know-how protection .......................................................................... 76
8.8 Write protection .................................................................................. 77
9 Annex ................................................................................................................ 78
9.1 Service and support ........................................................................... 78
9.2 Links and literature ............................................................................. 79
9.3 Change documentation ...................................................................... 79
1 Introduction
Guideline for library handling in TIA Portal
Entry ID: 109747503, V1.0, 11/2017
5
Siemens AG 2017 All rights reserved
1 Introduction
1.1 The type instance concept
1.1.1 Objective of the guideline
This guideline describes the creation of a corporate library by using typified library
elements in TIA Portal.
You have the option to create types or master copies of TIA Portal elements (e.g.
function blocks) (see Figure 1-1: Typification with user libraries).
By using types, they are “instanced” in the project All type instances have a fixed
connection to your type in the library. This is how you can control the version of the
library elements and make changes centrally that are then updated in the complete
project in a system-supported way.
Master copies are independent copies of TIA Portal elements. They have no
connection to your places of use in the project and no option to control the version
in a system-supported way or any central changeability.
Your decision should always be based on these differences, whether you want to
create type or master copies in the libraries.
Figure 1-1: Typification with user libraries
LibraryProject
type V1
type V2
type instance V2
type instance V2
type instance V2
central update
to newer version
master copy
update
use
use
use
without typification
with typification
1.1.2 Advantages of type instance concept
Based on the following advantages, this guideline recommends the use of types:
Central update function of all instances in the project
Central display of the places of use of the types
System-supported version management of library elements
System-supported change tracking of library elements
Consistent library elements for several users
Typified elements (type instances) are especially highlighted in the project
1.1.3 Using the type instance concept
In order to make optimum use of the advantages of the type instance concept,
there needs to be a defined workflow. The optimum workflow is described in
chapter 2 Creating a Corporate Library.
剩余78页未读,继续阅读
资源评论
工控搬砖人
- 粉丝: 487
- 资源: 197
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- 海信智能电视刷机数据 LED42K330X3D(0000) 生产用软件数据 务必确认机编一致 强制刷机 整机USB升级程序
- shujudaochuceshi
- learn-ruby.zip
- test111111111111111111
- face-detect.ipynb
- 以下是一些关于ACM(国际大学生程序设计竞赛)、NOI(全国青少年信息学奥林匹克竞赛)以及CSP(全国青少年信息学奥林匹克竞赛提
- 是一些电子设计竞赛(电赛)经验分享,包括备赛策略、项目管理、团队合作和比赛期间的注意事项
- 全能运行库修复工具DirectX Repair v4.1.0.30770
- las格式点云数据使用详解(附VS编译好的LAStools工具)
- KRPano插件一键解密大师1.4.0 (解压密码1234)
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功