Emerson Exchange 365

PK100 Not able to communicate over Ethernet/IP on different assembly instance other than 101,100,102

In PK100 controller when i am trying to set the communication with different assembly details it is not comunicating but when i change the assembly instance details to 101,100,102 it works fine.

i have to communicate around 1500bytes. so i am making different LDT with different assembly instance as i think PK100 doesnot support extended Ethernet/IP configuration. i have limitation of 100 signals or 500 bytes in each LDT.

• Ethernet/IP
• pk100

Shaswat Raj

• 20 May 2023 7:33 PM
• Cancel

7 Replies

• Inocencio Perez

  

  • 22 May 2023 6:18 AM

  I think the limit of 100 signals per LDT is standard it not depends on the PK.

  • Cancel
• Shaswat Raj

  

  • 23 May 2023 11:28 AM

  In reply to Inocencio Perez:

  Yes..that is correct ...100 signals or 500bytes...
  So as it is increasing more than limit I tried to create another LDT with different assembly instance
  104,103 and 102 as shown in snapshot to accomodate another set of signals but this is not communicating...
  So I am not getting what can go wrong ...(license I was seeing ) but even when I changed the assembly instance details with single instance still it was not working .
  LDT1 104,103,102 is not working
  But same LDT1 101,100,102 IS WORKING
  
  When I tried with Rockwell PLC it is working ....

  • Cancel
• Inocencio Perez

  

  • 23 May 2023 11:46 AM

  In reply to Shaswat Raj:

  You need to use the same values in each LDT.

  • Cancel
• Andre Dicaire

  

  • 23 May 2023 2:55 PM

  In reply to Inocencio Perez:

  100 Signals is what Emerson has chosen for the size of LDT's. This seems to have carried over from the design of Modbus Data sets on Serial cards, and within the new EIOC and PK controller drivers. I wouldn't call it a "Standard". It is simply a design limit to help manage the communication load and spread out the data exchange over multiple calls to the end device. PLC's often use binary values like 64 or 128.
  
  As for the LDT configuration, the Input and Output size in bytes must match the size of the Input and Output Assembly instances. If they don't match, I don't think it can be successful. You need to know the content of the assemblies in order to map the data into signals.

  Andre Dicaire

  • Cancel
• Inocencio Perez

  

  • 24 May 2023 8:31 AM

  In reply to Andre Dicaire:

  It's DeltaV standard, so you can go further than that or change that limit...

  • Cancel
• Shaswat Raj

  

  • 27 May 2023 9:15 AM

  In reply to Inocencio Perez:

  Which means I should use 101,100,102 in each LDT ?

  • Cancel
• Shaswat Raj

  

  • 27 May 2023 9:18 AM

  In reply to Andre Dicaire:

  That's correct , Bytes are matching when I just change the assembly to 101,100,102 it works perfectly but when I switch back to assembly to 104,103,102 on both PLC and PK100 side it doesn't work.... But the same config work between two different PLC i.e. Compactlogix and Wago PLC ...so I was puzzled if I am missing something in PK100 CONFIG

  • Cancel