Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <428EE246.1080507@ieee.org>
Date: Sat, 21 May 2005 08:24:54 +0100
From: Jason Pearce <jason DOT pearce AT ieee DOT org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Cygwin List <cygwin AT cygwin DOT com>
Subject: Re: Using Perl to access serial ports
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

>
>
>On May 20 19:25, Jason Pearce wrote:
>  
>
>>> There was some recent discussion about serial ports and Perl.
>>>    http://sourceware.org/ml/cygwin/2005-05/msg00013.html
>>> 
>>> But I did not see any resolution.
>>> Did anyone end up porting either Win32::SerialPort or Win32API::CommPort 
>>> as Reini suggested?
>>> 
>>> I need to talk to a thermometer via a serial link. The protocol is not 
>>> very complex.
>>> Could I just use a system call to stty to set the baudrate and then pipe 
>>> the thermometer comand to /dev/ttyS0 and read the response from 
>>> /dev/ttyS0 using file handles?
>>    
>>
>
>Why don't you try it?
>
>
>Corinna
>
I will!
But there are that many variables when trying to get a serial link up 
(baud rates, parity, the type of flow control, the cable type), that I 
was hoping to get an idea if my expectations were at least plausible. If 
I know it should work I know to persist - but if you say "no thats not 
implemented" I know to try another method.

Regards,
Jason

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/