• Not Answered

Fieldbus outputs are frozen

Hello,

We have a DeltaV system at our school for student training, and last year we upgraded to version 13.

All I/O is working except the Fieldbus output devices, temperatures are ok, but the output from the Fieldbusblock is frozen

I copied the channel numbers exactly from the old working system, commisioned it, and there are so far as I can see no configuration errors. 

This is the Control block 

You can see that the input is 73,79 % and he output stays at 51,13 %

I have downloaded the fieldbus device also.

I am out of options , please help ? thank you !

 FYI All Fielbus devices, FT-2200 is damaged

5 Replies

  • The first problem you have is with the configuration of the module FIC-2100, you need to have a wire from the AO1/BKCAL_OUT to the PID1/BKCAL_IN. Try this and see if this resolves your issue.

    If still a problem please indicate or show the statuses on these parameters as well as what the target and actual modes are on the AO1 block.
  • In reply to Matt Stoner:

    Thank you Matt, I wil try it tomorrow !
  • In reply to Matt Stoner:

    The Bkcal connection from AO to PID is important as it establishes the cascade connection that initializes the PID to the AO value and prevents wind up of the PID when the AO block is not in CAS mode.

    The AO shows its CAS in at 73% while the AO out is at 51%. This seems to indicate the AO block is not in CAS mode. Without the BKCAL connection the PID OUT would be in GoodNonCascade and a transition to CAS mode will bump the AO from 51 to 73%. You have to check the Target and Actual mode. The TARGET may be in CAS, but if the ACTUAL is in AUTO or MAN, that would explain the disconnect of the AO from the CAS_IN.

    The AO block indicates a BLOCK_ERROR with the yellow "?". This could be that the AO has SIMULATE enabled, some other issue. SIMULATE enabled would not explain the difference in CAS_IN to OUT. You should look at the BLOCK_ERR parameter of the AO block to determine if this is related to the AO not following CAS_IN.

    But you certainly need to connect BKCAL_OUT to PID/BKCAL_IN to have the proper initializing behavior of the control loop.

    Andre Dicaire

  • In reply to wjdreves:

    Hello Matt, the loop is oke now, thanks for your assistance

    regards Wim
  • In reply to Andre Dicaire:

    Hello Andre, thanks for your assistance, the loop is oke now

    Regards Wim