@koahnig said in How to synchronize QTcpSocket data and timer data in the GUI:

Best you try it with a small example. Within the thread, you need to read the system clock and output.

Doing this .

Best you try it with a small example. Within the thread you need to read the system clock and output.
At the day's end all depends on the actual thread scheduling of your computer and device. The weakest link in the chain determines the accuracy.
You will probably need to do a lot of testing. Also you need to consider what you actually want to have. One thing could be the even scaling for plotting or is it the precise and accurate knowledge of when the values are taken.

double elapsed=clock.elapsed();
int no_of_interval=256;
double msecs=no_of_interval-(clock.elapsed()-elapsed);
if(msecs>0.0)
QThread::usleep(qRound(msecs*1000));

If this is your only option, you can try. Note, gut feeling on my side is that you will have varying time intervals between your "measured values". If this is acceptable, you need to decide.

there might be possibility to run a thread checking the contents of the buffer very quickly.

I can go with a thread.
if I connect readyRead() to collectData() and store the data in buffer.
after that by using QwtSystemClock clock in socket.cpp and calling sendToGui() every second and passing the data, Can I go with it?.

IMHO you will need time tags from device sending through tcp/ip. That is the most accurate possibility.

QTcpSocket has a buffer and all in-coming data will be accumulated there. Typically sometime at the beginning you will receive a readyRead signal. At which time your application will react on the signal is dependend on a couple of factors (e.g. cpu load, time retrieve each data record, time to plot, ...).

If you have a fast machine with a couple of cores, there might be possibility to run a thread checking the contents of the buffer very quickly. This would allow for assigning a time-tag for each value, but probably not too close to actual measuring time.