Results 1 to 5 of 5
Hi,
I'm running the Angstrom Distro on an overo gumstick.
I'm trying to run the obdgpslogger program.
The program only correctly connects to the serial port after I run minicom.
...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-24-2012 #1Just Joined!
- Join Date
- Jun 2012
- Posts
- 9
Serial port only works after I run minicom
Hi,
I'm running the Angstrom Distro on an overo gumstick.
I'm trying to run the obdgpslogger program.
The program only correctly connects to the serial port after I run minicom.
I run minicom at 9600 and no flow control.
When I reboot the serial port goes back to its initial configuration and I can't communicate with it.
Seems like I should use stty or setserial, but I'm confused and need some help.
How can I configure the serial port correctly without needing to run minicom.
All the best,
Anthony G.
- 10-26-2012 #2Trusted Penguin
- Join Date
- May 2011
- Posts
- 3,745
try this stty command:
check this thread for an explanation of stty options.Code:stty -F /dev/ttyS0 -ixon -ixoff
if that works, you can stick in a start-up file, to be called every time the system reboots. Look for a file like /etc/rc.local or /etc/rc.d/rc.local or similar.
- 10-26-2012 #3Just Joined!
- Join Date
- Jun 2012
- Posts
- 9
Thanks.
I tried this and it worked. I put it right before I call the obdgpslogger in the startup scripts.
and I made a udev scriptstty -F /dev/obdii -crtscts -clocal ispeed 9600 ospeed 9600
./obdgpslogger -s /dev/obdii -a 2 -d /home/root/obd.db &
# Put this in /etc/udev/rules.d/ as 99-usb-serial.rules
# for the usb gps.
SUBSYSTEM=="tty", ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", SYMLINK+="usbgps"
# the ftdi, obdii to serial to usb
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A800JRNJ", SYMLINK+="obdi"
- 10-26-2012 #4Trusted Penguin
- Join Date
- May 2011
- Posts
- 3,745
that's cool with the udev stuff. you know you can even combine them: add the stty command to the udev rule. you can try something like this:
you'd put that after one of your matching SUBSYSTEM lines.Code:RUN+="/path/to/stty-script.sh"
- 10-26-2012 #5Just Joined!
- Join Date
- Jun 2012
- Posts
- 9
I was having issues were sometimes the gps ended up /dev/ttyUSB0 and sometimes the obdii->serial->usb converter ended up being /dev/ttyUSB0, so I needed the udev script to help differentiate the two.
Thanks for the help!



