Subject:
|
Re: Can't open serial port in Linux
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Thu, 30 Dec 1999 19:46:21 GMT
|
Viewed:
|
2107 times
|
| |
|
|
Hi. I just got through fixing a similar problem with my linux box
(the fix involved a lot of tedious changing IRQ's in the BIOS, with
a lot of tedious rebooting in between). Beyond Dave's good advice,
you might want to check out the linux serial port HOWTO if you're
still stuck. It's at:
http://www.linuxhq.com/HOWTO/Serial-HOWTO.html
You might also find the TclRCX bytecode compiler helpful, which is at:
http://www.autobahn.org/~peterp/rcx/
The good thing about this is that you can write a very brief script
to see if you can contact the RCX via your serial port/tower...
#! /usr/bin/tcl
source rcx.tcl
connect /dev/ttyS1 # Or whatever your serial port is
ping # Will print "OK" if it sees the RCX
It also gives better error messages than NQC does. I'm trying to see
if I can make NQC a little better in this regard; if so I'll send a
patch to Dave. (Hi Dave).
Cheers, Tim
|
|
Message has 1 Reply:
 | | Re: Can't open serial port in Linux
|
| (...) Currently there isn't any notion of an "error code" from the serial port class - opening the serial port just returns true/fals. I'm wary of adding error codes here because they'd need to be added in a portable manner (and across the Unix, (...) (25 years ago, 30-Dec-99, to lugnet.robotics.rcx.nqc)
|
Message is in Reply To:
| | Re: Can't open serial port in Linux
|
| Check the permissions on /dev/ttyS1. I think the default is for it to be locked down to superuser only. If this is the case, then running nqc from a normal user account would cause the error you got. You'll need read/write rights to /dev/ttyS1 in (...) (25 years ago, 29-Dec-99, to lugnet.robotics.rcx.nqc)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
