Jeff, Verify that PRIBLK is set correctly in each block. It should be TRUE (1) for all but the most Primary (upstream) block. Because AIN is not a Primary block this means the SWCH bloc should have PRIBLK = 0. What do the other downstream blocks (BIAS, AOUT) do when SWCH is tracking? Is the SWCH block TOGGLE set to look at the AIN Input? Thomas J. Badura Plastics Engineering Company 920-458-2121 x3366 tbadura@xxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Hurt Sent: Tuesday, July 14, 2009 9:33 AM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] BCALCI/BCALCO question We're building a control loop that looks like this: AIN -> SWITCH BLOCK -> BIAS BLOCK -> AOUT The connections are made automatically in the IACC. When the BCALCI, BCALCO, BCALC1, BCALC2 connections are made, there is no output out of the switch block and it indicates it is tracking. When the BCALC connections are removed, everything works correctly and the switch block no longer indicates it is tracking. Any thoughts as to why it doesn't work with the BCALC connections? Thanks, Jeff _______________________________________________________________________ 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 _______________________________________________________________________ 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