starred/luci-app-3ginfo-lite

Fork 0

mirror of https://github.com/4IceG/luci-app-3ginfo-lite.git synced 2026-04-25 11:25:50 +03:00

[GH-ISSUE #65] Add RSRP\RSRQ\SINR of SCC cell for Quectel Module #49

New issue

Closed

opened 2026-03-04 11:58:10 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 11:58:10 +03:00

Owner

Originally created by @stich86 on GitHub (Apr 7, 2024).
Original GitHub issue: https://github.com/4IceG/luci-app-3ginfo-lite/issues/65

Hi @4IceG,

do you think it will be possible to add RSRP\RSRQ\SINR also for secondary bands?

the AT+QCAINFO reports it for SCC bands:

+QCAINFO: "PCC",1850,100,"LTE BAND 3",1,130,-91,-11,-62,13
+QCAINFO: "SCC",3025,75,"LTE BAND 7",1,16,-104,-8,-87,0,0,-,-
+QCAINFO: "SCC",525,75,"LTE BAND 1",1,225,-93,-8,-77,15,0,-,-
+QCAINFO: "SCC",643296,10,"NR5G BAND 78",622

It will be very useful to create something like i've ported to ZTE CPE:

So you can also decide which bands are better or not.

Let me know :)

Originally created by @stich86 on GitHub (Apr 7, 2024). Original GitHub issue: https://github.com/4IceG/luci-app-3ginfo-lite/issues/65 Hi @4IceG, do you think it will be possible to add RSRP\RSRQ\SINR also for secondary bands? the `AT+QCAINFO` reports it for SCC bands: ``` +QCAINFO: "PCC",1850,100,"LTE BAND 3",1,130,-91,-11,-62,13 +QCAINFO: "SCC",3025,75,"LTE BAND 7",1,16,-104,-8,-87,0,0,-,- +QCAINFO: "SCC",525,75,"LTE BAND 1",1,225,-93,-8,-77,15,0,-,- +QCAINFO: "SCC",643296,10,"NR5G BAND 78",622 ``` It will be very useful to create something like i've ported to ZTE CPE: <img width="834" alt="image" src="https://github.com/4IceG/luci-app-3ginfo-lite/assets/27808541/f3fc23b1-39ae-478e-8642-c164a04b8dc0"> So you can also decide which bands are better or not. Let me know :)

kerem closed this issue

2026-03-04 11:58:10 +03:00

kerem commented

2026-03-04 11:58:11 +03:00

Author

Owner

@4IceG commented on GitHub (Apr 8, 2024):

Hi @stich86 ,
I have a problem with this 🤔. I am already receiving information from users that 3ginfo-lite shows something that their LTE modems do not have. Another thing is that new modems return much more data and now I get questions why the package shows so little...

I don't want to expand the package too much because it will lose its simplicity. I have to wonder if it's possible to keep the appearance for the primary band and somehow extend the data to the aggregation bands.

@4IceG commented on GitHub (Apr 8, 2024): Hi @stich86 , I have a problem with this 🤔. I am already receiving information from users that 3ginfo-lite shows something that their LTE modems do not have. Another thing is that new modems return much more data and now I get questions why the package shows so little... I don't want to expand the package too much because it will lose its simplicity. I have to wonder if it's possible to keep the appearance for the primary band and somehow extend the data to the aggregation bands.

kerem commented

2026-03-04 11:58:11 +03:00

Author

Owner

@stich86 commented on GitHub (Apr 8, 2024):

Hi @stich86 , I have a problem with this 🤔. I am already receiving information from users that 3ginfo-lite shows something that their LTE modems do not have. Another thing is that new modems return much more data and now I get questions why the package shows so little...

I don't want to expand the package too much because it will lose its simplicity. I have to wonder if it's possible to keep the appearance for the primary band and somehow extend the data to the aggregation bands.

i'll try to add it in the SCC string, just to have a reference

@stich86 commented on GitHub (Apr 8, 2024): > Hi @stich86 , I have a problem with this 🤔. I am already receiving information from users that 3ginfo-lite shows something that their LTE modems do not have. Another thing is that new modems return much more data and now I get questions why the package shows so little... > > I don't want to expand the package too much because it will lose its simplicity. I have to wonder if it's possible to keep the appearance for the primary band and somehow extend the data to the aggregation bands. i'll try to add it in the SCC string, just to have a reference

kerem commented

2026-03-04 11:58:11 +03:00

Author

Owner

@4IceG commented on GitHub (Apr 8, 2024):

Now I focused on the transfer package, I had no plans to modify 3ginfo-lite, but I will think about it.

I don't want to create a package that will scroll like a long pdf, and I've seen such modifications (it makes me sad). It's a waste of my work when someone then does something like that, like in a competition, who can read more from the modem and put it on one page.

@4IceG commented on GitHub (Apr 8, 2024): Now I focused on the transfer package, I had no plans to modify 3ginfo-lite, but I will think about it. I don't want to create a package that will scroll like a long pdf, and I've seen such modifications (it makes me sad). It's a waste of my work when someone then does something like that, like in a competition, who can read more from the modem and put it on one page.

kerem referenced this issue

2026-03-13 13:31:49 +03:00

[GH-ISSUE #49] Error: Bad control character in string literal in JSON at position 67 #171

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/luci-app-3ginfo-lite#49

No description provided.

Rows
Columns