![]() It makes the impression that - About to connect, it's just few second left and then should be all good, really promising -> and then, just seconds before (now if I used host OS it would soon commit to log in to the device and show all settings in front of me) it goes out with a "could not connect" or similar message.Īnd all steps and habits described above takes a lot of time, so if I want to do a change in the settings I should make only settings that I believe can make any difference, such as adjusting the fifo buffers in com port Alabalcho - I'd be very glad if you're able to provide that utility name - because I'd giving up using only Virtualbox.I have problems to map a host serial port (Windows) into the guest serial port (Linux). The software is (very offensive words should go in here) because each time I test with new settings, the dialog box and graphics are incredible deceptive. But If I where to try out many different configurations, I think that would take a couple of weeks. I haven't made a table or list of every possible configurations I've tried, so I cannot rule out the possibility that there exist the one magical configuration that actually works. I know that the baud rate of 19200 are accepted by the device and always work, so I don't test with other baud rates. I tried a lot of settings regarding the com port. Starting the software and run another test (all of them failed).Adjusting com port settings from within guest OS.Since that is unclear, I spend a lot more time because for each time I was going to adjust some parameters to the COM-port, I did in following steps: In both host OS and guest OS, I can navigate through device manager and adjust properties to the COM port - however I cannot find any sources saying wich one (host or guest OS) that overrides the other, or if it doesn't matter at all. I have to give up trying to connect the guest OS because of: So the situation is still : The communication always work when the software runs on the host machine, it never (rare fluke not counting) works when using the Virtualbox. One time, where the baud rate was set to 19200 the software was seemingly had a successfully connection to the device, but that turned out being a rare fluke - I never got the software to repeat that again. However, the bugfix mentioned did not solve the issue. Today I had a test where I upgraded Virtualbox to most recent version as of today. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |