Re: [foxboro] Select point and assign to trend picks the wrong historian
- From: Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 16 Nov 2010 12:24:50 +0900
No, aimh01 is 13th out of 15. The historian I want is 15th out of 15, I'll
edit to put aimh01 at the end and see if that makes a difference.
Cheers,
Kevin
On Tue, Nov 16, 2010 at 12:07 PM, Joseph M. Riccardi <Joe@xxxxxxxxxxxxx>wrote:
> Kevin,
>
> What is the 1st Historian name in the list of your histlns file; aimh01?
>
>
> Joseph M. Riccardi
> DCS Services - Industrial Process Control
>
> "To give real service you must add something that cannot be bought or
> measured with money; and that is sincerity and integrity." - Donald A.
> Adams
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On
> Behalf Of Kevin Fitzgerrell
> Sent: Monday, November 15, 2010 10:01 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] Select point and assign to trend picks the wrong
> historian
>
> Hi all,
> I've got an odd problem on 2 of my Nodebus AWs in one plant area. When I
> pick a tag using "select point" and assign to a trend (using the A button),
> for some reason the wrong historian (aimh01) is assigned to the tags.
> Depending on which tag I try to assign it should be hist01, hist07 or
> hist08
> - the three legacy historians on Nodebus AWs in that plant area. The wrong
> historian, aimh01, is on a Solaris Mesh workstation - the only relationship
> it has to the problem AWs is that it hosts the ATS modules that connect the
> mesh to those nodes.
>
> These AWs are running 6.5.6 with Display Manager and legacy historians, and
> their nodes connect to the mesh via ATS. My other AWs with the same
> configuration are not seeing this problem.
>
> Does anyone know what the mechanism is that is assigning the historian with
> the tag to a trend line? What file(s), if any, might be driving this
> behavior?
>
> I've checked the /etc/histln, histlns and histlocs files and they all
> appear
> to be correct. /etc/fox/loghost is also correct.
>
> Cheers,
>
> Kevin
>
>
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://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 Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://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 Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://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:
