Re: [foxboro] FBM232 with Modbus Device Driver
- From: "Johnson, Alex P \(IPS\)" <alex.johnson@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 16 Apr 2007 12:51:15 -0400
I don't have a solution to your problem, but I'm curious as to the
choice of FBM.
Why did you use the FBM232/233 (Ethernet) vs. FBM230/231 (Serial;
RS232/422/485)?
Regards,
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of dave.caldwell@xxxxxxxxxxxxxx
Sent: Monday, April 16, 2007 11:43 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FBM232 with Modbus Device Driver
David,
Thanks for the reply. We've come up with two work-arounds that seem
similar to what you suggest...
Since the FBM232 is a 10/100 enet device and the Fireye is 4800 baud
RS-485 we have used an enet-to-RS485 io gateway made by Advantech called
Adam 4572 to interface between the two. Work-around #1 was to take 3
Adam's (each with its own IP address) and connect them to a single
FBM232 (requires one ECB200). This allowed us to create 3 separate
device ECB201s. Since we are communicating with separate devices
(although the same RTU), we get separate read queries as desired. To
complete this scheme, we tied the outputs of each ADAM's RS-485 together
and to the Fireye. This is kludgey, because there are 3 Modbus masters
on the same RS-485 bus, but it mostly works.
Work-around #2 requires 3 FBM232s tied into the same enet network as the
Adams for the 7 Fireyes on site. FBM232 #1 would make the read request
for the first 6 registers from all 7 RTUs. FBM232 #2 would make the read
request for the next 3 registers from all 7 RTUs. FBM232 #3 would make
the read request for the last 6 registers from all 7 RTUs. Here we would
have 7 separate ECB201s for each FBM232 (ECB200). This one we haven't
tried, but believe it should work.
If you can think of another work-around we've missed please let us know.
We don't much like either one of the ones we've come up with so far. ;)
Thanks,
Dave
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of David Johnson
Sent: Monday, April 16, 2007 11:14 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FBM232 with Modbus Device Driver
At 10:01 AM 4/16/2007, you wrote:
>We are attempting to read Modbus data from a Fireye 110 Flame Monitor
>System with EPD 160 Programmer ...
You have my sympathy. I have also had to interface to these beasts=3D20
and found fireye's implementation of modbus to be particularly brain
damaged.
I have not had to use the newer modbus FDSI with these yet, but have=3D20
used it for some other applications. Would it not be possible to=3D20
make separate transaction files and use them in the different=3D20
compounds. I don't know that this would work, but it should force=3D20
the reads to be only what you want.
Regards,
David
=3D20
=3D20
_______________________________________________________________________
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
=3D20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D20
=
=
_______________________________________________________________________
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=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=
Confidentiality Notice:
The information contained in this electronic message and any attachment(s) =
to this message are intended for the exclusive use of the recipient(s) and =
may contain confidential, privileged or proprietary information. If you are=
not the intended recipient, please notify the sender immediately, delete a=
ll copies of this message and any attachment(s). Any other use of the E-Mai=
l by you is prohibited.
_______________________________________________________________________
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
Other related posts:
