Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Problems After Project Conversion

Created by: frmr at: 12/16/2019 5:22 PM (8 Replies)

Rating (1)

Thanks 2

9 Entries

12/16/2019 5:22 PM	Rate (0)
frmr Advanced Member Joined: 1/15/2019 Last visit: 1/12/2023 Posts: 8 Rating: (1)	Hello, I've converted a project from V7.1 SP2 to v9.0 SP1. For now I'm just trying to get the OS to work. - I've migrated and compiled the OS - Downloaded to the server - Run the OS It all works except for some apl faceplate features, namely apl_oa_analog. The Faceplate appears in runtime but I can't change the value. I think the problem is permissions and the LinkTag3 Value, but my knowledge is lacking in the pcs7 world and after fiddling a bit with it I can't get it to work. Unless I go to the old project and copy the @pg_apl_oa_analog_xxx.pdl file to the converted project and use that instead. But I think that's not the best option. If anyone as any inputs regarding my problem, I'd be very thankful

Suggestion To thank Quote Answer

12/16/2019 8:21 PM	Rate (0)
mark1507 Platinum Expert Joined: 6/23/2008 Last visit: 11/7/2024 Posts: 1168 Rating: (283)	Hello frmr, which rights does the current WinCC user have? If you did not already, create a user having all rights existing in the 'User Administrator' and test again. Are there any custom made levels in the 'User Administrator'? Please check also the OSPerm bits of the blocks (start with a specific instance, and open faceplate of this instance for testing). Also you should check the value of 'Op_Level' in CFC of the inputs which are operated from the faceplate. In e.g. for the setpoint of the block of type PIDConL open the properties of an instance in CFC, go to the input 'SP_Int' and scroll to the right to check what value is given in column 'Operator authorization level'. For 'SP_Int' the standard value is '1'. 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.
Suggestion To thank Quote Answer

12/17/2019 12:21 PM	Rate (0)
frmr Advanced Member Joined: 1/15/2019 Last visit: 1/12/2023 Posts: 8 Rating: (1)	Hi mark1507, Thanks for the reply, -I've already tried with an user with all rights and the problem is the same. -Checked the 'Op_level' of the inputs I can't change and it says 0 in the Operator autorization field -In the User Administration there aren't any new levels, unless something got lost in conversion As far as I've checked my problem is in the custom faceplates, in e.g. PIDConL I can modify the value, the only problem there is the input field gets black and I can't see the value until I press 'Enter'. In the Custum faceplates In Some cases there is no action when i click over the analog_op_display field or when there is an action it shows the current value in the IO field but I can't change it. I've also triedsetting LinkTag3 to -1 and BitIndex4 to 0, cause in the custom block I don't have any os_Perm tag, but it did nothing thank you for your help.
	Last edited by: frmr at: 12/17/2019 14:00:31
Suggestion To thank Quote Answer

12/17/2019 7:44 PM	Rate (1)
mark1507 Platinum Expert Joined: 6/23/2008 Last visit: 11/7/2024 Posts: 1168 Rating: (283)	Hi, frmr ... -I've already tried with an user with all rights and the problem is the same. -Checked the 'Op_level' of the inputs I can't change and it says 0 in the Operator autorization field ... Ok. If 'Op_level' is '0', I think it's the reason why no operation is possible with the original @pg_apl_oa...pdl, at least for standard blocks like PIDConL. For operation you need at least '1'. From the other information you gave it sounds like sombody created own blocks with own faceplates, but didn't understand how the entire authorization stuff works and hence didn't implemented the necessary functionallities on block side. As a workaround he modified the @pg_apl_oa... To be honest, I actually only partially remember the topic as it is very complex... Yes, to 'LinkTag3' usually the tag '.OSPermLog' is connected. Make sure the reference to this tag is deleted if your block doesn't have it. Configure '1' (not '-1') to static value of 'LinkTag3'. Yes, 'BitIndex4' shoul be on '0' in that case.
	"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.
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users Heisenberg2 frmr

12/19/2019 4:23 PM	Rate (0)
frmr Advanced Member Joined: 1/15/2019 Last visit: 1/12/2023 Posts: 8 Rating: (1)	Do you have any idea of a workaround to enable these value fields for operation, preferably without changing the blocks? As I understand the operation is enabled with the op_level, so how where they able to modify the values in this custom blocks in the original project if it was set to 0? When I open any PIDConL block, used in the project, go to properties and check the Operator authorization level, second to last column in the I/Os tab, all the entries have 0, but in runtime it is possible to change the sp value, so: - Is the op level something that can only be verified Online? - How does it work in these blocks but not in the custom ones?
	Last edited by: frmr at: 12/19/2019 16:24:52
Suggestion To thank Quote Answer

12/19/2019 7:51 PM	Rate (0)
mark1507 Platinum Expert Joined: 6/23/2008 Last visit: 11/7/2024 Posts: 1168 Rating: (283)	Hello frmr frmr ... As far as I've checked my problem is in the custom faceplates, in e.g. PIDConL I can modify the value, the only problem there is the input field gets black and I can't see the value until I press 'Enter'. ... Please describe a little bit more specific; Are the input fields black when you have the original @PG_APL_OA....PDL from V9.0 in the GraCS folder or is this happening when you have the @PG_APL_OA....PDLs from the old project in the GraCS folder? frmr ... In the Custum faceplates In Some cases there is no action when i click over the analog_op_display field or when there is an action it shows the current value in the IO field but I can't change it. .... The same question here. Which @PG_APL_OA....PDLs are used when this happens? frmr ... As I understand the operation is enabled with the op_level, so how where they able to modify the values in this custom blocks in the original project if it was set to 0? .... Didn't you say that you can only modify the values when copying the @PG_APL_OA....PDLs from the old project??? Sorry, but we need to clarify this excactly... Please tell me how is the situation for standard blocks (in e.g. PIDConL) with original @PG_APL_OA....PDLs from V9.0 ? How is the situation for standard blocks with @PG_APL_OA....PDLs from the old project? How is the situation for custom blocks (with custom faceplates) with original @PG_APL_OA....PDLs from V9.0 ? How is the situation for custom blocks with @PG_APL_OA....PDLs from the old project? frmr ... When I open any PIDConL block, used in the project, go to properties and check the Operator authorization level, second to last column in the I/Os tab, all the entries have 0, but in runtime it is possible to change the sp value... Up to now I undersood you in that way that it is only possible to modify SP when the @PG_APL_OA....PDLs from the old project are used. If this is correct and you want to get rid off the old @PG_APL_OA....PDLs from the old project, the only solution for the standard blocks is to modify the 'Operator authorization level' not to '0'. Did you try my suggestion to put '1' at 'Operator authorization level' of 'SP_Int' of 'PIDConL'? Please be aware that this needs OS-compilation (and download). This is of interest with the original V9.0 @PG_APL_OA....PDLs and only if with '0' you can't operate it (see question above). frmr ... - Is the op level something that can only be verified Online? On WinCC side an internal tag is created for each operable input of a block having 'Operator authorization level'. On WinCC side they get the name '<CHARTNAME>/<BLOCKNAME>.<IO_NAME>#Op_Level mark1507 ... Yes, to 'LinkTag3' usually the tag '.OSPermLog' is connected. Make sure the reference to this tag is deleted if your block doesn't have it. Configure '1' (not '-1') to static value of 'LinkTag3'. Yes, 'BitIndex4' shoul be on '0' in that case. Did you try this suggestion at a custom faceplate? Of course this is to be done at the object in the faceplate which opens the @PG_APL_OA..... So in e.g. in the standard view, means in the @PG_<CUSTOM_BLOCK_NAME>_Standard.pdl
	"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.
Suggestion To thank Quote Answer

12/20/2019 1:05 PM	Rate (0)
frmr Advanced Member Joined: 1/15/2019 Last visit: 1/12/2023 Posts: 8 Rating: (1)	Hi mark1507, I will try to answer as best as I can, thanks for the help, mark1507 Please describe a little bit more specific; Are the input fields black when you have the original @PG_APL_OA....PDL from V9.0 in the GraCS folder or is this happening when you have the @PG_APL_OA....PDLs from the old project in the GraCS folder? Yes, the input fields get black with the V90 @PG_APL_OA....PDL mark1507 The same question here. Which @PG_APL_OA....PDLs are used when this happens? The PDL ,when I can't change the values are the, V90 ones. In this case the faceplate is opened trough an event, with APL_OpenFaceplate(IpszPictureName, IpszObjectName,1,"PG_MyFaceplate_Standard.PDL","Objectname") This calls an APL_Analog_OP_Display object that uses the V90 @PG_APL_OA....PDL The value is displayed only, instead of being gray with with cursor for editing The other case is when I open PG_MyFaceplate_Standard.PDL directly and there are some I/O fields, I can't do any action, it only displays the value, when I press over the value it doesn't open the V90 @PG_APL_OA....PDL mark1507 Didn't you say that you can only modify the values when copying the @PG_APL_OA....PDLs from the old project??? Sorry, but we need to clarify this excactly... In the custom faceplates I can only modify the value if I use the V71 @PG_APL_OA....PDLs. For standard blocks I haven't changed anything, so it uses the standard v90 @PG_APL_OA....PDLs mark1507 Please tell me how is the situation for standard blocks (in e.g. PIDConL) with original @PG_APL_OA....PDLs from V9.0 ? How is the situation for standard blocks with @PG_APL_OA....PDLs from the old project? The standard blocks with the V90 @PG_APL_OA....PDLs works Ok, the only problem is the one described in the first topic . I haven't tried the old V71 @PG_APL_OA....PDLs in standard blocks. mark1507 How is the situation for custom blocks (with custom faceplates) with original @PG_APL_OA....PDLs from V9.0 ? How is the situation for custom blocks with @PG_APL_OA....PDLs from the old project? I think I've answered this one in the second topic, if you have any question regarding this please tell me. mark1507 Up to now I undersood you in that way that it is only possible to modify SP when the @PG_APL_OA....PDLs from the old project are used. If this is correct and you want to get rid off the old @PG_APL_OA....PDLs from the old project, the only solution for the standard blocks is to modify the 'Operator authorization level'not to '0'. Did you try my suggestion to put '1' at 'Operator authorization level' of 'SP_Int' of 'PIDConL'? Please be aware that this needs OS-compilation (and download). This is of interest with the original V9.0 @PG_APL_OA....PDLs and only if with '0' you can't operate it (see question above). The standard blocks work, most of it, I think my new explanation above is better. I have some questions about the CFC conversion, I have not performed a conversion, from V7.1 to CFC V9.0, I wanted to install the old V71 library and not convert, for now, but I'm having some trouble with this. So I can't modify any of the 'Operator authorization level', If I'm not mistaken. In last resort I can always copy the old PDLs go on to every custom faceplate and do something like @PG_APL_OA..._V71.PDL, but for now I wanted to understand the problem. mark1507 On WinCC side an internal tag is created for each operable input of a block having 'Operator authorization level'. On WinCC side they get the name '<CHARTNAME>/<BLOCKNAME>.<IO_NAME>#Op_Level Checked all the tags in Tag Management and I can't find any "'<CHARTNAME>/<BLOCKNAME>.<IO_NAME>#Op_Level" in any of the structures, not even PIDConL.SP_Int mark1507 mark1507 ... Yes, to 'LinkTag3' usually the tag '.OSPermLog' is connected. Make sure the reference to this tag is deleted if your block doesn't have it. Configure '1' (not '-1') to static value of 'LinkTag3'. Yes, 'BitIndex4' shoul be on '0' in that case. Did you try this suggestion at a custom faceplate? Of course this is to be done at the object in the faceplate which opens the @PG_APL_OA..... So in e.g. in the standard view, means in the @PG_<CUSTOM_BLOCK_NAME>_Standard.pdl I've made these changes, but could only try them with the AS systems Offline, and like this I the input field is not enabled. Thank you very much for your help and sorry for the long post and for any bad explanation.

Suggestion To thank Quote Answer

12/20/2019 3:05 PM	Rate (0)
mark1507 Platinum Expert Joined: 6/23/2008 Last visit: 11/7/2024 Posts: 1168 Rating: (283)	Hi, actually I'm a little bit in a hurry. I will come back to what you wrote later. Maybe you can check the following in between: When looking on WinCC side for the tags 'Op_Level' make sure the cursor is on 'internal tags' Also check your private messages... 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.
Suggestion To thank Quote Answer

12/20/2019 6:52 PM	Rate (0)
mark1507 Platinum Expert Joined: 6/23/2008 Last visit: 11/7/2024 Posts: 1168 Rating: (283)	Hi, frmr mark1507 Please describe a little bit more specific; Are the input fields black when you have the original @PG_APL_OA....PDL from V9.0 in the GraCS folder or is this happening when you have the @PG_APL_OA....PDLs from the old project in the GraCS folder? Yes, the input fields get black with the V90 @PG_APL_OA....PDL It sounds that somthing for the upgrade procedure wasn't done. Did you follow the guide "PCS 7 Software update without utilization of new functions for PCS 7 V9.0..." In e.g. did you run the 'OS Project Editor'. This is important to renew the system PDLs. frmr The other case is when I open PG_MyFaceplate_Standard.PDL directly and there are some I/O fields, I can't do any action, it only displays the value, when I press over the value it doesn't open the V90 @PG_APL_OA....PDL Do you know the script diagnosis? Can you open it and watch what it says when clicking? frmr mark1507 Didn't you say that you can only modify the values when copying the @PG_APL_OA....PDLs from the old project??? Sorry, but we need to clarify this excactly... In the custom faceplates I can only modify the value if I use the V71 @PG_APL_OA....PDLs. For standard blocks I haven't changed anything, so it uses the standard v90 @PG_APL_OA....PDLs Again I'm more confused... Are the custom faceplates use own @PG_APL_OA....PDLs.? Usually there are only three types of @PG_APL_OA....PDLs. The same @PG_APL_OA....PDL is used by different blocks (their faceplates). I expected the custom faceplate to use the same @PG_APL_OA....PDLs. You see, there is a lot of potential for missunderstanding and also a lot of things to analyze. I'm afraid we will not come forward this way... frmr The standard blocks with the V90 @PG_APL_OA....PDLs works Ok, the only problem is the one described in the first topic . .... The standard blocks work, most of it, ... Problem with standard blocks or not? Also one problem is a problem...'most of it' is fuzzy... frmr I have some questions about the CFC conversion, I have not performed a conversion, from V7.1 to CFC V9.0, I wanted to install the old V71 library and not convert, for now, but I'm having some trouble with this. So I can't modify any of the 'Operator authorization level', If I'm not mistaken. You can not leave out the conversion of CFC. It is a 'must do' ! Updating the blocks is an own topic and independant of converting the charts to the current version of CFC. frmr Checked all the tags in Tag Management and I can't find any "'<CHARTNAME>/<BLOCKNAME>.<IO_NAME>#Op_Level" in any of the structures, not even PIDConL.SP_Int See my pervious post. frmr I've made these changes, but could only try them with the AS systems Offline, and like this I the input field is not enabled. Maybe you can use PLCSIM together with WinCC....
	"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.
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on