Re: [foxboro] Fw: Few Tags not updating in PI
- From: "Lowell, Timothy" <Timothy.Lowell@xxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Sat, 5 Feb 2011 09:28:43 -0600
Ajit,
What do you have configured as the Location3 in PI for SUL_RCV_25:92XA207A.CIN?
I can't tell if you have a 2 configured and it wants a 5, or the other way
around. I'm not sure what a 2 is. I don't have my documentation handy. Most CIN
blocks are 5 in PI.
On SUL_RCV_15:92XA104A.CIN, it looks like this block doesn't exist in I/A. You
might have a typo there, or it is in another compound. Double-check that the
block exists in that compound and that it is looks normal on the detail display.
Tim
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of
Ajit.S.Kumar@xxxxxxxxxxxxx [Ajit.S.Kumar@xxxxxxxxxxxxx]
Sent: Saturday, February 05, 2011 8:30 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Fw: Few Tags not updating in PI
Dear Tim,
We have a few errors in /opt/piapi/dat/pimesslogfile such as below
...Please let me know how this can be rectified.
01-Feb-11 09:18:22
FXBIA- 7> Warning: IA obj SUL_RCV_25:92XA207A.CIN, IA type=2 (not 5),
idx=3842
PItag (92XA207A.CIN) list= 8
01-Feb-11 09:18:53
FXBIA- 7> pisn_sendexceptionqx error -999007,tag: 92XA207A.CIN, pt: 63659,
pttype: D, cstat: 0
01-Feb-11 09:18:53
FXBIA- 7> No connection: IA obj SUL_RCV_15:92XA104A.CIN, status 0x0000
(prev 0x0000), idx=3011
PItag (92XA104A.CIN), list=8
Best Regards
A.kumar
----- Forwarded by Ajit S Kumar/Technical/SAMREF/SA on 05/02/2011 05:24 PM
-----.
Re: [foxboro] Few Tags not updating in PI
Lowell, Timothy
to:
foxboro@xxxxxxxxxxxxx
04/02/2011 09:52 PM
Sent by:
foxboro-bounce@xxxxxxxxxxxxx
Please respond to foxboro
Ajit,
Your first step would be to check foxspy (/opt/fox/ais/bin/foxspy or
d:\opt\aim\bin\foxspy). You should know which FoxAPI set the tags are in
by the Location2 parameter in the PI configuration. You can find this list
in FoxAPI by invoking foxspy and typing in 913 at the first prompt, and
then 1. The list name will be PILISTF(Location1)L(Location2). Type the
number of that set (not the Location2 number, but the FoxAPI set number)
at the foxspy prompt, and you will see the list of points in that set. If
the list doesn't contain the points you think it should, then PI is not
creating the points for some reason. The usual reason is a typo in the
InstrumentTag parameter, but there could be lots of reasons. If the point
is there in the list, the value should be 0 or 1, and the status should
end in 23. Anything else is an error of some sort.
The next step is to check the pi log file in /opt/piapi/dat/pimesslogfile
or c:\program files\pipc\dat\pipc.log. Search in that file for one of the
points that isn't updating, and it should give you some clue as to what is
happening.
You should also make sure that the Location3 value is 5, for a digital
point. That has gotten me a few times when I was copying a bunch of analog
points to create some digitals and forgot to change the Location5 value.
Tim Lowell
Control Systems Engineer
Tesoro Refining and Marketing Company | 19100 Ridgewood Parkway | San
Antonio, TX 78259
210-626-4929 (w) | 210-253-0225 (c) | timothy.lowell@xxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Ajit.S.Kumar@xxxxxxxxxxxxx
Sent: Friday, February 04, 2011 12:27 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Few Tags not updating in PI
Hi,=0DWe have a few Digital tags configured in PI re= cently, but these
tagsare showing as timeout in PI trends.=0DWh= at could be the possible
cause.Checked the configuration in PI.Its is okay,= I confirmed this by
addding new tags and thats okay.=0DI h= ave checked these tags in foxapi
list but couldn't find it there.What = could be the possible problem.=0DWe
have a file created for AIM*= alias.cfg,does that need to be updated with
these tags.I know this is only= for Historian tags configuration.=0DAny
thoughts =0D= =0DThanks in advance=0DA.kumar=0D=0D=
_______________________________________________________________________
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
_______________________________________________________________________
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:
