Well according to the documentation the NetAPI MFC wrapper should work with FoxAPI & AimAPI. Here is a snip from the Documentation (BO400BJ rev B): ------------------------------------------------------- Chapter 1 Overview The class provides a C++ wrapper around an extensive library of C language calls developed earlier with Networked FoxAPI(tm) software and AIM*API(tm) software. The class provides a thread-safe connection interface, and simplifies the interface requirements, as developers use fewer, more advanced C++ methods, and yet have all of the functionality and access of the earlier APIs. ---------------------------------------------- Thanks Peter ________________________________ From: Lowell, Timothy [mailto:Timothy.Lowell@xxxxxxxxxxx] Sent: Tuesday, April 21, 2009 12:10 PM To: Bruley, Peter T Subject: RE: [foxboro] FoxAPI and AIM*API Well, I think that confirms that your application is not supported using FoxAPI. You're lucky that it reads using FoxAPI, but when trying to write, it crashes because NetMFC is only supported using AIM*API. Looks like you'll have to shell out for an extra AIM*API license. Isn't Invensys great? Tim Lowell Control Systems Engineer Tesoro Petroleum Company <mailto:Timothy.Lowell@xxxxxxxxxxx> ________________________________ From: Bruley, Peter T [mailto:Peter.T.Bruley@xxxxxxxxxxxxxx] Sent: Tuesday, April 21, 2009 7:53 AM To: Lowell, Timothy Cc: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] FoxAPI and AIM*API Hi Tim We also have PI and have had no problems writing into the Foxboro system using v4.3.1 or v4.3.2 of FoxAPI. However the PI api was written using the true FoxAPI C-calls (not the Net-MFC wrapper) The problem we have is a completely different application (not PI) that was compiled with the Net-MFC wrapper that can read from both FoxAPI & AimAPI however can only write to AimAPI. Peter ________________________________ From: Lowell, Timothy [mailto:Timothy.Lowell@xxxxxxxxxxx] Sent: Friday, April 17, 2009 11:21 AM To: Bruley, Peter T Subject: FoxAPI writes Peter, Are you absolutely sure you are running FoxAPI v. 4.3.2? We have v.8.4.2 in Hawaii, and just yesterday, we were trying to do writes from OSI PI, and FoxAPI kept failing. We double-checked our version by using d:/opt/fox/ais/bin/foxtst and selecting option "1229" from the prompt (there is no menu pick for the 1200 series of commands - nice design there, Invensys). This reported that the FoxAPI version we were using was 4.3.1. We had a FoxAPI v.4.3.2 installation CD available, so we went and loaded it on the v.8.4.2 box, and now the writes work correctly from PI. You should verify the version, and if you really are running v.4.3.2, then it looks like the issue is with the netMFC class client application. It reads to me from Alex's e-mail that netMFC class client applications are only compiled to work with AIM*API. At least that's how I read it. Here is the pertinent passage in Alex's e-mail that leads me to that conclusion: "FoxAPI/netFoxAPI using the FoxAPI client which supports OM, Historian, and CSA calls. AIM*API/NetAIM*API using the netMFC client which supports OM, Historian, and CSA calls." I hope that helps you figure out the problem. Tim _______________________________________________________________________ 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