Hello. I have Mikrrotik LHGG (RouterOS 7.4) + EM160R-GL (EM160RGLAUR02A07M4G)
The modem reboots several times a day. Error in logs:
lte info: lte1 mbim: error: protocol error: not opened
lte error: lte1 mbim: modem’s control interface have reset
interface info: lte1 link down
…
After a few seconds, starts automatically.
Doesn’t depend on heat. Did a hard reset of the modem. I ask for help.
Hi,
Normally, the EM160 module does not restart automatically. Check whether the power supply of the EM160 module is stable. And whether the upper computer has the pWRkey key of the module to repeatedly pull down the action, I hope to help you.
1 Like
Hi!
How to check module power EM160R-GL?
pWRkey missing.
Hello Aleksey!
I think what you wanted to ask with “what measuring instruments can I use to check the stability of the power supply of the module”? Is this true or false?
pWRkey missing.
Are you absolutely sure about this?
Could you provide a link to such information?
Добрый день! я вообще не понял что хотели от меня ) что такое pWRkey ?
I suggest you rewrite the last message in English. This forum is visited by people from all over the world. And anyone can help you, from anywhere in the world. And technical support will not read your messages in Cyrillic.
To get started, download the datasheet for the EM160R-GL module. Study it carefully. And then search the Internet for what pWRkey means. Many questions after studying the materials, I think, will be clear to you.
You have an unofficial mobile operator tariff with a static public IP address.
Did the module work fine with a dynamic private IP address?
And why didn’t you provide the full log from the moment of the lte link down event to the moment of lte link up? And from the moment of the lte link up event to the moment of lte link down. (You can hide confidential information).
No difference, static ip or dynamic
Before and after logs the same. I just chose one of the cases, and there are several of them. Why post the same thing but with different information?
From the three lines of the log fragment you provided, nothing is clear at all. ((
Is this also a fragment of your log?
06:03:56 lte,async lte1: sent AT+QNWCFG=“rat_seq”,0403
06:03:56 lte,async lte1: rcvd ERROR ?
If yes, then ask the seller of your SIM card or mobile operator why the error occurred.
The Quectel tech support man rightly started to rule out the simplest possible causes of the problem.
P.S.
And once again - translate your up text from Cyrillic to Latin. At technical support, your message was displayed as unreadable characters. (Maybe that’s why they didn’t answer you anymore).
yes, I forgot about the full log
6:03:43 lte,info lte1 mbim: error: protocol error: not opened
06:03:43 lte,error lte1 mbim: modem's control interface have reset (12)
06:03:43 lte,debug lte1 mbim: state 16=>0
06:03:43 interface,info lte1 link down
06:03:43 lte,account lte1 session: 17199s 124846225/33496456 bytes 172807/112689 packets
06:03:43 lte,debug lte1 mbim: <<< close
06:03:55 lte,async lte1: sent AT E0 V1
06:03:56 lte,async lte1: sent AT E0 V1
06:03:56 lte,async lte1: rcvd OK
06:03:56 lte,async lte1: sent AT+CMEE=2
06:03:56 lte,debug lte1 mbim: state 0=>1
06:03:56 lte,debug lte1 mbim: wdm max tx 4096
06:03:56 lte,debug lte1 mbim: <<< open
06:03:56 lte,async lte1: rcvd OK
06:03:56 lte,async lte1: sent AT+CGREG=2
06:03:56 lte,async lte1: rcvd OK
06:03:56 lte,async lte1: sent AT+CEREG=2
06:03:56 lte,async lte1: rcvd OK
06:03:56 lte,async lte1: sent AT+EGMR=0,5
06:03:56 lte,async lte1: rcvd +EGMR: "MPC22BS2F0015880P"
06:03:56 lte,async lte1: sent AT+QSIMDET=1,1
06:03:56 lte,async lte1: rcvd OK
06:03:56 lte,async lte1: sent AT+QGMR
06:03:56 lte,async lte1: rcvd EM160RGLAUR02A07M4G_01.001.01.001
06:03:56 lte,async lte1: sent AT+QNVFR="/nv/item_files/Thin_UI/enable_thin_ui_cfg"
06:03:56 lte,async lte1: rcvd +QNVFR: 01
06:03:56 lte,async lte1: sent AT+QCFG="pdp/duplicatechk"
06:03:56 lte,async lte1: rcvd +QCFG: "pdp/duplicatechk",0
06:03:56 lte,async lte1: sent AT+QNETINFO="cmrctl",1
06:03:56 lte,async lte1: rcvd OK
06:03:56 lte,async lte1: sent AT+QCFG="lte/bandprior",3,7,1
06:03:56 lte,async lte1: rcvd OK
06:03:56 lte,async lte1: sent AT+QNWCFG="rat_seq",0403
06:03:56 lte,async lte1: rcvd ERROR
06:03:56 lte,async lte1: sent AT+QNWCFG="bearer",0,1
06:03:56 lte,async lte1: rcvd ERROR
06:03:56 lte,async lte1: sent AT+QNVFW="/nv/item_files/Thin_UI/enable_thin_ui_cfg",00
06:03:56 lte,async lte1: rcvd OK
06:03:56 lte,debug lte1 mbim: >>> N service: connect, command: subscriber ready status
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet 00000000 00000000 00000000 00000000
06:03:56 lte,packet 00000000 00000000 00000000
06:03:56 lte,debug lte1 mbim: subscriber ready state: 0
06:03:56 lte,debug lte1 mbim: >>> N service: connect, command: connect
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet 00000000 03000000 00000000 00000000
06:03:56 lte,packet 00000000 00000000 00000000 00000000
06:03:56 lte,packet 00000000
06:03:56 lte,debug lte1 mbim: connect: #0 deactivated 0
06:03:56 lte,debug lte1 mbim: >>> N service: connect, command: radio state
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet 01000000 01000000
06:03:56 lte,debug lte1 mbim: >>> N service: sms, command: configuration
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet 01000000 00000000 0f000000 00000000
06:03:56 lte,packet 18000000 18000000 2b003700 39003200
06:03:56 lte,packet 36003200 39003000 39003000 39003000
06:03:56 lte,debug lte1 mbim: >>> N service: sms, command: configuration
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet 01000000 00000000 0f000000 00000000
06:03:56 lte,packet 18000000 18000000 2b003700 39003200
06:03:56 lte,packet 36003200 39003000 39003000 39003000
06:03:56 lte,debug lte1 mbim: >>> N service: connect, command: register state
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet 00000000 03000000 01000000 20000000
06:03:56 lte,packet 01000000 30000000 0a000000 3c000000
06:03:56 lte,packet 0e000000 00000000 00000000 02000000
06:03:56 lte,packet 32003500 30003000 32000000 4d006500
06:03:56 lte,packet 67006100 46006f00 6e000000
06:03:56 lte,debug lte1 mbim: >>> N service: connect, command: packet service
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet 00000000 01000000 00000000 00000000
06:03:56 lte,packet 00000000 00000000 00000000
06:03:56 lte,debug lte1 mbim: packet service: attaching data class: 0 nwe:
06:03:56 lte,debug lte1 mbim: >>> N service: conn_ext, command: location info
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet ffffffff e9130000 0439dc0d
06:03:56 lte,debug lte1 mbim: >>> N service: unknown: 8d8b9eba37be449b8f1e61cb034a702e, command: 10
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet e6070000 07000000 1a000000 03000000
06:03:56 lte,packet 03000000 33000000 b4000000 00000000
06:03:56 lte,packet 00000000
06:03:56 lte,debug lte1 mbim: >>> N service: connect, command: packet service
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet 00000000 02000000 20000000 80f0fa02
06:03:56 lte,packet 00000000 00e1f505 00000000
06:03:56 lte,debug lte1 mbim: packet service: attached data class: 20 nwe:
06:03:56 lte,debug lte1 mbim: >>> N service: conn_ext, command: lte attach status
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet 01000000 03000000 28000000 16000000
06:03:56 lte,packet 00000000 00000000 00000000 00000000
06:03:56 lte,packet 00000000 00000000 66006900 78006500
06:03:56 lte,packet 64006900 70002e00 6d007300 6b000000
06:03:56 lte,debug lte1 mbim: lte status: attached apn: fixedip.msk iptype: 3
06:03:56 lte,debug lte1 mbim: >>> N service: unknown: 4bf384761e6a41dbb1d8bed289c25bdb, command: 1
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet 01000000 fa000000 05000000 50000000
06:03:56 lte,packet 19000000
06:03:56 lte,debug lte1 mbim: >>> N service: connect, command: subscriber ready status
06:03:56 lte,packet lte1 mbim: status data:
06:03:56 lte,packet 01000000 1c000000 1e000000 3c000000
06:03:56 lte,packet 28000000 00000000 00000000 32003500
06:03:56 lte,packet 30003000 32003600 39003900 33003500
06:03:56 lte,packet 33003600 34003600 30000000 38003900
06:03:56 lte,packet 37003000 31003000 32003600 39003900
06:03:56 lte,packet 33003500 33003600 34003600 30003200
06:03:56 lte,packet 46004600
06:03:56 lte,debug lte1 mbim: subscriber ready state: 1
06:03:57 lte,debug lte1 mbim: open done, status: 0
06:03:57 lte,debug lte1 mbim: state 1=>2
06:03:57 lte,debug lte1 mbim: set radio: off
06:03:57 lte,debug lte1 mbim: <<< S service: connect, command: radio state
06:03:57 lte,debug lte1 mbim: >>> N service: connect, command: packet service
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 00000000 01000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000
06:03:57 lte,debug lte1 mbim: packet service: attaching data class: 0 nwe:
06:03:57 lte,debug lte1 mbim: >>> N service: conn_ext, command: lte attach status
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 00000000 00000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000
06:03:57 lte,debug lte1 mbim: lte status: detached iptype: 0
06:03:57 lte,debug lte1 mbim: >>> N service: connect, command: register state
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 00000000 01000000 01000000 00000000
06:03:57 lte,packet 01000000 00000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 02000000
06:03:57 lte,debug lte1 mbim: >>> N service: connect, command: register state
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 00000000 02000000 01000000 00000000
06:03:57 lte,packet 01000000 00000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 02000000
06:03:57 lte,debug lte1 mbim: >>> N service: connect, command: packet service
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 00000000 04000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000
06:03:57 lte,debug lte1 mbim: packet service: detached data class: 0 nwe:
06:03:57 lte,debug lte1 mbim: >>> N service: connect, command: radio state
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 01000000 00000000
06:03:57 lte,debug lte1 mbim: >>> D service: connect, command: radio state
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 01000000 00000000
06:03:57 lte,debug lte1 mbim: state 2=>5
06:03:57 lte,debug lte1 mbim: <<< Q service: connect, command: device services
06:03:57 lte,debug lte1 mbim: >>> N service: connect, command: register state
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 00000000 01000000 01000000 00000000
06:03:57 lte,packet 01000000 00000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 02000000
06:03:57 lte,debug lte1 mbim: >>> N service: sms, command: configuration
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 01000000 00000000 0f000000 00000000
06:03:57 lte,packet 18000000 18000000 2b003700 39003200
06:03:57 lte,packet 36003200 39003000 39003000 39003000
06:03:57 lte,debug lte1 mbim: >>> D service: connect, command: device services
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 11000000 00000000 90000000 6c000000
06:03:57 lte,packet fc000000 30000000 2c010000 20000000
06:03:57 lte,packet 4c010000 2c000000 78010000 28000000
06:03:57 lte,packet a0010000 24000000 c4010000 20000000
06:03:57 lte,packet e4010000 20000000 04020000 30000000
06:03:57 lte,packet 34020000 20000000 54020000 34000000
06:03:57 lte,packet 88020000 3c000000 c4020000 44000000
06:03:57 lte,packet 08030000 4c000000 54030000 24000000
06:03:57 lte,packet 78030000 20000000 98030000 20000000
06:03:57 lte,packet a289cc33 bcbb8b4f b6b0133e c2aae6df
06:03:57 lte,packet 00000000 00000000 14000000 01000000
06:03:57 lte,packet 02000000 03000000 04000000 05000000
06:03:57 lte,packet 06000000 07000000 08000000 09000000
06:03:57 lte,packet 0a000000 0b000000 0c000000 0d000000
06:03:57 lte,packet 0f000000 10000000 13000000 14000000
06:03:57 lte,packet 15000000 16000000 17000000 533fbeeb
06:03:57 lte,packet
06:03:57 lte,packet 14fe4467 9f9033a2 23e56c3f 00000000
06:03:57 lte,packet 00000000 05000000 01000000 02000000
06:03:57 lte,packet 03000000 04000000 05000000 e550a0c8
06:03:57 lte,packet 5e82479e 82f710ab f4c3351f 00000000
06:03:57 lte,packet 00000000 01000000 01000000 4bf38476
06:03:57 lte,packet 1e6a41db b1d8bed2 89c25bdb 00000000
06:03:57 lte,packet 00000000 04000000 01000000 02000000
06:03:57 lte,packet 03000000 04000000 d8f20131 fcb54e17
06:03:57 lte,packet 8602d6ed 3816164c 00000000 00000000
06:03:57 lte,packet 03000000 01000000 02000000 03000000
06:03:57 lte,packet 1d2b5ff7 0aa148b2 aa5250f1 5767174e
06:03:57 lte,packet 00000000 00000000 02000000 01000000
06:03:57 lte,packet 03000000 d1a30bc2 f97a6e43 bf65c7e2
06:03:57 lte,packet 4fb0f0d3 00000000 00000000 01000000
06:03:57 lte,packet 01000000 883b7c26 985f43fa 980427d7
06:03:57 lte,packet fb80959c 00000000 00000000 01000000
06:03:57 lte,packet
06:03:57 lte,packet 01000000 2d0c12c9 0e6a495a 915c8d17
06:03:57 lte,packet 4fe5d63c 00000000 00000000 05000000
06:03:57 lte,packet 01000000 02000000 03000000 04000000
06:03:57 lte,packet 05000000 e9f7dea2 feaf4009 93ce90a3
06:03:57 lte,packet 694103b6 00000000 00000000 01000000
06:03:57 lte,packet 01000000 5967bdcc 7fd249a2 9f5cb2e7
06:03:57 lte,packet 0e527db3 00000000 00000000 06000000
06:03:57 lte,packet 01000000 02000000 03000000 04000000
06:03:57 lte,packet 09000000 0a000000 6427015f 579d48f5
06:03:57 lte,packet 8c54f43e d1e76f83 00000000 00000000
06:03:57 lte,packet 08000000 01000000 02000000 03000000
06:03:57 lte,packet 04000000 05000000 06000000 07000000
06:03:57 lte,packet 08000000 c2f6588e f0374bc9 8665f4d4
06:03:57 lte,packet 4bd09367 00000000 00000000 0a000000
06:03:57 lte,packet 01000000 02000000 03000000 04000000
06:03:57 lte,packet 05000000 06000000 07000000 08000000
06:03:57 lte,packet
06:03:57 lte,packet 09000000 0a000000 3d01dcc5 fef54d05
06:03:57 lte,packet 0d3abef7 058e9aaf 00000000 00000000
06:03:57 lte,packet 0c000000 01000000 03000000 04000000
06:03:57 lte,packet 05000000 06000000 07000000 08000000
06:03:57 lte,packet 09000000 0a000000 0b000000 0c000000
06:03:57 lte,packet 0e000000 68223d04 9f6c4e0f 822d2844
06:03:57 lte,packet 1fb72340 00000000 00000000 02000000
06:03:57 lte,packet 01000000 02000000 8d8b9eba 37be449b
06:03:57 lte,packet 8f1e61cb 034a702e 00000000 00000000
06:03:57 lte,packet 01000000 0a000000 11223344 55667788
06:03:57 lte,packet 99aabbcc ddeeff11 00000000 00000000
06:03:57 lte,packet 01000000 01000000
06:03:57 lte,debug lte1 mbim: device service: a289cc33bcbb8b4fb6b0133ec2aae6df command count: 20
06:03:57 lte,debug lte1 mbim: device service: 533fbeeb14fe44679f9033a223e56c3f command count: 5
06:03:57 lte,debug lte1 mbim: device service: e550a0c85e82479e82f710abf4c3351f command count: 1
06:03:57 lte,debug lte1 mbim: device service: 4bf384761e6a41dbb1d8bed289c25bdb command count: 4
06:03:57 lte,debug lte1 mbim: device service: d8f20131fcb54e178602d6ed3816164c command count: 3
06:03:57 lte,debug lte1 mbim: device service: 1d2b5ff70aa148b2aa5250f15767174e command count: 2
06:03:57 lte,debug lte1 mbim: device service: d1a30bc2f97a6e43bf65c7e24fb0f0d3 command count: 1
06:03:57 lte,debug lte1 mbim: device service: 883b7c26985f43fa980427d7fb80959c command count: 1
06:03:57 lte,debug lte1 mbim: device service: 2d0c12c90e6a495a915c8d174fe5d63c command count: 5
06:03:57 lte,debug lte1 mbim: device service: e9f7dea2feaf400993ce90a3694103b6 command count: 1
06:03:57 lte,debug lte1 mbim: device service: 5967bdcc7fd249a29f5cb2e70e527db3 command count: 6
06:03:57 lte,debug lte1 mbim: device service: 6427015f579d48f58c54f43ed1e76f83 command count: 8
06:03:57 lte,debug lte1 mbim: device service: c2f6588ef0374bc98665f4d44bd09367 command count: 10
06:03:57 lte,debug lte1 mbim: device service: 3d01dcc5fef54d050d3abef7058e9aaf command count: 12
06:03:57 lte,debug lte1 mbim: connect ext cids: 1,3,4,5,6,7,8,9,10,11,12,14
06:03:57 lte,debug lte1 mbim: device service: 68223d049f6c4e0f822d28441fb72340 command count: 2
06:03:57 lte,debug lte1 mbim: device service: 8d8b9eba37be449b8f1e61cb034a702e command count: 1
06:03:57 lte,debug lte1 mbim: device service: 112233445566778899aabbccddeeff11 command count: 1
06:03:57 lte,debug lte1 mbim: <<< Q service: connect, command: device caps
06:03:57 lte,debug lte1 mbim: >>> D service: connect, command: device caps
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 01000000 01000000 01000000 02000000
06:03:57 lte,packet 3c000000 03000000 01000000 08000000
06:03:57 lte,packet 00000000 00000000 68000000 1e000000
06:03:57 lte,packet 40000000 26000000 88000000 12000000
06:03:57 lte,packet 45004d00 31003600 30005200 47004c00
06:03:57 lte,packet 41005500 52003000 32004100 30003700
06:03:57 lte,packet 4d003400 47000000 38003600 35003300
06:03:57 lte,packet 36003100 30003500 30003200 37003600
06:03:57 lte,packet 33003100 30000000 45004d00 31003600
06:03:57 lte,packet 30005200 5f004700 4c000000
06:03:57 lte,debug lte1 mbim: device caps: cls:3c sms:3 ctr:1 max_sess:8
06:03:57 lte,debug lte1 mbim: <<< Q service: connect, command: provisioned contexts
06:03:57 lte,debug lte1 mbim: >>> D service: connect, command: provisioned contexts
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 05000000 2c000000 34000000 60000000
06:03:57 lte,packet 3c000000 9c000000 3c000000 d8000000
06:03:57 lte,packet 44000000 1c010000 4c000000 01000000
06:03:57 lte,packet 7e5e2a7e 4e6f7272 736b656e 7e5e2a7e
06:03:57 lte,packet 00000000 00000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 00000000
06:03:57 lte,packet 02000000 b43f758c a5604b46 b35ec586
06:03:57 lte,packet 9641fb54 34000000 06000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 00000000
06:03:57 lte,packet 00000000 69006d00 73000000 03000000
06:03:57 lte,packet b43f758c a5604b46 b35ec586 9641fb54
06:03:57 lte,packet 34000000 06000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 00000000
06:03:57 lte,packet 73006f00 73000000 04000000 7e5e2a7e
06:03:57 lte,packet 4e6f7272 736b656e 7e5e2a7e 34000000
06:03:57 lte,packet 10000000 00000000 00000000 00000000
06:03:57 lte,packet
06:03:57 lte,packet 00000000 00000000 00000000 69006e00
06:03:57 lte,packet 74006500 72006e00 65007400 05000000
06:03:57 lte,packet 7e5e2a7e 4e6f7272 736b656e 7e5e2a7e
06:03:57 lte,packet 34000000 16000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 00000000
06:03:57 lte,packet 66006900 78006500 64006900 70002e00
06:03:57 lte,packet 6d007300 6b000000
06:03:57 lte,debug lte1 mbim: provisioned ctx: 1, type: internet, apn:
06:03:57 lte,debug lte1 mbim: provisioned ctx: 2, type: none, apn: ims
06:03:57 lte,debug lte1 mbim: provisioned ctx: 3, type: none, apn: sos
06:03:57 lte,debug lte1 mbim: provisioned ctx: 4, type: internet, apn: internet
06:03:57 lte,debug lte1 mbim: provisioned ctx: 5, type: internet, apn: fixedip.msk
06:03:57 lte,debug lte1 mbim: state 5=>3
06:03:57 lte,debug lte1 mbim: state 3=>6
06:03:57 lte,debug lte1 mbim: <<< Q service: connect, command: subscriber ready status
06:03:57 lte,debug lte1 mbim: >>> D service: connect, command: subscriber ready status
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 01000000 1c000000 1e000000 3c000000
06:03:57 lte,packet 28000000 00000000 00000000 32003500
06:03:57 lte,packet 30003000 32003600 39003900 33003500
06:03:57 lte,packet 33003600 34003600 30000000 38003900
06:03:57 lte,packet 37003000 31003000 32003600 39003900
06:03:57 lte,packet 33003500 33003600 34003600 30003200
06:03:57 lte,packet 46004600
06:03:57 lte,debug lte1 mbim: subscriber ready state: 1
06:03:57 lte,async lte1: sent AT+CGEREP=2,0
06:03:57 lte,debug lte1 mbim: state 6=>8
06:03:57 lte,debug lte1 mbim: set lte attach apn: fixedip.msk
06:03:57 lte,debug lte1 mbim: <<< S service: conn_ext, command: lte attach config
06:03:57 lte,async lte1: rcvd OK
06:03:57 lte,async lte1: sent AT+CMGF=0
06:03:57 lte,async lte1: rcvd OK
06:03:57 lte,async lte1: sent AT+CNMI=1,1,0,1,0
06:03:57 lte,async lte1: rcvd OK
06:03:57 lte,async lte1: sent AT+CPMS="SM","SM","SM"
06:03:57 lte,async,event lte1: +CPMS: 0,15,0,15,0,15
06:03:57 lte,async lte1: rcvd OK
06:03:57 lte,debug lte1 mbim: >>> D service: conn_ext, command: lte attach config
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 03000000 1c000000 44000000 60000000
06:03:57 lte,packet 44000000 a4000000 44000000 00000000
06:03:57 lte,packet 00000000 01000000 2c000000 16000000
06:03:57 lte,packet 00000000 00000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 66006900 78006500
06:03:57 lte,packet 64006900 70002e00 6d007300 6b000000
06:03:57 lte,packet 00000000 01000000 01000000 2c000000
06:03:57 lte,packet 16000000 00000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 66006900
06:03:57 lte,packet 78006500 64006900 70002e00 6d007300
06:03:57 lte,packet 6b000000 00000000 02000000 01000000
06:03:57 lte,packet 2c000000 16000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 00000000
06:03:57 lte,packet 66006900 78006500 64006900 70002e00
06:03:57 lte,packet 6d007300 6b000000
06:03:57 lte,debug lte1 mbim: lte attach ctx source: 1 roam: 0 ip: 0 apn: fixedip.msk
06:03:57 lte,debug lte1 mbim: lte attach ctx source: 1 roam: 1 ip: 0 apn: fixedip.msk
06:03:57 lte,debug lte1 mbim: lte attach ctx source: 1 roam: 2 ip: 0 apn: fixedip.msk
06:03:57 lte,debug lte1 mbim: request register, operator: [auto]
06:03:57 lte,debug lte1 mbim: <<< S service: connect, command: register state
06:03:57 lte,debug lte1 mbim: >>> D service: connect, command: register state
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 00000000 01000000 01000000 00000000
06:03:57 lte,packet 01000000 00000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 02000000
06:03:57 lte,debug lte1 mbim: register state: deregistered, operator id: , class: gsm, avail data classes: 0, nwe:
06:03:57 lte,debug lte1 mbim: state 8=>9
06:03:57 lte,debug lte1 mbim: set radio: on
06:03:57 lte,debug lte1 mbim: <<< S service: connect, command: radio state
06:03:57 lte,debug lte1 mbim: >>> N service: connect, command: radio state
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 01000000 01000000
06:03:57 lte,debug lte1 mbim: >>> D service: connect, command: radio state
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 01000000 01000000
06:03:57 lte,debug lte1 mbim: >>> N service: connect, command: register state
06:03:57 lte,packet lte1 mbim: status data:
06:03:57 lte,packet 00000000 02000000 01000000 00000000
06:03:57 lte,packet 01000000 00000000 00000000 00000000
06:03:57 lte,packet 00000000 00000000 00000000 02000000
06:03:57 lte,debug lte1 mbim: register state: searching, operator id: , class: gsm, avail data classes: 0, nwe:
06:03:57 lte,debug lte1 mbim: state 9=>10
06:03:58 lte,debug lte1 mbim: >>> N service: sms, command: configuration
06:03:58 lte,packet lte1 mbim: status data:
06:03:58 lte,packet 01000000 00000000 0f000000 00000000
06:03:58 lte,packet 18000000 18000000 2b003700 39003200
06:03:58 lte,packet 36003200 39003000 39003000 39003000
06:03:58 lte,debug lte1 mbim: >>> N service: conn_ext, command: location info
06:03:58 lte,packet lte1 mbim: status data:
06:03:58 lte,packet ffffffff e9130000 0439dc0d
06:03:58 lte,debug lte1 mbim: >>> N service: connect, command: register state
06:03:58 lte,packet lte1 mbim: status data:
06:03:58 lte,packet 00000000 03000000 01000000 20000000
06:03:58 lte,packet 01000000 30000000 0a000000 3c000000
06:03:58 lte,packet 0e000000 00000000 00000000 02000000
06:03:58 lte,packet 32003500 30003000 32000000 4d006500
06:03:58 lte,packet 67006100 46006f00 6e000000
06:03:58 lte,debug lte1 mbim: register state: home, operator id: 25002, class: gsm, avail data classes: 20, nwe:
06:03:58 lte,debug lte1 mbim: state 10=>12
06:03:58 lte,debug lte1 mbim: auto attach
06:03:58 lte,debug lte1 mbim: >>> N service: connect, command: packet service
06:03:58 lte,packet lte1 mbim: status data:
06:03:58 lte,packet 00000000 01000000 00000000 00000000
06:03:58 lte,packet 00000000 00000000 00000000
06:03:58 lte,debug lte1 mbim: packet service: attaching data class: 0 nwe:
06:03:58 lte,debug lte1 mbim: state 12=>14
06:03:58 lte,debug lte1 mbim: >>> N service: connect, command: packet service
06:03:58 lte,packet lte1 mbim: status data:
06:03:58 lte,packet 00000000 02000000 20000000 80f0fa02
06:03:58 lte,packet 00000000 00e1f505 00000000
06:03:58 lte,debug lte1 mbim: packet service: attached data class: 20 nwe:
06:03:58 lte,debug lte1 mbim: state 14=>15
06:03:58 lte,debug lte1 mbim: >>> N service: conn_ext, command: lte attach status
06:03:58 lte,packet lte1 mbim: status data:
06:03:58 lte,packet 01000000 03000000 28000000 16000000
06:03:58 lte,packet 00000000 00000000 00000000 00000000
06:03:58 lte,packet 00000000 00000000 66006900 78006500
06:03:58 lte,packet 64006900 70002e00 6d007300 6b000000
06:03:58 lte,debug lte1 mbim: lte status: attached apn: fixedip.msk iptype: 3
06:03:58 lte,debug lte1 mbim: >>> N service: unknown: 8d8b9eba37be449b8f1e61cb034a702e, command: 10
06:03:58 lte,packet lte1 mbim: status data:
06:03:58 lte,packet e6070000 07000000 1a000000 03000000
06:03:58 lte,packet 03000000 38000000 b4000000 00000000
06:03:58 lte,packet 00000000
06:03:59 lte,debug lte1 mbim: do connect activate #0
06:03:59 lte,debug lte1 mbim: apn: fixedip.msk iptype: 0
06:03:59 lte,debug lte1 mbim: <<< S service: connect, command: connect
06:03:59 lte,debug lte1 mbim: >>> N service: connect, command: connect
06:03:59 lte,packet lte1 mbim: status data:
06:03:59 lte,packet 00000000 02000000 00000000 00000000
06:03:59 lte,packet 7e5e2a7e 4e6f7272 736b656e 7e5e2a7e
06:03:59 lte,packet 00000000
06:03:59 lte,debug lte1 mbim: connect: #0 activating 0
06:03:59 lte,debug lte1 mbim: waiting for done
06:03:59 lte,debug lte1 mbim: >>> D service: connect, command: connect
06:03:59 lte,packet lte1 mbim: status data:
06:03:59 lte,packet 00000000 01000000 00000000 01000000
06:03:59 lte,packet 7e5e2a7e 4e6f7272 736b656e 7e5e2a7e
06:03:59 lte,packet 00000000
06:03:59 lte,debug lte1 mbim: connect: #0 activated 0
06:03:59 lte,debug lte1 mbim: get ip config #0
06:03:59 lte,debug lte1 mbim: <<< Q service: connect, command: ip configuration
06:04:00 lte,debug lte1 mbim: >>> D service: connect, command: ip configuration
06:04:00 lte,packet lte1 mbim: status data:
06:04:00 lte,packet 00000000 0f000000 00000000 01000000
06:04:00 lte,packet 3c000000 00000000 00000000 44000000
06:04:00 lte,packet 00000000 02000000 48000000 00000000
06:04:00 lte,packet 00000000 dc050000 00000000 1c000000
06:04:00 lte,packet 1fad19f7 1fad19f8 551a928b 551a9ebb
06:04:00 lte,debug lte1 mbim: received ip config #0 15,0
06:04:00 lte,debug lte1 mbim: IPv4: 31.1**.2**.2**, DNS: 85.26.146.139,85.26.158.187
06:04:00 lte,debug MTU: 1500
06:04:00 lte,info lte1 IPv4: 31.1**.2**.2**, DNS: 85.26.146.139,85.26.158.187
06:04:00 lte,debug lte1 mbim: state 15=>16
06:04:00 interface,info lte1 link up
06:04:00 lte,async lte1: sent AT+CMGL=4
06:04:00 lte,async lte1: rcvd
06:09:05 lte,debug lte1 mbim: >>> N service: connect, command: packet service
06:09:05 lte,packet lte1 mbim: status data:
06:09:05 lte,packet 00000000 02000000 20000000 00ab9041
06:09:05 lte,packet 00000000 00ab9041 00000000
06:09:05 lte,debug lte1 mbim: packet service: attached data class: 20 nwe:
If no one else answers, send a description of the problem to technical support with a log attached as a text file.
Hi I had pretty much the exact same issue with that modem firmware in an OpenWRT router, I studied the logs for weeks. Finally after upgrading to the …09m4g firmware, this resolved the constant reboots in my situation. Your router pings default or manually configured server to monitor connection such as 8.8.8.8, with multiple unsuccessful pings, also default or manually configured it will perform a ping reboot. Read “( [OpenWrt Wiki] Watchcat - network watchdog utility)” This most likely could resolve your case with the modem firmware upgrade.
Please send a link to the firmware update via DFOTA for EM160R-GL
Hello, it is known that the EM160RGLAUR02A09M4G version should be able to solve your current restart problem. I can provide you with this firmware version and upgrade tool, you can upgrade through the USB port of the module. For the upgrade method, please refer to the use document in the path of qFlash tool I sent to you. I will apply internally for DFOTA subcontracting to upgrade EM160RGLAUR02A07M4G to EM160RGLAUR02A07M4G, but it is expected to take three to five days to make the DFOTA package internally, so I suggest you use the local USB upgrade method I sent you first to upgrade. I will share the DFOTA package with you as soon as it is finished. Thank you.
Software version link:Sign in to your account
Links to upgrade tools and documentation:Sign in to your account
Thank you. I’ll be waiting DFOTA package. Since I do not yet have the opportunity to update via USB.
I solved the problem. Updated firmware via USB (EM160RGLAUR02A09M4G).
Uptime > 20h.
speedtest 
Hi,
OTA file download connection as shown below:
A07–>A10:
https://cnquectel-my.sharepoint.com/:u:/g/personal/kerr_yang_quectel_com/EW-0vNfhQ_1Dp-4VywuQorYB_sKe3rW9OyWVFKyYWYHOhw?e=AiMBVz
Hi,
When the module came to me with version(EM160RGLAUR02A07M4G) i had the same problem with Aleksey.now i have upgrade with (EM160RGLAUR02A09M4G) and this problem solved ,but onother problem appear.im running EM160R module on mikrotik RBM33G on first boot of board,module recognize normal from board, lte1 connection appear on interface but cant lock any frequency so no connection to the internet .in this time if i disable and enable again lte1 interface the connection working perfect .this problem appear after upgrade mpdule.what should i do .any idea ?
1 Like
HI
I have exactly the same problem now. as an option to enable the script for ping through netwatch
Script:
/int disable lte1
:delay 5s
/int enable lte1
/log info message="RESTART LTE"
Good idea,but is not solution for me because i have failover with wired backup connection,so when lte is down after boot netwatch will ping through wired connection .
for now i found other solution but quectel must provide a fix for this bug of last firmware .
The solution that i found is to schedule a script 2min after boot to lock e.g on 3bands.
hi,
1)is it possible to upgrade from version EM160RGLAUR02A05M4G to version A10 with the links above?
2)since mikrotik uses quectel modem , could you provide him with firmware updates so that he can use the update firmware function of RoS
-this would facilitate the 'update in an easier way without disassembling the modem and using USB adapters