Return-Path: Message-ID: From: Robert Wlaschin To: "'Marcel Holtmann'" , Robert Wlaschin Cc: "'bluez-devel@lists.sourceforge.net'" Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm Date: Tue, 4 Oct 2005 15:46:14 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5C935.6CEEDBD0" List-ID: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C5C935.6CEEDBD0 Content-Type: text/plain; charset="iso-8859-1" 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:marcel@holtmann.org] Sent: Tuesday, October 04, 2005 12:59 PM To: Robert Wlaschin Cc: 'bluez-devel@lists.sourceforge.net' 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 " and you will get a new /dev/rfcomm0 TTY device. Now use a terminal program like minicom or cu for the communication. Regards Marcel ------_=_NextPart_001_01C5C935.6CEEDBD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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:marcel@holtmann.org]
Sent: Tuesday, October 04, 2005 12:59 PM
To: Robert Wlaschin
Cc: 'bluez-devel@lists.sourceforge.net'
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

------_=_NextPart_001_01C5C935.6CEEDBD0--