wAP LTE kit modem missing after reboot

Hi there!
I have a problem with wAP LTE kit, after reboot lte is missing 9 times of 10. If shutdown device, wait 5-6 seconds and power on then lte is present at 8 times of 10.
I tried different versions of firmware (current 6.46.6), saw this topic http://forum.mikrotik.com/t/ltap-mini-series-lte-missing/137294/1 please see info below:

[admin@MikroTik] /system resource> /system resource usb print detail     
 0 device="1-0" vendor="Linux 3.3.5 ehci_hcd" name="RB400 EHCI" serial-number="rb400_usb" 
   vendor-id="0x1d6b" device-id="0x0002" speed="480" ports=1 usb-version=" 2.00" 

 1 device="1-1" vendor="MikroTik" name="R11e-LTE" serial-number="000000000000" vendor-id="0x2cd2" 
   device-id="0x0001" speed="480" usb-version=" 2.00" 

[admin@MikroTik] /system resource>> /system  resource irq print where users~"usb"    
Flags: ro - read-only 
 #    IRQ USERS                                                       CPU ACTIVE-CPU         COUNT
 0      3 usb1                                                       auto          0       435 567

[admin@MikroTik] /system resource>> /interface lte print      
Flags: X - disabled, R - running 
 0  R name="lte1" mtu=1480 mac-address=AC:FF:FF:00:00:00 apn-profiles=default 
      network-mode=gsm,3g,lte

[admin@MikroTik] >> /interface  lte  export         
# may/04/2020 09:39:57 by RouterOS 6.46.6
# software id = IBYY-5TZA
#
# model = RBwAPR-2nD
# serial number = B3850B90DFEE
/interface lte
set [ find ] mac-address=AC:FF:FF:00:00:00 name=lte1

[admin@MikroTik] >> /system routerboard modem print     
bad command name modem (line 1 column 21)

[admin@MikroTik] >> /interface  lte firmware-upgrade lte1          
  installed: MikroTik_CP_2.160.000_v015
     latest: MikroTik_CP_2.160.000_v015

If lte present after reboot it can work fine 14 and more days. I’m confused about the serial number.
Anyone have same problems? What other information is needed for the investigation?

Please enable logs, topic=lte.

we should grab logs from good boot, and bad boot.
In both scenatrio you should create a supout.rif and send both to support@mikrotik.com becasue your device not work as out-of-box as plug-and-play and that is strange behavior !.



/system logging add action=memory prefix=wAPR__LTE topics=lte

save logs to file by
log print file=log-with-proper-lte.txt
log print file=log-with-fail-lte.txt

Hi!
Unfortunately logs for bad boot does not contains any row with wAPR__LTE prefix. It’s look like a hardware problem. All information i’ll send to support.

Thanks for your answer!