Hey,

Im very new to scripting and cant figure out how to solve this problem:

We are opening Faceplates on our main HMI screen via the "OpenFaceplateinPopUP" function in a java script. The faceplates then opens but with the Close Button ("X") in the upper right corner. However, for closing the faceplate we want the user to use a custom closing button within the faceplate. Unfortunately I can't seem to find the property for hiding the default closing button. We tried the ".hideCloseButton = true;" but this only seems to work when using the function "openscreeninpopup".

Do you have any suggestions? When I place a Faceplate Container directly into the HMI it is possible to hide it in the property settings.

We use TIA Portal V17 & a Unified Comfort Panel MTP 700

Thanks a lot in advance!

Greetings

Hey,

thanks alot for the quick answer. Very usefule information! Sadly, its not working for me. Maybe you can spot the mistake. We are running this as a global function which is activated when pressing a button on the HMI (the button itself is not a faceplate, just a plain object):

export function OP_PUMPE_EINF(ltext, kks_) {

let number = "faceplate_number" ;
let kks = Tags ("kks");
kks.Write(kks_);
let HText= kks_ + ' ' + ltext;
let ID = Tags("Faceplate_ID")

//internal check for if the same window has already been opened. If yes, it'll be closed

for (let i = 0; i < 10; i++) {
let idi = Tags("Faceplate_ID.ID["+i+"]");
let ID2 = idi.Read();
if (ID2 === kks_){
po[i].Close();
let tag1 = Tags("Faceplate_ID.ID["+i+"]");
tag1.Write(''); }
}

//wirte constant "data";

const data = {UDT:{Tag:kks_},

FS_MITTEGRAU:{Tag:"FS_MITTEGRAU"},
FS_ROT:{Tag:"FS_ROT"},
FS_BLAU:{Tag:"FS_BLAU"},
FS_DUNKELGRAU:{Tag:"FS_DUNKELGRAU"},
FS_GELB:{Tag:"FS_GELB"},
FS_GRUEN:{Tag:"FS_GRUEN"},
FS_HELLGRAU:{Tag:"FS_HELLGRAU"},
FS_MAGENTA:{Tag:"FS_MAGENTA"},
FS_MW:{Tag:"FS_MW"},
FS_ORANGE:{Tag:"FS_ORANGE"},
FS_SYMBOL:{Tag:"FS_SYMBOL"},
FS_ROT:{Tag:"FS_ROT"},
FS_WEISS:{Tag:"FS_WEISS"},

STAT:{Tag:kks_+"_STAT"},
FP_ID:{Tag:"Faceplate_number"},
KKS: {Tag:"kks"},
ID:{Tag:"Faceplate_ID"}};

// Open faceplate

po[number] = UI.OpenFaceplateInPopup("OP_PUMPE_EINF_V_0_4_18",HText,data,Screen);
po[number].Left = item.Left;
po[number].Top = (item.Top+10);
po[number].HMIWindowFlag = 64; // also tried WindowFlags = 64;
po[number].Visible = true;

}

Everything else is working. However I sometimes I have a feeling that all the attributes after the line with "UI.OpenFaceplateInPopup" are not being applied properly (Visbile = true/false doesnt seem to make a difference).

I also tried using your example code and it also didnt work for me. It underlined "faceplate" in the line "let po = Faceplate.OpenFaceplateInPopup" red. When I use the snippets it says to use UI.OpenFaceplateinPopup... whats the difference?

Sorry for the amateurishness. Like I said Im very new PLC programming and especially to JavaScript.

DM987

Hey!

The example shows the use of several properties for the popup - (ShowCaption (1): Show title + ShowBorder (2): Show border + CanClose (64): Can be closed) (1+2+64=67)

Hi,

is it just me or is the error pretty obvious.

Use "WindowFlags" instead of "HMIWindowFlag" what you did. You can copy&paste the property Name of any object that has this property (all Controls) by rightclicking on it. The Traceviewer should output an error message with your code, that HMIWindowFlag is not existing.

Greetings
ZickZackTIA

Hey!

so I tried all of your options and even copied DM987 Skript from the screenshot and it just wont work. It still gives me an error for the function "let po = Faceplate.OpenFaceplateinPopUp....." and says that "Faceplate" is a not supported in current scope.

Are we on the same version? I read about some Updates to V17 which also changed some things about faceplates (Our MTP 700 is set to V17.0.0.0).

@ZickZackTIA We are also still trying to get Traceviewer to work. Currently it only traces whatever we write in TIA Portal. But I tried all the exampels from DM987 with no success.

Thanks a lot guys!

Hi,

the error message, that Faceplate.... is not defined is correct here.

The example provided before is probably taken from inside a faceplate.

From the outside your code should have worked, you just failed in that one line, where you wrote po[number].HMIWindowFlag = 64;

By the way, i don't know how you store that number. You create an array of possible Faceplates and fill the index with a text-string?

Have a look at the following document on how to trace / debug:

https://support.industry.siemens.com/cs/ww/en/view/109758536 

I would be curious, if po[number] is the correct object. If so, WindowFlags should work on that. 

Greetings
ZickZackTIA

Got TraceViewer to work now and Im still looking through the logs. Cant seem to find an error message involving "WindowFlags".... very mysteriously. I'll be testing this new tool today.

We have an array of wstrings to which we write the identfiers of the specifc components(i.e. a pump with an uniqe ID / "KKS" = Pump123456 for example). When the symbol is pressed we check if this Faceplate ID has already been written to the array. If yes, it'll close the window and reopen it (not the best solution but its working fine for us). If the kks is not found in the array a functions looks for a free array space and writes the kks into it and opens the faceplate. When closing a faceplate, the kks is being erased from the array.
We dont want the user to open the same faceplate of a component more than once and also want to limit the total number of faceplates open on the screen (currently we use an array of 10, so we can open 10 Faceplates of different components at once)

This is also why we want to hide the Close button.The function for deleting the ID from the Array when closing a faceplate window is being called when our custom closing button within the faceplate is pressed. We also tried to tie this script to an event (when the Faceplate is being cleared, see screenshot) but this only works like maybe 2 out of 10 times. So our solution was to hide the default closing button and just use our own because it worked flawlessly.

I also think that the po[number] thing is not working correctly somehow. But since not even the simple example from DM987 is working Im really baffled.

Hopefully the Traceviewer will give me some answers today.