We use a combination of MCIN/MCOUT and AIN/AOUT blocks in an AB Gateway. It is redundant, but for individual alarms, CIN blocks may be connected to MCIN blocks. Chuck Jones -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Jaime Claramunt R. (Inforsa) Sent: Tuesday, May 24, 2005 7:39 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Foxboro I/A interface with PLC5/30's About the way to adress points... are you using MCIN/MCOUT, PACKIN/PACKOUT ? and if it's so, how do you treat individual alarming in DCS for each signal ? We have some similar AB-DCS comms (old ABStation, and INT30-KF2), but we are usung CIN/COUT because of the alarm/acknowledge capacities... Operator disliked those blocks with 8 alarms because the ack is for all 8, not each one separatelly (BOOLALM). So we cannot optimize loads and/or add more points. Do you think using MCIN/MCOUT in integrators and MCIN+CIN in CP is a feasible approach ? (more pear-to-pear, though) Jaime Claramunt Inforsa ***************************************************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you have received this email in error please notify the sender immediately. Please note that we reserve the right to monitor and read any emails sent and received by the Company in accordance with and to the extent permitted by applicable legal rules. ***************************************************************************************************** _______________________________________________________________________ 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