public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Zygo Blaxell <zblaxell@feedme.hungrycats.org>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: Zygo Blaxell <zblaxell@dactyl.hungrycats.org>,
	linux-bluetooth@vger.kernel.org
Subject: Re: The link I had working quit.  Help
Date: Tue, 7 Apr 2009 16:40:55 -0400	[thread overview]
Message-ID: <20090407204055.GB18671@hungrycats.org> (raw)
In-Reply-To: <200904070008.48621.gene.heskett@verizon.net>

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

On Tue, Apr 07, 2009 at 12:08:48AM -0400, Gene Heskett wrote:
> On Monday 06 April 2009, Zygo Blaxell wrote:
> >Do you seriously have a Coco3 wired up to Bluetooth?  How?  Presumably not
> >with a native stack...some kind of dongle?
> >
> Roger Taylor is selling a remake of the old Deluxe RS-232 pack, with an a7 
> eb101 module taking the place of the db25 connector.  $65.  Uses the same old 
> rs-232 drivers.  He is one of the movers & shakers of the coco list on 
> maltedmedia.com.

After reading http://www.a7eng.com/downloads/a7-ds-eb101.pdf it looks
like the device has an automatic discovery mode which is activated by
pressing a switch for more than 5 but less than 10 seconds.  It seems
to assume it's talking to another device which has a serial port profile
service enabled...maybe it only works with other eb101's.

It also has a command mode (http://www.a7eng.com/downloads/a7-qs-serial.pdf)
which lets you read things like the device settings and information about
remote devices from the module's point of view.  Especially interesting
ones (page 9) are:

	get connectable  (should be on)
	get trustedlist  (should include your paired bluez device)


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

  reply	other threads:[~2009-04-07 20:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04 20:36 The link I had working quit. Help Gene Heskett
2009-04-05 20:59 ` Gene Heskett
2009-04-05 21:59   ` Gene Heskett
     [not found]     ` <alpine.LNX.2.00.0904060246560.29837@nge2.ngu.pk>
2009-04-06 18:57       ` Gene Heskett
2009-04-06 22:14         ` Zygo Blaxell
2009-04-07  4:08           ` Gene Heskett
2009-04-07 20:40             ` Zygo Blaxell [this message]
2009-04-08  4:11               ` Gene Heskett
2009-04-07 18:54           ` Gene Heskett
2009-04-07 20:02             ` Zygo Blaxell
2009-04-07 21:35               ` Gene Heskett
2009-04-07 21:56                 ` Zygo Blaxell
2009-04-07 23:05               ` Bastien Nocera
2009-04-08  4:26                 ` Gene Heskett
2009-04-08 15:06                 ` Gene Heskett
2009-04-08 16:17                   ` Zygo Blaxell
2009-04-08 18:50                     ` Gene Heskett
2009-04-08 19:30                       ` Zygo Blaxell
2009-04-08 19:35                         ` Gene Heskett
2009-04-08 19:36                           ` Zygo Blaxell
2009-04-09  2:40                             ` Gene Heskett
2009-04-09 14:55                               ` Zygo Blaxell
2009-04-09 18:28                                 ` Gene Heskett
2009-04-08 19:03                     ` Gene Heskett
     [not found]         ` <alpine.LNX.2.00.0904062153190.3436@nge2.ngu.pk>
2009-04-07  4:47           ` Gene Heskett

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=20090407204055.GB18671@hungrycats.org \
    --to=zblaxell@feedme.hungrycats.org \
    --cc=gene.heskett@verizon.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=zblaxell@dactyl.hungrycats.org \
    /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