Using Simulink Code Generation as a backend

We at GOcontroll recently started using Crank Storyboard for our new Moduline Display. Since we mainly use Simulink to program our controllers  I wanted to make a way to interact with the GUI from a Simulink model.

This is the result of that desire, it is currently still in pre-release but I've made a working model for the ThermostatIO demo.

It will eventually be available through the Matlab Add-On explorer, but while in pre release it has to be downloaded from the releases page. Once installed 3 blocks become available:


Crank receive channel: This is the block where all the incoming events (from the backends perspective) get pulled out of the channel, for every event present in the channel it will execute a function call. So hook this function call up to a function call subsystem, in this subsystem is where block number two comes into play. There can be only one of these blocks per receive channel.


Crank deserialize event: This block actually makes the data contained in the event available and also does another function call, only the data could be enough, but there are also events without data, without this function call output it would not be possible to act on this event.


Crank serialize event: This block sends events to the GUI, place this block, configure it accordingly, and the inputs will automatically adjust to what is specified in the event description header file.

Currently this blockset only works for targets that use the elf executable format i.e. targets where you need greio.a. It is primarily used/tested with our toolchain, but it should work with any toolchain that is appropriate for the target.

One more goal would be to control a GUI through the tcp/ip interface.

0

Comments

0 comments

Please sign in to leave a comment.

Didn't find what you were looking for?

New post