Hello,

your connection window option from TSEND_C or in case of conn structure used, you need to show here so we can look at this cfg you did. From screenshot is clear what IP and Port has PC SW so I expect same at your cfg. The problem can be in case that other app or device want connect to same IP and Port at same time as you want, this is not possible generally.

About that STATUS values, if you look at TIA help about your block, you can easy see that all is ok, connection is established and monitored (7004) and data was sent, after your trigger (7002).

Your change of STATUS also depends what values you have set to parameters of TSEND block. So you say that REQ is in false, so you not send any message then and your STATUS shows still 7002? I recommend check TIA help for sure where CONT and REQ are described. problem is if your code resets any of this signal and you don't know about that. Visual check isn't that correct check here.

Hello,

user

...but I have deleted all TCON, TSEND_C and TRCV_C function blocks...

here is something strange and maybe cause of your problem - use of TCON although _C blocks are used. If you're use _C blocks, you don't need use TCON because they use internally prepared connection procedure already, all is clear from description of blocks (CONT param????). Here then can be problem with exact connection to device because 2 connection requests can be initiated, one from TCON and other from TSEND_C block. Next question is how you did cfg of that _C blocks in case you want also receive data from that laser device. generally is recommended to use some PC app like Hercules (if you don't have other) instead of PLC and connect to that laser and test data exchange like simulator. You can then better uinderstand how data are formed and prepare PLC code better.

Hello,

AutoGen_4649711

Hello Ivan,

I did not have the TCON, TSEND_C and TRCV_C blocks at the same time configured. I was testing them one by one. My point was that now all of them are deleted from the code, but the Laser PC still shows a client is connected to it and based on the IP address and port, it is the PLC.

As I said in the first post, i tried the connection to the laser PC from my PC with the program Socket Test V3.0. It is working. At the moment this connection is not active.

What I need now is how to check why mu PLC is still connected to the laser when I have no blocks for TCP/IP connection in my code?

aaah thnx for better description, clear now. Really its strange. I think basically like this, you don't have PLC cleared still or PC app is still shows some old message. Pls understand, I don't see real life your situation, I can only guess. I can offer to you next tip to test your PLC. As I said, there is Hercules SW on web (or use that one you have now) and you can run it on your PG/PC with TCP Server set. Then try connect from your PLC with your code with laser access, Hercules acts here like that laser app, check all carefully what IP and Port you set to Hercules and also set this inside PLC with Update inside PLC (Recompile all). This is all what I can recommend to you, you need simply find source of problem - wrong PLC cfg or PC laser app problem.

Hello,

ok, to your questions.

1. All of your suggestions I tried and explained in the first post, but anyhow. I installed Hercules, disconnected the laser PC from the network physically and changed my PC IP address to that of the laser 192.168.0.20. In Hercules I entered the configured port 2049 in Server settings and clicked Listen.

As soon as I started Hercules with this setup I got a green message in Client connection status that a client is connected with IP address 192.168.0.1, but the Clients count was 0. The STATUS of TSEND_C was 7000.Why is this happening?

A: Client was connected? Where it is indicated? Client connection is proceeded only after CONT->true so really hard to say where you have error.

2. Then I set CONT to true and I got a black message in Client connection status that a client is connected with IP address 192.168.0.1, but the Client count now is 1. The STATUS of TSEND_C was first 7002, then 7004. As I can see in the Help documentation, 7002 meansConnection is currently being established (REQ irrelevant), and 7004 meansCommunication connection has been established and is being monitored. No send job execution active.

A: I see this as correct state. You set CONT as Connect to Server proceedure but REQ is false, so send data was not proceeded.

3. I set REQ to true and the STATUS changed to 7005 -Data transfer in progress. and then to 7004.

A: Correct, data send is set.

4. The text that was configured at DATA was sent to Hercules successfully.

A: Perfect, I see no problems.

5. Then I set CONT to false and STATUS changed to 7000. On Hercules I got a message that Client 192.168.0.1 closed connection.

A: Correct, with set false to CONT you set disconnection proceedure from Server. As is described in Help.

My last idea, look pls also to HW cfg inside Device & Networks, look to Connections if you don't have there defined some configured TCP connection. This is not expected here because all is configured inside _C blocks Connection dialog Window. This is only my last tip where that one strange TCP connection can exists. If it is there, delete it with rebild of HW cfg. pay attention also if you don't have some TAGs initialisation inside OB100 so then maybe f.ex. CONT is set already with PLC start, who knows, only for sure.

Update: one important thing. Prior set CONT to false (disconnect) it's better to set REQ also to false (stop send data) but this is expecetd to do right after send data is indicated as ok, also if help recommend maybe set some pulse triger, in case, is up to you. One other question also is why you want disconnect, it is generally expecetd to be connected till is really expected to go out, only REQ sets with new message build and send/stop procedure.

Hello,

glad it is solved, you're welcome.