Re: [foxboro] FoxView Library Objects - Slow performance
- From: "Pat Motteshard" <mottesha@xxxxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 24 Oct 2016 09:22:44 -0500
Maks,
EVO 9.1 using FoxDraw 10.4.2 , I/A 8.4.4 using FoxDraw 10.2.4 I/A 7.6 using
display builder
I have found that displays built at 10.2.4 levels have to be opened in FoxDraw
10.4.2 before they are opened in FoxView 10.4.2. When I am going from 10.2.4
to 10.4.2 I open the 10.2.4 files in FoxDraw 10.4.2 first. 10.4.2 will ask to
convert to wide format, I answer yes, once the displays have been opened once,
the call up time is acceptable. If I don't let 10.4.2 convert the 10.2.4 files
the call up times are unacceptable no matter how many times I try to open them
most of the time FoxView 10.4.2 won't even open the 10.2.4 files. It appears
an FDF file are not the same because even though both versions of FoxView are
the wide format FoxView doesn't like opening the counter parts files.
Rgds.
Pat Motteshard
Dirk Pauwels <dirk.pauwels@xxxxxxxxxx> 10/24/2016 12:50 AM >>>
Maks,
I/A 8.7, foxview 10.2.3.
We use foxview displays with a lot of symbols. All of the valves and pumps and
some of the analog values with alarming behind it are symbols.
The highest complexity index is 1.5, and this is a very "crowded" display. Fast
scan is off. Displays open within 0.5sec.
Our symbols are in /opt/customer/displib/symbols.
1.7 sounds like a very complex display. Have you tried taking out symbols until
the index drops and check opening time then? Seems to me it should be possible
to drop the index a little.
After a reboot of the station, the first time a display is called it takes
longer to open. This seems to be normal behavior.
Do you have scripting on your displays?
If you zoom out in foxdraw, as much as possible, are there any objects outside
the display frame on the displays with symbols?
Do you have this problem on one station only or on all stations?
Once the display is open, are there any values/objects/symbols "smurfed"?
Have you tried optimizing the display with the optimize command? Never had to
use this....
Rgds,
Dirk
-----Oorspronkelijk bericht-----
Van: foxboro-bounce@xxxxxxxxxxxxx [
mailto:foxboro-bounce@xxxxxxxxxxxxx] Namens ;
Maks Wilde
Verzonden: vrijdag 21 oktober 2016 21:29
Aan: foxboro@xxxxxxxxxxxxx
Onderwerp: Re: [foxboro] FoxView Library Objects - Slow performance
I can confirm that the display timestamp does not change on call-up every time.
I'm not sure what else can be done other than not using library symbols.
Should I be putting in a CAR for this or is there anything else that can be
done to improve the speed?
Thanks,
Maks Wilde
________________________________
Lawter Notice: The information (including any attachments) contained in this
communication is confidential, private and proprietary, may be privileged or
otherwise protected by applicable law or legal rule, and is intended only for
the use of the addressee(s). Unauthorized use, disclosure, distribution or
copying is strictly prohibited and may be unlawful. If you have received this
communication in error, please notify the sender immediately by reply e-mail,
or by calling the sender, and then delete it completely from your system.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list:
//www.freelists.org/list/foxboro
to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list:
//www.freelists.org/list/foxboro
to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts: