UART sending string VS CharByChar
I am working on an embedded device with an UART connection. Via putty I send commands to that device using ASCII chars. When i send the chars one by one - pressing them manually- (default putty configuration) the device acknowledges the command, But when i enter the whole string and send it all on ENTER press (a different putty option) the device will not recognize the command.
I am sniffing the UART line and in both cases the same chars are detected on the line, on both configuration.
Fix?What may be causing this? Is it a known issue?
putty serial-port
asked Jan 10 at 8:03
user983288user983288
1
add a comment |
I am working on an embedded device with an UART connection. Via putty I send commands to that device using ASCII chars. When i send the chars one by one - pressing them manually- (default putty configuration) the device acknowledges the command, But when i enter the whole string and send it all on ENTER press (a different putty option) the device will not recognize the command.
I am sniffing the UART line and in both cases the same chars are detected on the line, on both configuration.
Fix?What may be causing this? Is it a known issue?
putty serial-port
asked Jan 10 at 8:03
user983288user983288
1
add a comment |
I am working on an embedded device with an UART connection. Via putty I send commands to that device using ASCII chars. When i send the chars one by one - pressing them manually- (default putty configuration) the device acknowledges the command, But when i enter the whole string and send it all on ENTER press (a different putty option) the device will not recognize the command.
I am sniffing the UART line and in both cases the same chars are detected on the line, on both configuration.
Fix?What may be causing this? Is it a known issue?
putty serial-port
asked Jan 10 at 8:03
user983288user983288
1
I am working on an embedded device with an UART connection. Via putty I send commands to that device using ASCII chars. When i send the chars one by one - pressing them manually- (default putty configuration) the device acknowledges the command, But when i enter the whole string and send it all on ENTER press (a different putty option) the device will not recognize the command.
I am sniffing the UART line and in both cases the same chars are detected on the line, on both configuration.
Fix?What may be causing this? Is it a known issue?
putty serial-port
putty serial-port
asked Jan 10 at 8:03
user983288user983288
1
asked Jan 10 at 8:03
user983288user983288
1
asked Jan 10 at 8:03
user983288user983288
1
asked Jan 10 at 8:03
user983288user983288
1
asked Jan 10 at 8:03
user983288user983288
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Embedded devices often have limited processing power and it is quite usual for some to be unable to process serial input at maximum baud rate without some artificial delay.
If your device implements some handshaking (hardware or XON/XOFF) you need to enable the corresponding options in putty, if not you are stuck with the need for some delay.
answered Jan 10 at 8:14
Eugen RieckEugen Rieck
10.2k22228
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
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%2fsuperuser.com%2fquestions%2f1392639%2fuart-sending-string-vs-charbychar%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Embedded devices often have limited processing power and it is quite usual for some to be unable to process serial input at maximum baud rate without some artificial delay.
If your device implements some handshaking (hardware or XON/XOFF) you need to enable the corresponding options in putty, if not you are stuck with the need for some delay.
answered Jan 10 at 8:14
Eugen RieckEugen Rieck
10.2k22228
add a comment |
Embedded devices often have limited processing power and it is quite usual for some to be unable to process serial input at maximum baud rate without some artificial delay.
If your device implements some handshaking (hardware or XON/XOFF) you need to enable the corresponding options in putty, if not you are stuck with the need for some delay.
answered Jan 10 at 8:14
Eugen RieckEugen Rieck
10.2k22228
add a comment |
Embedded devices often have limited processing power and it is quite usual for some to be unable to process serial input at maximum baud rate without some artificial delay.
If your device implements some handshaking (hardware or XON/XOFF) you need to enable the corresponding options in putty, if not you are stuck with the need for some delay.
answered Jan 10 at 8:14
Eugen RieckEugen Rieck
10.2k22228
Embedded devices often have limited processing power and it is quite usual for some to be unable to process serial input at maximum baud rate without some artificial delay.
If your device implements some handshaking (hardware or XON/XOFF) you need to enable the corresponding options in putty, if not you are stuck with the need for some delay.
answered Jan 10 at 8:14
Eugen RieckEugen Rieck
10.2k22228
answered Jan 10 at 8:14
Eugen RieckEugen Rieck
10.2k22228
answered Jan 10 at 8:14
Eugen RieckEugen Rieck
10.2k22228
answered Jan 10 at 8:14
Eugen RieckEugen Rieck
10.2k22228
10.2k22228
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1392639%2fuart-sending-string-vs-charbychar%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
