TCP port time between signals trouble

General
1

Hello, I hope someone can help me with a signal over TCP port with the time between signal increasing. Which causes a lag in reading the data.

I’m running Node-Red version 7.0.4 on Windows 10, dashboard v2. There is a sensor sending a signal 8x a second (~125ms) to port 2113. When I measure the interval time between signal it start at 125ms between signal which I believe is the correct amount of time. From the sensor without using NR I can measure a consistent signal at 125ms interval. The TCP server node, node-red-contrib-tcp-client2, connects to the signal well. However, after a few minutes the interval goes from 125ms to 260ms and higher.
It would be nice to know how to know how to optimize a TCP port connection and keep it running smoothly. If anyone has any suggestions on how to optimize a TCP port or could suggest what to look for I would greatly appreciate it. Thank you in advance.

2

Hi

just wondering why you are using a contrib node rather than the built in tcp node ?

Also what are you then doing with the data ? Are you doing something potentially slow with it ? Like calling out to some other process ? ( that could cause it to start backing up)

3

This is not a valid version of node-red. Latest node-red version of 4.1.0.

This is not a core node. Any reason you are not not using built in TCP nodes?

Regarding the slow down, perhaps something you are doing after recieving the messages?

4

Sorry, running NR v4.0.9

5

Thank you for the comment. What is the difference between the contrib nodes and the built in TCP node? I’ll test the built in TCP node.

The data is sent to a chart in dashboard v2. The chart is one minute of data at a sample rate of x8 per second, ~125ms. The chart data is cleared every minute.