Using Input Ports as State Control Dependencies - 3 Cases
Feature Description
NOTE:States do not require a Control Dependency to be functional in eXpress
Case 1: A OUT is only a State Control Dependency (State is on when A IN is present) - "Passive mode setup"
(B OUT net to flag is in Passive mode showing B IN upstream functions on B OUT Net Functions as seen above)
State Setup
State Control Dependency = EN (A OUT)
Resulting Test (EN is a State Conrol Dependency but not a functional dependency of B OUT - No upstream A path coverage)
Here the diagnostics will include A as detected because it is a State Control Dependency even though there is no upstream coverage. (Will be in Ambiguity with B)
Case 2: A OUT is both a State Control Dependency and a functional dependency of B "Active mode setup"
(B OUT net to flag is in active mode showing single function on B OUT Net Functions as seen above)
State Setup
State Control Dependency = EN (A OUT)
Same as Case 1
Resulting Test (EN is a State Control Dependency and a functional dependency of B OUT)
Here the diagnostics will include A. It is both a functional dependency and a State Control Dependency and there will be upstream coverage.
This approach will also result in the following Error Message
Control port used as both dependency and State Enable will cause an error message.
This "Possible Error" level Error Message will not preclude diagnostics from running.
Case 3: No State Control Dependency (EN is only a functional dependency of B OUT) "Active mode setup"
This result is identical to Case 2 above except there will be no error message generated.
Reccomendations:
If A is a sensor that is only used for State Control Dependency use "Case 1" as Sensor isolation would require independent sensor calibrationanyway.
If A is a Computational output or other circuitry use "Case 2" or "Case 3"
