mellis
Member
PLCNovel,
See if this meets your needs.
You have a PLC in the field (call it PLC B) with some data scattered around in various data files that another PLC (call it PLC A) needs to access. PLC A is the one that will be doing the reading and writing. PLC B just has to provide the data to PLC A and accept some data from PLC A. I think that is what you have described so far. The question is, what do you have to do in PLC B?
First make two lists. One of all the data addresses that you have to provide (read from PLC A) and one of all the data that PLC A is providing (write from PLC A). It would be a good idea to let us see that list. For the sake of simplicity, I will assume that none of the data is floating point (file type F). So all the data you need to deal with is of type B or N.
Pick an unused integer file (type N), say file N10. It would be nice if you can use the same file in both PLCs. Allocate a chunk of file N10 for data from PLC A and another chunk for data to PLC A. I generally allocate at least 10 words each way as a minimum. In reality you can allocate up to 100 words in each direction and the message performance is essentially the same.
Arrange all the data in a nice neat package in this file. Use Excel to layout where each bit and word of your data gets assigned in file N10. Once you have it all laid out, you can add a group of rungs to move the data into and out of file N10. For words of data, you use a MOV instruction. For bits of data, you use an XIC and OTE instruction for each bit (contact and coil). It's a bit tedious, but if you want to move scattered data in a single message, that's what it takes.
Give the person responsible for programming PLC A a copy of your Excel sheet and he will have all the info he needs to decode the N10 file on his end.
There is one thing you mentioned in your first message that causes me a little concern. You said some of the data is R/W. You can do this, but it will take extra logic in PLC A. Basically, each individual point can do one or the other at any given time, but it needs to decide which it is doing at the moment. That might be the responsibility of the person programming PLC A. For you it may be as simple as R/W data just goes in both chunks of data, but you should find out.
Show us the list of data, I'm sure there will be more suggestions once we see what you are actually dealing with.
Good luck,
See if this meets your needs.
You have a PLC in the field (call it PLC B) with some data scattered around in various data files that another PLC (call it PLC A) needs to access. PLC A is the one that will be doing the reading and writing. PLC B just has to provide the data to PLC A and accept some data from PLC A. I think that is what you have described so far. The question is, what do you have to do in PLC B?
First make two lists. One of all the data addresses that you have to provide (read from PLC A) and one of all the data that PLC A is providing (write from PLC A). It would be a good idea to let us see that list. For the sake of simplicity, I will assume that none of the data is floating point (file type F). So all the data you need to deal with is of type B or N.
Pick an unused integer file (type N), say file N10. It would be nice if you can use the same file in both PLCs. Allocate a chunk of file N10 for data from PLC A and another chunk for data to PLC A. I generally allocate at least 10 words each way as a minimum. In reality you can allocate up to 100 words in each direction and the message performance is essentially the same.
Arrange all the data in a nice neat package in this file. Use Excel to layout where each bit and word of your data gets assigned in file N10. Once you have it all laid out, you can add a group of rungs to move the data into and out of file N10. For words of data, you use a MOV instruction. For bits of data, you use an XIC and OTE instruction for each bit (contact and coil). It's a bit tedious, but if you want to move scattered data in a single message, that's what it takes.
Give the person responsible for programming PLC A a copy of your Excel sheet and he will have all the info he needs to decode the N10 file on his end.
There is one thing you mentioned in your first message that causes me a little concern. You said some of the data is R/W. You can do this, but it will take extra logic in PLC A. Basically, each individual point can do one or the other at any given time, but it needs to decide which it is doing at the moment. That might be the responsibility of the person programming PLC A. For you it may be as simple as R/W data just goes in both chunks of data, but you should find out.
Show us the list of data, I'm sure there will be more suggestions once we see what you are actually dealing with.
Good luck,