The problem:
Brand new hAp ax lite LTE6 lost LTE1 interface after a few days of work.
Tried:
Waiting for:
Question:
Does anybody solved such problem without replacing device?
Right now I have 5 of them active on different sites and I didn’t encounter this problem… I hope it’s not some kind of serial defect…
Modem is soldered to the board so in case of modem fault easiest solution would be to replace whole unit…
At the risk of stating the obvious…
Already tried to just create that lte interface again ?
I managed once on an sxt lte to remove that interface by accident ( wanted to disable, hit the wrong button).
It came right back after create.
Very nervous 5 minutes, I can tell you…
Does it show up in /ports (System>Ports)? Is there a “ppp-out1” interface instead of “lte1”?
Using the “/interface lte settings set mode=serial”, rebooting, you can see if that gets up a ppp-out1. That not want you’d want to use (it be limited to 25Mbs), but if it shows up… it’s not likely the hardware. And switch back to “auto”, but the transition get it “lte1” to be picked up..
I could answer the question when the device will be on my desk as “device has to be sent back to me”.
Strange but somehow I have no remote access to it 
BTW … ordered new one …intresting how long it will survive?
Fair enough. It’s tough when remote…
More saying I’m betting a RouterOS issue, than hardware. Don’t have one of these… But all modems have subtle different messages/times & the hAPaxLite-LTE6 uses a Fibocom modem, instead of the Quectel they used for a bit… My general advice is to upgrade it to latest RouterOS & associated firmware on the new one.
When I’ve seen problems with LTE interface detection (e.g. missing), it’s generally been some firmware mismatch. And even then physically depowering the device for >10 seconds generally causes the modem to actually shutdown sometimes gets them back. e.g. a /system/reboot may not “reboot” the modem.
The log says
LTE1: no response for: AT E0 V1
Lots of posts on Forum eith the same problem. Same SIM in the new device works without problems.
Any idea?
No usb2 modem, no serial port, usb1 removed for test, recreated by router after restart.
Netinstall did not help, even worse … serial0 and usb2 flaps 
And where is wifi interface ??
package wifi2 not installed .. no need at this moment
Wild suggestion then…
What if you do install it and then reboot ?
Or reset config ?
No change … reset, upgrade, downgrade, reset, power on, power off .. so many tries … tired trying.
LTE is missing … Fibocom USB device is on a list of devices then vanish … resurrects … USB2 flaps … no interface no matter what combination of above steps is taken.
Time for warranty.
Fair enough. I’d still grab a supout.rif, ideally after a reboot with “debug” topic enabled, and send that to Mikrotik. I would have though netinstall or even just /system/reset-configuration would have gotten this working.
While removing wifiwave2 driver should be fine – that might be involved here. Easy to imagine that Mikrotik never tested what happens if you removed the wifiwave2 driver. 
The logs kinda make sense since defconf waits ~30 seconds looking for wireless interfaces and, if none, it does a log and /quit. But that failure doesn’t explain not finding LTE, since the defconf does not create the LTE interface or do anything with LTE.
Actually it does do “something” but creating them, that it doesn’t do.
(e.g. it does add it to WAN interface list, looked it up in default config for AX Lite LTE 
)
True. And, firewall be missing too since wireless check happens early, but failure should actually get you a blank config anyway (@holvoetn, see “revert” part at bottom of /system/default-configuration). I have every faith that @BartoszP can build a config if that were the problem here . It’s the “no response for: AT E0 V1” that’s seems like Mikrotik bug.
Unforentently the “AT E0 V1” error is kinda generic — it’s just the first command it tries, so that alone doesn’t tell you much about the nature of the problem (e.g. could be modem hung, modem not in right USB mode, routeros not using right channel, and/or actual hardware failure) – it just tell you to look at /port and /system/resource to see if it showing up as serial device & seen on USB bus at least.
If it’s showing up in /ports and has channels, this is almost certainly a RouterOS bug*. The “AT E0 V1” is also curious since I think that’s a Quectel command (but not 100% it’s ONLY quectel), but the hAPaxLiteLTE6 has a fibocom modem.
* which may have been fixed in latest fw/ros/boot software … but @BartoszP already using 7.12rc1 “testing”…
It “might” be a bug in the system thinking it needs to speak “Quectel” wheres it should speak “Fibocom” for that device.
@BartoszP:
what’s factory SW version on that device ? (mine is powered down, otherwise I need to power it up again to see 
)
You might try to netinstall that specific version again ?
Just to see ?
I agree supout.rif might still be interesting for support.
Once you sent it back, no way anymore to find back what caused the problem.
OTOH, just this morning I upgraded my device to 7.12rc1. No issues found for the time it was powered on.
So it’s certainly not a generic problem.
Well, the command isn’t returning anything that’s the bigger problem. e.g. modem would report error back on the usb serial channel.
FWIW /system/serial-terminal usb2 channel=1 (or channel=0, or “usb1”), let get you the modem’s AT command interface. If that comes up and “ATI” does reports something with “OK”, it’s almost certainly not hardware.
@holvoetn, on your hAPaxLite is the modem at “usb1” or “usb2” in the port list? e.g. @BartoszP is showing “usb2”.
Darn, now I do need to power it on again 
USB2
Serial in red, usb2 in black since interface is operational.