Qt Quick QML Read Data over Serial Port and Show on GUI
-
Hi,
Only with QtQuick ? You can't. However you can use QSerialPort for that on the C++ side for the serial port communication and then QtQuick for the UI.
Hope it helps
-
There's no example of that case precisely, but you can take a look at the Extending QML with C++ chapters from Qt's documentation, the bases are the same.
-
Hi,
So with QSerialPort they get data only once ? From a quick look, their code is doing that, get the data once, set it in your QML code and start the application. There's even a memory leak.
Do you have access to the code they wrote for QSerialPort ?
-
That's all the code they've written. They didn't use QSerialPort ta all but used ioinput stuff in C++ I believe.
We asked them to get data from serial port and keep changing the GUI. However their code only does this once. They claim that with Qt you can only get the data once, when application starts, and not possible to keep receiving data and keep changing the GUI.
We have told them that Qt is a powerful tool that's able to do but they're arguing otherwise.
-
I am the contractor who written this code.
what this while(1) is doing. Is it not continuously looping and reading the data. It is a loop, and it is continously reading. it is not 1 time read.
while (1) {
char *data = GetNextLine(fp);
printf( " %s , %d\n", data, strlen(data));ya, I had not cleared the buffers yet. But that is this customer kept asking for this data to be refreshed on the GUI UML continously.
For that , it needs to have additional triggers, like atleast a button, so that it will do the signal and read.
or it needs to do the serial port reading from QML. What the customer gave as requirement is , read from serial port and display . ya, ie done.
QT is taking the last data read and display in QML.
For refreshing QML atleast He should tell, there should be an additional button object. So that we press that and it continously refresh.
As I kept working on that, I had not yet deleted the memory allocated for the buffers. I kept helping him , explaining him. But he could not understand.Now you tell me , after the app.exec, control goes in that GUI and never returns back to the program. Then without a signal and slot or without any check, How it will send message to the QT GUI?.
The QSerial port of the customer returns canRead() function to be false all the time. So I used C++ method to read the code.
Please explain if this canread() function comes as false, then no read can be performed. what needs to be done.
I am expert in my ways. So I used C++ to do this. Now about QT GUI refresh with the data for QML from the indefiniteloop, what I need to do?. without a button / or any other signal handlers?
-
The first while loop will run exactly once since at the end you either assert or call return app.exec().
There's no need for any infinite loop nor additional triggers. Use the asynchronous technique aka signals and slots. The terminal example from the qtserialport module shows how to do it.
-
It is running indefinitely and it is printing the output in the console log by keep reading and displaying. the major issue with QTSerial port is
it is getting recognized. But it is returning
canReadable as false.ie the problem I have in that.
you are asking to use this way.
@
QSerialPort port;// ... serial port initialization here // Connect signals/slots connect(&port, SIGNAL(readyRead()), this, SLOT(readData())); port.open(); // Start a new message loop on this thread exec();
@
But the following things in QTSerial port is returning false.
http://doc.qt.io/qt-5/qtserialport-terminal-example.html
and
http://qt-project.org/forums/viewthread/33090
http://qt.apidoc.info/5.2.0/qtserialport/examples.html
http://qt-project.org/wiki/QtSerialPortHe has problem with his Serial port way, I had corrected that for my work even 4 things on that and made the data to come by normal cpp reading.
Please let me know what to do for this?
@
#include <QtCore/QCoreApplication>
#include <QtCore/QDebug>#include <QtSerialPort/QSerialPort> #include <QtSerialPort/QSerialPortInfo> QT_USE_NAMESPACE int main(int argc, char *argv[]) { QCoreApplication a(argc, argv); // Example use QSerialPortInfo foreach (const QSerialPortInfo &info, QSerialPortInfo::availablePorts()) { qDebug() << "Name : " << info.portName(); qDebug() << "Description : " << info.description(); qDebug() << "Manufacturer: " << info.manufacturer(); // Example use QSerialPort QSerialPort serial; serial.setPort(info); if (serial.open(QIODevice::ReadWrite)) serial.close(); } return a.exec(); }
@
This is taken from http://qt-project.org/wiki/QtSerialPort
This is the code. It is working upto recognization and give the corresponding manufacturer and the port number etc.
but the QSerialPort::canReadLine() also returning false.had been referenced for this.
This is the source code of QtSerialPort had been referenced.,
CanReadLine() function is returning a false as the value.,serial.open(QIODevice::ReadWrite) also returning false.
the QT Serial port device recognization had been done.
what needs to be done for this?. if it comes with false as value and not reading it.
thanks,
regards,
MVS[edit: added missing coding tags @ SGaist]
-
Did you check what error you got since open failed ?
canReadLine will only return true if you received a line of data on your serial port.
-
The terminal example works fine on our Linux machine. Hence the port works absolutely fine. What we've noticed is that with the Qt terminal example the port initialises fine and it works even if the device that outputs the serial data is disconnected and reconnected. With the pure C++ code that the contractor has provided this is very glitch and manual. We need to go to Linux terminal and set the budrate every time off it to work.
-
So finally He agreed , He needs to set some values to make it to work.
" We need to go to Linux terminal and set the budrate every time off it to work. "
So this is his fault. And I kept trying with QTSerialPort several time and it had returned with CanReadWrite() as false.
I had provided the right soln and I know it is right. His serial port is not getting value with CanReadWrite() as true. He is now telling this.
In linux terminal port, He is setting some baud rate to make it to work.
I had verified , for corrections, 4 times on his port and made the normal way to work. Now for this , He is tellingthis is not his fault. CanReadWrite() as true only QT Serial Port will work.
If QTSerialPort is working fine, then CanReadWrite() will return value as true.
ie the proof. So why it is returned as false?. whether he again claims that His serial port baud rate or his on off of device, or no data had come?.we work by hrs. we are not infront of the machine and checking and doing it. When it returns false as value, I am sure it had not worked. He is now taking more time than needed.
As Expert always , I gives best soln. I had checked this and told him. Now I am really doubt to work with him again.
-
[quote author="valliammal" date="1418522987"]So finally He agreed , He needs to set some values to make it to work.
" We need to go to Linux terminal and set the budrate every time off it to work. "
So this is his fault. And I kept trying with QTSerialPort several time and it had returned with CanReadWrite() as false.
I had provided the right soln and I know it is right. His serial port is not getting value with CanReadWrite() as true. He is now telling this.
In linux terminal port, He is setting some baud rate to make it to work.
I had verified , for corrections, 4 times on his port and made the normal way to work. Now for this , He is tellingthis is not his fault. CanReadWrite() as true only QT Serial Port will work.
If QTSerialPort is working fine, then CanReadWrite() will return value as true.
ie the proof. So why it is returned as false?. whether he again claims that His serial port baud rate or his on off of device, or no data had come?.we work by hrs. we are not infront of the machine and checking and doing it. When it returns false as value, I am sure it had not worked. He is now taking more time than needed.
As Expert always , I gives best soln. I had checked this and told him. Now I am really doubt to work with him again.[/quote]
You're mixing things up.
The Qt terminal example uses the QtSerialPort library, and works fine on our machine. This means that it initialises the serial port correctly and hence reads it fine. Therefore there is nothing wrong with the actual serial port.
Your code needs this command to run on Linux terminal in order for it to work:
stty -F /dev/ttyUSB0 115200This makes things very manual!
If the code that you tried with QtSerialPort library returns false with CanReadWrite(), there must be something wrong with your code and not with the actual serial port. As explained above Qt terminal example works fine and it does makes used of the QtSerialPort library.
-
Hi guys, we have managed to use QtSerialPort libraries to achieve what we need.
Our serial read code runs in a separate thread in a forever to receive the data and update the GUI.
Here is the serial code. Would you kindly have a look and make sure it is good to go?
Our data that arrives looks like this:-
234|654\n@QString elem0;
QString elem1;forever {
if (serialPort.waitForReadyRead(1500)) //set the timeout time for the port { serialPort.flush(); /make sure there is no old data every time we want to read QByteArray data; QStringList myArrayOfNums; if (serialPort.canReadLine()) //If we can read the data then read it { data = serialPort.readLine(); //Read line of data as Byte Array QString myData(data); //Convert the received the data to String myArrayOfNums = myData.split("|"); //Split the data as it's delimited and put into a String List //USE THE FINAL DATA elem0 = myArrayOfNums[0].simplified(); //simplified removes any white spaces/characters elem1 = myArrayOfNums[1].simplified(); qDebug() << elem0; qDebug() << elem1; } }@
One thing we've noticed is that when waitForReadyRead() is set to for example waitForReadyRead(30), so only 30 millisecs, then waitForReadyRead() returns false quite alot. Does anyone know the reason for that?
Additionally if we monitor the data that arrives into the Qt application, every often canReadLine() also returns false. Is there a way to make sure it always returns true so receiving data can become smoother and loss of data eliminated?
-
Why not it in asynchronous mode and use readyRead() + readAll() ?
-
Actually most of the issues are sorted.
Still not using readyRead() though. However I have connected our microcontroller to our Raspberry Pi via the UART (Rx/Tx pins) with a level shifter.
The Qt app cannot read anything from the /dev/ttyAMA0. It all works fine if the microcontroller is connected to the Raspberry Pi via USB.
Is this normal?
-
Depends, do you have the rights to read/write from /dev/ttyAMA0 ?