I’m trying to use the tcpclient to connect to a .net service to upload its data. The process is working but i’m receiving duplicate values on my server side. this is some of my code form my electron client.connect(server_host, server_port); Serial.printlnf("send_To_Server"); Ser…

Your code looks OK (from what I can tell) but you haven’t shown the whole loop. It could be something else, other than what you have shown causing the problem. I see where you connect to the server with client.connect() and then send data with client.write(), but do you ever call client.stop()? I se…

Thanks I close the tcpclient once i have received the OK from the server. Normally on the server side I check for the IsCompleted flag from the asyn connection - but that is always returning true even when the tcpclient is sending a packet > 1024 bytes… So unless i can send more than 1024 bytes in…

Check out this post by @rickkas7 which deals with sending large amount of data from a Photon to a server via TCPClient: [image] Sending large data off Photon using TCPClient Tutorials I was wondering exactly how fast you can get data off a Photon using a direct TCP connec…

thanks - i had seen this but i’ll have another read through.

On the Electron you can’t send more than 1024 bytes at a time. You’ll need to break it up into partial writes, the optimum size is actually 512 bytes per write. Ideally, you should use a state machine like the link above, so that you don’t block loop for the entire send process. It’s best to return…

I have done some testing and no matter how i do it ( either a loop with 512 bytes or sending the whole byte array) i only ever get the final bytes = 0 on my server if i send the client.stop(); int client_written = client.write((unsigned char *)nP, sizeof(nP)); // Serial.println(client_written); …

TCP does not work that way. There is no send zero bytes option in TCP. You can either send a packet of data, and the packet may include the FIN bit that marks it as the final packet. The FIN bit is sent after calling client.stop(). The FIN may be in a packet with data or without data, so I suppose t…

Hello Thank you for that - I’ve only ever worked with TCP connections i suppose as end user where i’m just receiving stuff and not having to manage both sides. ( these could send more than 1024 bytes i believe so not had to work around this issue before ) I’ll add the packet length to the start of…

TCP connections offer in-order reliable delivery so you shouldn’t be getting any data out of order. But you do need to be careful because even if you send 512 bytes, for example, there’s no guarantee that the server will receive 512 bytes at once. Often they will but it’s not guaranteed. They could…

My server code manages the multiple packets it receives from the particle tcpclient and stitches them together. I’ve tested with a sting 1500 chars long and I receive the data in 2 packets. Now I know I have to include the length and terminator myself I should be fine. Thanks

Electron tcpclient.write issues

Firmware

ninjatill August 24, 2018, 3:47pm 4

Check out this post by @rickkas7 which deals with sending large amount of data from a Photon to a server via TCPClient:

Topic		Replies	Views
Electron TCPClient.write issue Firmware	20	5318	April 8, 2016
[solved] Electron: TCPClient weirdness Troubleshooting	16	5681	May 1, 2016
Cloud/server communication speed General	3	1764	May 4, 2016
TCPClient HTTP POST on Electron is Intermitant Troubleshooting	5	1788	February 19, 2017
Electron sending buffer to server (TCP client) Troubleshooting	0	639	March 24, 2017

Electron tcpclient.write issues

Related topics