Re: [foxboro] FBM224 PAKOUT Behavior MODBUS
- From: "Wilson, Brad" <brad.wilson@xxxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Sat, 23 Apr 2011 12:19:01 -0400
You can always use the integer value of the packed output and pass it with IOUT.
--------------------------
Sent from my BlackBerry Wireless Device
----- Original Message -----
From: Johnson, David [mailto:David.Johnson@xxxxxxxxxxxxxxxxxx]
Sent: Saturday, April 23, 2011 12:13 AM
To: foxboro@xxxxxxxxxxxxx <foxboro@xxxxxxxxxxxxx>
Subject: [foxboro] FBM224 PAKOUT Behavior MODBUS
Hello everybody,
I have a question relating to using a PAKOUT in manual in an FBM224.
I'm asking because I know the behavior of a PAKOUT when placed in manual is not
the same on the AB FDSIs as a MCOUT behaved in an AB INTEGRATOR 30.
BUT, I do not know if a PAKOUT in an FBM224 exhibits the same behavior that a
MCOUT did in a Modbus Integrator 30. This is kind of important, since I don't
have any way to modify the canned MODBUS program, and BOUTs don't seem to work
with holding registers. (BOUTs only work with coils, is that correct?)
Anyway, they were making use of the bi-directional sets of the MCOUTs in the
old integrator and now I don't know if that will work. I know I could make it
work with BOUTs if I could use them to set a bit in a holding register, but so
far I can't seem to do that either.
Thanks for any help,
David
________________________________
Confidentiality Notice:
The information contained in this message is private and confidential. This
information is intended only for the individual or entity named above. If the
reader of this message is not the intended recipient, you are hereby notified
that any use, review, dissemination, distribution, copying or action taken
based on this message or its attachments, if any, is strictly prohibited. If
you are not the intended recipient, please contact the sender by reply email
and delete or destroy all copies of this message and any attachments. Thank you.
_______________________________________________________________________
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
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person. This email comes from a division of the Invensys
Group, owned by Invensys plc, which is a company registered in England and
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X
7AW (Registered number 166023). For a list of European legal entities within
the Invensys Group, please go to
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.
You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
reception@xxxxxxxxxxxxx This e-mail and any attachments thereto may be subject
to the terms of any agreements between Invensys (and/or its subsidiaries and
affiliates) and the recipient (and/or its subsidiaries and affiliates).
_______________________________________________________________________
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:
