Bonjour,
L'ET200S, c'est pour les très petite applications, effectivement il n'y a pas les fonctionnalié que vous souhaitez
par contre Il y a la communication ISO.
Ci dessous un copier/coller de la doc dans mon 1er post
3.4 Open communication via Industrial Ethernet
Requirement
● STEP 7 V5.4 + Servicepack 4 or higher
Functionality
The IM 151-8 PN/DP CPU interface module with integrated PROFINET interface supports
open communication functionality via Industrial Ethernet (abbreviated to open IE
communication).
The following services are available for open IE communication:
● Connection oriented protocols
– TCP to RFC 793, connection type B#16#01
– TCP to RFC 793, connection type B#16#11
– ISO on TCP to RFC 1006
● Connectionless protocols
– UDP according to RFC 768
Features of the communication protocols
The following distinctions are made between protocol types in data communication:
● Connection oriented protocols:
Prior to data transmission these establish a (logical) connection to the communication
partner and close this again, if necessary, after transmission is completed. Connection
oriented protocols are used when security in especially important in data transmission. A
physical cable can generally accommodate several logical connections.
For the FBs to open communication by means of Industrial Ethernet, the following
connection oriented protocols are supported:
– TCP according to RFC 793 (connection types B#16#01 and B#16#11)
– ISO on TCP according to RFC 1006 (connection type B#16#12)
● Connectionless protocols:
These operate without a connection. There is also no establishing or terminating a
connection to remote partner. Wireless protocols transmit data to the remote partner
without any acknowledgement; data transfer is, therefore, not secure.
The FBs for open communication over Industrial Ethernet support the following wireless
protocol:
– UDP according to RFC 768 (connection type B#16#13)
How to use open IE communication
To allow data to be exchanged with other communication partners, STEP 7 provides the
following FBs and UDTs under "Communication Blocks" in the "Standard Library":
● Connection oriented protocols: TCP/ISO-on-TCP
– FB 63 "TSEND" for sending data
– FB 64 "TRCV" for receiving data
– FB 65 "TCON", for connecting
– FB 66 "TDISCON", for disconnecting
– UDT 65 "TCON_PAR" with the data structure for the configuration of the connection
● Connectionless protocol: UDP
– FB 67 "TUSEND" for sending data
– FB 68 "TURCV" for receiving data
– FB 65 "TCON" for establishing the local communication access point
– FB 66 "TDISCON" for resolving the local communication access point
– UDT 65 "TCON_PAR" with the data structure for configuring the local communication
access point
– UDT 66 "TCON_ADR" with the data structure of the address parameters of the remote
Partner
Je vous passe le reste de la doc qui se trouve page 42
Bref grosso modo en TCP ISO, il vous faut utiliser
- le FB65 pour ouvrir la connexion avec l'UDT65 pour avoir la bonne structure de donnée.
- Vous semblez vouloir lire des variables dans l'ET200S, il faut a ce moment utiliser le FB63 "TSEND"
Pour tout ce qui est adresse et autre il faut ouvrir STEP 7 et la page d'aide de la fonction (je n'ai pas de console avec moi pour te donner plus d'indication)
Du coté de votre soft alors la je ne sais pas du tout je ne sais pas avec quoi vous programmez
En espérant vous avoir donné une piste, sinon faut craquer la tirelire
A+
)