Re: [foxboro] Foxapi delay

This may open up a can of worms, but I am beginning to believe that =
using
FoxAPI isn't the best method for implementing programs that need to read =
and
write Foxboro data via C calls.

Although Foxboro/Invensys claims that FoxAPI is the best method for =
this, I
have found it very buggy, and I have had many many problems using it.
One example: On one system, there is an installed yet unrelated Foxboro
product, Connoisseur, which closes our FoxAPI lists, causing conflict.

I have gone back to using the old core Object Manager calls (which are =
well
documented in the "Programming" section of docs), and I find:
1. Much better performance.  I can write to Foxboro values many times =
faster
than using FoxAPI
2. Much better flexibility, like I can write the smurf/OOS status to a
block. =20
3. I don't run into the issue of other FoxAPI programs competing for =
FoxAPI
resources. =20
4. By using core OM calls, I am not tied to running the program only in =
an
AP/AW.... I can also use the program in a WP.
5. The time to startup a new list is near nothing with core OM calls
6. If dynamically adding a new variable to read or write while the =
program
is running... With FoxAPI you would need to close the current list, and
start a new one, which is very time consuming and not real time; where =
with
core OM calls, you can do the same fairly quickly and close to =
real-time.
7. The core OM calls really have not changed much since the beginning of =
the
IA system.  Changing the OM would require Foxboro to recode all their =
core
IA apps.  Thus I am led to believe that the core OM calls will be around
forever.

I realize that there are cons to using core OM calls over FoxAPI, but I =
have
been "bit by the dog" way too often to be friendly towards it.

Mark Dumond
Sr App Engineer
FeedForward, Inc.

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
On
Behalf Of Miacca Marcelo (Grupo Pittaro)
Sent: Thursday, September 23, 2004 3:22 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Foxapi delay


Hi, we are using foxapi calls in a C program....

scopen...
bwrite...
clsset...

Any time we run this program it takes 14 seconds for the three =
statements.
scopen uses read write access.

This time is normal???
Can we decrease this time???

Thanks in advance...

Miguel




=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20

 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: