• Not Answered

Undoing old Splitter Block (SPLTR) work-around

A few years back a KB published a work-around for an issue one might experience with a Splitter block - from what I recall and what I see in the module, the containing controller's "Partner Available" parameter transitioning to "off" or false would modify the status of the BKCAL_OUT of the downstream AO blocks (sets the status to 192).

Is it safe to assume whatever bug has been rectified and this work-around can be dismantled? Operations is experiencing some random "shed to manual" events - the error only lasts a second (one scan) and I wonder if the intervening CALC blocks (which normally just pass the "IN" status to the "OUT" status) are occasionally sending a "not invited" (or simply bad) status for some reason. Their execution order does place them "after" the splitter block.

The containing controller (MQ running 14.3.1) has a Control Performance Index of "4" and "5" for the other rated parameters. No other contemporary events (e.g. partial download) appear in the event log, which shows "PIC-84302/SPLTR1" (the containing module) in the Desc1 column and "I/O Output Failure" in the Desc2 column.

Any other thoughts are welcome.