![]() ![]() With this socat solution this has worked 100% even after repeated attempts, plugins etc etc. I took home an omron NT20s HMI panel this week that has been a pain to upload code to through direct usb vbox connection (perhaps 1 in 20 attempts worked). Subprocess.call( (s,"-x","-d","-d","-d", s1, s2) )ġ) copy code to a file in your fs Ģ) ensure first line points to your python execĤ) set up vbox with com port with named pipe eg /tmp/vbox-com1 (2 out of 3 work and only on some hardware and then mean uptime %s" %(tty, pty)) Issue #2: Using Vbox usb support ,usb-serial adaptors work (just) but are unreliable to downright flaky. Seems to me changing default behavior to non-enforced pipe at startup, and reattempting connection on loss of pipe would help immensely. Most annoying, especially as usb-serial adaptors are always slightly unreliable. Issue #1: Vbox enforces named pipe presence at startup, and then if port drops during session it fails to reattempt a connection. ![]() With the use of pluggable serial ports under vbox there are a number of problematic issues! (linux host, now vbox 2.02, no serial port laptop, XP guest)Ĭannot get direct port to work reliable.named pipes appear to work as advertised. Have had lots of fun getting reliable serial port under vbox on my laptop using usb serial devices.
0 Comments
Leave a Reply. |