After my node-red connects to the tcp server, if there is a slight load in the function that gets the data. It seems that debug sometimes outputs the next set of buffer data. If I reuse msg objects. [image] Testing function code // msg = { payload: [] } msg.payload = [] ; (() => { let i = 0…

[image] fullmooooon: interspersed with periodic data. You need to use the "TCP-In" for unsolicited data (the periodic data) And you should use "TCP-out" for sending the commands to end point. If you do manage to put together a drawing and can provide the protocol detail i may be able to hel…

Topic		Replies	Views
Tcp request node issue General	8	501	25 July 2022
Tcp request node, host/port via flow works only once General	20	6734	3 February 2019
Send message on tcp node General	18	634	29 January 2023
NodeRed TCP OUT Node Success Response General	17	585	27 September 2023
TCP-IN node send data internally General	9	228	18 April 2023

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Tcp msg is reassigned to the next data before debug output

Related topics