Linux bluetooth development
 help / color / mirror / Atom feed
From: "Albert Huang" <albert@csail.mit.edu>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Programming in C with Bluetooth Sockets
Date: Wed, 19 Apr 2006 12:56:56 -0400	[thread overview]
Message-ID: <ef9938ec0604190956r40a902b5sce596c16e40ce8e1@mail.gmail.com> (raw)
In-Reply-To: <c6a2f99a0604190804k7de31858i94b74e2d06b3ff11@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3176 bytes --]

use hcidump -X -V to examine the packets that actually get transmitted and
received.  That might give you some insight on where things are going wrong.

-albert

On 4/19/06, Eric Munson <ebmunson@gmail.com> wrote:
>
> Thanks for the link, but I have already been through that
> documentation and my initial attempt was a direct copy of of his
> RFCOMM socket code found here:
> http://people.csail.mit.edu/albert/bluez-intro/x499.html  This code
> gave the results that I am describing (only getting the first 4 bytes
> of a string).
>
> Thanks,
> Eric
>
> On 4/18/06, Sowmya Gattupalli <sowmya.gattupalli@gmail.com> wrote:
> > I think u are not doing the socket programmin properly
> > check out this link
> > http://people.csail.mit.edu/albert/bluez-intro/index.html
> > by Albert
> >
> >
> > On 4/19/06, Eric Munson <ebmunson@gmail.com> wrote:
> > >
> >  I am attempting to move data across a bluetooth connection using
> > RFCOMM sockets in C.
> >
> > I am able to establish the connection and I can successfully send and
> > receive the first four bytes of the message.  The sending program
> > reports a complete success and the receiving program only reads the
> > first four characters.
> >
> > I have tried several things to make this work, first was to send the
> > message size initially and then break the message up into pieces no
> > bigger than 4 bytes and send them individually.  The sending program
> > again reports a complete success and the receiving program gets the
> > correct message size and only the first four bytes of the message.
> >
> >  The next step I tried was to have each side close the socket after
> > each transmission and open a new socket for each data chunk.  This led
> > to the same results as before.
> >
> > I am at a loss about what I am doing wrong after searching the web for
> > information on bluetooth socket programming.  Has Anyone seen this
> > sort of problem before and if so what did you do to fix it?  Thanks
> > for your help.
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> > that extends applications into web and mobile media. Attend the live
> webcast
> > and join the prime developer group breaking into this new coding
> territory!
> > http://sel.as-us.falkag.net/sel?cmdlnk&kid\x110944&bid$1720&dat\x121642
> > _______________________________________________
> > Bluez-users mailing list
> > Bluez-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-users
> >
> >
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmdlnk&kid\x120709&bid&3057&dat\x121642
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>

[-- Attachment #2: Type: text/html, Size: 4400 bytes --]

  parent reply	other threads:[~2006-04-19 16:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19  2:25 [Bluez-users] Programming in C with Bluetooth Sockets Eric Munson
2006-04-19  4:18 ` Sowmya Gattupalli
2006-04-19 15:04   ` Eric Munson
2006-04-19 16:50     ` Sowmya Gattupalli
2006-04-19 16:56     ` Albert Huang [this message]
2006-04-19 18:26       ` Eric Munson
2006-04-19 18:32         ` Albert Huang
2006-04-19 20:41           ` Eric Munson
2006-04-20  6:46             ` Eric Munson

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=ef9938ec0604190956r40a902b5sce596c16e40ce8e1@mail.gmail.com \
    --to=albert@csail.mit.edu \
    --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