Your options are:
1) INI-15 - Two CmP-15 modules linked back to back dedicated lines or
modems. X.25 based. Hardware is near end-of-line, but the product has not
been withdrawn. Very easy to configure. Hard to get running. Accesses up to
1000 points from a remote system. The set of accessible points consists of
all C:B.Ps in any of the configured compounds. Up to 250 compounds may be
configured. Remote compound names must be 10 characters or less because the
INI15 adds a two character prefix. Full support for Select/FoxSelect
including all detail display parameters. Message forwarding supported if and
only if you have a PW (Venix) or AP-20 at the remote end. No redundancy.
2) 2 DI-30s - Generally, using Modbus protocol, two DI-30s can be used
to transfer. Hardware readily available. Software used at hundreds of
locations. Requires configuration at both ends of the link. Configuration is
not easy, but no worse than any other gateway. Good for bringing over a few
critical points, but a pain if there is a lot of data to acquire. Alarming
done locally so maintaining alarm limits is an issue. Can be FT is some
cases. Can be run over modems.
3) Ethernet Integration Package - Package developed by the Power Group
in F/M. Uses a TCP/IP connection. Gets remote values and stores them in
local locations (Shared Variables are typical). No alarm support unless you
write the data to an alarm block locally. Be aware of network loading.
4) API-DBM - Package developed by Foxboro Canada. Very flexible with a
good human interface. Used many times for various applications.
Your account rep should be able to get you information on each of these
packages. If he or she does not know who to contact, point them in my
direction.
In addition,
* TxtToSV can be used to read an ASCII file and store the results into
Shared Variables. The file can be transferred periodically from another host
- typically some mini or mainframe.
* I have a script that does a local omget or omgetimp and uses rsh to
do an omset or omsetimp on a remote system. This approach is pretty slow,
but it's quick to implement.
I think that is everything available today, but I might have missed
something.
Regards,
Alex Johnson
10707 Haddington
Houston, TX 77063
713.722.2859(v)
713.722.2700(sb)
713.932.0222(f)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: Brian Bates [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, September 27, 2000 10:20 AM
To: [EMAIL PROTECTED]
Subject: transferring data between two CLANs
Hi All.
Does Foxboro make a gateway that can transfer data between two
separate
C-LAN's?
-Thanks in advance, Brian Bates.
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company.
All
postings from this list are the work of list subscribers and no
warranty
is made or implied as to the accuracy of any information
disseminated
through this medium. By subscribing to this list you agree to hold
the
list sponsor(s) blameless for any and all mishaps which might occur
due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]