Recent Posts51
PLUS+1 GUIDE / Re: A system with multiple controllers - GUIDE project architecture
« Last post by Matt on October 06, 2025, 05:03:53 PM »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.
haha)
), you can find "Cloud Set Value". Using this component, and leaving the cloud connection parameter set to false, serves the same purpose as a regular set parameter, with namespace tagged on the front.