2005-10-04 22:46:14

by Robert Wlaschin

[permalink] [raw]
Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm

Marcel,

That was a good suggestion. I've seen usage of those programs on various
help/websites.

Due to a hardware limitations, I only have microcom available which seems
flaky at best. I seem to be getting the 'Exitcode 2 - cannot open device
/dev/rfcomm0' error message. But I have tried opening a standard serial
connection with microcom and it does function.

The code in attest should work given the method I am using, is this correct?
If so I can just rewrite it to something ... a little more towards my
purpose.

Thanks,
Robert

-----Original Message-----
From: Marcel Holtmann [mailto:[email protected]]
Sent: Tuesday, October 04, 2005 12:59 PM
To: Robert Wlaschin
Cc: '[email protected]'
Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm


Hi Robert,

> In regards to the type of communication, I'm trying to create a BT
> serial connection. The device I'm attempting to connect to is
> actually a weight scale (medical device). It doesn't support any
> other services. I probably need to add that I changed rfcomm.conf to
> listen, bind, and connect for rfcomm0. Note: The last time I used
> linux was in college and it was only to compile my assignments, so I'm
> not savvy.

you need to do a "rfcomm bind 0 <bdaddr> <channel>" and you will get a
new /dev/rfcomm0 TTY device. Now use a terminal program like minicom or
cu for the communication.

Regards

Marcel


2005-10-05 04:10:42

by Marcel Holtmann

[permalink] [raw]
Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm

Hi Robert,

> That was a good suggestion. I've seen usage of those programs on
> various help/websites.
>
> Due to a hardware limitations, I only have microcom available which
> seems flaky at best. I seem to be getting the 'Exitcode 2 - cannot
> open device /dev/rfcomm0' error message. But I have tried opening a
> standard serial connection with microcom and it does function.
>
> The code in attest should work given the method I am using, is this
> correct? If so I can just rewrite it to something ... a little more
> towards my purpose.

check if the /dev/rfcomm0 device node has been created and if yes, then
run "hcidump -X -V" to see why the RFCOMM channel can't be opened.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel