Cannot execute echo command in QProcess

Question

I want to launch a SCPI command in my device using netcat utility under Ubuntu 10.04 LTS with Qt. My code looks like:

env = "echo TRIG | nc 192.168.1.100 23 -q1";
process1.execute(env);
process1.waitForFinished(1000);

This command does not return any data but simply triggers the data acquisition. If using terminal with same "echo TRIG | nc 192.168.1.100 23 -q1" command, everything works fine. From Qt, it does not work. The debug output is "TRIG | nc 10.0.3.250 23 -q1" ... so without an "echo". My device does not receive the TRIG command.

Could you please advise what I'm doing wrong? Many thanks.

Duplicate of http://stackoverflow.com/questions/10701504/command-working-in-terminal-but-not-via-qprocess — Frank Osterfeld, Oct 29 '13 at 07:56
Why on Earth would you do that when Qt natively supports sending data via TCP/IP sockets? Opening a connection and sending a simple message is easy. — Kuba hasn't forgotten Monica, Oct 29 '13 at 18:30

Kuba hasn't forgotten Monica · Answer 1 · 2017-04-20T17:55:12.433

The code below shows a fairly complete, asynchronous implementation of this functionality. It demonstrates how it can be done without launching external processes, and how to leverage C++11 lambdas in Qt 5. For Qt 4, the slots from main() would need to live in their own QObject-derived class.

screenshot

#include <QtWidgets>
#include <QtNetwork>

class SocketSignaler : public QObject
{
   Q_OBJECT
   Q_SLOT void stateChanged(QAbstractSocket::SocketState state) {
      if (state == QAbstractSocket::UnconnectedState) emit unconnected();
      else emit busy();
      emit hasState(this->state());
   }
public:
   explicit SocketSignaler(QAbstractSocket * socket) : QObject(socket) {
      connect(socket, &QAbstractSocket::stateChanged, this, &SocketSignaler::stateChanged);
      connect(&(const QObject&)QObject(), &QObject::destroyed, this, // defer signal emission
              [=]{ emit stateChanged(socket->state()); }, Qt::QueuedConnection);
   }
   Q_SIGNAL void busy();
   Q_SIGNAL void unconnected();
   Q_SIGNAL void hasState(const QString &);
   QString state() const {
      switch (static_cast<QAbstractSocket*>(parent())->state()) {
      case QAbstractSocket::UnconnectedState: return "Disconnected";
      case QAbstractSocket::HostLookupState: return "Looking up host";
      case QAbstractSocket::ConnectingState: return "Connecting";
      case QAbstractSocket::ConnectedState: return "Connected";
      case QAbstractSocket::ClosingState: return "Closing";
      default: return {};
      }
   }
};

class Ui : public QWidget {
   Q_OBJECT
   Q_PROPERTY(bool busy WRITE setBusy)
   QVBoxLayout m_layout{this};
   QFormLayout m_form;
   QLineEdit m_target{"192.168.1.100"};
   QLineEdit m_message{"TRIG"};
   QLabel m_state;
   QDialogButtonBox m_box;
   QPushButton * const m_send = m_box.addButton("Send", QDialogButtonBox::AcceptRole);
   QPushButton * const m_cancel = m_box.addButton(QDialogButtonBox::Cancel);
   QMessageBox m_msgBox{this};
public:
   Ui() {
      m_form.addRow("Target Host", &m_target);
      m_form.addRow("Command", &m_message);
      m_layout.addLayout(&m_form);
      m_layout.addWidget(&m_state);
      m_layout.addWidget(&m_box);
      m_msgBox.setIcon(QMessageBox::Critical);
      connect(m_send, &QPushButton::clicked, this, &Ui::send);
      connect(m_cancel, &QPushButton::clicked, this, &Ui::cancel);
   }
   void setState(const QString & text) { m_state.setText(text); }
   QString target() const { return m_target.text(); }
   QString message() const { return m_message.text(); }
   void showError(const QString & text) {
      m_msgBox.setText(text);
      m_msgBox.show();
   }
   void setBusy(bool busy) {
      m_send->setEnabled(!busy);
      m_cancel->setEnabled(busy);
   }
   Q_SIGNAL void send();
   Q_SIGNAL void cancel();
};

int main(int argc, char *argv[])
{
   const int targetPort = 23;
   QApplication app{argc, argv};
   Ui ui;
   ui.show();

   QTcpSocket socket;
   SocketSignaler socketSig{&socket};
   QObject::connect(&socketSig, &SocketSignaler::hasState, &ui, &Ui::setState);

   QStateMachine machine;
   QState sReady{&machine};
   QState sBusy{&machine};
   sReady.assignProperty(&ui, "busy", false);
   sBusy.assignProperty(&ui, "busy", true);
   sReady.addTransition(&socketSig, &SocketSignaler::busy, &sBusy);
   sBusy.addTransition(&socketSig, &SocketSignaler::unconnected, &sReady);

   QObject::connect(&ui, &Ui::send, [&](){
      socket.connectToHost(ui.target(), targetPort);
   });
   QObject::connect(&ui, &Ui::cancel, [&](){ socket.abort(); });
   QObject::connect(&socket,
                    static_cast<void (QAbstractSocket::*)(QAbstractSocket::SocketError)>
                    (&QAbstractSocket::error), [&]()
   {
      ui.showError(socket.errorString());
   });
   QObject::connect(&socket, &QAbstractSocket::connected, [&](){
      auto msg = ui.message().toLatin1();
      msg.append('\n');
      if (socket.write(msg) >= msg.size()) socket.close();
   });
   QObject::connect(&socket, &QAbstractSocket::bytesWritten, [&](){
      if (!socket.bytesToWrite()) socket.close();
   });

   machine.setInitialState(&sReady);
   machine.start();
   return app.exec();
}
#include "main.moc"

score 1 · Accepted Answer · answered Oct 29 '13 at 08:49

1

You can't use the pipe command (|) with QProcess that way.

There are a few ways to tackle this: -

You can call the first command and retrieve its output before processing it either in Qt or with another call to QProcess.

Or, create a script that you call from QProcess and retrieve the output.

Finally, assuming you're using linux / OSX, you can call QProcess with /bin/bash and pass the command to that. For example: -

env = "/bin/bash \"echo TRIG | nc 192.168.1.100 23 -q1\"";
process1.execute(env);

You can probably find an equivalent to /bin/bash for windows, perhaps cmd.exe

answered Oct 29 '13 at 08:49

TheDarkKnight

27,181
6
55
85

1

Thank for the hint. However, it returns the following: /bin/bash: echo TRIG | nc 192.168.1.100 23 -q1: No such file or directory This is probably something different (path?) – user2655700 Oct 29 '13 at 09:10
What is 'TRIG', is it a script or program? I don't recognise it as a standard bash call. – TheDarkKnight Oct 29 '13 at 09:13
TRIG is just a SCPI command that triggers the data acquisition on my remote device. – user2655700 Oct 29 '13 at 09:14
Can you use the full path to the command? I would guess that the environment path is not set up, in which case, alternatively, you can set the process environment before calling exec. – TheDarkKnight Oct 29 '13 at 09:17
It seems to me that "echo" is a problem. If I try to use just env = "/bin/bash \"echo abc\"" it returns same error. Maybe I don't understand the /bin/bash syntax. The "TRIG" command is a SCPI command and does not have a full path. I think I use that correctly. I'll try your other two proposals if this one doesn't work (but it's the most convenient one). – user2655700 Oct 29 '13 at 09:27
When I said to set up the environment I meant call the QProcess function setProcessEnviroment, not to pass it in the command to QProcess. Like this: QProcessEnvironment env = QProcessEnvironment::systemEnvironment(); – TheDarkKnight Oct 29 '13 at 10:08

Cannot execute echo command in QProcess

2 Answers2

Linked