[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] master/slave switch problem
I guess you are trying to form a piconet with 3 units or? There should
be no problem as long as all of them support M/S switching. At the moment
OpenBT won't disconnect if the M/S switch fails due to unsupported remote
feature so if you first connect one client that support it and after that
connect another one which doesn't and disconnect the first one it's
not possible to connect again as the module doesn't support scatternet at
the moment. Please provide more logs if my assumption about your setup
> -----Original Message-----
> From: firstname.lastname@example.org">mailto:email@example.com]
> Sent: Monday, November 11, 2002 12:00 PM
> To: firstname.lastname@example.org
> Subject: [bluetooth-dev] master/slave switch problem
> I'm working with CSR modules that support M/S swith. I've
> established a
> connection between 2 modules and this is the result:
> BT SYS: lp_connect_rsp: Early m/s switch
> BT SYS: process_event: ROLE CHANGED
> BT SYS: process_event: Our role is master for BD Address ...
> The problem appears when I disconnect one of them. Now when I try to
> connect again I can't because the server is the master yet.
> Someone know how can I restablish the original situation?
> Best regards.
> To unsubscribe from this list: send the line "unsubscribe
> bluetooth-dev" in
> the body of a message to email@example.com
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to firstname.lastname@example.org