Assuming this a UDC 3300E (E = expanded/enhanced model) that does 2 PID loops in one model, with a model number like:
DC330E - Kx - 2 D/E/G/H 3 - xx - xxxxxx - x
- 2nd character in 3rd field can be any of the alpha characters, any of which indicates 2 loops of control
- if the 3rd character is 0, then you need to purchase a digital input card (I suspect parts are still available)
- if the 3rd character is 3, then a digital input card was factory installed
I've never done this action on a two loop controller before, only on a single looper. So, whether the DI actions are unit-based or loop-based is conditional on how the factory made it, and the manual isn't exactly clear on the point.
There are two digital inputs (on the DI option card), each is assigned to a respective loop, when the controller is in 2 LOOP mode:
(UDC 3300E manual, pg 54, pdf)
DIG IN 1 Digital Input 1 Selections
NOTE: DIG IN 1 applies to Loop 1 when 2 LOOPS or CASCAD is configured.
DIG IN 2 Digital 2 Input Selections
Same as DIG IN 1
NOTE: DIG IN 2 applies to Loop 2 when 2 LOOPS or CASCAD is configured.
A digital input state change (when DI input is shorted by a dry contact closure) can force a full scale output value through one of two techniques, when the digital input's action is configured to either:
MAN FS
Unit goes to manual mode, output goes to the failsafe value.
Failsafe value has to be configured for = whatever value (%) which = 20mA on the output. (o or 100; depends on action, direct or reverse)
or
ToAout
Output is forced to value set at control prompt “AUTO OUT” when controller is in automatic mode.
A potential problem with setting Auto Out to a value = 20mA is that that's what the output will immediately go to on a cold start power up. So make sure that a 'cold start' can tolerate a 20mA output condition. The PID calculation immediately affects the output value, but 20mA might not be a reasonable cold start condition and slow responding PID terms might not be what is needed on a cold start.
I suspect that both MAN FS and ToAout are both loop actions (affecting only the loop the DI is associated with) but I can't guarantee it. MAN FS could well have been interpreted as a unit action, affecting both loops, or just a loop action for the specific loop that the DI is tied to. (I don't have a dual loop unit to play with to find out).
The manual is about a 600Kb file, so it won't post here (300Kb limit). Private message me with your email if you need a copy.
Dan