From: Marcel Holtmann <marcel@holtmann.org>
To: Robert Wlaschin <robertw@healthhero.com>
Cc: "'bluez-devel@lists.sourceforge.net'"
<bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm
Date: Tue, 04 Oct 2005 21:58:45 +0200 [thread overview]
Message-ID: <1128455925.26362.21.camel@blade> (raw)
In-Reply-To: <CBBBD909D2D6D211B4700090273F9E6E04C49A66@polaris.hhn.com>
Hi Robert,
> In regards to the type of communication, I'm trying to create a BT
> serial connection. The device I'm attempting to connect to is
> actually a weight scale (medical device). It doesn't support any
> other services. I probably need to add that I changed rfcomm.conf to
> listen, bind, and connect for rfcomm0. Note: The last time I used
> linux was in college and it was only to compile my assignments, so I'm
> not savvy.
you need to do a "rfcomm bind 0 <bdaddr> <channel>" and you will get a
new /dev/rfcomm0 TTY device. Now use a terminal program like minicom or
cu for the communication.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-10-04 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 16:32 [Bluez-devel] Cannot send through serial device rfcomm Robert Wlaschin
2005-10-04 19:58 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-05 18:38 Robert Wlaschin
2005-10-05 18:55 ` Marcel Holtmann
2005-10-05 17:32 Robert Wlaschin
2005-10-05 17:54 ` Marcel Holtmann
2005-10-04 22:46 Robert Wlaschin
2005-10-05 4:10 ` Marcel Holtmann
2005-10-03 20:42 Robert Wlaschin
2005-10-04 11:16 ` Marcel Holtmann
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=1128455925.26362.21.camel@blade \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=robertw@healthhero.com \
/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;
as well as URLs for NNTP newsgroup(s).