Re: [foxboro] FoxAPI Writing Difficulties

From: "Schouten, Frits JF" <Frits.Schouten@xxxxxxxxxxxxxxxxxx>
To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
Date: Mon, 29 Nov 2010 14:30:02 +1300
Hi Nicholas,
Contact me off list. I've written plenty of FoxAPI functions that read and 
write to C:B.Ps
I'll send you a few examples.

Frits.schouten@xxxxxxxxxxxxxxxxxx

Cheers,
Frits.

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of Nicholas J Mezza
Sent: Monday, 29 November 2010 1:26 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FoxAPI Writing Difficulties



Hello List,

We are attempting to use the FoxAPI on our AW51 system, but are
experiencing difficulties in writing values to the DCS.  I am hoping I can
get some suggestions to try or tips that might lead us to solve the
problems we are encountering.

Currently we are using FoxAIS on a OpenVMS VAX system via a X.25 connection
to perform both reads and writes using set based functions such as
QOPEN/QREAD and BOPEN/BREAD/BWRITE.  We are upgrading to an OpenVMS Itanium
system and since the API is not supported for that platform, we are
migrating API functionality over to our Solaris AW51 system.  So far I've
been able to implement all read functionality and it appears to be working
correctly, but am still having trouble performing writes.

So far the only addresses I've been able to use BWRITE on without an
explicit error are those which we already write to with our VAX system.
For these tests we shut down the VAX system so the addresses are not
secured.  In these cases, BWRITE returns 0 and a reterr of 0.  However,
when these addresses are then read with a bread or qread, their values had
not changed.   Our process engineer has provided several other  addresses
but all of these report an error during a BOPEN/QOPEN operation - most of
these report the point could not be found, and others report they are not
an input point.  Out of a large number of addresses only a couple reported
a 'secured' status.

Our process engineer assures me that the addresses we tried covered both
input and output addresses of points.  I've tried modifying several of the
API configuration options, using both CSA and OM methods.  Both setting
exhibit the same behavior, with the exception that the OM method sometimes
causes the program to freeze when we run across an output only point.

I'm completely out of ideas at this point, so I'm looking for at least a
push in the right direction.  Thanks in advance for any advice you can
provide!


Nicholas Mezza
U. S. Steel - Great Lakes Works
Business Services Specialist


_______________________________________________________________________
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




NOTICE - This message and any attached files may contain information that is 
confidential, legally privileged or proprietary. It is intended only for use by 
the intended recipient. If you are not the intended recipient or the person 
responsible for delivering the message to the intended recipient, be advised 
that you have received this message in error. Any dissemination, copying, use 
or re-transmission of this message or attachment, or the disclosure of any 
information therein, is strictly forbidden. BlueScope Steel Limited does not 
represent or guarantee that this message or attachment is free of errors, virus 
or interference.

If you have received this message in error please notify the sender immediately 
and delete the message. Any views expressed in this email are not necessarily 
the views of BlueScope Steel Limited.
 
 
_______________________________________________________________________
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
References:
- [foxboro] FoxAPI Writing Difficulties
  - From: Nicholas J Mezza
Re: [foxboro] FoxAPI Writing Difficulties

Other related posts:
