RSSI property is inquiry RSSI and this should be stated here especially
that we plan to add connection RSSI property soon.
---
v2: Added ConnectionTXPowerMax property to device.
doc/device-api.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/device-api.txt b/doc/device-api.txt
index 2d9fa3c..7a301d3 100644
--- a/doc/device-api.txt
+++ b/doc/device-api.txt
@@ -191,5 +191,5 @@ Properties string Address [readonly]
int16 RSSI [readonly, optional]
- Received Signal Strength Indicator of the remote
+ Received Signal Strength Indicator (inquiry) of the remote
device.
--
1.8.4
Hi Marcel,
On 8 May 2014 22:33, Marcel Holtmann <[email protected]> wrote:
> Hi Lukasz,
>
>> This patch introduces device method to start and stop connection monitor
>> and two new device properties ConnectionRSSI, ConnectionTXPower and
>> ConnectionTXPowerMax.
>>
>> ConnectionRSSI and ConnectionTXPower are tracked when monitor is active
>
> lets leave this until we have figure out the kernel API for this. We are still going forth and back on that.
Whatever way we choose to get those data from the kernel, I have
feeling that this API will work with.
Adding those information as properties of device keep consistency with
existing API(similar to RSSI).
I made those properties optional so we don't have to have it now.
The only thing we could think of is if we want to have poll method as
Scott proposed or some kind of Monitor as it is now proposed and
roughly discussed with Szymon and Johan.
Any comment?
Please also keep in mind that the kernel mgmt API will not be present
on many systems for at least 6 month.
>
Ok I understand. Anyway, If there is no major issues with that api, It
would be very helpful if we could fix it.
> Regards
>
> Marcel
>
Thanks and BR
Lukasz
Hi Lukasz,
> This patch introduces device method to start and stop connection monitor
> and two new device properties ConnectionRSSI, ConnectionTXPower and
> ConnectionTXPowerMax.
>
> ConnectionRSSI and ConnectionTXPower are tracked when monitor is active
lets leave this until we have figure out the kernel API for this. We are still going forth and back on that. Please also keep in mind that the kernel mgmt API will not be present on many systems for at least 6 month.
Regards
Marcel
This patch introduces device method to start and stop connection monitor
and two new device properties ConnectionRSSI, ConnectionTXPower and
ConnectionTXPowerMax.
ConnectionRSSI and ConnectionTXPower are tracked when monitor is active
---
doc/device-api.txt | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 51 insertions(+)
diff --git a/doc/device-api.txt b/doc/device-api.txt
index 7a301d3..0b44417 100644
--- a/doc/device-api.txt
+++ b/doc/device-api.txt
@@ -100,6 +100,34 @@ Methods void Connect()
Possible errors: org.bluez.Error.DoesNotExist
org.bluez.Error.Failed
+
+ void StartConnectionMonitor()
+
+ This method starts connection monitor session.
+
+ This method enables connection information tracking.
+ E.g. ConnectionRSSI, ConnectionTXPower.
+
+ Use StopConnectionMonitor to release session.
+
+ Possible errors: org.bluez.Error.NotReady
+ org.bluez.Error.Failed
+ org.bluez.Error.NotConnected
+ org.bluez.Error.NotSupported
+
+ void StopConnectionMonitor()
+
+ This method stops previous StartConnectionMonitor
+ session.
+
+ Note that connection monitor is shared between all
+ monitor sessions thus calling StopConnectionMonitor
+ releases a single session.
+
+ Possible errors: org.bluez.Error.Failed
+ org.bluez.Error.NotReady
+ org.bluez.Error.NotAuthorized
+
Properties string Address [readonly]
The Bluetooth device address of the remote device.
@@ -193,3 +221,26 @@ Properties string Address [readonly]
Received Signal Strength Indicator (inquiry) of the remote
device.
+
+ int16 ConnectionRSSI [readonly, optional]
+
+ Received Signal Strength Indicator of connected remote
+ device.
+
+ This property is present only if at least one connection
+ monitor session is active.
+
+ Note that RSSI has different units for BR/EDR (dB)
+ and LE (dBm) as specified in BT Core ver. 4.1, Vol. 2,
+ Part E, Chapter 7.5.4
+
+ int16 ConnectionTXPowerMax [readonly, optional]
+
+ Maximum transmit power level to connected remote device.
+
+ int16 ConnectionTXPower [readonly, optional]
+
+ Transmit power level to connected remote device.
+
+ This property is present only if at least one connection
+ monitor session is active.
--
1.8.4