Faceplate Tab element navigation time

I have less graphic elements in my faceplate second tab.But the diagnostic of second tab shows more Navigation time.Attached Screrenshot.How can i reduce the navigation time for the faceplate Tabs?

Comments (0) New comment

jagadheesan.s@in.abb Rank: 505

Asked 2 months ago

Answer this question Follow

Answers

Hi.
Is it actually slow to open the second tab or is it just the Diagnostics you feel show wrong?
The diagnostics will use the moment when you first clicked on the faceplate as a start-time, and the moment that your view is loaded as end-time. This can give you strange timings in Diagnostics it you change views of the faceplate.
If you change the tab view of the diagnostics to Timing, is most of the time used for Navigation?
Regards
Ned

Comments (2) New comment

by jagadheesan.s@in.abb Rank: 505 on 2/23/2021 3:50:56 AM | Like (0) | Report

I feel Diagnostic showing wrong timing. Actual Navigation timing of faceplate element is less. But after connecting the same element in the faceplate ,the same element showing High navigation time .

by Ned Rizvanovic Rank: 963 on 2/23/2021 4:10:03 AM | Like (0) | Report

Ok, I see.
Then your problem is more of an academic nature. You don't have the slowness, but you feel the Diagnostics are not to be trusted?
There is a tracker at the development right now, regarding the faceplates and the non-reliable diagnostics. It is under evaluation.
See below my thoughts on the issue, which I sent in as a comment to the development:

"It seems like the timing is calculated wrongly;
The start time-point is always the same - the time point when the faceplate is called. Once the faceplate is up, the timing is ok, as a stop point for this calcuation is set correctly - when the faceplate was completely up and showing in its default view.
So far, so good.
However if you start changing views in the faceplate, the stop time-point of the faceplate is re-set to the time point of end of load of this new view, which can be a cuple of minutes after it was open in the first (default) view... Stop-time minus start-time(which is still the time the faceplate was opened first time in its default view) will give us strange timings for this faceplate.

On the other hand, it is hard to do this correctly. Which time should be set as start time once a view is changed? The faceplate as an overlap is already there, so load of this container can't be presented. The load of this next view will be presented without this overhead..."

As you are loading another faceplate element in the next tab, I feel the problem applies to you as well.
If you need the PIN for this issue, I can provide.
Regards
Ned

Add new comment

Ned Rizvanovic Rank: 963

Answered 2 months ago

Question details

Faceplate Tab element navigation time

Answers

Other questions needing answers

Related topics

AKS experts