QT transmitting large data over Serial Port





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















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);









share|improve this question

























  • 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 '18 at 14:06




















0















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);









share|improve this question

























  • 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 '18 at 14:06
















0












0








0








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);









share|improve this question
















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 '18 at 16:09







Hengy

















asked Nov 22 '18 at 15:21









HengyHengy

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 '18 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 '18 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 '18 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 '18 at 14:06














0






active

oldest

votes












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















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

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







Popular posts from this blog

Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

ComboBox Display Member on multiple fields

Is it possible to collect Nectar points via Trainline?