[srslte-users] "Status"

[Francisco Paisana]

Ah, I also forgot the new way to get enb reports via
"--expert.report_json_enable=true". That should create a new file in
/tmp/enb_report.json with all the enb parameters in json format.

Kind Regards,
Francisco


On Thu, May 6, 2021 at 8:19 PM Francisco Paisana <
francisco.paisana at softwareradiosystems.com> wrote:

> Ah apologies you mentioned the srsenb traces. You could also "tail" the
> enb.log for "PHR" or any other information.
>
> Kind Regards,
> Francisco
>
>
> On Thu, May 6, 2021 at 8:17 PM Francisco Paisana <
> francisco.paisana at softwareradiosystems.com> wrote:
>
>> What about pressing "t" in the srsenb command line to get the traces?
>>
>> Kind Regards,
>> Francisco
>>
>>
>> On Thu, May 6, 2021 at 2:08 PM Andrea Valori <avalori at gmail.com> wrote:
>>
>>> Dear All,
>>>
>>> Is there a way to get a "status" of the system?
>>> Questions I would like to answer are of the kind
>>>
>>>    1. "which users are connected?"
>>>    2. "which one is their phr?" (to understand if they are moving away
>>>    and likely to drop)
>>>
>>> I seem to understand that this is not something so simple to
>>> implement... at the moment I can get the answer to 1. by tracking attach
>>> and detach from the stdout of srsepc, and I can get answer 2. from tracking
>>> and parsing the trace of srsenb... not really something "straightforward",
>>> but maybe I am missing something?
>>> Is there a more sensible way to approach this? Or maybe something
>>> already implemented in the stack that I am not aware of?
>>>
>>> Cheers
>>> _______________________________________________
>>> srslte-users mailing list
>>> srslte-users at lists.softwareradiosystems.com
>>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20210506/20cdbb54/attachment.htm>