On the MPC20 display, the state timer is skipping counts. Using a stopwatch to test the accuracy of the state timer, one minute of elapsed time as shown on the MPC20 panel is anywhere between 45 seconds and 50 seconds. The design was built with 2.7.10439, OS 5.2

Hi jajorgenson,

We really need more details to determine where the problem could be.

What are the states? Since you refer to this as a state timer, what are the conditions to transition into the state that starts the timer? Does it expire or does a condition stop it? Is this the only place where the timer could be started/stopped?

If this is with the standard, uncustomized MPC-20 configuration, could you provide the details so I could find the states and timer in the configuration?

Any other details you can provide to help recreate the problem.

Thanks!

Sara,

I have modified the MPC-20 design that you previously posted to the dropbox with Tim Springer. That design has a state timer display on the main page and on the multigauge display pages. This is the state timer that I am monitoring.

I have timed the state timer countdown and witnessed that the state timer on the MPC-20 display is skipping counts. For example, in the Spindown state, the Time Spindown variable is set to 90 seconds, but the state timer on the main page skips multiple counts and zeros after about 75 seconds.

If you wish, I can reload the configuration that you loaded in the dropbox to see if the state counter is accurate. I have not modified the Engine State Timer Tick activity diagram or the Engine AppEvent timer, so I believe the problem would also occur on the configuration you provided to me on July 17th.

Joel Jorgenson (jajorgenson)

Hi Joel,
That is a good idea. It might help us focus on where the issue could be. If it is in the original config, then we can go from there.

Hi Joel,

You are correct, it looks as though certain conditions will cause an early out of the timer. Such as engine temp < Start temp, Engine Start Type is not started and the current engine state is stopped, standby, stabilize or prestart 1. There are other similar conditions.

If you have found that the timer is finishing early when it should not, then I need the information about your conditions and the steps you take to recreate the issue.

Thanks!

Sara,

I have seen the state timer skip counts in all engine states (Stopped, Stabilized, Running_Loaded, .....). I have not correlated any activities that trigger or suspend the skipped counts.

I tried to change the software from the <State Timer = State Timer - 1> to the following:
<State Timer Temp = State Timer>
<Fire 200 ms timer>
<State Timer = State Timer Temp - 1>
I believe this might have improved the stability, but am not positive that this resolved the issue.

Joel