-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WiFi101 TCP data corrupted on MKR1000 after reading large number of bytes #184
Comments
Hi @Sudeshna19, I've tried to reproduce this using
Could you please try again and use Wireshark to capture the data transfer, then upload a saved capture here? |
Also, please provide the output of the sketch to the serial monitor. |
@sandeepmistry I have tried on Windows10 this time. Same issue. Let me know if you need further info. |
In the above test IP addresses are as below: |
So in the Wireshark trace, the first two TCP packets have 99 bytes of data: This is followed by 3 TCP packets contain 1 byte with value @Sudeshna19 could you please provide the exact sketch you used to produce #184 (comment), it seems to differ from the sketch provided in #184 (comment). Please also try the master version of this library, it includes some changes from pull request #204 - just want to confirm the issue still exists with these changes, or if they are resolved. |
I'm closing this for now due to lack of feedback. |
I am using MKR1000 as WiFi TCP server and an application in Windows7 machine as WiFi TCP client. The idea is to connect the client to TCP server and send many bytes (~ 200 bytes). TCP server reads the received data and sends it back to client. I am using Hercules SETUP utility 3.2.8 (http://www.hw-group.com/products/hercules/index_en.html) as the TCP client on Windows.
The code is below:
Attached below is the snapshot of the data sent and received using Hercules Utility
![hostreceive](https://user-images.githubusercontent.com/29605115/28016473-1764f2a6-6592-11e7-86d6-0bf3983260e4.PNG)
I sent a repeating pattern of ABCDEFGHI (7 times in 3 rows) resulting in ~210 bytes. In the attached snapshot you can see in area marked under red that the data read from TCP buffer gets corrupted after reading some 100 bytes. I receive something as:
Sent ÎSent YSent óSent ½Sent Sent 'Sent ÝSent WSent �Sent Sent ÛSent ¹Sent 9Sent Sent ÊSent ÆSent Sent eSent Sent Sent þSent aSent ôSent °Sent sSent îSent øSent �Sent /Sent YSent ¯Sent ¼Sent ÖSent §Sent ´Sent ¥Sent ÕSent ¨Sent _Sent Sent 3Sent ÎSent vSent 'Sent ºSent 2Sent ¡Sent ùSent îSent ÆSent {FF}Sent WSent Sent i
The text was updated successfully, but these errors were encountered: