Just a correction for the archives on this note I posted before: FoxView can
handle filenames starting with a number, but it cannot save files without ANY
alphabetic characters in the name. We had a DM filename that consisted of
numbers and an underscore, which did not convert correctly and was converting
on the fly when called up in FV. I had to open it from FoxView and resave,
using a new name.
-Joe
-----Original Message-----
Sent: Tuesday, November 01, 2016 11:26 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FoxView Library Objects - Slow performance
Just in case you need more things to check...
-We had some displays converted from DM to FV that came up slow in FV every
time because the filename started with a number, which FoxView does not like. I
think it was converting on the fly every time.
-Make sure the newest version of the library objects is copied to the same
location on the WP as on the AW where you built the graphics (if the WP is the
one loading slow), and then restart all FoxView instances to reload the library
objects.
-Are the connections coming over the ATS from a nodebus CP to FoxView on a Mesh
workstation or vice versa? Are they coming from multiple CPs? I assume these
would make it slower, not sure by how much.
-Should you be using custom faceplates rather than regular library objects? You
mentioned PIDA, valves, etc, are you making faceplate-style objects or just
showing parameters?
-Supposedly multiple fonts can slow things down. Do all objects have the same
font, and are all the fonts installed on all machines so it doesn't have to
replace them? You can do Select All and change font for all objects at once to
a single font to make sure.
-I've always used Foxray/System Auditor to check for bad connections, under
Integrity Checks or Displays. Dedit may be better, but if you have SA you might
check it too.
-Plain text objects with bad connections won't show up cyan/smurfed the way
background text does, as FoxDraw warns you when connecting a plain text object.
-Are you sure all your library object aliasing was done correctly? Curly
brackets like {C}:{B}.{P}, {TEXTXXX}, etc in the m1 files. Are there any
aliases you forgot to resolve in the main graphic?
-Are you using any special ranges such as RO01 instead of a fixed range? I
remember having trouble figuring out the right way to type these in the library
objects, and resolve the aliased ones, can't remember the proper method now but
if you have those you could replace them with fixed ranges to test.
And as someone else mentioned, different versions of FV/FD can have trouble
reading each other's files. I tried copying files made in FD 10.4 to a machine
running 10.2, and they wouldn't come up at all, so I had to convert to g then
back to fdf. Probably not your problem, but just in case it's worth mentioning.
Hope this is helpful,
-Joe
_________________________________________________________________________
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
