Hal Vaughan wrote:
....
> On the other end, in what will be another thread once I get it all
> working, I'm writing to the serial ****t as a binary file and I open it
> like this:
>
> int serfd;
> string serdev = "/dev/ttyS0";
> serfd = open(serdev, O_RDWR | O_NOCTTY | O_NDELAY);
Just as an update:
This method works and the device connected to the serial ****t responds to
it. The other method I tried (using fopen, putc), didn't work. I don't
know if there's an issue with the serial ****t or not, but I can write a
character at a time to the serial ****t either way, so I'm not changing
what
works.
I also realize it's possible this changes settings that I'll be setting
once
I add all the initialization code to make sure the ****t is behaving on all
computers no matter what was using it last, but if it works, I'm not going
to fix it.
Just for general info, in case anyone is curious, I'm controlling an HD
Radio from the computer. The idea is to make this part of a carputer.
Unless you go with a pre-made system, you can't control your car radio
from
a carputer, so you can pick your tunes or switch over to the car radio,
but
you can't do both from one control point. When this is done, and after we
send the code to nGhost to use, it'll be part of that system for Linux
carputers and on the LinuxICE distro.
Now that I've got the programs actually listening and writing to the
serial
****t and we have tables of the command codes, the rest is basically
tedious
bookkeeping to decode and encode commands and data.
Thanks for the help! (I'm sure I'll be back to read more and ask more if
I
get stuck again!)
Hal
|
