Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Open Communication and data transfer monitoring

Created by: Jusbe at: 5/27/2009 12:41 PM (2 Replies)

Rating (0)

Thanks 0

3 Entries

5/27/2009 12:41 PM	Rate (0)
Jusbe Member Joined: 5/4/2009 Last visit: 11/23/2023 Posts: 2 Rating: (0)	Hi, I'm using a 317F-2PN/DP (V.2.6.7) to communicate with a laser scanner via ethernet using open communication (FB63/TSEND, FB64/TRCV). I send different kind of commands to the scanner. All commands use the same FC in communicating. Each command has its own DB. Each command creates an own any-pointer for the communication FBs (send data and lenght, rcv location and lenght). Some commands work fine, I get Send_DONE and I get RCV_NDR. But some command only get Send_DONE and RCV_BUSY bit stays always on, RCV_RET_VAL is 7002. I have re-re-re-re-checked send_DBs of those problematic commands and everything is in order. But still no RCV_NDR (=receive done). I have changed the length of RCV_data pointer from short to long etc. No success. Send/Rcv DBs (command messages, response-DBs) are according to the scanner manufacturer. I've also tried different kind of message structures if manual is wrong (which it is not probably). Is it possible to monitor the ethernet traffic to see what data is coming from the scanner to CPU (when using integrated PN interface)? I'm really desperate because most of the commands work fine and some crucial don't. Thanks for any help on this! Br, Jusbe

Suggestion To thank Quote Answer

5/27/2009 9:24 PM	Rate (0)
jklm Platinum Member Joined: 12/22/2006 Last visit: 1/25/2022 Posts: 1742 Rating: (306)	Hello, To monitor the traffic between the CPU and the scanner you need 1) either a hub, or a switch where you can activate the monitoring of a port. A scalance X208 for instance could do the job (in the switch menu you will find the monitring function) 2) a PC with a freeware like wireshark (see www.wireshark.org) that you connect o the hub or the monitoring port of the switch. You could also try the value 0 for the parameter LEN of the TRCV. LEN = 0 has the following meaning: - the data are available immediately - The data go into a buffer whose length x is specified in the ANY pointer of the receive buffer (DATA parameter). After being received, a data block is immediately available in the receive buffer. The amount of data received (RCVD_LEN parameter) can be no greater than the size specified in the DATA parameter. Receiving is indicated by NDR = 1.
	Last edited by: edr at: 5/27/2009 9:26 PM Best regards jklm Suggestion was helpful? Feel free to rate it.
Suggestion To thank Quote Answer

5/28/2009 11:34 AM	Rate (0)
Jusbe Member Joined: 5/4/2009 Last visit: 11/23/2023 Posts: 2 Rating: (0)	Hi, I don't have that kind of a switch at hand. So that is a lost cause. I'm using 0 in TRCV's LEN. The data pointer defines the receive message's db and area length. RCVD_LEN is set to 0. As I said, eight other commands work fine with the same communication program block, but this one doesn't. The only reason then is the command itself and it being incorrect some way. But you can not help me with that problem.. (unless you know something about SICK's scanners... SET_FUNCTION -command to be exact. Thanks for the help, the problem is not in the communication then. Br, Jusbe edr Hello, To monitor the traffic between the CPU and the scanner you need 1) either a hub, or a switch where you can activate the monitoring of a port. A scalance X208 for instance could do the job (in the switch menu you will find the monitring function) 2) a PC with a freeware like wireshark (see www.wireshark.org) that you connect o the hub or the monitoring port of the switch. You could also try the value 0 for the parameter LEN of the TRCV. LEN = 0 has the following meaning: - the data are available immediately - The data go into a buffer whose length x is specified in the ANY pointer of the receive buffer (DATA parameter). After being received, a data block is immediately available in the receive buffer. The amount of data received (RCVD_LEN parameter) can be no greater than the size specified in the DATA parameter. Receiving is indicated by NDR = 1.

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on