Active Topics

 


Reply
Thread Tools
Posts: 12 | Thanked: 1 time | Joined on Jul 2008
#1
Hi, Can anyone point me to a place where I can get rfcomm for diablo?
 
Posts: 45 | Thanked: 5 times | Joined on Oct 2007 @ Austria
#2
I think it's rtcomm you are looking for

http://rtcomm.garage.maemo.org/
 
Posts: 12 | Thanked: 1 time | Joined on Jul 2008
#3
Not really. I am looking for rfcomm which is a program that can map a bluetooth connection onto a serial device. It should be in some bluetooth package but I can't find it. I read reports that is used to be in bluez-untils-test but I can't find this package (perhaps pre Diablo?)
 
Posts: 45 | Thanked: 5 times | Joined on Oct 2007 @ Austria
#4
okay...my fault
 
Posts: 12 | Thanked: 1 time | Joined on Jul 2008
#5
I might have found it. It could be here. I will try to install this this evening.
 
Posts: 2,152 | Thanked: 1,490 times | Joined on Jan 2006 @ Czech Republic
#6
Bluez stack moved to using D-Bus almost exclusively. Check kbdd for some D-Bus shell scripting hackery for allocating rfcomm ports. See dbus-bluez-rfcomm inside kbdd.tar.gz or see wiki.bluez.org for other examples.

Advantage of using d-bus for allocating rfcomm port is that is plays nice with rest of the system, you don't need to hardcode specific rfcomm port number and hope system will not use it.
__________________
Newbies click here before posting. Thanks.

If you really need to PM me with troubleshooting question please consider posting it to the forum instead. It is OK to PM me a link to such post then. Thank you.

Last edited by fanoush; 2008-07-11 at 12:20.
 

The Following User Says Thank You to fanoush For This Useful Post:
tz1's Avatar
Posts: 716 | Thanked: 236 times | Joined on Dec 2007
#7
You need the bluez-utils-test deb, which is only visible by adding the diablo SDK and diablo tools archive.

https://bugs.maemo.org/show_bug.cgi?id=3405

This one can be found in the Diablo SDK repo. The structure of dists is
different though. I can see it in my Diablo with N800 in redpill.

Details:
Catalogue Name: Maemo Diablo
Web address: http://repository.maemo.org/
Distribution: diablo
Components: sdk/free tools/free sdk/non-free tools/non-free

Or (not tested), these lines in your sources.list[.d]:
deb http://repository.maemo.org/ diablo/sdk free non-free
deb-src http://repository.maemo.org/ diablo/sdk free
deb http://repository.maemo.org/ diablo/tools free non-free
deb-src http://repository.maemo.org/ diablo/tools free
 
tz1's Avatar
Posts: 716 | Thanked: 236 times | Joined on Dec 2007
#8
Also, kbdd has some shell scripts and python that does the same things as rfcomm (and a few others do) via dbus.
 
Posts: 12 | Thanked: 1 time | Joined on Jul 2008
#9
Thanks, I have installed the bluez-utils-test package and it works great.
 
cmdowns's Avatar
Posts: 100 | Thanked: 13 times | Joined on Mar 2008
#10
Hello, I'm also trying to set up a serial port for bluetooth communication. I'm working with an n800 running Diablo.

I've purchased a BlueSMirf modem and I'm attempting to setup a serial connection on a project I've been working on that is described in this post.

In this post in the same thread jethro.itt recommended I use rfcomm in order to replace my hardwired serial connection with a bt connection.

So I installed bluez-utils, bluez-utils-dist, and bluez-utils-test. Not sure if I really needed all of them, but I assume it won't hurt (it won't, right?).

I can bring up rfcomm in xterm, and using hcitool scan gives me the bt address of the modem (which is successfully paired with my n800).

If I try
Code:
 rfcomm connect [bt address]
Xterm tells me
Code:
 Can't open RFCOMM config file: No such file or directory
So my questions are: 1) Is rfcomm the best tool to do what I'm trying to do. Some of the discussion in this thread lead me to believe that there might be other, better programs 2) Am I using the rfcomm connect command correctly 3) What's the deal with the missing config file?

Any help you NIT gurus could provide would be much appreciated!
 
Reply


 
Forum Jump


All times are GMT. The time now is 13:01.