This command reads the Tx power level for a given connected device
---
doc/mgmt-api.txt | 28 ++++++++++++++++++++++++++++
1 files changed, 28 insertions(+), 0 deletions(-)
@@ -815,6 +815,34 @@ Unblock Device Command or failure.+Read Tx Power Level Command+======================++ Command Code: 0x0028+ Controller Index: <controller id>+ Command Parameters: Address (6 Octets)+ Address_Type (1 Octet)+ Type (1 Octet)+ Return Parameters: Address (6 Octets)+ Address_Type (1 Octet)+ Status (1 Octet)+ Level (1 Octet)++ Possible values for the Address_Type parameter:+ 0 BR/EDR+ 1 LE Public+ 2 LE Random++ Possible values for the Type parameter:+ 0 Current Transmit Power Level+ 1 Maximum Transmit Power Level++ This command can only be used when the controller is powered.++ This command generates a Command Complete event on success+ or failure.++ Set Device ID Command =====================
This command reads the Tx power level for a given connected device
---
doc/mgmt-api.txt | 28 ++++++++++++++++++++++++++++
1 files changed, 28 insertions(+), 0 deletions(-)
@@ -815,6 +815,34 @@ Unblock Device Command or failure.+Read Tx Power Level Command+======================++ Command Code: 0x0028
how is this suppose to work. This command and Set Device ID are suppose
to have the same command code?
+ Controller Index: <controller id>
+ Command Parameters: Address (6 Octets)
+ Address_Type (1 Octet)
+ Type (1 Octet)
+ Return Parameters: Address (6 Octets)
+ Address_Type (1 Octet)
+ Status (1 Octet)
+ Level (1 Octet)
+
+ Possible values for the Address_Type parameter:
+ 0 BR/EDR
+ 1 LE Public
+ 2 LE Random
+
+ Possible values for the Type parameter:
+ 0 Current Transmit Power Level
+ 1 Maximum Transmit Power Level
Which ones do you care about? And why not just read both and return both
at the same time.
I think that I made this pretty clear multiple times already. The mgmt
API is not for stuffing random HCI commands into it. Please explain your
usage pattern of the results clearly.
Who is triggering this command and who is consuming the results?
Regards
Marcel
On Mon, Mar 12, 2012 at 02:42, Marcel Holtmann [off-list ref] wrote:
Hi Arik,
quoted
This command reads the Tx power level for a given connected device
---
=A0doc/mgmt-api.txt | =A0 28 ++++++++++++++++++++++++++++
=A01 files changed, 28 insertions(+), 0 deletions(-)
+
+ =A0 =A0 Possible values for the Address_Type parameter:
+ =A0 =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 BR/EDR
+ =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 LE Public
+ =A0 =A0 =A0 =A0 =A0 =A0 2 =A0 =A0 =A0 LE Random
+
+ =A0 =A0 Possible values for the Type parameter:
+ =A0 =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 Current Transmit Power Level
+ =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 Maximum Transmit Power Level
Which ones do you care about? And why not just read both and return both
at the same time.
I think that I made this pretty clear multiple times already. The mgmt
API is not for stuffing random HCI commands into it. Please explain your
usage pattern of the results clearly.
Who is triggering this command and who is consuming the results?
Well the proximity reporter and proximity monitor profiles are the
ones using this (with LE connections only). The proximity monitor can
query the reporter for the Tx power level. The spec claims there's no
point in polling for this, as the value doesn't change during an LE
connection.
Both profiles only care about the current Tx power level. I added the
type for flexibility. It can be removed of course.
In the proposed implementation the reporter reads this value when a
device connects and caches it. When a remote device asks for this
value (via an ATT read as part of the TPS profile), we return the
cached value.
Regards,
Arik
This command reads the Tx power level for a given connected device
---
doc/mgmt-api.txt | 28 ++++++++++++++++++++++++++++
1 files changed, 28 insertions(+), 0 deletions(-)
@@ -815,6 +815,34 @@ Unblock Device Command or failure.+Read Tx Power Level Command+======================++ Command Code: 0x0028
how is this suppose to work. This command and Set Device ID are suppose
to have the same command code?
Ah you're right I missed that. I'll put 0x29 then.
quoted
quoted
+ Controller Index: <controller id>
+ Command Parameters: Address (6 Octets)
+ Address_Type (1 Octet)
+ Type (1 Octet)
+ Return Parameters: Address (6 Octets)
+ Address_Type (1 Octet)
+ Status (1 Octet)
+ Level (1 Octet)
+
+ Possible values for the Address_Type parameter:
+ 0 BR/EDR
+ 1 LE Public
+ 2 LE Random
+
+ Possible values for the Type parameter:
+ 0 Current Transmit Power Level
+ 1 Maximum Transmit Power Level
Which ones do you care about? And why not just read both and return both
at the same time.
I think that I made this pretty clear multiple times already. The mgmt
API is not for stuffing random HCI commands into it. Please explain your
usage pattern of the results clearly.
Who is triggering this command and who is consuming the results?
Well the proximity reporter and proximity monitor profiles are the
ones using this (with LE connections only). The proximity monitor can
query the reporter for the Tx power level. The spec claims there's no
point in polling for this, as the value doesn't change during an LE
connection.
so why are we not just reading that value when creating a LE connection?
What is the penalty for doing it on every LE connection?
Both profiles only care about the current Tx power level. I added the
type for flexibility. It can be removed of course.
In the proposed implementation the reporter reads this value when a
device connects and caches it. When a remote device asks for this
value (via an ATT read as part of the TPS profile), we return the
cached value.
On Mon, Mar 12, 2012 at 19:29, Marcel Holtmann [off-list ref] wrote:
Hi Arik,
quoted
quoted
quoted
This command reads the Tx power level for a given connected device
---
=A0doc/mgmt-api.txt | =A0 28 ++++++++++++++++++++++++++++
=A01 files changed, 28 insertions(+), 0 deletions(-)
+
+ =A0 =A0 Possible values for the Address_Type parameter:
+ =A0 =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 BR/EDR
+ =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 LE Public
+ =A0 =A0 =A0 =A0 =A0 =A0 2 =A0 =A0 =A0 LE Random
+
+ =A0 =A0 Possible values for the Type parameter:
+ =A0 =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 Current Transmit Power Level
+ =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 Maximum Transmit Power Level
Which ones do you care about? And why not just read both and return bo=
th
quoted
quoted
at the same time.
I think that I made this pretty clear multiple times already. The mgmt
API is not for stuffing random HCI commands into it. Please explain yo=
ur
quoted
quoted
usage pattern of the results clearly.
Who is triggering this command and who is consuming the results?
Well the proximity reporter and proximity monitor profiles are the
ones using this (with LE connections only). The proximity monitor can
query the reporter for the Tx power level. The spec claims there's no
point in polling for this, as the value doesn't change during an LE
connection.
so why are we not just reading that value when creating a LE connection?
What is the penalty for doing it on every LE connection?
Well presumably it should only be read when the TPS profile if
enabled. The cost is sending another command to the controller on each
connection. Not sure it's very high.
Maybe we can even integrate it into the "device connected" event, and
just read it for all connecting devices.
I guess it's a matter of personal preference.
I think this API is better for future proofing - it gives the caller
the option to get the Tx power for BR/EDR devices as well, at
arbitrary times (since it can change during a BR connection).
Some earlier emails suggested it might be useful.
quoted
Both profiles only care about the current Tx power level. I added the
type for flexibility. It can be removed of course.
In the proposed implementation the reporter reads this value when a
device connects and caches it. When a remote device asks for this
value (via an ATT read as part of the TPS profile), we return the
cached value.
+
+ =A0 =A0 Possible values for the Address_Type parameter:
+ =A0 =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 BR/EDR
+ =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 LE Public
+ =A0 =A0 =A0 =A0 =A0 =A0 2 =A0 =A0 =A0 LE Random
+
+ =A0 =A0 Possible values for the Type parameter:
+ =A0 =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 Current Transmit Power Level
+ =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 Maximum Transmit Power Level
Which ones do you care about? And why not just read both and return b=
oth
quoted
quoted
quoted
at the same time.
I think that I made this pretty clear multiple times already. The mgm=
t
quoted
quoted
quoted
API is not for stuffing random HCI commands into it. Please explain y=
our
quoted
quoted
quoted
usage pattern of the results clearly.
Who is triggering this command and who is consuming the results?
Well the proximity reporter and proximity monitor profiles are the
ones using this (with LE connections only). The proximity monitor can
query the reporter for the Tx power level. The spec claims there's no
point in polling for this, as the value doesn't change during an LE
connection.
so why are we not just reading that value when creating a LE connection?
What is the penalty for doing it on every LE connection?
Well presumably it should only be read when the TPS profile if
enabled. The cost is sending another command to the controller on each
connection. Not sure it's very high.
Maybe we can even integrate it into the "device connected" event, and
just read it for all connecting devices.
I guess it's a matter of personal preference.
I think this API is better for future proofing - it gives the caller
the option to get the Tx power for BR/EDR devices as well, at
arbitrary times (since it can change during a BR connection).
Some earlier emails suggested it might be useful.
quoted
quoted
Both profiles only care about the current Tx power level. I added the
type for flexibility. It can be removed of course.
In the proposed implementation the reporter reads this value when a
device connects and caches it. When a remote device asks for this
value (via an ATT read as part of the TPS profile), we return the
cached value.
+ Controller Index: <controller id>
+ Command Parameters: Address (6 Octets)
+ Address_Type (1 Octet)
+ Type (1 Octet)
+ Return Parameters: Address (6 Octets)
+ Address_Type (1 Octet)
+ Status (1 Octet)
+ Level (1 Octet)
+
+ Possible values for the Address_Type parameter:
+ 0 BR/EDR
+ 1 LE Public
+ 2 LE Random
+
+ Possible values for the Type parameter:
+ 0 Current Transmit Power Level
+ 1 Maximum Transmit Power Level
Which ones do you care about? And why not just read both and return both
at the same time.
I think that I made this pretty clear multiple times already. The mgmt
API is not for stuffing random HCI commands into it. Please explain your
usage pattern of the results clearly.
Who is triggering this command and who is consuming the results?
Well the proximity reporter and proximity monitor profiles are the
ones using this (with LE connections only). The proximity monitor can
query the reporter for the Tx power level. The spec claims there's no
point in polling for this, as the value doesn't change during an LE
connection.
so why are we not just reading that value when creating a LE connection?
What is the penalty for doing it on every LE connection?
Well presumably it should only be read when the TPS profile if
enabled. The cost is sending another command to the controller on each
connection. Not sure it's very high.
Maybe we can even integrate it into the "device connected" event, and
just read it for all connecting devices.
I guess it's a matter of personal preference.
I think this API is better for future proofing - it gives the caller
the option to get the Tx power for BR/EDR devices as well, at
arbitrary times (since it can change during a BR connection).
Some earlier emails suggested it might be useful.
quoted
quoted
Both profiles only care about the current Tx power level. I added the
type for flexibility. It can be removed of course.
In the proposed implementation the reporter reads this value when a
device connects and caches it. When a remote device asks for this
value (via an ATT read as part of the TPS profile), we return the
cached value.
So it gets always read anyway.
Only when TPS server is enabled.
Is the current API acceptable?
I don't know yet. Send a new version with detailed explanation and I
have another look. I am currently not fully convinced. I have the
feeling we should be doing this differently.
Regards
Marcel
+
+ =A0 =A0 Possible values for the Address_Type parameter:
+ =A0 =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 BR/EDR
+ =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 LE Public
+ =A0 =A0 =A0 =A0 =A0 =A0 2 =A0 =A0 =A0 LE Random
+
+ =A0 =A0 Possible values for the Type parameter:
+ =A0 =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 Current Transmit Power Le=
vel
quoted
quoted
quoted
quoted
quoted
quoted
+ =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 Maximum Transmit Power Le=
vel
quoted
quoted
quoted
quoted
quoted
Which ones do you care about? And why not just read both and retur=
n both
quoted
quoted
quoted
quoted
quoted
at the same time.
I think that I made this pretty clear multiple times already. The =
mgmt
quoted
quoted
quoted
quoted
quoted
API is not for stuffing random HCI commands into it. Please explai=
n your
quoted
quoted
quoted
quoted
quoted
usage pattern of the results clearly.
Who is triggering this command and who is consuming the results?
Well the proximity reporter and proximity monitor profiles are the
ones using this (with LE connections only). The proximity monitor ca=
n
quoted
quoted
quoted
quoted
query the reporter for the Tx power level. The spec claims there's n=
o
quoted
quoted
quoted
quoted
point in polling for this, as the value doesn't change during an LE
connection.
so why are we not just reading that value when creating a LE connecti=
on?
quoted
quoted
quoted
What is the penalty for doing it on every LE connection?
Well presumably it should only be read when the TPS profile if
enabled. The cost is sending another command to the controller on each
connection. Not sure it's very high.
Maybe we can even integrate it into the "device connected" event, and
just read it for all connecting devices.
I guess it's a matter of personal preference.
I think this API is better for future proofing - it gives the caller
the option to get the Tx power for BR/EDR devices as well, at
arbitrary times (since it can change during a BR connection).
Some earlier emails suggested it might be useful.
quoted
quoted
Both profiles only care about the current Tx power level. I added th=
e
quoted
quoted
quoted
quoted
type for flexibility. It can be removed of course.
In the proposed implementation the reporter reads this value when a
device connects and caches it. When a remote device asks for this
value (via an ATT read as part of the TPS profile), we return the
cached value.
So it gets always read anyway.
Only when TPS server is enabled.
Is the current API acceptable?
I don't know yet. Send a new version with detailed explanation and I
have another look. I am currently not fully convinced. I have the
feeling we should be doing this differently.
Sure. It'll take me a couple of days to formulate it.
Regards,
Arik