[Bluez-devel] modify RFCOMM_DISC_TIMEOUT

[Bluez-devel] modify RFCOMM_DISC_TIMEOUT

[Carlos AM]

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]

Hi

I am developing a GPS unit that communicates via RFCOMM and I noticed that the timeout of the RFCOMM disconnection is 20 seconds.
¿Does exists a way to change this timeout from a rfcomm server program that uses sockets?
It seems that changing this #define in the rfcomm.h is not enough

Regards
Carlos AM
Naxus Conectividad Móvil

[-- Attachment #2: Type: text/html, Size: 972 bytes --]

Re: [Bluez-devel] modify RFCOMM_DISC_TIMEOUT

[Marcel Holtmann]

Hi Carlos,

> I am developing a GPS unit that communicates via RFCOMM and I noticed
> that the timeout of the RFCOMM disconnection is 20 seconds.
> =BFDoes exists a way to change this timeout from a rfcomm server progra=
m
> that uses sockets?
> It seems that changing this #define in the rfcomm.h is not enough

what do you expect that RFCOMM_DISC_TIMEOUT is doing?

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] modify RFCOMM_DISC_TIMEOUT

[Marcel Holtmann]

Hi Carlos,

> I run a rfcomm server built on top of bluez using sockets, the client runs a
> different bluetooth protocol implementation that is very buggy and sometimes
> stops the rfcomm comunication without sending a DISC. So the rfcomm server
> waits for 20 seconds (RFCOMM_DISC_TIMEOUT) and then closes the connections
> and become available again. The sending loop of the server is:
> 
> //using sockets
> //send until write returns -1
>  while(n>=0)
>  {
>     n=write(client,s,strlen(s));
>     sleep(1);
>  }
> //go to listen again
> 
> 
> If the client simply stops the communication, not disconnect, the server
> must be available as soon as possible. 20 seconds it's too long for our
> application.

what you want is an idle timeout detection. The RFCOMM_DISC_TIMEOUT is
not meant for doing this. Show us the output of "hcidump -x -t" while
this happens.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] modify RFCOMM_DISC_TIMEOUT

[Carlos AM]

[-- Attachment #1: Type: text/plain, Size: 2203 bytes --]

Hi Marcel

I think that i've finally found the origin of the errors. The kernel log
shows:

(...)
<4> Unknown HCI packet type 01
(...)


This message is dropped every five minutes (aproximately) and the packet
type is not always 01. It seems that the serial communication (UART) with
the bluetooth module (EYMF2CAMM from TAIYO YUDEN) isn't very confiable. Do
you agree?

I used to attach the hci device using this command:
/bluez/bluezmain hciattach -n /dev/tts/2 any 115200
and always works.

Then I configured the kernel with BCSP support and tried to attach the
device using:
/bluez/bluezmain hciattach -n /dev/tts/2 bcsp 115200
/bluez/bluezmain hciattach -n /dev/tts/2 swave 115200

but none of them work at all. The error message is [hcid] Can't init device
hci0. Connection timed out(110)

What do you think about it?


Thanks for your interest.
Best Regards
CarlosAM








----- Original Message -----
From: "Marcel Holtmann" <marcel@holtmann.org>
To: "Carlos AM" <Carlos@naxus.biz>
Cc: "BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Sent: Friday, July 23, 2004 11:39 AM
Subject: Re: [Bluez-devel] modify RFCOMM_DISC_TIMEOU

> Hi Carlos,
>
> > I run a rfcomm server built on top of bluez using sockets, the client
runs a
> > different bluetooth protocol implementation that is very buggy and
sometimes
> > stops the rfcomm comunication without sending a DISC. So the rfcomm
server
> > waits for 20 seconds (RFCOMM_DISC_TIMEOUT) and then closes the
connections
> > and become available again. The sending loop of the server is:
> >
> > //using sockets
> > //send until write returns -1
> >  while(n>=0)
> >  {
> >     n=write(client,s,strlen(s));
> >     sleep(1);
> >  }
> > //go to listen again
> >
> >
> > If the client simply stops the communication, not disconnect, the server
> > must be available as soon as possible. 20 seconds it's too long for our
> > application.
>
> what you want is an idle timeout detection. The RFCOMM_DISC_TIMEOUT is
> not meant for doing this. Show us the output of "hcidump -x -t" while
> this happens.
>
> Regards
>
> Marcel
>
>

Carlos AM
Naxus Conectividad Móvil

[-- Attachment #2: Type: text/html, Size: 3479 bytes --]

Re: [Bluez-devel] modify RFCOMM_DISC_TIMEOUT

[Marcel Holtmann]

Hi Carlos,

> I think that i've finally found the origin of the errors. The kernel
> log
> shows:
> 
> (...)
> <4> Unknown HCI packet type 01
> (...)
> 
> 
> This message is dropped every five minutes (aproximately) and the
> packet
> type is not always 01. It seems that the serial communication (UART)
> with
> the bluetooth module (EYMF2CAMM from TAIYO YUDEN) isn't very
> confiable. Do
> you agree?

out of sync H4 streams are really a big problem. This can happen if you
can't enable automatic flow control. To avoid this you have to use BCSP
if it is a CSR based chip.

> Then I configured the kernel with BCSP support and tried to attach the
> device using:
> /bluez/bluezmain hciattach -n /dev/tts/2 bcsp 115200
> /bluez/bluezmain hciattach -n /dev/tts/2 swave 115200
> 
> but none of them work at all. The error message is [hcid] Can't init
> device
> hci0. Connection timed out(110)

The swave will only work if your chip is Silicon Wave based and the BCSP
method only works if you switch from H4 to BCSP first with the correct
PS key settings. Contact your module manufacturer.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel