LHG LTE6 kit LTE dropout

RouterOS General
1

Good morning and thanks for taking the time to read this - Hopefully someone may be able to give some assistance.

Some time ago I purchased this Kit for my in-laws in Kent. I am no stranger to the kit as I have installed in locations in Norfolk too.

At the in-laws we use the same dish on EE and connect to a mast around 4-5 miles away. They get a stable connection which fluctuates between 30 and 70MB with an SNIR of around 10-16 operating on band 3 and 20 in tandem.

I recommended to somebody nearby a an identical system again with the same hardware on EE. They are actually 2 miles closer to the antenna we connect to from the in-laws however we struggled to connect - I assume the direction / landscape / atmospherics prevent connectivity.

I redirected the dish to an antenna around 6 miles away which instantly an SNIR of 22 and we are obtaining 95MB down and 30MB up! Fantastic I thought! The connection wasn’t overly stable and failed speed tests at random intervals. After looking into the setup page again we noticed the current provider went from EE or 23430 to +CME Error. Shortly after EE came back and all was fine. Then again the +CME error and a drop of connection.

From looking at the Logs we are getting every two minutes LTE1 :reply timeout for AT+EEMGINFO? (Please see screen shot)

I have checked the SIM is inserted and safe
The cable is good (Although it looks to be a config related issue as the dropouts are so constant)
I have replaced the POE injector to make sure it wasn’t a power drop.
I have used the APN “everywhere” and with the auto config without APN security we get the same result as when we use APN “everywhere”. Username “eesecure” Password “secure” Auth type “pap”

Really getting quite perplexed by this - Hopefully someone may have had experience of this or know a week to get it going.

If we were really low signal I would understand however everything looks to be good. I have connected to masts over 7 miles away without this much grief!

Thanks very much in advance!

2

First step, is the LTE6 firmware the same in both machines?

/interface lte firmware-upgrade lte1 upgrade=no

3

Thanks for your reply!

Yes both on the same firmware however both now on different masts. My supplier suggested earlier that we look at the LTE6 firmware which we did however for some reason the console reported that the update had been downloaded to the modem, then it was installing then back to text entry. After waiting the WIKI suggested 10 minutes and then restarting the device, a recheck of the firmware version showed it still on V020 not V025.

Our supplier has suggested getting in contact with MT to obtain a full version of the firmware to load from the console - hopefully, this may help? Really perplexing, to be honest. We thought it was a problem running on B7 as we set it to B3 and it was slow yet stable. after a while again it failed with the same error. I will post below the log with LTE logging - On quickset it just comes up with +CME error - and it is usually when performing a speed test or uploading / downloading a large file.

**Just deleted the log - It was far too long! I will get the file as described in the next post.

4

At least the modem has survived the upgrade with the previous version still available. Mikrotik warns that the FOTA upgrade must be done using latest stable versions, 6.46.4 was already fine enough for the purpose, there were some related fixes in 6.46. So if you are not at 6.46 at least, get to 6.46.7 and don’t forget to upgrade also the firmware of the RB itself before trying FOTA again.


Hard to say. I have no idea whether an upgrade from console is available for LTE6 in particular.


This sounds like a load issue or a channel aggregation issue. I’d say there’s no point in digging in other directions before you succeed with the upgrade to V025, and I’d definitely recommend to take the device to the place where you know the other one to work OK for doing the upgrade. The V020 may have an issue with something specific to the sector where it is currently being used, and the fewer trouble when doing the upgrade the better the chance that it succeeds.

One more thought related to this, power insufficiency. How long is the Ethernet cable between the PoE injector and the unit on the mast?


/log print file=somename on the command line gives a much better readable output. Posting the result as an attachment or between [****code] and [/****code] tags makes the posts easier for reading too. You may want to edit your previous post accordingly, but I don’t think in this particular case the log sheds more light to the issue. It is just an evidence that the issue appears.

5

Thank you for your reply! Yes from going over it again and realising how much of a BA reading my post I see what you mean RE Log file :slight_smile:

I will get the log as you describe when next on-site.

Do you know power did cross my mind too - It is a fairly long cable however I am going to get power to the dish when next there and hook it straight into the laptop. I will report back.

We can connect to another mast just with a really low SNIR and associated speed however as you mentioned - might be stable enough to perform the U/G.

Hopefully, I will be there later and will report back,

Thanks, Sindy

6

Hello,

Please post a log with topic=lte .

I recommend to use ros6.47.4 or newer and the lte module firmware should be 026.
I solve for some users with MikroTik support some similar problems and support have a new beta.. but first public your logs.

You can track changes at cells etc by LTE Logger: http://forum.mikrotik.com/t/r11e-lte6-2ca-not-staying-connected/136004/22

What CME ERROR you have, give log.
23430 is not a cme error but ID of ISP EE in UK, base at CellMapper information.

7

Hi all,

Interesting, I’m seeing the same issue here in Norfolk on the LHG LTE6 Kit, but not on the SXT LTE6 Kit.
I’ve tried firmware versions 6.46.4, 6.46.8 Long Term and 6.47.8, all with the same result.
I’ve tried a second unit LHG LTE6 Kit from our stock and got the same error, so its not hardware.
I’ll try new firmware and upgrading the LTE firmware to see where that gets us.

Pete.

8

@Pete,
check the LTE FIRMWARE by:https://wiki.mikrotik.com/wiki/Manual:Interface/LTE#Modem_firmware_upgrade
SXTR and LHGR in option “LTE6 Kit” have a mPCIe lte module know as R11e-LTE6 who have latest firmware 026 what you can see in lte1\General tab.

LOGs !
What the same ERROR ?? CME ERROR should have some NUMBER !!! GIVE LOG or NUMBER or Screenshot :slight_smile: I cannot say about error you not provide.

9

Hi all,

OK I’ve upgraded everything to 6.47.8 and the firmware is already on V025
There’s an upgrade to V026 but the interface is still unstable and I’m worried that an interface drop during the upgrade process will break it for good.

I’ve changed carrier from EE to O2 and it’s stable.

See log files below, line 377 was with EE SIM, no error since moving to O2.
Dec/14/2020 13:49:18 lte,info lte1: registered home
Dec/14/2020 13:49:25 interface,info lte1 link up
Dec/14/2020 13:49:49 lte,error lte1: reply timeout for: AT+EEMGINFO?
Dec/14/2020 13:49:49 interface,info lte1 link down
Dec/14/2020 13:50:00 lte,error lte1: reply timeout for: ATE0
Dec/14/2020 13:50:28 lte,info lte1: registered home
Dec/14/2020 13:50:35 interface,info lte1 link up
Dec/14/2020 13:51:17 lte,error lte1: reply timeout for: AT+EEMGINFO?
Dec/14/2020 13:51:17 interface,info lte1 link down
Dec/14/2020 13:51:28 lte,error lte1: reply timeout for: ATE0
Dec/14/2020 13:52:47 system,info device changed by freeclix
Dec/14/2020 13:52:59 script,info Running Firmware check
Dec/14/2020 13:52:59 script,info Firmware check, no action required
Dec/14/2020 13:54:29 lte,info lte1: registered home
Dec/14/2020 13:54:36 interface,info lte1 link up
Dec/14/2020 13:57:59 script,warning LTE traffic counter 0 MB
Dec/14/2020 14:00:01 script,info LTE still active now with O2 as carrier
Dec/14/2020 14:00:32 script,info LTE no drops

Pete.

10

Hi All,

Now that the unit is stable, running with O2 as the carrier.
I’ll perform the LTE modem firmware update and then test again back on EE when it’s done.

I’ll update the post in a few mins, probs after lunch :wink:

Pete.

11

/system logging add topics=lte
/system reboot

wait 3m until lte1 try connect or error happens.

/log print file=log-YYYY-MM-DD—HHSS.txt
Share that file here in code or quote syntax or pastbin.

Your prev. logs not have anythink like error CME ERROR. Try do upgrade firmware to 026.
Even if your ISP is not stable, r11e-lte6 will first download a firmware file and only when it will be done then he go to upgrade procedure who will be offline of cource and r11e-lte6 will have own default settings on it.

12

Hi All,

The issue is resolved, moving to another carrier and upgrading the modem firmware to V026 has resolved the issue.

See logs below:
Dec/14/2020 13:50:28 lte,info lte1: registered home
Dec/14/2020 13:50:35 interface,info lte1 link up
Dec/14/2020 13:51:17 lte,error lte1: reply timeout for: AT+EEMGINFO?
Dec/14/2020 13:51:17 interface,info lte1 link down
Dec/14/2020 13:51:28 lte,error lte1: reply timeout for: ATE0
Dec/14/2020 13:52:47 system,info device changed by freeclix
Dec/14/2020 13:52:59 script,info Running Firmware check
Dec/14/2020 13:52:59 script,info Firmware check, no action required
Dec/14/2020 13:54:29 lte,info lte1: registered home
Dec/14/2020 13:54:36 interface,info lte1 link up
Dec/14/2020 13:57:59 script,warning LTE traffic counter 0 MB
Dec/14/2020 14:00:01 script,info LTE still active now with O2 as carrier
Dec/14/2020 14:00:32 script,info LTE no drops
Dec/14/2020 14:02:59 script,info Running Firmware check
Dec/14/2020 14:02:59 script,info Firmware check, no action required
Dec/14/2020 14:04:08 interface,info lte1 link down
Dec/14/2020 14:05:51 lte,info lte1: registered home
Dec/14/2020 14:05:59 interface,info lte1 link up
Dec/14/2020 14:07:29 lte,info lte1: not registred, state: 0
Dec/14/2020 14:07:29 interface,info lte1 link down
Dec/14/2020 14:08:00 system,info device changed by freeclix
Dec/14/2020 14:09:06 lte,info lte1: registered home
Dec/14/2020 14:09:13 interface,info lte1 link up
Dec/14/2020 14:10:05 script,error Upgrade LTE Firmware completed - Now running EE SIM again
Dec/14/2020 14:12:59 script,info Running Firmware check
Dec/14/2020 14:12:59 script,info Firmware check, no action required
Dec/14/2020 14:12:59 script,warning LTE traffic counter 0 MB
Dec/14/2020 14:22:59 script,info Running Firmware check
Dec/14/2020 14:22:59 script,info Firmware check, no action required
Dec/14/2020 14:27:59 script,warning LTE traffic counter 0 MB
Dec/14/2020 14:32:59 script,info Running Firmware check
Dec/14/2020 14:32:59 script,info Firmware check, no action required
Dec/14/2020 14:42:59 script,info Running Firmware check
Dec/14/2020 14:42:59 script,info Firmware check, no action required
Dec/14/2020 14:42:59 script,warning LTE traffic counter 0 MB
Dec/14/2020 14:52:59 script,info Running Firmware check
Dec/14/2020 14:52:59 script,info Firmware check, no action required
Dec/14/2020 14:57:59 script,warning LTE traffic counter 0 MB

Current time stamp: Dec/14/2020 15:09:33

There has been no link down or error message since moving to V026.
Both carriers are working with there respective APN settings as they should.
Only EE had the issue, O2 worked without any need for the upgrade.
There’s obviously something carrier related to the “lte,error lte1: reply timeout for: AT+EEMGINFO?” message that makes the EE connection unstable.

I hope this information is helpful to everyone.

Regards,

Pete.