• 1214C PUT to 1215C
• 1214C GET from 1215C
• 1215C PUT to 1214C
• 1215C GET from 1214C

- - -

• DB9 (DB_CountData)  - contains an array of 40 DINTs (first 160 bytes) and a DINT (next 4 bytes).
• DB10 (GET_FROM_1215C)  - contains an array of 40 DINTs (160 bytes) - data from 1215C to be put here by local GET call.
• DB11 (PUT_FROM_1215C) - contains an array of 40 DINTs (160 bytes) - data from 1215C to be put here by 1215C PUT call.

• DB9  - DB_CountData - contains an array of 40 DINTs (first 160 bytes) and a DINT (next 4 bytes).
• DB10 - GET_FROM_1214C - contains an array of 40 DINTs (160 bytes) - data from 1214C to be put here by local GET call.
• DB11 - PUT_FROM_1214C - contains an array of 40 DINTs (160 bytes) - data from 1214C to be put here by 1214C PUT call.

• The PUT and GET calls initiated on the 1215C are working correctly.  DB11 on 1214C and DB10 on 1215C are updating as expected.
• The PUT and GET calls initiated on the 1214C are not working.  DB11 on 1215C and DB10 on 1214C are not updating.

Hi.

Compliments on your comprehensive write-up. Sorry I have only speed read through it.

Maybe a possible issue with the IDs used. Consider a configuration listed in the picture which I have used on a similar setup.

EDIT: And do not use the same trigger for both PUT and GET.

Regards.

• Create four unique connections and assign a different one to each of four PUT/GET calls.
• Switch which PLC actively creates the connection by toggling the Connection Properties - Special Connection Properties - "Active connection establishment" checkbox on both sides of the connection.

1. Ensure PUT and GET is allowed by the hardware security/protection setting.
   
   
2. Increase in the hardware setting how much time is allowed for communication tasks.
   
   
3. Ensure that the latest version of the instruction is used.
   
   
4. Do not use a clock pulse to trigger the instructions.
   
   
5. Use the busy and done status bits to determine when to trigger the next instruction. Keep in mind that when the partner1 is busy, partner2 will have difficulty doing its task at that moment. Having a static clock can cause problems.
   
   
6. Capture the status word of the instruction.. especially when an error occurs (fault finding).
   
   
7. Search through the Forum pages for some details on what is mentioned above.

zstephens_aka

Hi William_B,

I found this post with some discussion about a 1215C running firmware 4.2, but showing as 4.1 in TIA v13 HW Config (4.2 is not an option AFAIK in TIA v13).  As in that post the difference is flagged as a warning when downloading, but it allows me to ignore and continue.  Any chance that is related to this communication issue?

Cheers,

Zach

Possible but I doubt it.
Did you see my previous post?