Hi,

till now, I am testing tcp communication between cpu 317 2, and my pc using telnet as terminal. The cpu prints on my screen what I'm expect but the tsend.status remains on 7001 (start of job execution)... The problem is that tsend remains busy even when my data is printed on screen... I do not use TDISCON btw. 

Any opinion, suggestion?

Janko

hi janko,

can you post a screenshot of your code, that we can see how you use the TSend-Block?

regards, 

HI, 

I send you a Photo of my code... One again, everything seems to be working correctly, but net_send.Busy as always TRUE and status is 7001... even after everything got printed on screen...

I really do not know what to do with that... and thank you very much!!!

Janko

i´m not that expert in SCL, but it seems to me, like you are setting the net_send.REQ in every cycle to True and after calling the net_send immediatly to false. So you are starting the Request in every cycle.

regards,

So, you are thinking that I should implement some sort of positive edge for setting up REQ tag ?! 

Janko

i should told you before that I cannot even capture net_send.DONE = TRUE during the job execution. Don't you think it's a bit strange?! 

Janko

net_send.DONE shouldn´t come during the sending. it comes after sending. but in your case it couldn´t come, because you are starting the next sending before the last is done yet. The sending starts with a positive edge on REQ. You have a positive edge on REQ in every cycle. Just try to delet net_send.REQ:= FALSE in your code.

regards,

jankoslayer

i should told you before that I cannot even capture net_send.DONE = TRUE during the job execution. Don't you think it's a bit strange?! 

Janko

Meaning of the parameters REQ, RET_VAL and BUSY
with asynchronous instructions (TIA Portal, in-software help)

Parameter REQ

The input parameter REQ (request) is used solely to start the job:

• If you call the instruction for a job that is not currently active, the job is started with REQ = 1 (case 1).

• If a particular job has been started and not yet completed and you call the instruction again to perform the same job (for example, in a cyclic interrupt OB), then REQ is not evaluated by the instruction (case 2).

DONE is kept high until finding a new request.. new request = rising edge on REQ.

I tried with different possibilities til now but without any result... 

Janko