Hi everyone,

I've tried searching the forum but I cannot find a thread that talks about my actual issue. I recently got my Chateau 5G and I own the Chateau 12 but I don't experience the same kind of reset on my old device. I am thinking that there might be just an issue with my config or this is a hardware issue (actual Quectel chip onboard). Can anyone give light to this issue please.

What I have done so far:

• Switched "data_interface" mode from PCIe to USB and vice versa with AT commands // AT+QCFG="data_interface"[,<network>
  ,<diag>]

• Check modem temp during speed test for possible overheating, temps where normal // AT+QTEMP=?

• Changed the usbspeed from default 3.0 to 2.0 // AT+QCFG="usbspeed"[,<speed>]

Current firmware: RG502QEAAAR11A06M4G
Router firmware: 7.1.1 and 7.2rc3

Hello,

You should leave the data_interface to pci for the chateau 5G and the usb speed to 3.0.

Please enable lte debug logging and send the supout.rif file from your device to support@mikrotik.com generated after encountering the issue.

LTE debug logging can be enabled from CLI by issuing this command:
/system logging add topics=lte

This article explains how to make a supout.rif file:
https://wiki.mikrotik.com/wiki/Manual:S ... utput_File

Regards,
Emīls

@emilst

I purposely downgraded to RouterOS v7.1.1 and sent a supout file to the email provided above.

I also found that manually setting the CA combination to LTE B3 + 5GNR n41 reduces the reset. I say this as my provider supports LTE B1+B3 or B3+B1 + 5GNR n41 - I notice that the reset happens frequently with thicombination.

Hello everyone,
I have exactly the same issue on a LTE12 that I bought few week ago. I have tried same releases as Szxa21 has mentioned, and updated the modem firmware to the last release available I have also opened a ticket on support (SUP-74577), but I don’t have received answer yet. On your side have you few news about this issue?

09:59:57 lte,packet,raw lte1 mbim: wdm >>> recv #0
09:59:57 lte,packet,raw 04000080 10000000 00000000 05000000
09:59:57 lte,info lte1 mbim: error: function error: not opened
09:59:57 lte,error lte1 mbim: modem's control interface have reset (5)
09:59:57 lte,debug lte1 mbim: state 16=>0
09:59:57 interface,info lte1 link down

hello

same problem with lhgg and quectel em160
it seems issue disapeared if b3 is the main band.

hello

same problem with lhgg and quectel em160
it seems issue disapeared if b3 is the main band.

Hello,

This should be a modules firmware issue. The log entry means that the module has crashed. Dump logs from the module should be collected and sent to Quectel for investigation.

I am also seeing this issue on the Chateau 5G. It is happening multiple times per day.

Firmwares are up to date. I am happy to dump module logs but need some instruction or guidance.

I am also seeing this issue on the Chateau 5G. It is happening multiple times per day.

Firmwares are up to date. I am happy to dump module logs but need some instruction or guidance.

Were you able to resolve the issue? Im having random restarts as well, and looking for a way to solve it.

I have the same issue on Chateau LTE12. Running latest routeros, and firmwares.

How can I get the dump logs from the modem and send to support?

I have the same issue with my Chateau LTE18 for the past few months. It is mostly independent for the firmware and the routerOS version. It is dependent to the LTE module temperature. The enclosure does not offer good passive cooling and with high room temperature or direct sun light and increased demand for data transfer, the LTE module shuts down. Currently, I am thinking of methods to cool it down

Dmch write:

The enclosure does not offer good passive cooling and with high room temperature or direct sun light and increased demand for data transfer, the LTE module shuts down.

Even you can use some workaround, please take a minute to create a supout.rif and send it to support@mikrotik.com - all cases that way reported can "force" to build next revision of that device and do some limitation on SoC when temp is to high.. .

I have the same issue with Chateau 5G.

I changed the previous TCL modem with Mikrotik 5G and the LTE interface is resetting quite often with this error on the logs:

lte1 mbim: error: protocol error: not opened
lte1 mbim: modem's control interface have reset (9)
lte1 link down
lte1 IPv4: xxx.xxx.xxx.xxx, DNS: xxx.xxx.xxx.xxx,xxx.xxx.xxx.xxx
lte1 link up

The sim is the same and with TCL I never had issues, now I get internet disconnections all the days

Same issue

Issue found on another Chateau 5G, same operator, same issue:

lte1 mbim: error: protocol error: not opened
lte1 mbim: modem's control interface have reset
lte1 link down
lte1 IPv4: 10.16.187.72, DNS: 151.5.216.25,151.5.216.225
lte1 link up


--> LTE firmware: RG502QEAAAR13A02M4G
RouterOS 7.6
software id = 5C6S-A37J
model = D53G-5HacD2HnD

That is still the modem crashing. It shouldn't do that.

RouterOS 7.6

Check you modem firmware is latest and RouterOS is running the current "stable" before that however.
If that doesn't work, send it to Mikrotik at help.mikrotik.com with the logs+supout as directed above.

oh boy. I have the Chateau LTE12 and only with the very latest modem firmware EG12EAPAR01A13M4G these issues (interface resets, modem crashes, LTE interruption until I reset the interface, ...) have stopped.

I was hoping to upgrade to the Chateau LTE18 ax soon but now I'm in doubt if I'll maybe face my old nemesis again with that one...

Same problem here! RG502Q-EA (RG502QEAAAR11A07M4G) crashes when 5G is enabled.

lte1 mbim: error: protocol error: not opened
lte1 mbim: modem's control interface have reset (7)

Crash occur very often with combination: B7+B3+N78, but it's very weird because i had the same issue during march, then april no crashes, and now crash again.
It could be my provider, but i have no issue with my phone

Please send help

open a ticket with MT support.
i had this issue with the LTE12 modem and while it was never officially confirmed, Mikrotik worked with quectel and i went through one or two modem beta firmwares and workarounds and now with the latest firmware the issue has been resolved.

be aware though, that it took about almost a year from beginning to end, until the issue was finally resolved.

If your not running 7.10rc already, I'd recommend trying that.

open a ticket with MT support.
i had this issue with the LTE12 modem and while it was never officially confirmed, Mikrotik worked with quectel and i went through one or two modem beta firmwares and workarounds and now with the latest firmware the issue has been resolved.

be aware though, that it took about almost a year from beginning to end, until the issue was finally resolved.

Could you specify the firmware that resolved the issue for you? Thanks.

open a ticket with MT support.
i had this issue with the LTE12 modem and while it was never officially confirmed, Mikrotik worked with quectel and i went through one or two modem beta firmwares and workarounds and now with the latest firmware the issue has been resolved.

be aware though, that it took about almost a year from beginning to end, until the issue was finally resolved.

Could you specify the firmware that resolved the issue for you? Thanks.

EG12EAPAR01A13M4G

I also experience this with MikroTik Chateau LTE12 RBD53G-5HacD2HnD-TC&EG12-EA.

Router OS 7.9.1 and 7.10rc1.
The latest modem firmware EG12EAPAR01A13M4G doesn't resolve it.

Sometimes but not always do I get the "lte,error lte1 mbim: modem's control interface have reset" log message when it stops working. It seems once in this hung state the LTE connection is still established and sends some LTE data but receives no LTE data anymore. Disabling/enabling the LTE interface resolves the issue.

For me too it seems to happen mainly during data burst - for instance when performing a speed test and similar. The LTE modem does warm up in such cases but the temperature still seem to be in normal ranges. Other parts of the router warm up too, even more so I would say. I may try to install some heatsinks next and see how it goes.

Actually I downgraded to RouterOS 7.7, and the lte interface doesn't reset anymore (which is weird), but it links down/up very often during speed test

Hi EveryOne,

Same issue

Same here with 7.10 firmware, device - Mikrotik 5G LMT

Dear Mikrotik,

can we please get some proper response from you to address this issue? Some of us would like to buy your product but it does not make sense for us, if the device is unstable, overtheating or losing connection with the base tower.

• What devices are afected by this issue? Is it same for Chateau 5G AX?

• Is it common issue for all devices now? Or is it just firmware issue of the modem? Or is it overheating issue?

• Are you working on solving this issue?

Please give us some response, we would like to buy your product Thank you

Any updates here ?

still having

new firmware - 7.11 - still the same

8 reboots in an ±1 hour

Installing heat-sinks on the CPU and modem didn't help. It still happens with the latest routeros 7.11.2 and I get it on a daily basis. Disabling/enabling the LTE interface does solve it once it happens for me.

For me, it looks like it is connected with 4G\5G coverage - if the router is switching between 4G\5G, 5G is crashing more. I placed the router in a different place, where 5G is better - and lte1 was reset less often.

What your signal look like? When you move it do the bands or other things in the signal data change?
/interface lte [find] monitor once

You might want to add more logging...
/system/logging/add topics=lte,!packet,!raw

If the RouterBOOT firmware is NOT matching 7.11.2, you might want to update that too...
/system routerboard upgrade

If those don't work or debug logs don't have any clues, you might want to make supout.rif, and file a report a Mikrotik.

i hope this is a needed logging

Short follow up from my side - the issue seems fixed. Environment:
- Chateau LTE12 RBD53G-5HacD2HnD-TC&EG12-EA
- Router OS 7.12
- Latest modem firmware EG12EAPAR01A13M4G_02.001.02.001 which came with Router OS 7.12

Either Router OS 7.12 or the new modem firmware seems to fix it for me. The LTE interface is now rock solid and doesn't lose its connection anymore.