ADAPT Blocks and Significant Change Specifications
Can the significant change specification (S7 for FC 30, S8 for FC 222, S9 for FC 223, S30 for FC 177) be adapted? If it can be and does not crash the controller, does it work?
A simple way to prove it works would be to import the exception report using an AI/L or DAANGI/L block and plot both the raw value and the imported value.
The user would like to have very precise display in the HMI of an output value from a Station block FC 80 when the station is in manual, but not load the system down the same way when it is in auto. The client says that the operator wants to see the new output on the graphic immediately instead of waiting up to a minute for the TMax timeout. 75.03% is not the same as 75.01%, right?
Actually testing this in a test module would be very useful. There probably are many situations when you would like to provide coarser or finer resolution of exception reported values and this would do it, if it worked.
A simple way to prove it works would be to import the exception report using an AI/L or DAANGI/L block and plot both the raw value and the imported value.
The user would like to have very precise display in the HMI of an output value from a Station block FC 80 when the station is in manual, but not load the system down the same way when it is in auto. The client says that the operator wants to see the new output on the graphic immediately instead of waiting up to a minute for the TMax timeout. 75.03% is not the same as 75.01%, right?
Actually testing this in a test module would be very useful. There probably are many situations when you would like to provide coarser or finer resolution of exception reported values and this would do it, if it worked.
Asked 1 month ago
Voted best answer
1
Hi Geoff,
I haven't tried this in a long while but see no reason for the FC behaviour to change. As of Composer 5.0, attempting to adapt the sig change spec will fail for FC30 (not tunable), and with BlockIO/S800, FC222 and FC 223 will also fail (go to error with incorrect data type, same as trying to adapt an alarm setpoint). FC177 spec 30 can be adapted of course but using S15 of the DAANG to force an exception report when required also works well (more weller even, imho).
Another solution might include removing the 2 least significant decimals from the CO value on the HMI😉.
Regards,
Alan
I haven't tried this in a long while but see no reason for the FC behaviour to change. As of Composer 5.0, attempting to adapt the sig change spec will fail for FC30 (not tunable), and with BlockIO/S800, FC222 and FC 223 will also fail (go to error with incorrect data type, same as trying to adapt an alarm setpoint). FC177 spec 30 can be adapted of course but using S15 of the DAANG to force an exception report when required also works well (more weller even, imho).
Another solution might include removing the 2 least significant decimals from the CO value on the HMI😉.
Regards,
Alan
Answered 1 month ago
Add new comment