From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] rfcomm device blocking/data available behaviour
Date: Sat, 17 Jun 2006 12:19:11 +0200 [thread overview]
Message-ID: <1150539551.17539.11.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <4492D0E1.5090806@marples.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
prev parent reply other threads:[~2006-06-17 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 13:23 [Bluez-users] rfcomm device blocking/data available behaviour Dave Marples
2006-06-16 15:40 ` Dave Marples
2006-06-17 10:19 ` Marcel Holtmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1150539551.17539.11.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox