Re: The link I had working quit. Help

[Zygo Blaxell <zblaxell@faye.furryterror.org>]

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

On Wed, Apr 08, 2009 at 10:40:11PM -0400, Gene Heskett wrote:
> Anyway the a7 eb101 responses are as follows:
> 
> get address local returns the correct bdaddr of that device.
> get address remote	err 4
> get connectable		on

connectable is good...

> get ecbonding		responder
> get ecconnection	auto
> get encryption		on
> get esschar		+
> get flow		hardware  (this changed to none after I did an 'rst factory'
> get linktimeout		0
> get name local		eb101
> get name remote		err 4
> get parity		none
> get security		off

security off is interesting, given encryption is on...you might want
to try the other three combinations of those flags.

> get sleep		off
> get sniff		on
> get status		false
> get trustedlist		empty return

Now that's a problem.  You should have the address of the USB dongle here
if you've paired with it.  That suggests that pairing maybe isn't working
on the eb101?  Or maybe you have to use 'set trustedlist'?

> get txpower		10
> get visible		11:11:11:11:11:11
> 
> And finally, a 'con 11:11:11:11:11:11' munches along for several seconds 
> before returning an 'err 14'

That makes sense...you haven't set up a serial port service on the Linux
machine for the eb101 to connect to.

> Did anyone take a look at that tarball I sent yet?

Not yet, although from eyeballing quickly it looks like bluetoothd has
done service discovery and picked up service records.  I'll decode it
the next time I have the tarball, the Bluetooth spec, and some time all
together in one place.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]