Sat 14 Mar 2015 02:02:27 AM UTC, comment #13:
Marking as closed
|
Tue 10 Mar 2015 10:47:47 PM UTC, comment #12:
s1 = serial("\\\\.\\COM15") does work. Thanks
|
Wed 04 Mar 2015 04:26:27 PM UTC, comment #11:
So for COM15,
s1 = serial("\\\\.\\COM15")
Can you verify that it works for you?
|
Mon 02 Mar 2015 09:52:18 PM UTC, comment #10:
Windows requires special naming for ports > COM9.
http://support.microsoft.com/kb/115831
|
Mon 02 Mar 2015 09:49:33 PM UTC, comment #9:
I think I was able to get it working. It appears that it doesn't like high COM port numbers eg. COM1 works but COM18 does not. I will have to play with it a bit more to see if that was indeed the problem.
|
Mon 02 Mar 2015 12:53:27 AM UTC, comment #8:
Can you verify in some other software that you can open/commuicate on them?
|
Sun 01 Mar 2015 10:58:53 PM UTC, comment #7:
There are a couple bluetooth serial ports that are always open and then whatever is plugged in. One that I was testing with is labeled "Arduino Mega 2560 (COM1)".
I tried entering it as COM1, COM001, com1, and several other things. Always the same error.
|
Sun 01 Mar 2015 10:04:04 PM UTC, comment #6:
What com ports does it report in control panel?
|
Sun 01 Mar 2015 09:25:52 PM UTC, comment #5:
I have tried multiple COM ports and devices. I just did a fresh install and no change. It doesn't recognize the COM ports, but it still says "Serial: Supported"
|
Sun 01 Mar 2015 01:39:07 PM UTC, comment #4:
ok after some more testing I saw in Windows as well - reported on https://savannah.gnu.org/bugs/?44397
|
Sun 01 Mar 2015 01:27:57 PM UTC, comment #3:
The Ctrl-C issue seems to be a problem in GUI mode. octave --no-gui and octave-cli works. (Tested with linux)
|
Sun 01 Mar 2015 01:08:06 PM UTC, comment #2:
Ctrl-C works in octave-3.8.2 (windows), but not the devel octave.
|
Sun 01 Mar 2015 12:30:10 PM UTC, comment #1:
Works for me - make sure that you opening the correct COMXXX port.
I do notice (at least on devel version of octave) that I can no longer Ctrl-C the read, but not sure yet whether that is a octave or instrument-control issue.
|
Sun 01 Mar 2015 05:15:30 AM UTC, original submission:
I am running MXE Octave build 3.8.2-5 installed from http://mxeoctave.osuv.de/ on an Windows 7 64 bit machine. Specifically I am using the portable version. I have installed the instrument control package 0.2.1
When running sample code for instrument control toolbox I get the following error, "error: serial: Error opening the interface: Bad file descriptor"
I can see the serial ports in the device manager, but it doesn't seem to recognize them.
|