kamenges
Member
There is so much separation between user program entry and what the processor sees with the AB plc products that is is hard to say exactly what is happening.
I do know that from a programmers standpoint N10 and N11 are adjacent. They may not be adjacent in memory but they are certainy adjacent from a programming standpoint. I very highly doubt that the index operation is a raw operation. Since it is massaged by the interpreter on the plc it can move to anywhere it wants. On the flip side, addition of data files in the PLC/SLC family require a full program download. So it is reasonable to assume that the memory map is massaged and downloaded as a result. Putting adjacent files together in memory seems pretty natural but that's not a guarantee.
I also don't know what it would do with something like an N10 and and N15 with no defined files in between. Would the index/indirection 'jump the gap' or would it fault? With the New Platform PLC5 every open file 'space' would chew up 6 bytes or so. This infers there is something in that space maintaining at least a relative location. But, again, it more depends on what the interpreter decides to do with that.
Without someone from Rockwell ponying up the info I don't think we will really know. The AB products don't provide the hooks to allow you to figure it out.
Keith
I do know that from a programmers standpoint N10 and N11 are adjacent. They may not be adjacent in memory but they are certainy adjacent from a programming standpoint. I very highly doubt that the index operation is a raw operation. Since it is massaged by the interpreter on the plc it can move to anywhere it wants. On the flip side, addition of data files in the PLC/SLC family require a full program download. So it is reasonable to assume that the memory map is massaged and downloaded as a result. Putting adjacent files together in memory seems pretty natural but that's not a guarantee.
I also don't know what it would do with something like an N10 and and N15 with no defined files in between. Would the index/indirection 'jump the gap' or would it fault? With the New Platform PLC5 every open file 'space' would chew up 6 bytes or so. This infers there is something in that space maintaining at least a relative location. But, again, it more depends on what the interpreter decides to do with that.
Without someone from Rockwell ponying up the info I don't think we will really know. The AB products don't provide the hooks to allow you to figure it out.
Keith