Simulink Design Verifier Dead Logic

I have recently used simulink design verifier to check my state machine model. And some dead logics are detected. But in fact this dead logic is resulted from the execution order. Here is an example: State A is active when transition 1 [a>20] is true, State B is active when transition 2 [a<=20] is active. And the execution order is that first the transition 1 will be checked and then transition 2. My Simulink Design Verifier told me that transition 2 can not be false. The reason behind is that every time when a>20 the transition 1 will be firstly checked and fulfilled. The system goes directly in state A. So the transition 2 will not be checked.

Now the model should be optimized to avoid this error detection with Design Verifier. Has anybody ideas?

[Pat Canny]

What is the possible range of values for your variable a?

[galaxy]

Yes, I have same problem.

Red line is dead logic, data type of input1 and input2 are int16.

Could you please explain to me??

Answer 1

[Nikhilesh]

Please have a look at the follwing discussions.

Why does Simulink Design Verifier only find dead logic when I swap the order of my logical operands? - MATLAB Answers - MATLAB Central (mathworks.com)

Simulink Design Verifier Dead Logic - MATLAB Answers - MATLAB Central (mathworks.com)