Splitter Block Version 12

Gents

We have a PID block connected to two AO blocks visa a splitter block. 0,50,50,100 out 100,0,0,100. Standard stuff. When one of the AO's is placed in AUTO the splitter block Remains Cascade/Cascade even though the BKCAL_IN_1 in Good Cascade NotInvited.

This is not what I was expecting or belive I have previously seen. Has this always been like this that both AO blocks have to be in Auto/Auto before the splitter block and then the PID block go Cascade/IMAN.

Has anybody seen this before as we are using this for split range temp control and if somebody puts one of the AO's in auto then the PID and the phases do not react and just sit there waiting for temperature even though this will never be achieved.

1 Reply

  • Steve,
    That is the way the splitter block has always worked. As long as at least one of the downstream blocks is in CAS (or RCAS IF USED), the splitter block will stay in CAS (or RCAS IF used). You could use and ACTION block to force both AO blocks to AUTO if one is taken out of CAS or RCAS.
    James