You are not logged in.

#1 2017-04-30 16:30:25

kmsgli
Member
Registered: 2015-08-15
Posts: 33

strange rfcomm issues

Hello I have a strange issue with rfcomm.  I have used it before to connect to a serial Bluetooth device in the past.  I can use a front end like blueman and right click the device and connect as serial port and it connects fine to /dev/rfcomm0 but the issue becomes when i disconnect and want to reconnect it will not do it automatically and when i reconnect manually it uses /dev/rfcomm1.  That in turn makes the program that i am using need to change ports to /dev/rfcomm1 and its a pain.  I used to be able to use the command rfcomm bind and it would disconnect and reconnect on its own as power was turned on an off to the device.

Two questions;
1)when I try to manually type in rfcomm command i get a bash error "rfcomm command not found" even if i a m typing rfcomm --help, it is as if rfcomm is not on my system?

2) Is there any way to get blueman to just connect to /dev/rcomm0 when power is on and reconnect after a power cycle to /dev/rfcomm0?

I did a good bit of searching and it is either so simple as to why I don't have access to rfcomm via command that no one put it on the net or the problem is very rare?

Offline

#2 2017-05-02 18:28:21

kmsgli
Member
Registered: 2015-08-15
Posts: 33

Re: strange rfcomm issues

I am not sure where to start to get rfcomm commands back as it seems its part of the bluez package and ive tried reinstalling it a few times?  Any ideas?

Offline

Board footer

Powered by FluxBB