Some signals in the configuration can have an extra attribute, "quality" in addition to having a value. This quality can be tested, and used to determine the validity of a signal.
As of DBDOC 10.4, lines representing signals on CAD and CLD diagrams indicate the presence of quality on a signal by being blue or purple.
When live data is not active for a document, a blue line indicates that a signal has quality, but not whether the quality is bad or good (since that depends on the live quality value). When live data is enabled for a document, a blue line indicates that quality is present, and also that it is good. Bad quality is indicated with a purple line. When live data is enabled but stale, these colors are dulled to differentiate from fresh live data.
Not all signals have a quality attribute. The outputs of the following function codes do have quality attributes, so they may have quality.
Function Code | Outputs with Quality (N is the base block number) |
Outputs without Quality (N is the base block number) |
FC25, FC26, FC27, FC28, FC29, FC30, FC41, FC42, FC43, FC44, FC45, FC48, FC67, FC95, FC96, FC97, FC114, FC121, FC122, FC131, FC145, FC150, FC158, FC177, FC178, FC179, FC182, FC193, FC194, FC211, FC212, FC216, FC222, FC223, FC224, FC225, FC229, FC241 | Single Output | none |
FC46, FC63, FC64, FC84, FC137, FC138, FC185, FC186, FC221, FC227 | All | none |
FC55 | N through N+5 | N+6 through N+9 |
FC79 | N through N+8 | N+9 |
FC102, FC103, FC109 | N | N+1 through N+3 |
FC104 | N | N+1 through N+2 |
FC130 | N through N+1 | N+2 through N+3 |
FC132 | N through N+4 | N+5 |
FC149 | N through N+6 | N+7 |
FC205 | N through N+7 | none |
FC206 | N through N+7 | none |
FC207 | N | none |
FC210 | N+1 through N+32 | N and N+33 through N+35 (This is the only function that has quality, but not on the base block). |
FC228 | N | N+1 |
FC230 | N through N+13 | N+14 through N+16 |
CLIF FC239 | N through N+13 | |
CLIF FC240 | N through N+14 | |
FC242 | N through N+15 | N+16 |
FC247 | N through N+11 | N+12 |
FC248 | N through N+19 | none |
Note:
Related error situations DBDOC routinely checks for: