raceandski
Guest
R
Hello
I could use some help on SLC500 Peer to Peer comms.
Specifically, I have 2 5/05 processors. Master and slave for clarity's sake. They are on a common ethernet hub.
What I need to do is have the slave call the master's I/O table image and place these images into an N: file in the slave.
What I do understand is I'll be using the MSG command. However AB's documentation of this command in the instruction reference leaves a little bit to be desired. I do have Publication 1747-RM001D-EN-P so please feel free to reference this doc.
I am also wondering about how much overhead this is going to produce in
a- the master SLC, and
b- on the network.
I'll be calling for all 16 bits on 15 digital I/O cards.
This is not time critical data (around 1sec is plenty of responce time) so should I only call the MSG instruction say every 20-50 scans? (using a CTU-RES combo)
Any help would be greatlt appreciated.
Ian
I could use some help on SLC500 Peer to Peer comms.
Specifically, I have 2 5/05 processors. Master and slave for clarity's sake. They are on a common ethernet hub.
What I need to do is have the slave call the master's I/O table image and place these images into an N: file in the slave.
What I do understand is I'll be using the MSG command. However AB's documentation of this command in the instruction reference leaves a little bit to be desired. I do have Publication 1747-RM001D-EN-P so please feel free to reference this doc.
I am also wondering about how much overhead this is going to produce in
a- the master SLC, and
b- on the network.
I'll be calling for all 16 bits on 15 digital I/O cards.
This is not time critical data (around 1sec is plenty of responce time) so should I only call the MSG instruction say every 20-50 scans? (using a CTU-RES combo)
Any help would be greatlt appreciated.
Ian