Greetings ptine ...
you said:
I have always thought that the MSG was a one way instruction....that the data was sent from the node that the MSG was in to the target node.
there are at least two things that might be confusing you here ... I doubt that this first one is of any interest - but I’ll cover it anyway just for kicks ...
it is possible to change an MSG (Message) instruction “on-the-fly” and make it (for example) change the address of the other (source/target) node ... you could even make a single MSG function as a “read” message at some times - and then flip it to function as a “write” message at other times - if you really wanted to do so ... the trick would be to have your ladder logic program alter the data stored in the MSG’s “Control Block” ... some programmers do things like this to minimize the amount of code in their programs ... other programmers - and technicians - HATE this approach because it is extremely difficult to troubleshoot the system whenever any particular message doesn’t “go through” as planned ...
I doubt that this approach is what is confusing you in the program that you’re examining ... just be aware that sometimes you might run into something like this ...
now here’s the thing that really confuses MOST people - until they get used to it ...
in the picture above, the words “This PLC-5” make perfect sense ... now notice that the MSG is being configured to perform a “READ” operation - and not a “WRITE” operation ... the confusing thing is that the words “Target Device” do NOT make sense ... they should instead say “Source Device” ... specifically, this MSG is going to READ/GET data from another SOURCE ... it is not going to WRITE/DATA to another TARGET ...
secret handshake: the words “Target Device” will NOT change to reflect the direction of the data transfer ... specifically, this legend will ALWAYS say “Target Device” regardless of which way the data is flowing ...
tip: always look at the “Communication Command” setting when you need to determine which way the data is supposed to flow ...
is that the part that you found confusing? ... if so, you would certainly not be the first ...
now if I had been on the team who originally created the MSG setup screen, I’d have insisted that we call this particular legend “Other Device” ... that way it would have made sense regardless of which way the MSG was transferring the data ... but obviously the folks at Rockwell didn’t invite me to participate ...
hope this helps ...