By right there is a process named hislnbc (hit logical name broadcast that is
uppose to be running when you have AIM that keeps those files updated.
It runs every minute to see if new instances have been created and populates
those files.
Many time users will disable that process to lower the broadcasting once they
know there historians are established and wont be changing.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Chad Ziesemer
Sent: Monday, September 26, 2016 11:29 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Foxview trend reverting to wrong historian
Update, It looks like Russ's suggestion copied below fixed the issue, I waited
a few days to send this out to make sure:
In /etc/histlns & /etc/histlocs no historian was listed so I added hist80 to
both, with its server letter bug in histlocs.
In /etc/fox/histlns & /etc/fox/histlocs only hist01 was listed, so I added
hist80 as the first line in both, again with its letterbug in histlocs.
I am going to keep looking into Russ's comment that the historian may not be
consistently available since the above fix may just be hiding a different issue.
Mike, to answer your question (and further complicate this issue!): There is
still a hist01 on our system, it is the older AIM* historian relegated to just
OAJ and Alarm History. The part that makes this issue a bit more complicated is
we have an off-mesh Wonderware historian (hist80) that is using the on-mesh
AIM* server as a handoff or fetch server for the process data. The way it's
been explained to me is Wonderware, at least at our revision, could not store
alarm history and OAJ and have everything accessible in FoxView. It makes
sense now that if it couldn't find hist80 for a moment, it would look at the
lists above and see hist01 as a viable historian, check there, and there is no
process data so I get no data in the trend. I obviously need to learn more
about this set-up I'm stumbling on the details, but looks like we've got it
working in the meantime!
Thanks to all who helped with this!
Chad
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Boulay, Russ
Sent: Wednesday, September 21, 2016 9:26 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Foxview trend reverting to wrong historian
Sounds like the trends are not consistently finding the historian data, so it
substitutes to try and find the data by broadcasting to historians.
I believe that happens according to the order in /etc/histlns or
/etc/fox/histlns ....and also histlocs is an important file.
But I believe the source of your issue is that the active historian is not
consistently available.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Michael Jaudon
Sent: Thursday, September 22, 2016 3:08 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Foxview trend reverting to wrong historian
Chad,
I would have thought Dale's suggestion would have worked.
We've had similar issues as you're describing.
Foxray (System Auditor) has picked up "Points in a Trend that aren't
Historized" before when all four trend points were, in fact , in the historian.
The issue arose when a point was inserted via copy & paste. The solution was to
edit the .g file (to find the hidden/embedded C:B.P) or to rebuilt the trend
from scratch.
Is there another hist01 somewhere on the system? I would have thought once it
was turned off it would no longer find it (even though it might still look for
it).
Mike Jaudon
PSI
On Tuesday, September 20, 2016, Chad Ziesemer <cziesemer@xxxxxxxxxxxxxxxxxxx>
wrote:
Hi list,
I have a number of trends in FoxView that recently decided to go look
for an old historian and therefore not populating with data, here's
the
behavior:
1. If I right click on the dysfunctional trend, go to advanced, and
go to advanced pen 1 (2,3,4), under historian name it says hist01 (old
historian name).
2. When I open the same trend in foxdraw it is configured to hist80
(proper historian name).
3. Back in Foxview If I change this to hist80, select "permanent"
under save/exit choices, and refresh the trend it works at first.
4. I can open and close the trend and it keeps coming up hist80 and
good data.
5. Randomly(ish), I'll open the exact same trend and I'll get no
data. The advanced pen screen shows again hist01. Foxdraw still
shows it's configured as hist80. Some of the trends I fixed are still
working, others reverted back, I can't pick up a pattern to the madness.
Has anyone experienced anything similar or have an idea to try?
I/A 8.4.2
FoxView 10.1
ICC
______________________________________________________________________
___ 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
<javascript:;>?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx ;<javascript:;>
?subject=leave
