I'd be a little surprised if you were overloading the display's processor, but three PI loops might be doing it.  You might check to see what your ExecTimeWork, ExecTimeOut. amd ExecTime are set to.  Maybe you need to request a slower processing time (ExecTimeOut)?

Thanks acmall, found my issue was how i was addressing the RGB HEX Color code, I failed to put the required 00 on the end thus my graphic wasn't displaying correctly.

For others to reference see my code below, thanks!

Hi Tom yes I put checkpoints in the program for the PI loop output and then the PWM output of the loop, no issues there, constant output as desired.

I found that if I set the DefOutputValue (which is what the I/O module should do if comms are lost) of one of the MFOutputs to 1/True.
Consequently I then did not have any Pulsing/Flashing of that output, proving that it was a comms issue.

So then on a whim I changed the default settings of TimeOut_Outputs from 100 to 500ms.
Problem solved; kinda, I find on power up of the display and i/o module the outputs pulse for a few seconds, I'm assuming this is as the display and I/O module are establishing comms, so obviously there there is lots of traffic there, causing a >500ms delay on the output comms.

Unfortunately I cannot find any API documentation on the IOX024 module that elaborates further on the default settings.
I checked similar MC024 API documentation but there is nothing similar/referencing to TimeOut_Outputs

I don't believe that I could/should be overloading the DM430E processors with the program, is there anyway to test/tell?
Bus load is on average 6% as viewed with the service tool connected.
The screen definitions I believe are simple, only a pressure feedback numerical and bar graph display and numerical pressure input value,
I have similar on 3 different screen definitions, each controls/inputs to 3 PI loops and thus 3 PWM outputs.
Or is that pushing the envelop for the DM430E capabilities?

As G3 was mentioning you could use a comparison on the source voltage.  For most controllers that'll be C1P2.voltage, and you could just check to see if it's greater than 20V to determine which voltage source you've got.

No, you can't connect the signals as you've done in that image.  You will want to use either a Boolean Switch or a couple of Value Connect components along with that comparison that I mentioned.

If you put a checkpoint on the PI loop output is that reading steady?  If not then I guess post your PI loop logic here.

If so then are the repetition times and timeout time settings for your I/O module all set to default, or might something be off?  See attached for the default settings.