SetTimeout and serialport events - order of code execution
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have a code which is consequently performed in the following order.
result:
START APP,
After 5000 [ms],
Port is open
Why, I have to wait for the port to be opened until settimeout function is called?
const serial = require('serialport');
var mySerialPort = new serial("COM5", {
baudRate: 9600,
dataBits: 8,
parity: 'none',
stopBits: 1,
flowControl: false,
//autoOpen: false,
});
console.log("START APP");
//Events
mySerialPort.on('open', function() {
console.log("Port is open");
});
setTimeout(() => console.log("After 5000 [ms]"), 5000);
node.js settimeout node-serialport
asked Jan 3 at 20:20
Krzychu KieronskiKrzychu Kieronski
1
add a comment |
I have a code which is consequently performed in the following order.
result:
START APP,
After 5000 [ms],
Port is open
Why, I have to wait for the port to be opened until settimeout function is called?
const serial = require('serialport');
var mySerialPort = new serial("COM5", {
baudRate: 9600,
dataBits: 8,
parity: 'none',
stopBits: 1,
flowControl: false,
//autoOpen: false,
});
console.log("START APP");
//Events
mySerialPort.on('open', function() {
console.log("Port is open");
});
setTimeout(() => console.log("After 5000 [ms]"), 5000);
node.js settimeout node-serialport
asked Jan 3 at 20:20
Krzychu KieronskiKrzychu Kieronski
1
add a comment |
I have a code which is consequently performed in the following order.
result:
START APP,
After 5000 [ms],
Port is open
Why, I have to wait for the port to be opened until settimeout function is called?
const serial = require('serialport');
var mySerialPort = new serial("COM5", {
baudRate: 9600,
dataBits: 8,
parity: 'none',
stopBits: 1,
flowControl: false,
//autoOpen: false,
});
console.log("START APP");
//Events
mySerialPort.on('open', function() {
console.log("Port is open");
});
setTimeout(() => console.log("After 5000 [ms]"), 5000);
node.js settimeout node-serialport
asked Jan 3 at 20:20
Krzychu KieronskiKrzychu Kieronski
1
I have a code which is consequently performed in the following order.
result:
START APP,
After 5000 [ms],
Port is open
Why, I have to wait for the port to be opened until settimeout function is called?
const serial = require('serialport');
var mySerialPort = new serial("COM5", {
baudRate: 9600,
dataBits: 8,
parity: 'none',
stopBits: 1,
flowControl: false,
//autoOpen: false,
});
console.log("START APP");
//Events
mySerialPort.on('open', function() {
console.log("Port is open");
});
setTimeout(() => console.log("After 5000 [ms]"), 5000);
node.js settimeout node-serialport
node.js settimeout node-serialport
asked Jan 3 at 20:20
Krzychu KieronskiKrzychu Kieronski
1
asked Jan 3 at 20:20
Krzychu KieronskiKrzychu Kieronski
1
asked Jan 3 at 20:20
Krzychu KieronskiKrzychu Kieronski
1
asked Jan 3 at 20:20
Krzychu KieronskiKrzychu Kieronski
1
asked Jan 3 at 20:20
Krzychu KieronskiKrzychu Kieronski
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Thread with this error: https://github.com/node-serialport/node-serialport/issues/1751. Topic can close.
answered Jan 6 at 12:46
Krzychu KieronskiKrzychu Kieronski
1
add a comment |
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
});
}
});
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%2f54029241%2fsettimeout-and-serialport-events-order-of-code-execution%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
Thread with this error: https://github.com/node-serialport/node-serialport/issues/1751. Topic can close.
answered Jan 6 at 12:46
Krzychu KieronskiKrzychu Kieronski
1
add a comment |
Thread with this error: https://github.com/node-serialport/node-serialport/issues/1751. Topic can close.
answered Jan 6 at 12:46
Krzychu KieronskiKrzychu Kieronski
1
add a comment |
Thread with this error: https://github.com/node-serialport/node-serialport/issues/1751. Topic can close.
answered Jan 6 at 12:46
Krzychu KieronskiKrzychu Kieronski
1
Thread with this error: https://github.com/node-serialport/node-serialport/issues/1751. Topic can close.
answered Jan 6 at 12:46
Krzychu KieronskiKrzychu Kieronski
1
answered Jan 6 at 12:46
Krzychu KieronskiKrzychu Kieronski
1
answered Jan 6 at 12:46
Krzychu KieronskiKrzychu Kieronski
1
answered Jan 6 at 12:46
Krzychu KieronskiKrzychu Kieronski
1
1
add a comment |
add a comment |
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.
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%2f54029241%2fsettimeout-and-serialport-events-order-of-code-execution%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
