Dear all,

Context:

We use Profinet communication.

I have 1S7-1500as data concentrator to populate a Rack-PC supervisorWinCC.(connected with PN)

TheS7-1500retrieves20 DWordsfrom all the30 S7-1200on the field to updateWinCC.

TheS7-1500also sends2 DWordsto all the30 S7-1200on the field fromWinCC.

All 30 S7-1200 have their own electrical panel and do their own process.

Note:

We use DWords to save communication bandwidth between S7-1500 and S7-1200.

Also we use DWords to save Powertags between S7-1500 and Rack-PC supervisor WinCC

DWords contain statuses, faults, memories... (not only DI / DO)

Question:

As we need to send a lot of information bits between S7-1200 PLCs and the S7-1500, I suppose that IODevice exchange is not a good choice.Better to send / receive DWords ?

So do we need to avoid to configure our 30 S7-1200 PLCs as IODevice ?

Or to configure them (S7-1200) as IODevice doesn't affect SEND_C / RECEIVE_C communication ? What is more preferable ?

Is there a native way more suitable to exchange those DWords (contained inside external DBs of each S7-1200) ?

Thanks in advance,

David

Hello,

For exchanging only 84 byte I device communication is best way, it can go upto 1kbyte. Its  real time communication.

I have good experience with 40 number of S71200 PLC with  single S71500  PLC as I device functionality for  data concentrator.

If you feel this post is useful then don't forget to rate it.

Thank you DJ_1 for your indication of the limits.

So it means until 30 DWords to exchange between each IODevice to the IOController, I-Device is performing well.

But I think we can only transmit Inputs and Outputs from IODevice to IOController (I, Q, HSC, Pulse generator).

How to affect DataBlock data (external or instance) to Inputs / Outputs ? Is it possible ?

Thank you for your help,

David

Hello,

You can't read or write physical IO memory of IO device or IO controller.

You will get Virtual INPUT and OUTPUT memory . Which can not overlap with your used IO memory.

So externally you need to transfer DB memory in Virtual IO memory address using instructions, for example move block.

So you can move DB1.DBW0 in to virtual Q address QW20 in io device, while reading in io controller it may be virtual i address as IW20 which need to be again move in to local memory.

If you feel this post is useful then don't forget to rate it.

Hi DJ_1,

This is a very good news, thanks.

Is it QW20 or PQW20 (for Peripheral Output) ?

Thank you for this info I couldn't find,

Regards,

David

Hello,

For Virtual IO memory it always IW and QW in TIA portal.

See the attached video for better understanding.

If you feel this post is useful then don't forget to rate it.