Return-Path: Message-ID: <20060411223157.86042.qmail@web61222.mail.yahoo.com> From: deva seetharam To: bluez-users@lists.sf.net MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1577216774-1144794717=:85725" Subject: [Bluez-users] bluetooth remote control Sender: bluez-users-admin@lists.sourceforge.net Errors-To: bluez-users-admin@lists.sourceforge.net Reply-To: bluez-users@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ users List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 11 Apr 2006 15:31:57 -0700 (PDT) --0-1577216774-1144794717=:85725 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit hello all, i am building bluetooth based handheld remote control devices. background information =============== the remote control devices are based on LMX9820 (National Semiconductor's single-chip bluetooth modules). when buttons are pressed, these devices send messages to an application running on a debian linux box. bluetooth connectivity is added to this linux box using D-Link DBT-120 bluetooth dongle. attempted architectures ============== i tried to implement this system using the following architectures: 1. RFCOMM server the linux box runs a bluetooth socket server on a particular channel. the remote control device connects to the server over the specific channel and sends messages. problems encountered: multiple remotes can't connect to the same server. i see that the accept method (unlike tcp implementation) returns the server port upon accepting an incoming connection. for instance, if the server is listening on port 16, when any remote connects to the server, the server port 16 is used to establish end-to-end connection with the client. now, another device cannot connect to the same server until the first remote disconnects. this problem stops us from using multiple remotes with a single linux server. 2. Serial port set up one or more bluetooth serial ports and the remote control devices can send messages to anyone of them by randomly selecting one of those channels. so i setup a port as listed by rfcomm show: rfcomm0: 00:0D:88:C0:61:55 channel 16 clean > sdptool add --channel=16 sp Serial Port service registered > rfcomm listen 0 16 Waiting for connection on channel 16 i tried to connect to rfcomm0 from a *different* linux machine. problems encountered: can't connect... >rfcomm connect 00:0D:88:C0:61:55 16 Can't connect RFCOMM socket: Host is down (although, when i do a l2ping, the second machine gets replies from the first). Questions ====== 1. what would be the best architecture for implementing bluetooth remote control? 2. is it possible to configure the accept function to return connection specific ports? 3. what do i need to get the bluetooth serial port working? pls. let me know. thanks in advance, dave --------------------------------- Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2?/min with Yahoo! Messenger with Voice. --0-1577216774-1144794717=:85725 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit hello all,
i am building bluetooth based handheld remote control devices. 

background information
===============
the remote control devices are based on LMX9820 (National Semiconductor's single-chip bluetooth modules).  when buttons are pressed, these devices send messages to an application running on a debian linux box. bluetooth connectivity is added to this linux box using D-Link DBT-120 bluetooth dongle.

attempted architectures
==============
i tried to implement this system using the following architectures:

1. RFCOMM server
the linux box runs a bluetooth socket server on a particular channel. the remote control device connects to the server over the specific channel and sends messages.

problems encountered: multiple remotes can't connect to the same server.

i see that the accept method (unlike tcp implementation) returns the server port upon accepting an incoming connection. for instance, if the server is listening on port 16, when any remote connects to the server, the server port 16 is used to establish end-to-end connection with the client. now, another device cannot connect to the same server until the first remote disconnects. this problem stops us from using multiple remotes with a single linux server.


2. Serial port
set up one or more bluetooth serial ports and the remote control devices can send messages to anyone of them by randomly selecting one of those channels.

so i setup a port as listed by rfcomm show:
rfcomm0: 00:0D:88:C0:61:55 channel 16 clean

> sdptool add --channel=16 sp
   Serial Port service registered

> rfcomm listen 0 16
Waiting for connection on channel 16

i tried to connect to rfcomm0 from a *different* linux machine.

problems encountered: can't connect...

>rfcomm connect 00:0D:88:C0:61:55 16
Can't connect RFCOMM socket: Host is down

(although, when i do a l2ping, the second machine gets replies from the first).

Questions
======
1. what would be the best architecture for implementing bluetooth remote control?
2. is it possible to configure the accept function to return connection specific ports?
3. what do i need to get the bluetooth serial port working?

pls. let me know.

thanks in advance,
dave




Love cheap thrills? Enjoy PC-to-Phone calls to 30+ countries for just 2?/min with Yahoo! Messenger with Voice. --0-1577216774-1144794717=:85725-- ------------------------------------------------------- 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?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users