@sykac said in Turning off power to a running QSerialPort:

One problem starts probably in the hardware. The COM port of the device disconnects from the PC (I don't why, it could be some driver/firmware issue)

Reading you topic title, could it be that the USB connection between PC and FTDI is interrupted? And that's what I said, this may lead to endless loops in the device driver.

This kind of problems can hardly be solved in the user space.

I agree you need to use a state machine for that case. http://doc.qt.io/qt-5/qstatemachine.html probably helps putting down the skeleton already

Please try

while (true) { if (SerialPort.waitForReadyRead(100)) { while (SerialPort.canReadLine()) qDebug() << SerialPort.readLine(); } }

Now you can work on the already ready buffer obtained from "SerialPort.readLine();"

@cesar93 so if your problem is solved, please mark this topic as SOLVED too. Thanks

Solved. The missing libQt5SerialPort.so.5 error on the target device was because that library effectively was not present. On the host side I added that library in the package list of the image and rebuild the image itself.

@kuzulis Thank you. It works perfectly now :-)

TLDR: My mistake was to not instantiate and open the QSerialPort in the thread i was reading from.

@aha_1980 Thank you so much for your ideas. Both problems solved.

After reconfiguring aptitude stuff to use "stable" instead of hard-coded "jessie" and half-a-day-long upgrades and cleaning the mess I really got not only higher version of Qt, but as well QParallelPort working as planned. Definitely worth the effort (even if I did not expect the upgrade to take so much time.)

My mistake. I missed this single character overload to append(). Thank you for pointing me there. Now I got completely rid of that development/release conditionals.

Case closed, thanks to all who assisted.

Hi,

You can get the native handle with QSerialPort::handle and then modify its properties.

Hope it helps

How did you install Qt ?

@tangxinzhou I'm afraid I do not have a solid solutions. I'm running a workaround now.

Let me post it for you:

void connectDevice(bool connect) { if(connect){ switch (mDevice->state()) { case QModbusDevice::ClosingState: case QModbusDevice::ConnectedState: case QModbusDevice::ConnectingState: mDevice->deleteLater(); mDevice = new QModbusRtuSerialMaster(this); setupSignalSlots(); QTimer::singleShot(100,this, [=]{setConnectParamter(m_port,m_paramter);}); break; case QModbusDevice::UnconnectedState: default: if(!mDevice->connectDevice()){ emit signalModbusError(mDevice->errorString()); mDevice->disconnectDevice(); } break; } }else{ stopPoll(); mDevice->disconnectDevice(); QTimer::singleShot(200,this,[=]{checkDisconnected();}); } } void checkDisconnected() { if(mDevice->state() != QModbusDevice::UnconnectedState){ mDevice->deleteLater(); mDevice = new QModbusRtuSerialMaster(this); setupSignalSlots(); } }

@AngrySkarpeta
Well it might be overkill
but it´sounds like its not really connected but
without actual errors then its not possible to guess at all.
Could be a driver issue or trust issue.
You should use other tools to try to test if they are really paired.

@QtExchange said in Segmentation fault or overflow when streaming from a QSerialPort:

The trick is one QByteArray receives the data (on signal slot basis)

QByteArray can receive nothing, it's an array of bytes - a container, nothing more, nothing less.

where the other container (which is just a copy of the receiver-QByteArray) is parsing the received Data, as the symbols come in a random order.

??!
How can you parse something that doesn't have any order? And where is this other container?

I could think of having an extra signal-slot that exchanges the data between both containers whenever it is demanded, but it sounds like I have to double check if I'm actually dealing with the most current data.

I don't follow. Why would be this even needed ...?

There's an extra mutex for the device access, and another one for the shared message container.

Qt imposes thread affinity on QObject instances, you don't need a mutex for device access, and you shouldn't share the message container.

and because I'm dealing with QElapsedTimer, that needs the thread.

In what universe QElapsedTimer needs a thread ...?! It's like saying that an integer needs a thread ... I don't get it.

It is not a qserialport issue, it is a kernel/driver issue. A driver of your serial port has bugs, you should try to update driver or to use another HW device.

@cdcc0606
Typical, can you upgrade to 5.3?

Hi,

What about reading the whole buffer and then search for the first occurrence of '\r' ? That way you avoid to loop on the input

@Basti46
Good work!
:)

Just to confirm that QSerialPort can be used on rooted Android. (Some info)

Notes:

#ifdef Q_OS_ANDROID /* This will open the Superuser app, * prompting for root permisions */ QProcess proc(&a); proc.start("su -c \"chmod 666 /dev/ttyUSB0\""); #endif Don't forget to disable SELinux on Android 4.2 and above :)

I figured out, it was nescessary to set DTR:

port.setDataTerminalReady(true);

Thanks & br, Clemens

So does the QT appends '\0' terminator after every append? (

For QByteArray - No.

Getting back to document conclusions of my research on best practice of using RaspiComm RS-485 under Qt for anybody, who finds this thread useful (I expect many of it is valid for RS-232 on same board as well, did not test myself):

Do not try to implement communication with MAX3140 UART chip yourself (maybe except of asm based implementation, what is however most probably unnecessary exertion). I succeeded to implement it based on kernel /dev/spidev0.0 only to find out that even this partially system driver supported solution is too slow for even 19 200 Bd speed (loosing about 5 characters on one received).
I myself feared about RaspiComm RS-485 driver /dev/ttyRPC0 based on some forums complaints and not clear versioning, however found out, that the forum thread was heavy outdated. These official installation instructions worked like a charm and the resulting driver worked out-of-box for my latest Raspbian Wheezy (4.1.7+ #817). So I strongly recommend to take this approach.

QSerialPort class has constructor with signature QSerialPort(const QString &, QObject *), where QString may contain even device which is not included in the QList that QSerialPortInfo::availablePorts() returns. This works with no surprise. If one does not set anything than (eventually) baud speed, one gets standard 8 bit, 1 stop bit, no parity without any character translations, good old plain raw binary. So QSerialPort may be used with /dev/ttyRPC0 directly and easily.

QSerialPort rpc0("/dev/ttyRPC0"); rpc0.write("Binary request\0even\xffcontaining weird\x03characters", length_of_binary); if(rpc0.waitForReadyRead(100)) // Enough long time in miliseconds QByteArray data = rpc0.readAll(); // You may have to wait/read repetitively in loop // and merge data on higher link speeds Hardware of RaspiComm uses RTS pin to select in/out direction of data. CTS is kept active permanently by wiring, so using default use RTS/CTS mode works properly with no inappropriate blocking.

That's all you should need, so enjoy your communication.

@kuzulis: Thanks for the hint to update to 5.6.0! Since it is some effort to update the embedded installation on the Qt target, I first tried the terminal example with 5.3.2, just adding /dev/ttyGS0 as a serial interface manually. Interestingly, transmission worked very well even after re-loading the g_serial driver.

So i had a look at my own qt program, again. First, very strangely, transmission didn't work at all, but after restarting the embedded system, doing a "clean all" on the project and built it again, everything now works perfectly also in my program... Very strange...

So I hope there has only happened something in the build directory and now everything is solved doing the clean and re-building...

Everybody, thanks a lot for your help!

Greetings,

Markus

PS: I also had to update my desktop qt installation for receiving the terminal example files (didn't find the bundled files on the qt site and my installation didn't provide them, also), but I guess this didn't have an effect on my cross-compiled application...

Just for the community to know, the problem was on the firmware of the integrated J-Link OB-SAM3U128.
Latest firmware upgrades bring this known bug with QSerialPort on windows.

More information can be found here:
[http://forum.segger.com/index.php?page=Thread&postID=8772](link url)

I fixed the problem downgrading the segger firmware to the 2014 Nov 28 10:32.
To do that, uninstall the segger application and drivers and install an older version you can find in the website.
For me worked the version 496g.

To downgrade the firmware before you have to invalidate it: with the jlink commander execute "exec InvalidateFW" and then, from the jlink configurator replace with the current host version (right click on the emulator raw -> replace firmware).

Hope this could save a few working hours to someone.

If anyone managed to found better work-arounds, please post them here!

Ok, even i tried copying by libraries to the deploying system, and exported it , then binary will execute, but serial port will not work as in the code.,

I didn't saw that there was no tooltip for them… At least there is for the flag and quote :)

Thanks :)

@Rondog @kuzulis I'm going to give the bytesWritten()signal a try, I will let you know how it worked out. I don't have a separate thread set up, but it's definitely worth the try! Big thanks for the reply's!

There are a few options.

char c; while(port.read(&c,1) > 0) // returns the number of char's read, -1 on error { if(c) { // 'c' does not contain null. do something with it } };

or maybe something like this

QByteArray data; data = port.readAll(); // QByteArray & QByteArray::replace(char before, const QByteArray & after) data.replace(char(0x00),QByteArray());

Yes, i made this program by the terminal example.

I solve it. I use QStringList to delete the first response.

But, i thank you for for answer.

Thank you for the idea. Yes, writing a wrapper class around the serial port worked like a charm. I implemented it a bit differently, a message handler manages the message building and sending it off to the serial port but the concept is the same. The only thing I found different from your example is that the timer isn't destroyed when it runs out. Instead of creating a new one every time, I created one as part of the class and use it over and over again.

Thank you very much for the insight!!

This might be the culprit:

while (serial->waitForReadyRead(200))

This will put your thread to sleep until data has arrived or 200 ms has elapsed. QSerialPort seems to rely on the message loop to handle data so this might interfere with it (?). There is no guarantee that you will have 512 bytes of data back at once either.

There is a signal (QSerialPort::readyRead() ) you can use when received data arrives. Connect this to a suitable slot and buffer what has arrived each time the signal is fired (I assume you will not get all the data at once). Do this until you have 512 bytes then process it. Keep the event loop active if you have some other 'heavy' function somewhere (QApplication::processEvents() ).

I am sorry about my last post. I made a stupid error. I updatet to QT5.5, but I haven't reconfigurated the project, so I was still using QT5.4.
Now I tried also the Chipi-X10 USB-RS converters. I have to say, they work a lot better. I have now for all three ports, this converter. With the others, a lot of times I had to unplug and replug the connectors to get dem work. So there is something strange. The Chipi worked really good until now, thank you jeroen3, this will save a lot of time.
After building the programm with QT5.5, the programm also work a lot better. I saw that the qcustemplot keeps plotting while I drag and drop the window. I have sometimes errors but now only sporadic. For example when I resize the window very fast, I can provoke it. But in general the errorrate is about one or two percent, and with that I can live.

PS: We here do not play in telepathists and predictors. If you want to get help, you should provide the minimal and simple example....

My problem was, that with the minimal simple example all seems to working. This communication problem I had only, wenn all the data was coming and when I was plotting someting in the same time. And I checked my code a lot of times. The problem is, my knowhow about QT and generell about programming with PCs is not very big. So I think there is something I do not know. So when I check my code a hundet times more, I will not find an error.

I made also an easy experiment to isolate the error:
My I slowed up the replot, so that I plot only every tenth time, but ten points at the same time. Like this I can see, that this error, comes only when the window is plotting. The error comes more, the more points he has to plot on the screen. So if I make fullscreen, and I set up the scale so that I have the maximum of points in the axis, the error comes every time again.
So QT has an influence to this problem. I think there is an overflow in some buffer, beause the program is to slow to read it or that he overwrites any part for some other reasons. But anyway.. For me I will pay attention now to not overcharge my comuter :)
Thank you for all help!

@SGaist

Thank you very much for your tips!
I probably should give up on the serial thread. It is beyond my ability to play with that problem.

Hi @pthinks,

I highly recommend you proofread your post.

It contains false advertising (you are not the top 2nd contributor in the forum) It contains outdated information (qt-project.org is now offline) It's full of formatting errors ("list listItem")

@syndrome

QSerialPort serial; ... // some stuff for initialisation and more char xon ( 17 ); char xoff ( 19 ); serial.writeData ( &xon, 1 ); // will send XON serial.writeData ( &xoff, 1 ); // will send XOFF

Check out writeData . Do you know how send the rest?

@JohnYork said:

based on my experience, I think some warning comments should be added into Qt's API documents, to avoid the unecessaried mistakes on Qt newbies, just like me. Do you think so?

It is tempting to want to place the blame on your framework or compiler however in my experience 99.9999% of the time it is the design or the programmer that is causing the issue.

For the most part the code was exactly what you programmed it to do. What makes things harder now days is you really don't know how long an object lives when it is created in some strange place. Most objects in the framework have a parent pointer and when the parent dies or if you don't use parent (in some cases) and the object dies because of scope then all bets are off if you have pointers to that object.

In the "old" days we pretty much managed everything ourselves. You created something, you had to get rid of it.

Even with the newer ways of managing items I still find that at times knowing exactly when an object is valid and when it is not is invaluable. Therefore somethings need to be singletons that you create and leave around until you decide you are done with them.

Anyway I doubt there is any comment that could be added to docs to help out with these concepts. The Qt docs document the use of the framework, not how to manage objects and object scope.

Since those principles apply to ALL C++ objects a standard C++ tutorial, book or online course will give you what you need. This forum with the great people here can help to fill in the gaps on Qt related stuff. You'll find the people here amazingly knowledgeable and talented.

@seltra2 said in QSerialPort, communicating through RS485:

Can you confirm that QtSerialPort can handle both Rs 232 and Rs 485

I confirm QSerialPort works on both RS232 and RS485, I use this normally. Take a look at my source, and see how things work.

I've put more examples, these examples I use with RS485. I hope I have helped and good luck. But remembering that I recommend the use of the converters with the CH340 chip, the FTDI are too problematic.

http://www.simcore.com.br/downloads/QtForum/53877/

#2 is wasteful way indeed!
but in low baud rates it will help, but in this case I don't think this is a low baud rate.

EDIT : I said for example 1ms, you really don't need it this fast, it depends on the frequency of getting bytes, for example for 20Hz you will have 20bytes every second which means you need a timer with at least 50ms refresh time and of course you read from serial port in asynchronous way then you can't 100% trust this way to read byte by byte, So as @JKSH said you better don't use this way if you don't have a specific reason.

Resurrecting this ancient thread with a concrete solution in case it helps someone: I just ran into this as well; libudev debug messages were cluttering the Application Output. It turns out you don't even have to query serial ports -- the messages are emitted just by virtue of including the serialport module.

Like the OP, turned out that I too had turned on some logging to debug a different problem ages ago. After some hunting, I discovered that this logging had been enabled by adding the line

udev_log="debug"

in /etc/udev/udev.conf. After I commented out that line and rebooted, the libudev messages are gone!

I added a delay function before reading the serial port,

console->SenDelay(70); QByteArray data = serial->readAll();

now everything is working.