I am seeing some instability with latest modem firmware now (16121.1034.00.01.01.05)
lte1 disappears from interfaces list after 5-10 mins and it’s simply gone.
In Resources however, there’s still a Fibocom FG621-EA visible.
Only resolution: reboot
Observed on 7.13.3 and 7.13.4
When turning on lte logging, it looks like the modem is trying and trying (sending AT commands) but nothing happens.
But it could also be the famous ‘modem boot loop’ observed in the past, where people were told to RMA the box.
(I can’t believe that - but read below)
I tried to downgrade modem firmware to 04 but it seems impossible.
File from here: https://upgrade.mikrotik.com/firmware/FG621-EA/16121.1034.00.01.01.04/image, it says “firmware successfully flashed” but it simply stays on 05, even after reboot.
Also tried various reset commands like
“AT+reset” → command not supported
“AT+RSTSET” → command not supported
The only command which works is “AT+CFUN=15” but it looks like this is just a soft reset (restart) of the modem.
Somehow it is all not working like described here https://help.mikrotik.com/docs/display/ROS/LTE
Netinstalled to 7.13.4 but of course this didn’t help - I just wanted to make sure and have a ‘clean’ device.
Default config - same issues.
I was reading on the forum somewhere that somebody solved this problem by simply upgrading to the latest BETA.
Gave it a try and upgraded 7.13.4 to 7.14.10 and voilà - indeed all okay, even overnight now.
I can’t see anything in the changelogs 7.13.4 → 7.14.10 that would (to my understanding) explain a different behavior here…
But I am willing to troubleshoot as it’s just a lab device.
To start off with - how to downgrade the modem firmware from local file?
Knowledge of the local file process is there - but box doesn’t take a lower version.
I wanted to re-flash 05 but it looks like a logic link like https://upgrade.mikrotik.com/firmware/FG621-EA/16121.1034.00.01.01.05/image doesn’t work, there’s no 05 image.
Wow, it was not me !!
I’m seeing the exact same problems after upgrade to latest modem firmware.
I saw it happening on latest 7.14beta, so I downgraded to 7.13.3.
Still saw it there.
Then I did a complete config reset and now it’s running for 10 minutes (wouldn’t last 5 before !!)
I also put in reference to this thread for support.
No clue how modem FW is to be downgraded.
LTE interface itself remains running but I see quite a bit of link down/up in log file (could be the flaky reception where it is located, I am aware of that. Will reposition the device to another place in the appt where I know it should remain stable).
Okay perfect.
I took mine home from office yesterday as well to have a location change.
Will be playing around a bit over the weekend now and if I find something, I will post it.
I doubt there will be news though as it looks like we’ve tried everything possible so far…
Reboot because of relocation aaaannndd … it’s there again.
07:48:59 lte,error lte1: no response for: AT E0 V1
..
07:49:19 lte,error lte1: no response for: AT E0 V1
…
07:49:39 lte,error lte1: no response for: AT E0 V1
I’m going back and forth with support now and they suggest it has something to do with APN settings.
But it worked just before the FW upgrade ??
That would be really coincidence that 2 users each in another country experience the EXACT same problem after a FW upgrade to the modem but for BOTH their LOCAL APN settings are to blame ? At the exact same timeframe ?
Hard to believe.
Ah, just got a message that there MAY be a FW crash happening. Now I need to find a way they can get direct access to that device.
Aha - I have 4 APN’s available and tested them all (IPv4/6, user/pw, cipher, ISP/manual, etc.)
Always the same issue.
Left it on default though for now.
Bring it online through eth1 and give them a lil BTH
Or they took it down pending investigation ?
After all, support did mention the log messages they saw where an indication of a firmware crash.
Don’t want that to go into the wild …
Not a real problem for me. This is a lab device. I mainly use it to test and in case of emergencies when I really REALLY have no wifi around (hotspot on cell phone also remains an option).
