CAN J1939

• 

  Jamie Villeneuve

  April 10, 2019 20:28 (Edited April 10, 2019 20:29)

  Storyboard is designed around the concept of abstracting the UI from the system logic to provide a clean architecture. With Storyboard the standard solution for this would be to use a separate process or task to read the CAN data and then use our SBIO messaging to send the UI related data to the Storyboard engine.

  You can find the SBIO documentation for 5.3 here:
  https://cranksoftware.com/cranksoftware ... /ch26.html

  Regards,
  Jason

  0
• 

  john.houle

  October 13, 2023 17:38

  Can the separate process be a Qt application that would write to the storyboard IO channel?

  0
• 

  Jamie Villeneuve

  October 13, 2023 17:49

  Hi John,

  Absolutely. 

  Storyboard IO is the mechanism to communicate with external device drivers, third-party applications, etc. Here is a tutorial on Storyboard IO along with a sample to follow along.

  Storyboard IO Feature and Tutorial
  https://www.youtube.com/watch?v=4qoGkXDUQ08&t
  The sample to follow along within the video is called ThermostatIO and is located in the Samples folder in your Storyboard installation. It also includes the backend source code so you can see how to send/receive data/events.

  Sending and Receiving Data with Storyboard IO
  https://support.cranksoftware.com/hc/en-us/articles/360056943692-Sending-and-Receiving-Data-with-Storyboard-IO

  Storyboard IO API
  https://support.cranksoftware.com/hc/en-us/articles/360057414271-Storyboard-IO-API

  Thanks,

  -Jamie

  0
• 

  john.houle

  October 13, 2023 18:28

  Or to bypass Qt all together, perhaps following this guide would be the way to go. 

  J1939 Documentation — The Linux Kernel documentation

  0

Please sign in to leave a comment.