Hello List, Does any one have any experience with the Matrikon OPC Server for Foxboro I/A? I am interested in the following: * Whether or not you are using the FoxAPI or OM API version? * Are you on Solaris or Windows? Which model AW? * Are you on nodebus or MESH? * What is your I/A version? * How many points collected, update frequency, and for what purpose? * Has the server been reliable? o How long has it gone without issue? o How often do problems arise? o What has been the symptoms and sources of trouble? * Are you using primary, distributed load, or stand-by server option? * Are you using COM (client local to server), DCOM, tunneling, or other? * Are you specifying a delta value and a scan rate for each point? o If so, does this mean the OM scanner in the remote station will scan .......the OM list for changes greater than delta every x seconds, and .......report a change to the station requesting the object? o Is delta specified in engineering units? o Is scan rate in seconds? o If no attribute is specified what are the defaults? * Is there a way to make the FoxAPI or OM API AW redundant? In other words, should something happen to the collector AW can a backup AW be automatically brought on-line to collect the points for the OPC Server? Thanks, Dave _______________________________________________________________________ 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