Industry Online Support
Technical Forum
7/29/2009 2:04 AM | |
Posts: 3 Rating: (0) |
Thanks for the offer Wireshark v1.2 .These traces where gained for issues posted https://www.automation.siemens.com/WW/forum/members/PostEdit.aspx?PostID=158487&ReturnUrl=%2fforum%2fguests%2fPostShow.aspx%3fPageIndex%3d1%26PostID%3d158487%26Language%3den%23158487&Language=en The normal wireshark pattern can be seen in the attached. As you can see the data part is not decoded. By looking at the time and for a data pattern in the stream, i worked out that packet 49578 was the reply to the read. The 05:cf was the give away for the CREF value. Yet back up at the API level. The05:cf was not seen but rather the 0xffff and buffer overflow error as reportedin my other post. i.e. the device was happy but SAPI wasn't. (this being theread reply, not the NO_MSG message) 32:03:00:00:05:cf:00:02:00:16:00:00:04:01:ff:04:00:90:00:00:00:00:00:0c:00:00:00:00:00:00:00:00:00:00:00:00 So my issue is split as i have done. My API issue but also if someone has created a dissector tailored for the SAPI S7 interface. Regards |
Last edited by: Greg Roberts at: 7/29/2009 2:37 AM |
|
Follow us on