Re: [foxboro] PI connection type

  • From: <G.Macdonald@xxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Wed, 24 Mar 2010 16:05:10 -0600

Thanks for all the advice and suggestions.  We were able to get it to work.  
You have to add all the write points to the alias.cfg file.  If any point is 
set as write (location3=-3) and is not in the alias.cfg file 
(d:\opt\fox\ais\bin\alias.cfg), then every point on that interface is 
flat-lined.

Grant Macdonald
DCS / SIS Specialist
Scotford Refinery

Shell Canada Limited
Bag 23, Fort Saskatchewan, Alberta T8L 3T2, Canada

Tel: + 1 780 992 3881
Email: g.macdonald@xxxxxxxxx
Internet: http://www.shell.ca

This email, any attachment and/or series of responses, is intended for the use 
of the recipient to which it is addressed, and may contain confidential, 
personal and/or privileged information. If you are not the intended recipient, 
telephone or email the sender and delete this message and any attachment 
immediately. Do not copy, distribute, or take action relying on it. Electronic 
communications over a public network are not secure and therefore Shell does 
not accept any legal responsibility for the contents of this message, including 
any damage caused by any virus transmitted by this e-mail.

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Johnson, Alex P (IOM)
Sent: March 24, 2010 2:03 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] PI connection type


Re: Tim wrote, "Did you put all the writes in a separate list?  You must put 
the writes in a separate list, or you'll have all kinds of problems."

The I/A Series OM supports:

1) Read lists (read only lists of points)
2) Write lists (write only lists of points)
3) Read/write lists (tags can be read and/or written)

FoxAPI supports:

1) Read only data sets (mapped to ro om lists)
2) Read/write data sets (mapped to the r/w om lists)

The interesting thing about write lists is that if any point is unavailable, 
e.g., a mispelled tag, all of the points are unavailable. The thinking was that 
this would be a good feature for APC programs.

The even more interesting thing about R/W lists (and, therefore, FoxAPI R/W 
datasets) is that if any point is unavailable ALL of the points are unavailable 
for both read and write operations.

Yes, I agree that is strange, but that's the way it works. 

My advice?

Segregate the points you want to read from those that need to be written. If 
the points on the write list fail to update, check for those that are missing.

Make sense?


Regards,
 
Alex Johnson
Invensys Operations Management
10900 Equity Drive
Houston, TX 77041
+1 713 329 8472 (desk)
+1 713 329 1600 (operator)
+1 713 329 1944 (SSC Fax)
+1 713 329 1700 (Central Fax)
alex.johnson@xxxxxxxxxxxx (current)
alex.johnson@xxxxxxxxxxxxxxxx (good until September 2010)


*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at Portland House, Bressenden Place, London, 
SW1E 5BF (Registered number 166023). For a list of European legal entities 
within the Invensys Group, please go to 
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. 
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail 
inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail 
 and any attachments thereto may be subject to the terms of any agreements 
between Invensys (and/or its subsidiaries and affiliates) and the recipient 
(and/or its subsidiaries and affiliates).


 
 
_______________________________________________________________________
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: