Chris Elston

Bob, Yes so see here this Panel View TAG: {[PLC]ML_DataBase.Display[0].RemainService} I want an indirect address where the ZERO is. {[PLC]ML_DataBase.Display[myvar].RemainService} I was just checking to see if I missed any updates or not that would allow this.

Does anyone know if Allen Bradley has added Indirect Addressing to PanelView Tags yet? I didn't hear anything in a while, but I thought I would ask in case I missed any new releases. 

I think his has been resolved. PDF Uploaded.

Same for me. I will report this to PDF Supply.

Well I dunno, thought I would post what I have so far in case anyone else runs into this. It seems you can only do large transfers through a MSG instruction, is what I have arrived at. I don’t know if that works for me for a SLAVE device connection to get the tags out I need or not. I would need to purchase these items to test it out to see if this can be setup, I have no clue if this works, but atleast I got an answer from RA what hardware and versions I need to attempt it and get someone else started too incase you encounter this as well.  Good Luck! As per attached snapshot of error , it seems that you are trying to increase data size for Generic ethernet module.  For Generic Ethernet module,  Error : Failed to modify properties Invalid Output size The number of output configured output tags is too large   The limit is 124 tags of the type DINT The limit is 248 tags of the type INT The limit is 496 tags of the type SINT   Error : Failed to modify properties Invalid Input size The number of input tags configured for the profile is too large   The limit is 125 tags of the type DINT The limit is 250 tags of the type INT The limit is 500 tags of the type SINT   Large CIP generic messages (messages up 3980 bytes) are available with some requirements. Large messages are typically used with socket programming to send and receive more then 480 bytes of data at a time. The Large Connection checkbox is enabled only when the Connected box is checked and CIP Generic is selected as the message type on the Configuration tab.   To use Large messages with a ControlLogix controller and a 1756-EN2T(R) module, the following are required:   ·  1756-EN2T(R) and 1756-EN3TR modules at revision 5.x and higher for socket support ·  Logix Designer application, version 21.00.00 or later and RSLogix 5000 software, version 20.00.00 or later ·  The Large Connection and Connected checkboxes must be checked in the message instruction(s) Selecting the CIP Generic message type enables the Large Connection option on the Communication tab. Use large CIP Generic connections when a message is greater than 480 bytes. 500 bytes is typical, but there are headers at the front of the message. Large CIP connections are for messages up to 3980 bytes.   • The Large Connection box is enabled only when the Connected box is checked and CIP Generic is selected as the message type on the Configuration tab. • The Large Connection option is available only in Logix Designer application, version 21.00.00 or later and RSLogix 5000 software, version 20.00.00 or later.  You can refer this from https://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1756-rm003_-en-p.pdf (Chapter 4)     I tossed a project together to grab the screen shots to go along with this:

  Do you have an Insight how to setup a MSG instruction to do that? The documents I find talk about Read Tag Fragmented service with the method you mention. When looking into the MSG instruction, there is not a Read Tag Fragmented in the services options. I don’t think this will work, because the problem is the CONNECTION to the SLAVE. If I was doing Producer/CONSUMER tags that are larger than 500 bytes, this would make sense to me to use a Read Tag Fragmented Service MSG instruction to get a UDT from one PLC to another PLC, however that is not what I am trying to do. An Omron PLC with Ethernet/IP can read the Large Forward tags on this same slave.   

Yes there is a size limit in Standard CIP EIP, but you can "enable" large forward open which allows up to 64K bytes! We are all digging trying to figure that out...the actual CIP specs says this: The maximum size of the MR request and MR response packet items in the SendRRData command is 504 bytes (the maximum size on Ethernet/IP), to ensure that a UCMM message can traverse all the links in a CIP network path. Devices may support the Large_Forward_Open service (see Volume 1, Chapter 3) to allow more efficient access to large application data sizes. and also: Connection Size The CIP connection size shall be no larger than 65511 bytes. NOTE: The Forward_Open request limits the connection size to 511 bytes; however, the optional Large_Forward_Open allows larger connection sizes. Have you seen how to enable that in an Allen Bradley PLC?  Omron NJ does it no problems.

Yes, Vendor does have an AOP EDS, I tried it with that, and same result. Got same 500 byte error.

  That didn't seem to work, but I have version 31 installed at the moment, haven't updated to 33 yet. I get an error when I try to bump over the 500 byte limit in the connection window.    

Ah HA! Someone who has seen this, that's my question... I have a standard Compact Logix, however I read a document that said the newer Compact Logix did support large_foward_open. I found this statement in a KB doc: The UDP sockets in the EN2T and new CompactLogix controllers can also handle the large forward open size (about 4k), so they can transfer more data.” Do you have a list somewhere or a compatibly chart you have seen? How do you configure the connection size when you find out you have one?

LOL...why am I always the one to do this crap first. Hahahaha... Here is the CIP SPEC I found, so I know it's real, just no information how to configure it yet. I have a ticket started with AB, but no reply yet. The maximum size of the MR request and MR response packet items in the SendRRData command is 504 bytes (the maximum size on Ethernet/IP), to ensure that a UCMM message can traverse all the links in a CIP network path. Devices may support the Large_Forward_Open service (see Volume 1, Chapter 3) to allow more efficient access to large application data sizes. and also: Connection Size The CIP connection size shall be no larger than 65511 bytes. NOTE: The Forward_Open request limits the connection size to 511 bytes; however, the optional Large_Forward_Open allows larger connection sizes. In most all of Allen Bradley documents, they just round it to 500 bytes.

Not getting anywhere with this, but I found this note: Does anyone know what this feature is?   The devices to be used must support Large Forward Open (optional CIP specification) For EtherNet/IP, the maximum data size must be at least 704 words per connection in cyclic communication.