Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Customized Object became Unknown

Created by: TerminalBuzz at: 7/16/2013 3:23 PM (2 Replies)

Rating (0)

Thanks 0

3 Entries

7/16/2013 3:23 PM	Rate (0)
TerminalBuzz Silver Member Joined: 11/4/2011 Last visit: 8/25/2024 Posts: 253 Rating: (53)	Hello. Has it happened to you that your Customized Object one day became Unknown? ^{(see attachment)} It happened to me several months ago but I did nothing to resolve this. Now just for the hell of it I'm interested whether someone else had the same issue before. I wanted to create a popup windows such as @PG_APL_OA_Binary103.pdl but with command buttons that would operate the bits in the Control Words. It's for self-made FBs cause I don't want and don't like to make separate BOOL Inputs for the operator commands. I prefer SCL + Control Words + AT on ControlWord with struct of a bunch of BOOLs. So I took @PG_APL_OA_Binary103.pdl and changed one button according to my needs. It was made in a test project. Everything worked fine. Later I added this pdl to my working project ^{(PCS7 of the same version 7.1 SP3)} and didn't pay attention to that button anymore for the next several months. After that I tried to use it in Runtime and saw that the button is broken in some way ^{(don't remember how it looked like)}. Then I opened pdl in Graphics Designer and that button was shown as white rectangle with the text "Unknown Object"^{(see attachment)}. I restored several previous versions of my working and test projects, and tried it on different PCs, too — it's all the same unknown. It was hard to modify the original @PG_APL_OA_Binary103.pdl for the first time so I haven't tried to recreate my button. Left it at that.. Attachment @PG_ANK_OA_Binary103.zip (93 Downloads)

Suggestion To thank Quote Answer

7/17/2013 10:16 AM	Rate (0)
Silent Bob Posts: 836 Rating: (100)	Hi, what was part of the customized object? Did it contain OCX controls? Did you change the Runtime language? Did you run the OS Project Editor in the meanwhile?
Silent Bob Posts: 836 Rating: (100)
Suggestion To thank Quote Answer

7/17/2013 11:14 AM	Rate (0)
TerminalBuzz Silver Member Joined: 11/4/2011 Last visit: 8/25/2024 Posts: 253 Rating: (53)	In general all the objects included in the CO are listed in a Configuration Dialog. I've attached a screenshot of that list of the system APL_OP_BUTTON4 button. Nothing special, typical objects of the PCS7: Analog Display (extended), I/O Field, Button, Static Text. I can't get the list of my modified CO button, but I don't think that I'd added new objects. The existed ones were enough. It was not the Runtime language switching that caused a problem. And don't forget that I tried to open same pdl in the test project where it was designed. I can't remind if I'd run OS Project Editor before the problem. Maybe it has something to do with OSPE. One new fact is that there were three similar PCS7 buttons made as COs that is named "APL_OP_BUTTON4". And I'd changed the name^{(in Configuration Dialog)} of my modified CO to "ANK_OP_BUTTON4" just to distinguish different COs. Some tip/issue here is that if you have several languages in a project, e.g. English and Russian, than to change the name of the Customized Object you must switch display language to English in Graphics Designer and give the CO's name only in English. Then the English text would be copied to the Russian text. I seems to me that CO names/types are registered somehow in the OS and my object had been unregistered. Cause if I have simple WinCC and I will open some pdl made in PCS7, then special PCS7's objects ^(e.g.^{Analog Display (extended))} would be shown as Unknown Object. Regards Attachment APL_OP_BUTTON4 components.jpg (102 Downloads)

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on