From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 11 17:08:21 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3297F16A403 for ; Wed, 11 Apr 2007 17:08:21 +0000 (UTC) (envelope-from vittorio@de-martino.it) Received: from vsmtp14.tin.it (vsmtp14.tin.it [212.216.176.118]) by mx1.freebsd.org (Postfix) with ESMTP id F02B613C4C7 for ; Wed, 11 Apr 2007 17:08:20 +0000 (UTC) (envelope-from vittorio@de-martino.it) Received: from [10.155.100.8] (82.55.226.152) by vsmtp14.tin.it (7.2.072.1) (authenticated as vdemart1@tin.it) id 460BD6E500FC8C2E for freebsd-bluetooth@freebsd.org; Wed, 11 Apr 2007 19:08:19 +0200 From: Vittorio De Martino To: freebsd-bluetooth@freebsd.org Date: Wed, 11 Apr 2007 19:07:51 +0000 User-Agent: KMail/1.9.5 References: <200704102004.34814.vittorio@de-martino.it> <1176235090.016851.473.nullmailer@galant.ukfsn.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200704111907.52164.vittorio@de-martino.it> Subject: Re: tomtom serial connection X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2007 17:08:21 -0000 :=20 Yes, I can smoothly pair the tomtom gps to my nokia cellular phone e61. No = pin=20 is required. The connection via umts is required from time to time by the=20 tomtom site to pdate traffic news . I tried the following but SP doesn't seem to exist victor$ sudo l2ping -a tomtom 44 bytes from tomtom seq_no=3D0 time=3D246.214 ms result=3D0 44 bytes from tomtom seq_no=3D1 time=3D28.889 ms result=3D0 44 bytes from tomtom seq_no=3D2 time=3D31.084 ms result=3D0 ^C victor$ sudo sdpcontrol -a tomtom search sp victor$ victor$ sudo rfcomm_sppd -a tomtom -t /dev/ttyp6 -c 1 rfcomm_sppd: Could not connect socket: Connection refused victor$ sudo rfcomm_sppd -a tomtom -t /dev/ttyp6 -c 2 rfcomm_sppd: Could not connect socket: Connection refused victor$ sudo rfcomm_sppd -a tomtom -t /dev/ttyp6 -c 3 rfcomm_sppd: Could not connect socket: Connection refused Ciao Vittorio Alle 20:31, marted=EC 10 aprile 2007, Maksim Yevmenkin ha scritto: > On 4/10/07, Iain Hibbert wrote: > > On Tue, 10 Apr 2007, Eric Anderson wrote: > > > On 04/10/07 15:04, Vittorio De Martino wrote: > > > > How can I make it? > > > > > > I don't see RFCOMM in the list above. > > > > yeah, Vittorio should try > > sdpcontrol -a tomtom search sp > > > > to see if the 'Serial Port' service is available.. > > > > > Record Handle: 0x00090001 > > > Service Class ID List: > > > Serial Port (0x1101) > > > Protocol Descriptor List: > > > L2CAP (0x0100) > > > RFCOMM (0x0003) > > > Protocol specific parameter #1: u/int8/bool 1 > > > > in the above example, you can connect to channel 1 directly since you > > know that the Serial Port service is there.. > > > > rfcomm_sppd -a xxx -t /dev/ttyp6 -c 1 > > > > perhaps if Vittorio can't find any serial port, try connecting to all t= he > > channels between 1 and 30 to see if he can find the one that the tomtom > > is listening on. > > well, it might or might not work. was tomtom gps previously paired > with another bluetooth device? > > some devices are quite paranoid and will not accept any incoming > connection unless it comes from "known/trusted" device. if fact, some > devices wont even advertise service once they were paired. the > assumption here is that "known/trusted" device saved all required > information (such as rfcomm channel number, link key or pin code) > locally and will use it next time to connect. > > so, if your tomtom gps supports "pairing" mode you need to put it into > this mode first time you try to connect "new" device to tomtom gps. > > also, as others already pointed out, it is better to use > > % sdpcontrol -a xxxx search sp > > instead of 'browse'. many devices do not bother to put advertised > services into public browse group, so 'browse' will not find them. > > thanks, > max