[foxboro] Modbus Communications
- From: Scott Matus <Scott.Matus@xxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 29 Sep 2008 16:24:07 -0500
When using a IOUT block can you disable/ignore the readback from the external
device?
We are trying to communicate via ModBus to a Atlas Copco Compressor using an
FBM224. The compressor came with its own controller called a Elektronicon, but
it is proprietary so a device called a Combox-S sets between the I/A system and
the compressor. Everything works well with the exception of registers
42001,42002 and 42004, which use a function code 06. Problem is that no matter
which one of these registers send a request(in which the compressor does
respond to correctly), only 42001 gets a readback, and it is the value that was
sent by the other register. Atlas Copco is telling us that these registers in
the Combox-S use a shared register and the Foxboro System needs to ignore the
readback. If this is true is this normal? There are other registers
41062,41062,41064,41065 that also use the function code 06 that work as what I
call normal, only the register that sends the request gets the readback. When
setting up the transaction table there is a selection for WRITE ONLY and one
for READ/WRITE. When selecting WRITE ONLY it does not establish communications
with the Combox-S.
_______________________________________________________________________
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: http://www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
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: http://www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
- Follow-Ups:
- Re: [foxboro] Modbus Communications
- From: Goldie, Shaun S
- References:
- Re: [foxboro] One IND block per compound -- still true?
- From: Corey R Clingo
- Re: [foxboro] One IND block per compound -- still true?
- From: Sascha Wildner
Other related posts:
- » [foxboro] Modbus Communications
- Re: [foxboro] Modbus Communications
- From: Goldie, Shaun S
- Re: [foxboro] One IND block per compound -- still true?
- From: Corey R Clingo
- Re: [foxboro] One IND block per compound -- still true?
- From: Sascha Wildner