Serial Port used in Virtual Box “stalls”












0














i have the following setup:
Windows Host has a Com Port "COM3". (The port is a high quality USB to Serial Converter Cable)



This port is made available to a virtual Box VM running Ubunutu 16.04.



The port is used to connect to a weighing appliance,
the connection basically works like this:
You connect to the serial port (e.g. using PicoCom under Linux or Putty under Windows)
You type a command (e.g. "<RN>") into the console and the appliance echos the weight into the console.



Now here is the problem:
The connection works fine for a certain time and then the system stops responding.




  1. You get a connect when opening the device

  2. You can still type your command

  3. But you dont get any response


When this problem first occurrs it does so until the VM is shut down and booted again.
Rebooting from the command line does not fix it.



I cannot see any suspicious messages in the unbuntu syslog and i cant see any other logfiles that have changed that look relevant to me.



I dont think the converter cable is the source of the problem because when i shut down the VM and open the serial port with putty it works fine.



I am looking for a way to get rid of the problem or for a way to fix it without shutting down the whole VM



Thanks in advance, folks!










share|improve this question
























  • I suspect the problem is somehow related to the power saving features of the Host Win10 system. I have deactivated stand-by and the response is stable so far.
    – Jens Kisters
    Nov 23 '18 at 12:26


















0














i have the following setup:
Windows Host has a Com Port "COM3". (The port is a high quality USB to Serial Converter Cable)



This port is made available to a virtual Box VM running Ubunutu 16.04.



The port is used to connect to a weighing appliance,
the connection basically works like this:
You connect to the serial port (e.g. using PicoCom under Linux or Putty under Windows)
You type a command (e.g. "<RN>") into the console and the appliance echos the weight into the console.



Now here is the problem:
The connection works fine for a certain time and then the system stops responding.




  1. You get a connect when opening the device

  2. You can still type your command

  3. But you dont get any response


When this problem first occurrs it does so until the VM is shut down and booted again.
Rebooting from the command line does not fix it.



I cannot see any suspicious messages in the unbuntu syslog and i cant see any other logfiles that have changed that look relevant to me.



I dont think the converter cable is the source of the problem because when i shut down the VM and open the serial port with putty it works fine.



I am looking for a way to get rid of the problem or for a way to fix it without shutting down the whole VM



Thanks in advance, folks!










share|improve this question
























  • I suspect the problem is somehow related to the power saving features of the Host Win10 system. I have deactivated stand-by and the response is stable so far.
    – Jens Kisters
    Nov 23 '18 at 12:26
















0












0








0







i have the following setup:
Windows Host has a Com Port "COM3". (The port is a high quality USB to Serial Converter Cable)



This port is made available to a virtual Box VM running Ubunutu 16.04.



The port is used to connect to a weighing appliance,
the connection basically works like this:
You connect to the serial port (e.g. using PicoCom under Linux or Putty under Windows)
You type a command (e.g. "<RN>") into the console and the appliance echos the weight into the console.



Now here is the problem:
The connection works fine for a certain time and then the system stops responding.




  1. You get a connect when opening the device

  2. You can still type your command

  3. But you dont get any response


When this problem first occurrs it does so until the VM is shut down and booted again.
Rebooting from the command line does not fix it.



I cannot see any suspicious messages in the unbuntu syslog and i cant see any other logfiles that have changed that look relevant to me.



I dont think the converter cable is the source of the problem because when i shut down the VM and open the serial port with putty it works fine.



I am looking for a way to get rid of the problem or for a way to fix it without shutting down the whole VM



Thanks in advance, folks!










share|improve this question















i have the following setup:
Windows Host has a Com Port "COM3". (The port is a high quality USB to Serial Converter Cable)



This port is made available to a virtual Box VM running Ubunutu 16.04.



The port is used to connect to a weighing appliance,
the connection basically works like this:
You connect to the serial port (e.g. using PicoCom under Linux or Putty under Windows)
You type a command (e.g. "<RN>") into the console and the appliance echos the weight into the console.



Now here is the problem:
The connection works fine for a certain time and then the system stops responding.




  1. You get a connect when opening the device

  2. You can still type your command

  3. But you dont get any response


When this problem first occurrs it does so until the VM is shut down and booted again.
Rebooting from the command line does not fix it.



I cannot see any suspicious messages in the unbuntu syslog and i cant see any other logfiles that have changed that look relevant to me.



I dont think the converter cable is the source of the problem because when i shut down the VM and open the serial port with putty it works fine.



I am looking for a way to get rid of the problem or for a way to fix it without shutting down the whole VM



Thanks in advance, folks!







ubuntu virtualbox serial-port






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 23 '18 at 12:28

























asked Nov 23 '18 at 9:54









Jens Kisters

13




13












  • I suspect the problem is somehow related to the power saving features of the Host Win10 system. I have deactivated stand-by and the response is stable so far.
    – Jens Kisters
    Nov 23 '18 at 12:26




















  • I suspect the problem is somehow related to the power saving features of the Host Win10 system. I have deactivated stand-by and the response is stable so far.
    – Jens Kisters
    Nov 23 '18 at 12:26


















I suspect the problem is somehow related to the power saving features of the Host Win10 system. I have deactivated stand-by and the response is stable so far.
– Jens Kisters
Nov 23 '18 at 12:26






I suspect the problem is somehow related to the power saving features of the Host Win10 system. I have deactivated stand-by and the response is stable so far.
– Jens Kisters
Nov 23 '18 at 12:26

















active

oldest

votes











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


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377773%2fserial-port-used-in-virtual-box-stalls%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.





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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377773%2fserial-port-used-in-virtual-box-stalls%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

AnyDesk - Fatal Program Failure

How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

QoS: MAC-Priority for clients behind a repeater