HI,

I often use the TCON, TSEND, TRCV, TDISCON in order to connect to a pc.
I often use the "help" on the TCON bloc (it create the DB with TCON_IP_V4)
and that works.

Now, I want to put all this things in one FB, I think I don't need to explain why, but :
- Now i known it is working, it's better to put the FB than copy/paste from another project
- I can put it in the library
- I can protect know-how
- It is better, that's all <>

But if I want to do that, I need to "point" the CONNECT PARAMETER in local variable (in the FB)
I read here it doesn't work....
Now it is V13 SP1 update 4, someone have tested ?

------------------------------------------------------------------------------------------
Split from The new TCON_IP_V4 connection parameters doesn't work in S7-1217C project.

hi sixthomas,

in TIA you can use the TSEND_C or TRCV_C blocks. The already contain the T_CON T_SEND/T_RCV T_DIAG T_RESET and T_DISCON blocks. 

You can call it as multi-instance and also the CONNECT- parameter can be stored in the static-variables of the instance above. You have to create a static variable of datatype CONN_xxx and put the label of it to the connect input by drag and drop. 

hope this helps, 

regards,

HI,

Thanks for the answer, I will have time next week, so I will test with a CPU1214C.

I'll be back !

Another question, I don't understand why it don't works, explain :

If the data "TCON_IP_V4" cannot be stored as an instance, why don't use data "CONN_ANY" with blocks TCON, TSEND, TRCV, TDSICON directly ?
If there is a difference between the TCON,TSEND,etc....  and the blocks TSEND_C, TRCV_C, why in the "help" I find this :

CONNECT = 

• Liaison programmée :

  • Pour TCP ou UDP, utilisez le type de données système TCON_IP_v4

    Pour la description, voir : Paramètres de liaison selon TCON_IP_v4

  • Pour ISO-on-TCP, utilisez le type de données système TCON_IP_RFC

    Pour la description, voir : Paramètres de liaison selon TCON_IP_RFC

  • Pour ISO, utilisez le type de données système TCON_ISOnative (uniquement pour CP1543-1)

    Pour la description, voir l'instruction "TCON".

• Liaison configurée :

• Pour une liaison existante, utilisez le type de données système TCON_Configured.

  Pour la description, voir "Type de données système pour les liaisons configurées" ci-dessous

Sorry for the french, but you can understand that in the parameter "CONNECT" there is only

- "TCON_IP_V4"  or "TCON_IP_RFC"   or "TCON_ISOnative"     and never "CONN_ANY"

regards,

HI,

(update 20/11/2015 17:36)

I just test my program with a CPU1214C and it is working with :  TCON_IP_V4  which is in static variable in a FB

so, no problem to have a FB "all-in-one" with differents connections !

So, for people who wants a FB to connect to a PC, and exchange some sockets in TCP/IP   can find it here.
(I write it in french, so I change to english but, perhaps, I forget some things)
(I write it in the case to have a visualization in a HMI, that's why I have lots of bits every where)

Some explanations :

- Take the attachment and load to your PLC (V13 SP1)
- Put on the same LAN a pc with terminal (I use http://www.hw-group.com/products/hercules/index_en.html , it's free and easy to use)
- Set the address of PC to 192.168.0.5 (in my exemple)
- Go to the "PARAMETER HERE" and apply settings.
- On the terminal, "TCP serveur" set "Listen"  (port:2000)
- Enjoy !

In the parameter you have :
- Auto-connect    the plc try to connect every 6s (4s before try, 2s before reset error)
- Auto-send   the plc send message every xxxtime
- Auto-reset   the plc "manage" the errors (no need manual reset)
- Auto-RCV   the plc try to receive message after every sending

To use with real project, after a receive, take the message just received and reset the bit RCV-OK 
Do what you want with the received message. the FB do the rest.
Put the bits ERROR-XXXX to the alarms in the HMI or log it

Hope this helps,

Regards,

Last thing : I know lots of people don't share projects, and I disagree.