A system with multiple controllers - GUIDE project architecture

[Lukey]

How do others go about managing multiple controllers for the 1 system?

Typically for a system with multiple controllers I have a GUIDE project for each controller, this is difficult to manage.
When we can use the IO modules we do so, but they do not always suit.

I thought using MODULES in a guide project would allow multiple controllers however this is not the case.

Is their an easier way?

[Fredrick]

In multi-ECU systems, I typically designate one ECU as the primary controller, while the remaining units operate as distributed I/O modules. The control logic resides entirely within the primary ECU and is communicated via CAN to the secondary ECUs

[Matt]

When we can use the IO modules we do so, but they do not always suit.

I have also been creating a GUIDE project per ECU, then writing CAN TX/RX to communicate among them.

I'm curious what the additional controllers are providing that the IO modules don't already provide. Is it just a need to distribute logic? So far I've tested one MC and several IO (combination of IOX and OX) and didn't seem to hit a roadblock that would require a controller instead of an IO module.

In multi-ECU systems, I typically designate one ECU as the primary controller, while the remaining units operate as distributed I/O modules. The control logic resides entirely within the primary ECU and is communicated via CAN to the secondary ECUs

In the case of a controller, a display, and IO modules, I've taken a similar approach. However I have found it tedious to write the CAN messaging between the controller and display whereas the IO modules come with that already included.

[Lukey]

I have had to use controllers when using some library blocks that only work with controllers.
1 example was a Danfoss orbital motor rotary sensor, the feedback i required from the input was the .per, which from memory is time between pulses, this function is not available on the expansion modules.

My program architecture is to always have 1 master/controller and the rest of the modules being of first preference expansions or else controllers(via rx/tx) that are simply remote I/O.

The issue i have is having multiple controllers requires multiple projects, this is tedious, I was hoping for a better way.
I thought the Modules feature of GUIDE would address this, however i have yet to find a practical application where i would implement different Modules in 1 GUIDE project.