From owner-freebsd-questions@FreeBSD.ORG Sat Apr 10 14:13:48 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA6A7106566C for ; Sat, 10 Apr 2010 14:13:48 +0000 (UTC) (envelope-from lin_g@o2.pl) Received: from tur.go2.pl (tur.go2.pl [193.17.41.50]) by mx1.freebsd.org (Postfix) with ESMTP id 717908FC19 for ; Sat, 10 Apr 2010 14:13:47 +0000 (UTC) Received: from rekin23.go2.pl (rekin23.go2.pl [193.17.41.16]) by tur.go2.pl (o2.pl Mailer 2.0.1) with ESMTP id A103523048A for ; Sat, 10 Apr 2010 15:41:57 +0200 (CEST) Received: from rekin23.go2.pl (rekin23 [127.0.0.1]) by rekin23.go2.pl (Postfix) with ESMTP id 0B9EE128BCF for ; Sat, 10 Apr 2010 15:41:55 +0200 (CEST) Received: from unknown (unknown [10.0.0.42]) by rekin23.go2.pl (Postfix) with SMTP for ; Sat, 10 Apr 2010 15:41:54 +0200 (CEST) Received: from riviera.nat.student.pw.edu.pl [194.29.137.1] by poczta.o2.pl with ESMTP id ArKKKf; Sat, 10 Apr 2010 15:41:54 +0200 Message-ID: <4BC0800D.9030407@o2.pl> Date: Sat, 10 Apr 2010 15:41:33 +0200 From: Grzegorz Daniluk User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-O2-Trust: 2, 61 X-O2-SPF: neutral Subject: reliable rs-232 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Apr 2010 14:13:48 -0000 Hi everybody, I have a question regarding rs-232 under FreeBSD. I need to write an application for FreeBSD to operate an industrial controller via rs-232. The trick is that it should have very good long term stability (reliably operation over years). It should be able to detect and correct (e.g by reconfiguration of rs-232 port parameters) when rs-232 hangs or changes its transmission parameters as a result of electrical interference/disturbances etc. First thought is to simply close and reopen rs-232 port every given time interval, so even if something 'strange' happens the failure would be fixed after finite time period. But maybe there is smarter way of doing that. Maybe some special fault-tolerant rs-232 kernel drivers ? Any help appreciated, maybe someone has other helpful advieces regarding reliable rs-232 programming ini general ? Thanks for all help and advices. Best regards, Greg