DCAF editor and relation to actual VI's

[JTB]

I'm struggling to put together some code based off of the temperature example.  I can see the association between the UI and the derived channel definitions as defined in User Interface.vi.  Tags get exposed via the UDP broadcast between the UI and the Simulation.  But how are the tags associated with controls or indicators on the Simulation side?  Do I have to run the Static Module scripting to create my own logic with it's own defined inputs/outputs?  Where's the "UI Configuration" for the Simulation side defined? 

Just a newbie. I've watched and read all the excellent materials published thus far.   🙂

[MattP]

Hello!

In the RT Temperature Controller example, the processing performed by the Simulation engine is defined by the the Temperature Controller Logic module.  This is a module created via the Static Module scripting utility to wrap the inputs/outputs of a particular subVI in a DCAF module so its inputs and outputs can be mapped to tags in the DCAF editor.

To make your own module (to be something other than a temperature controller), you would indeed need to create a new static module (use the DCAF Static Module project template as a starting point) and drop in your logic in User Process.vi.