I have been using numerous scratch pad instructions "Set I/O Unit Scratch Pad Float Table" and "Get I/O Unit Scratch Pad Float Table" for quite some time to share data between different controllers running various strategies throughout our facility for quite some time now and have a question regarding which method of communication is faster.
If the data is stored in a currently 50% (will continue to grow) filled 3000 element segregated table is it more efficient to use one "Set I/O Unit Scratch Pad Float Table" and move all 3000 elements in one shot? (I prefer this option)
The other option would be to use 6 or 7 "Set I/O Unit Scratch Pad Float Table" instructions and move only those groups of elements being used out of the 3000 in the table.
Adding a little more insight, we have 8 controllers that share lots of I/O and variables using the scratch pad and we have now added a 9th controller that is a dedicated scratch pad handler. It gathers all data from individual controllers and puts them in the 3000 element table and sends out the data for all others to read using " "Set I/O Unit Scratch Pad Float Table". This 3000 element table has specific element ranges for each controller to pull the data such as 100-299 = controller1, 300-699 = controller2...etc.
The end result of all this now each controller only has one set and one get I/O unit scratch pad float table instruction to the new dedicated scratch pad controller instead of have to go to every individual controller.