You don't mention how much data you're expecting. I have a voltmeter
set up to broadcast values once per second so it seems somewhat similar,
though my data rate is quite low. In playing around with using the
built in serial buffer I found it fills up and I start losing data if I
wait until several thousand values (6 bytes each, I don't remember
exactly how many thousand) have been sent. This is no problem for me, I
have set up a child process that gets around to reading the port every
few minutes at most.
My point; if you rely on the buffer, make sure you read it often enough
to avoid data loss. Probably there is some way to change the size of
the buffer, but it will still be finite.
Tom
Larry Griffin wrote:
>
> Hi
>
> I'm having a data gathering device built to front end a validation
> server I have. This has nothing to do with the internet. The new
> hardware will interface with multiple devices and make the data
> available on a single serial port.
>
> I'm trying to decide whether to rely on the serial buffer or employ some
> sort of interrupt technique. On one side I'd like to get the data as
> soon as it's available. On the other I don't want to leave my server w/o
> any CPU.
>
> I could end up with a half dozen of these interfaces, each on it's own
> serial port, and each interface talking to 48 devices. Any suggestions.
>
> Larry Griffin
>
> ------------------------------------------------------------------------
>
> Lawrence Griffin <[EMAIL PROTECTED]>
> President
> Southwest DataCom Corp.
>
> Lawrence Griffin
> President <[EMAIL PROTECTED]>
> Southwest DataCom Corp.
> P.O. Box 460485 Cellular: (210) 269-7708
> San Antonio Fax: (210) 829-4220
> Texas Work: (210) 576-1174
> 78246 Netscape Conference Address
> USA
> Additional Information:
> Last Name Griffin
> First Name Lawrence
> Version 2.1
-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to [EMAIL PROTECTED]
