Re: [foxboro] Modbus Communications
- From: "Goldie, Shaun S" <Shaun.Goldie@xxxxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 30 Sep 2008 14:37:02 +1300
I may be mis reading your problem but you can have lots of transactions
So 42001 can be RW with the others write only
Note transaction rates are read rates all writes happen straight away
Some devices wont alow span read over non used registers creating the
need for even more transactions or write single commands.
One thing to comment on here is the 224 gives a lot more control over
comms than a FDSI FBM so its more likely to go on a 224
Shaun
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Scott Matus
Sent: Tuesday, 30 September 2008 10:24
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Modbus Communications
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 a
nd 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
NOTICE - This message and any attached files may contain information that is
confidential, legally privileged or proprietary. It is intended only for use
by the intended recipient. If you are not the intended recipient or the person
responsible for delivering the message to the intended recipient, be advised
that you have received this message in error. Any dissemination, copying, use
or re-transmission of this message or attachment, or the disclosure of any
information therein, is strictly forbidden. BlueScope Steel Limited does not
represent or guarantee that this message or attachment is free of errors, virus
or interference.
If you have received this message in error please notify the sender immediately
and delete the message. Any views expressed in this email are not necessarily
the views of BlueScope Steel Limited.
_______________________________________________________________________
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
- 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
- [foxboro] Modbus Communications
- From: Scott Matus
Other related posts:
- » Re: [foxboro] Modbus Communications
- 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
- [foxboro] Modbus Communications
- From: Scott Matus