Then I have please to help me with proper diagnostic and report that to MikroTik as "additional case" - you will be 3rd with "proof".
Enable logging of LTE, regular logs.
/system logging action add memory-lines=10000 name=lte target=memory
/system logging add action=lte prefix=DIAG__LTE6 topics=lte
Upload a lteLogger2.rsc to your ros and do /import lteLogger2.rsc;
You see new scheduler&script items what are software watchdog for script lteLogger2 - it keeps that script is still running.
Watch your logs, detect problems like swape/hop/switch/replace eNB/phy-cellid/primary or ca band... to other one... maybe flapping ca in time... maybe every 4 or 5h... logs like this example:
That give you better perspective to see if something is change or not with LTE general.
Now we will discuss about your case. But this checking must be with time.
I will tested other firmware 024, 025, 026 with r11e-lte6 on LDFR in this near week time and good if you check your side, that what you can.
Main example is one. If you can connect to the same Tower, eNB with few bands, and that bands "should" aggregate then we have 50% of confirmation on our site.
When other (not R11e-LTE6) module can aggregate that bands then we have like 100% of sure that it should at lte6 be 2CA too.
You should set band 3, connect and report connected EARFCN and PHY-CELLID.
Do a CellMonitor and report others earfcn&pci. ROS in testing and development branch have a new parameter "max-age=2m" for cell-monitor.
I have that 43 possibility at sxtr and 5 are connected, yes, I do the 44 Cell Locks. I record in excel the eNB with 3x speedtest.net/run .
Now I know the best eNB and in future I repeat that all test to found other bands from that eNB.
Correct the position of SXTR to one of the best results thanks to Cell Lock at this earfcn&pci and a MikroTik App
, now I have better SINR
what give me +20Mb...
When I do that for other Bands like B1/7/20 then magic of Excel show me all Bands earfcn&pci of that eNB.
When I can do Cell Lock to all of them - this is proof you could connect to them.
At his level we not have more diagnostic like watch a SIB messages
in LTE between eNB and our module and we not know what they negotiate.. and our role end-s here.
When we have confirmation etc. then please use https://help.mikrotik.com/servicedesk
to create case with MikroTik Support Team and share case with me as firstname.lastname@example.org
You do not have the required permissions to view the files attached to this post.