SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Two CPU 315-2PN/DP connected via Scalance W788/W744 and TCP/IP problems

7/28/2008 12:29 PM	Rate (0)
frohme Posts: 18 Rating: (1)	Hi all! Maybe someone can explain me what wrong I've done? Both CPU as in topic are connected via wireless connection, and it works. I can go online to every part of hardware on both of them. Now I need exchange some data beetwen DB's with TCP native. After building with help of Wizzard for this purposes UDT65's for both CPU's and establishing the connection (FB65, active passive members and so on, flag connect done is set and it happens only one time at the beggining - call in OB100), I tried to send and receive short packets of data with FB63 and FB64 respectively. During sending I had no errors, but when I look on status of FB64 when receiving, it is sometimes #80a1, sometimes #80c4. Looking through error information for this FB, I only figure out that it is reinitialization of the interface - maybe, who knows.What a reason? Every help will be appreciated - thanks in advance. Regards frohme
frohme Posts: 18 Rating: (1)
Suggestion To thank Quote Answer

7/28/2008 11:58 PM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Dear Frohme, I am sorry, but it seems that the connection is not really established. The passive side shows that the Connect has not been finished successfully.. you will have to wait on the secondary side until the Connection is established. It might be that the Connection has been closed again already but this has to be checked by the program... this is why TCP is not that easy you have to care about the Keep Alive too. This leads me to one question... why do you not use S7 Connections in this situation? It would ease so much in this case. Do you have any restrictions or is it your preference? Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

7/29/2008 1:32 PM	Rate (0)
frohme Posts: 18 Rating: (1)	Hallo J_Bell! Thanks for reply. First of all I establish and check in program a connection by flag DONE at both sides - active and passive, so one problem is probably solved. Next, according to CPU clock pulses every 1 second I tried to send 16 bytes - no error flag had been set. At opposite side I tried to recive with errors as in post above. Of course I can set another S7-S7 connection between both CPU's, and it will be probably the simplest way, but there are (have to be established) some not mentioned connections with PC's with TCP/IP so from my point of view I had to do it now or in near future. Anyway I will try it according to You suggestions. Regards frohme
frohme Posts: 18 Rating: (1)
Suggestion To thank Quote Answer

7/29/2008 7:38 PM	Rate (0)
J_Bell Posts: 5822 Rating: (412)	Dear frohme, maybe it would be useful to check this sample: How is a TCP connection programmed for open communication via Industrial Ethernet? it may help you to find a simple solution. Best regards J_Bell
J_Bell Posts: 5822 Rating: (412)
Suggestion To thank Quote Answer

Share this page:

Share this page on...