1/4/2016 1:01 PM | |
Joined: 3/14/2008 Last visit: 9/20/2024 Posts: 2095 Rating: (936) |
Hello, Using custom DB's with PCS7 is generally not done.. A better and nicer way to do this is using SCL. In SCL you can create inputs with s7_m_c attribute. In that case, when you insert the block and compile to OS, the input is transferred to the OS and thus can be monitored in SCADA. You have a high level of flexibility with SCL...You can create a SCL block per equipment module or per unit, so the digital signals are grouped together. Or you can create a few SCL blocks with 50 inputs for example. P.S. When you assign the attribute: S7_archive, you can even make them show up in PCS7 taglogging. |
Last edited by: Oreca at: 1/4/2016 1:05:09 PMIf I could help you, you can use the RATE button. Thank you. |
|
1/8/2016 8:11 AM | |
Joined: 3/14/2008 Last visit: 9/20/2024 Posts: 2095 Rating: (936) |
Hi, Well, SCL is used as standard "language" to create your own custom blocks in PCS7. But OK, you say you don't use monitoring blocks. Do you mean you are not using the block icons on SCADA? In that case, I suggest you use digital monitoring blocks in your CFC, but disable the creation of a block icon. Just go to the block properties and deselect: "Create block icon". The option: "OCM possible" must be selected. What happens now is that the block parameters are mapped in SCADA during OS compilation and just like you want, but no block icon will be generated. |
Last edited by: Oreca at: 1/8/2016 8:12:31 AMIf I could help you, you can use the RATE button. Thank you. |
|
1/8/2016 11:16 PM | |
Joined: 6/23/2008 Last visit: 9/18/2024 Posts: 1168 Rating: (282)
|
Hello AkshayKumar1989, In your case I would activate the 'create block icon option' in the blocks again but create your own block icon. When you use the block icons, it is not only for generating them. It's also for update them in case of changes. So yes, of course it is possible to mantain an object in a template and update all excisiting ones automatically. How you can create your own template for block icons I roughly explained here. There is also a link to a documentation included in that thread. Best regards... |
"Expert" does not necessarily mean Siemens employee. Please cross-check your requirements always with official Siemens documentation. Also "Experts" are pleased about feedback. Please don't send support requests as PM. Questioners who don't follow up their thread will be put to my list of users to be ignored. |
|
This contribution was helpful to2 thankful Users |
1/9/2016 9:36 PM | |
Joined: 6/23/2008 Last visit: 9/18/2024 Posts: 1168 Rating: (282)
|
Hello AkshayKumar1989, Sorry, but explaining the full context of creating customized objects goes beyond the scope what I could do for you here in the forum. But I can give you a suggestion wich documention to read (and specific chapter) because I can imagin that it is sometimes not so easy to find the relevant information when people don't know what exactly to search for. Additionally I will give you some hints. 1.) The property 'Type' of an customized object is very importand. This property is assigning the structure type (not the instance). In e.g. you must give here the value 'MonDiL' at your template object if an object of structure type 'MonDiL' later should be generated/or you want to create an instance by copying to a user picture and using a wizard to connect it to an instance. 2.) If you wan't to generate/update block icons by OS-Compilation the value for 'Type' must have the prefix '@'. 3.) The part behind the character '/' determines the variant. If you have more than one variant of block icons for same structure type you can decide wich one should be generated. In e.g. you have two block icons in your template file (@PCS7TypicalsXyz.pdl) for the structure type MonDiL. First one has @MonDiL/101 and second one has @MonDiL/102 as value for the attribute type. By typing the number in the field (below checkbox 'Create block icon') of the properties of the block in CFC you decide wich variant will be generated. In e.g. if you put '102' the second variant will be generated. If the checkbox is set but no number is given at the block in CFC, always the one with the lowest number (or character) in the template file will be generated. You see that in CFC only the number must be given (without @MonDiL/). This is because the structure type in CFC is known. If there is no object in your template file with an matching structure type in the attribute 'Type', nothing will be generated for this block, even not if the checkbox is set. So you could create your own costomized object. Either for an existing block type in CFC (in e.g. MonDiL) or for your own block. As soon you have given your own block the atrribute 'S7_m_c' and your block has at least one parameter (e.g input/output) with the atrribute 'S7_m_c', a structure type for this block will be created during OS-Compilation. The only thing you need to do (for this specific demand) is; create a property 'type' in your block icon and assign the value like explained in hint 1-3. One way to do this is to add a simple text field to your customized object, assign the property 'text' to the interface of your customized object and name it 'Type'. You must know that each property has to names. One for the property dialog at the object properties (property name,language dependend) and one for using in functions (attribute name, language independent). So for property name give 'Type' and for attribute name give 'type'. This text field doesn't need to be visible in runtime, also you could make it tiny and hide it behind visible objects. The more fashioned way nowadays would be to use an object of type 'DataSet' for this job, but to explain that oject would go to far here and a text field is also ok. More detailed information on 'how to create customized objects' you can find here. If not opening automatically the chapter "Working with Customized Objects" please go manually to this chapter.
You could add an object of type 'Status Display' to your customized object. In the configuration dialog of this object you assign your emf files for the two states of your binary tag. You leave the field 'Tag' empty. You add the object to your customized object and you add the property 'State' to the interface of your object. You give the tag in the proberties of your block icons property 'State' then. Like for all the other tag connections you don't give the part before the '.' wich specifies the instance. The instance and hence the part before the '.' will be added automatically when creating the instance during OS-Compilation.
Yes, a minimum block icon for automatically generation/update for your demend could consist of an 'Status Display' (for display of the states by emf files) and a 'Text Field' (for the attribute/property 'type'). But honestly said, I would use the block MonDiL (or MonDiS) in CFC and modify an existing block icon (after copying in my own template) by adding the status display. Then I would move everything I actually don't want to see behind the new status display. Maybe you will recognize later that you need somthing of the original object again (in e.g. the group display for showing an alarm). Btw... It took me some time to collect this information for you and write it down.... would be nice if you have a 'Rate' for me Regards... |
Last edited by: mark1507 at: 1/10/2016 12:04:44 AM"Expert" does not necessarily mean Siemens employee. Please cross-check your requirements always with official Siemens documentation. Also "Experts" are pleased about feedback. Please don't send support requests as PM. Questioners who don't follow up their thread will be put to my list of users to be ignored. |
|
This contribution was helpful to4 thankful Users |
Follow us on