We currently use the Elsag-Bailey semAPI software running on WindowsNT Server to provide an interface from Citect to Bailey via a SCSI connection.

Now we want to upgrade our server hardware and also move to Windows 2000/2003 Server.

semAPI doesn't appear to work on Windows 2000 and above. We are using version 2.1. Does anybody know if this version or a newer version will work on Windows 2000? Is anybody using it? I haven't recieved any replies from ABB.

 

From : H.V.VASAVADA Date : 17th March, 2009

I have repeatedly posted on this forum that for such a legacy system, best way is to install a proven OPC Driver and an open MMI packages. Normally MMI package suppliers always upgrade there version very fast when ever Windows is upgraded. This is so because this is their primary business. Once the driver is supported by MMI packages, it becomes all the more easier to configure the tags and graphics. This is easy and effective solution without any change in hardware.

As a consultant in instrumentation, I did such conversions for the clients.

In case you want any more information, you may mail me on
[email protected]

 

As the above poster has mentioned, in most instances you can connect directly to Bailey using an OPC Server like this one: http://www.matrikonopc.com/opc-drivers/164/base-driver-details.aspx

Adriel Michaud
MatrikonOPC

 

There are a number of OPC IO Servers that do not need to use SemAPI, look at Matrikon or RoviSys. We used the Matrikon software with Wonderware, using the SCSI unterface, and found it quite good.

Trevor.

 

Yes, we already use a 3rd party OPC Server at other sites to perform the same function so i'm not looking for alternative solutions to my problem, but thank you for your reply. So before we are focred to spend $ to do that, i would just like an answer to my original post.
Thank you.

 

Hi, we did look at upgrading semAPI as we went from a NT4 server to Win2k server and was not able to get it to go, but at the end of the day we would have been up for a cost there anyway, and in our case we still had two communications packages.
Cheers,
Trevor.

 

Have it currently running ok on W2k Server have tested 2003 but only issue at the moment is if running in redundant mode cannot mix 2k and 2003. Awaiting to shutdown units and change all to 2003. Contact ABB they will give you latest information.

Rob

 

Hi,
but in the end did you manage to get it to work on w2k? How?

73 Fabio.

> we did look at upgrading semAPI as we went from a NT4 server to Win2k server <

 

I'm testing semapi 2.1 with scsi interface on w2k. I can configure the interface with iciconf and restart ici, but the comunication don't start.

How did you get it to work?
Bye Fabio