Move QModbusClient responseTimer into QModbusRtuSerialMaster

The TCP client doesn't use a queue system for requests and therefore
needs one timer per request. Therefore the abstraction offered by
QModbusClient is not suitable for the TCP client. As a consequence
we move the response timer into the RTU client implementation.

Change-Id: Ic30dfd730bcdae42ee7515be0fdf0eaff64af2fa
Reviewed-by: Karsten Heimrich <karsten.heimrich@theqtcompany.com>

1 files changed, 0 insertions, 5 deletions

diff --git a/src/serialbus/qmodbusclient_p.h b/src/serialbus/qmodbusclient_p.h
index 716067b..e9e3df4 100644
--- a/src/serialbus/qmodbusclient_p.h
+++ b/src/serialbus/qmodbusclient_p.h
@@ -86,10 +86,6 @@ public:
     bool processReadWriteMultipleRegistersResponse(const QModbusResponse &response,
                                                   QModbusDataUnit *data);
 
-    void startResponseTimer();
-    void stopResponseTimer();
-
-    virtual void handleResponseTimeout() {}
     virtual QModbusReply *enqueueRequest(const QModbusRequest &, int, const QModbusDataUnit &,
                                          QModbusReply::ReplyType) {
         return Q_NULLPTR;
@@ -98,7 +94,6 @@ public:
     virtual bool isOpen() const { return false; }
 
     int m_responseTimeoutDuration = 200;
-    QTimer *m_responseTimer = Q_NULLPTR;
 
     struct QueueElement {
         QPointer<QModbusReply> reply;