QT transmitting large data over Serial Port
up vote
0
down vote
favorite
I am trying to send a large amount of data via a QSerialPort (which actually goes over a RS232 connection). At present, I can get ~300 bytes of 80000 bytes. Using Putty, I can see all the data being transmitted, so the problem is with the receiving code, I believe.
Receiver code:
m_serial->waitForReadyRead(1000);
m_serial->waitForBytesWritten(20);
const QByteArray data = m_serial->readAll();
Transmitter code:
QByteArray sendData;
sendData.setRawData((char *)dataBuf, m->bufSize + sizeof(*mHeader) + 1);
m_serial->write(sendData);
I get valid data if I send any amount of data (at least the data I get).
Is the only solution to break up the data into separate transmits?
EDIT: I should mention that I am using an async implementation (the one from QTs examples - the async terminal program. It only sends and recieves small amounts of data, though)
The program connects to the readData() function using:
connect(m_serial, &QSerialPort::readyRead, this, &MainWindow::readData);
qt serial-port
asked Nov 22 at 15:21
Hengy
324
add a comment |
up vote
0
down vote
favorite
I am trying to send a large amount of data via a QSerialPort (which actually goes over a RS232 connection). At present, I can get ~300 bytes of 80000 bytes. Using Putty, I can see all the data being transmitted, so the problem is with the receiving code, I believe.
Receiver code:
m_serial->waitForReadyRead(1000);
m_serial->waitForBytesWritten(20);
const QByteArray data = m_serial->readAll();
Transmitter code:
QByteArray sendData;
sendData.setRawData((char *)dataBuf, m->bufSize + sizeof(*mHeader) + 1);
m_serial->write(sendData);
I get valid data if I send any amount of data (at least the data I get).
Is the only solution to break up the data into separate transmits?
EDIT: I should mention that I am using an async implementation (the one from QTs examples - the async terminal program. It only sends and recieves small amounts of data, though)
The program connects to the readData() function using:
connect(m_serial, &QSerialPort::readyRead, this, &MainWindow::readData);
qt serial-port
asked Nov 22 at 15:21
Hengy
324
If you are using the asynchronous example, you should NOT be using waitForXYZ methods, using them together with signals/slots leads to undefined behaviour. Other than that your example does not give enough information / working code to reproduce.
– markus-nm
Nov 23 at 14:06
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am trying to send a large amount of data via a QSerialPort (which actually goes over a RS232 connection). At present, I can get ~300 bytes of 80000 bytes. Using Putty, I can see all the data being transmitted, so the problem is with the receiving code, I believe.
Receiver code:
m_serial->waitForReadyRead(1000);
m_serial->waitForBytesWritten(20);
const QByteArray data = m_serial->readAll();
Transmitter code:
QByteArray sendData;
sendData.setRawData((char *)dataBuf, m->bufSize + sizeof(*mHeader) + 1);
m_serial->write(sendData);
I get valid data if I send any amount of data (at least the data I get).
Is the only solution to break up the data into separate transmits?
EDIT: I should mention that I am using an async implementation (the one from QTs examples - the async terminal program. It only sends and recieves small amounts of data, though)
The program connects to the readData() function using:
connect(m_serial, &QSerialPort::readyRead, this, &MainWindow::readData);
qt serial-port
asked Nov 22 at 15:21
Hengy
324
I am trying to send a large amount of data via a QSerialPort (which actually goes over a RS232 connection). At present, I can get ~300 bytes of 80000 bytes. Using Putty, I can see all the data being transmitted, so the problem is with the receiving code, I believe.
Receiver code:
m_serial->waitForReadyRead(1000);
m_serial->waitForBytesWritten(20);
const QByteArray data = m_serial->readAll();
Transmitter code:
QByteArray sendData;
sendData.setRawData((char *)dataBuf, m->bufSize + sizeof(*mHeader) + 1);
m_serial->write(sendData);
I get valid data if I send any amount of data (at least the data I get).
Is the only solution to break up the data into separate transmits?
EDIT: I should mention that I am using an async implementation (the one from QTs examples - the async terminal program. It only sends and recieves small amounts of data, though)
The program connects to the readData() function using:
connect(m_serial, &QSerialPort::readyRead, this, &MainWindow::readData);
qt serial-port
qt serial-port
asked Nov 22 at 15:21
Hengy
324
asked Nov 22 at 15:21
Hengy
324
edited Nov 22 at 16:09
asked Nov 22 at 15:21
Hengy
324
asked Nov 22 at 15:21
Hengy
324
asked Nov 22 at 15:21
Hengy
324
324
If you are using the asynchronous example, you should NOT be using waitForXYZ methods, using them together with signals/slots leads to undefined behaviour. Other than that your example does not give enough information / working code to reproduce.
– markus-nm
Nov 23 at 14:06
add a comment |
If you are using the asynchronous example, you should NOT be using waitForXYZ methods, using them together with signals/slots leads to undefined behaviour. Other than that your example does not give enough information / working code to reproduce.
– markus-nm
Nov 23 at 14:06
If you are using the asynchronous example, you should NOT be using waitForXYZ methods, using them together with signals/slots leads to undefined behaviour. Other than that your example does not give enough information / working code to reproduce.
– markus-nm
Nov 23 at 14:06
If you are using the asynchronous example, you should NOT be using waitForXYZ methods, using them together with signals/slots leads to undefined behaviour. Other than that your example does not give enough information / working code to reproduce.
– markus-nm
Nov 23 at 14:06
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53434035%2fqt-transmitting-large-data-over-serial-port%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If you are using the asynchronous example, you should NOT be using waitForXYZ methods, using them together with signals/slots leads to undefined behaviour. Other than that your example does not give enough information / working code to reproduce.
– markus-nm
Nov 23 at 14:06