[Bluez-users] /dev/rfcomm256 ...?

[Bluez-users] /dev/rfcomm256 ...?

[Thomas Lochmatter]

Hi

rfcomm devices with a number > 255 (e.g. /dev/rfcomm256) in "/etc/ 
bluetooth/rfcomm.conf" seem to be ignored by rfcommd. Is this a hard  
limit, or does anyone know a simple way to increase this? We  
currently have about 400 devices that should go into that file.

Thanks,
Thomas



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] /dev/rfcomm256 ...?

[Marcel Holtmann]

Hi Thomas,

> rfcomm devices with a number > 255 (e.g. /dev/rfcomm256) in "/etc/ 
> bluetooth/rfcomm.conf" seem to be ignored by rfcommd. Is this a hard  
> limit, or does anyone know a simple way to increase this? We  
> currently have about 400 devices that should go into that file.

yes, that is a hard limit. We only have 256 minor device numbers
available and that is actually quite a lot. Describe your use case,
because creating more than 256 TTY seems not like one of the best ways
to go.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] /dev/rfcomm256 ...?

[Thomas Lochmatter]

>> rfcomm devices with a number > 255 (e.g. /dev/rfcomm256) in "/etc/
>> bluetooth/rfcomm.conf" seem to be ignored by rfcommd. Is this a hard
>> limit, or does anyone know a simple way to increase this? We
>> currently have about 400 devices that should go into that file.
>
> yes, that is a hard limit. We only have 256 minor device numbers
> available and that is actually quite a lot. Describe your use case,
> because creating more than 256 TTY seems not like one of the best ways
> to go.

Thanks. We have 400 robots, numbered from 1 to 400 (with a couple of  
gaps) and equipped with a bluetooth chip (serial port profile). We  
don't need to communicate with more than 5 at the same time, but  
these 5 robots can be picked at random from the 400. Hence, we need  
to be able to establish a connection to all of them at any time.

Up to now, we only used the first 200 and put all them in /etc/ 
bluetooth/rfcomm.conf with "bind yes". This worked reasonably well  
(apart from the problems with concurrent access that I mentioned in  
another post). Is there a more elegant way?

Thomas



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] /dev/rfcomm256 ...?

[Marcel Holtmann]

Hi Thomas,

> >> rfcomm devices with a number > 255 (e.g. /dev/rfcomm256) in "/etc/
> >> bluetooth/rfcomm.conf" seem to be ignored by rfcommd. Is this a hard
> >> limit, or does anyone know a simple way to increase this? We
> >> currently have about 400 devices that should go into that file.
> >
> > yes, that is a hard limit. We only have 256 minor device numbers
> > available and that is actually quite a lot. Describe your use case,
> > because creating more than 256 TTY seems not like one of the best ways
> > to go.
> 
> Thanks. We have 400 robots, numbered from 1 to 400 (with a couple of  
> gaps) and equipped with a bluetooth chip (serial port profile). We  
> don't need to communicate with more than 5 at the same time, but  
> these 5 robots can be picked at random from the 400. Hence, we need  
> to be able to establish a connection to all of them at any time.
> 
> Up to now, we only used the first 200 and put all them in /etc/ 
> bluetooth/rfcomm.conf with "bind yes". This worked reasonably well  
> (apart from the problems with concurrent access that I mentioned in  
> another post). Is there a more elegant way?

rewrite your application to use the RFCOMM socket directly. In this case
you don't have this limit at all.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] /dev/rfcomm256 ...?

[Thomas Lochmatter]

>>>> rfcomm devices with a number > 255 (e.g. /dev/rfcomm256) in "/etc/
>>>> bluetooth/rfcomm.conf" seem to be ignored by rfcommd. Is this a  
>>>> hard
>>>> limit, or does anyone know a simple way to increase this? We
>>>> currently have about 400 devices that should go into that file.
>>>
>>> yes, that is a hard limit. We only have 256 minor device numbers
>>> available and that is actually quite a lot. Describe your use case,
>>> because creating more than 256 TTY seems not like one of the best  
>>> ways
>>> to go.
>>
>> Thanks. We have 400 robots, numbered from 1 to 400 (with a couple of
>> gaps) and equipped with a bluetooth chip (serial port profile). We
>> don't need to communicate with more than 5 at the same time, but
>> these 5 robots can be picked at random from the 400. Hence, we need
>> to be able to establish a connection to all of them at any time.
>>
>> Up to now, we only used the first 200 and put all them in /etc/
>> bluetooth/rfcomm.conf with "bind yes". This worked reasonably well
>> (apart from the problems with concurrent access that I mentioned in
>> another post). Is there a more elegant way?
>
> rewrite your application to use the RFCOMM socket directly. In this  
> case
> you don't have this limit at all.

Do you have a pointer to some documentation/tutorial?

Thanks,
Thomas



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] /dev/rfcomm256 ...?

[Marcel Holtmann]

Hi Thomas,

> >>>> rfcomm devices with a number > 255 (e.g. /dev/rfcomm256) in "/etc/
> >>>> bluetooth/rfcomm.conf" seem to be ignored by rfcommd. Is this a  
> >>>> hard
> >>>> limit, or does anyone know a simple way to increase this? We
> >>>> currently have about 400 devices that should go into that file.
> >>>
> >>> yes, that is a hard limit. We only have 256 minor device numbers
> >>> available and that is actually quite a lot. Describe your use case,
> >>> because creating more than 256 TTY seems not like one of the best  
> >>> ways
> >>> to go.
> >>
> >> Thanks. We have 400 robots, numbered from 1 to 400 (with a couple of
> >> gaps) and equipped with a bluetooth chip (serial port profile). We
> >> don't need to communicate with more than 5 at the same time, but
> >> these 5 robots can be picked at random from the 400. Hence, we need
> >> to be able to establish a connection to all of them at any time.
> >>
> >> Up to now, we only used the first 200 and put all them in /etc/
> >> bluetooth/rfcomm.conf with "bind yes". This worked reasonably well
> >> (apart from the problems with concurrent access that I mentioned in
> >> another post). Is there a more elegant way?
> >
> > rewrite your application to use the RFCOMM socket directly. In this  
> > case
> > you don't have this limit at all.
> 
> Do you have a pointer to some documentation/tutorial?

some years ago, I wrote a detailed email how easy it is to convert a TTY
based application into a RFCOMM socket based application. Besides this
email there exists no further documentation. However you might wanna
take a look at the attest.c source code for an example.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users