Start recurring timer on boot.

Comments

8 comments

  • Avatar
    Jacob Billeter

    Hi Jeff,

    From the applications manual, there is an event called Screen.ScreenReady

    1
    Comment actions Permalink
  • Avatar
    Justin Eldridge

    This is what we do: 100ms timer loop that starts as soon as the CPU boots

    1
    Comment actions Permalink
  • Avatar
    Jeff Paluck

    Thank you both, that's very helpful!

    0
    Comment actions Permalink
  • Avatar
    Jacob Billeter

    Do that same state machine but include the Screen.ScreenReady first.

    1
    Comment actions Permalink
  • Avatar
    Jeff Paluck

    Hi Jacob, would you please show how you were able to use the Screen.ScreenReady event as the transition in the state machine you posted?

    0
    Comment actions Permalink
  • Avatar
    Jacob Billeter

    Uncheck the "auto create" and then choose Screen.ScreenReady

     

    1
    Comment actions Permalink
  • Avatar
    Jeff Paluck

    Thank you!

    0
    Comment actions Permalink
  • Avatar
    Jeff Paluck

    Caveat for anyone who finds this thread:  After the ScreenReady event fires, the system still needs a moment before it sends any CAN messages.  I tried using this event to send some initial configuration data to a controller, and the first message in the series wouldn't get sent.  (I think it's due to the display doing the J1939 address reserve sequence at this moment)  I add a 2 second delay after the screenready event fires and that seems to be enough time that a message won't fail to send.  IF anyone has a better method for knowing when the display is fully ready to communicate, I'd love to hear it.

    1
    Comment actions Permalink

Please sign in to leave a comment.