From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: ofono@ofono.org
Subject: Re: Bug/Oversight in gatchat/gatresult.c with negative numbers
Date: Fri, 06 Aug 2021 15:06:20 +0100 [thread overview]
Message-ID: <0af28d41-60eb-47b7-7b9a-99fc734bab31@dynamicdevices.co.uk> (raw)
In-Reply-To: <70bd0c15-0fe5-59ea-f619-54dadd35e586@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
On 03/08/2021 15:28, Denis Kenzior wrote:
> Hi Alex,
>
>> I have been chasing this up with Quectel and they tell me this the
>> correct implementation.
>>
>> "QCOPS and QENG command show the RSSI、RSRP and SINR value of the
>> network, this is in accordance with the 3GPP TS regulations, so it is
>> normal for negative numbers to be displayed.image"
>
>
> So the image shows the value for <rsrp>
>
> '0' if -140 dbm
> ...
> '95' if dbm is -46 to -45
> etc.
>
> <rsrp> (what is actually sent over AT commands) is never negative.
> Isn't the image supporting my earlier assertion: 'AT commands do not
> have a concept of negative numbers'?
>
> oFono exposes the <rsrp> value from 3GPP:
>
> "byte ReferenceSignalReceivedPower [optional, lte]
>
> Contains the Reference Signal Received Power. Valid range of
> values
> is 0-97. Refer to <rsrp> in 27.007, Section 8.69 for more
> details.
> "
>
> Regards,
> -Denis
Denis - I am being directed to the ITU 36.133 spec here
https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=2420
This document defines this in 9.1.4
I can't see where RSRP_-17 is defined anywhere but the strong
implication to me is that this number should be -17
Can you confirm where it states that these numbers cannot be negative
numbers as I cannot find that requirement.
Thanks,
Alex
------------------------------------------------------------------------
A colleague has just pointed me to a UBlox document which specifies for
negative values too
Regards,
Alex
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 2729 bytes --]
[-- Attachment #3: omoepmpcdeogdgnp.png --]
[-- Type: image/png, Size: 46406 bytes --]
[-- Attachment #4: dcofklpjpnbjkooh.png --]
[-- Type: image/png, Size: 93293 bytes --]
next prev parent reply other threads:[~2021-08-06 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 16:11 Bug/Oversight in gatchat/gatresult.c with negative numbers Alex J Lennon
2021-07-27 14:38 ` Denis Kenzior
2021-07-27 15:02 ` Alex J Lennon
2021-08-03 9:48 ` Alex J Lennon
2021-08-03 14:28 ` Denis Kenzior
2021-08-03 14:45 ` Alex J Lennon
2021-08-06 9:31 ` Alex J Lennon
2021-08-06 14:06 ` Alex J Lennon [this message]
2021-08-06 14:20 ` Denis Kenzior
2021-08-06 14:28 ` Alex J Lennon
2021-08-06 14:44 ` Denis Kenzior
2021-08-06 14:49 ` Alex J Lennon
2021-08-06 15:02 ` Denis Kenzior
2021-08-09 6:40 ` Martin =?unknown-8bit?q?Hundeb=C3=B8ll?=
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0af28d41-60eb-47b7-7b9a-99fc734bab31@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.