From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marcel Holtmann To: BlueZ users In-Reply-To: <4492D0E1.5090806@marples.net> References: <4492B0C9.6010305@marples.net> <4492D0E1.5090806@marples.net> Date: Sat, 17 Jun 2006 12:19:11 +0200 Message-Id: <1150539551.17539.11.camel@aeonflux.holtmann.net> Mime-Version: 1.0 Subject: Re: [Bluez-users] rfcomm device blocking/data available behaviour Reply-To: BlueZ users List-Id: BlueZ users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-users-bounces@lists.sourceforge.net Errors-To: bluez-users-bounces@lists.sourceforge.net Hi Dave, > Replying to myself here, but moving over to the python library, the > following code _works_; > > import bluetooth > > s=bluetooth.BluetoothSocket( bluetooth.RFCOMM ) > s.connect(("xx:xx:xx:xx:xx:xx",1)) > s.send('ATZ\r') > while 1: > c=s.recv(1) > print "Got",len(c),"Detail:",ord(c),c > > ...so, I can only conclude that it's something to do with the device > emulation side of things. Hope this is helpful to someone. the RFCOMM TTY devices are not in raw mode by default. You need to do that by yourself. However every application should now what's the best mode to use the device and cat is simply too dumb. Regards Marcel _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users