Hi,
We have a CHATEAU LTE6 ax.
When we start the router and at each restart, the sim is LOCKED.
We have just to deactivate the LTE interface and reactivate it and suddenly it works correctly without changing any settings.
Do you have a solution for LTE to start on its own?
Thank’s
An option I already used in the past is, using a smartphone, remove the requirement to have to enter the SIM PIN after boot.
But you may not want to do that with Chateau since in my case it was for an SXT LTE device hanging 7m above ground so not easy to reach.
However this process should simply work.
Is something found in the log right after startup ?
Can you try the latest beta 7.11b4 ? Maybe not 100% relevant but I do see a log entry related to LTE startup.
*) lte - improved initial interface startup time for SXT LTE 3-7;
Otherwise it might be best to send ticket to support so they can confirm (or not) if it is a bug.
Just ask Rex how to disable PIN without a phone…
but I think is not binded to the fact that SIM have the PIN enabled, but on the fact that when SIM reset happen, RouterOS do not send again the PIN…
http://forum.mikrotik.com/t/is-there-a-way-to-disable-the-pin-of-an-lte-sim-card-from-within-the-wap-lte-router/125274/5
Yeah removing the PIN code likely avoid the issue.
But this does seem like a bug. The PIN is set, and if disable/re-enabled it works with PIN code specified – only at startup something goes wrong it seems. I suppose it worth a try with the 7.11beta. I’d recommend adding a log for the “lte” topic in System>Logging. If you file a support case at help.mikrotik.com, generate a “Supout.rif” in winbox after the reboot and re-enabling LTE – by adding the lte logging that be in the supout.rif which likely have the needed clues as what’s going wrong.
Thanks for your help.
I just disabled the PIN and it works.
It must be a bug.
I will open a support ticket.
Thanks again.
Hello,
I have the same problem - I have open MikroTik support ticket since 08/Jun/2023 - SUP-118664: “We will notify when new modem firmware will be available with fix.”
No now firmware for LTE card FG621-EA (16121.1034.00.01.01.03) 
There is only workaround to have a scheduler script to diasbale and enable lte interface after reboot
Cheers.
this could help
use scheduler and set interval to 1 minute
:if ([/interface lte get lte1 running]=false) do={
:log error “LTE DOWN”;
/interface disable lte1
/delay 1s
/interface enable lte1
} else={
:log info “LTE UP”;
}
Thanks for the Script bro, it works great
It´s really incredible how this bug still running on new firmwares (December 2023 v7.12.1)… Sometimes I feel idiot buying MK items. I want to use the new router hap ax lite LTE6 for a backup, if the router gets rebooted because a power problem, my sistem is not running any more because “THE SIM IS BLOCKED”. Why? don´t know, need to disable LTE interface and turn on and is running again, Why? don´t know. By the way, the router is a 30 km from here
Thanks again for the script, it check the LTE interface, disable and re-enable it. But why is my new router not working normally, I don´t know?
Mk, are you here to help us???
Make a support ticket with clear description of problem and supout.rif file.
MT staff is not reading all posts here (some pass by but not all).
This is a user forum.
Another approach is use /system/watchdog with watch-address of 8.8.8.8 or something. This will generate supout.rif & reboot entire router if ping fails after the associated timeouts. While script above covers if the LTE interface isn’t running… watchdog prevents a wide array of potential issues. And if watchdog activates, you’d already have the supout.rif ready to report to Mikrotik to get to the bottom of why disable/enable is even needed.
But it could be the problem is originating from a too soon startup which causes the SIM PIN not to be set at which point watchdog might get stuck in a bootloop.
So a reset of LTE interface some seconds after boot, might still be in order then.
Or one will never get out of the loop.
Again: I complete circumvented the issue unlocking the SIM card I use (in the mean time it moved from SXT LTE to AX Lite LTE).
This is far from being a “beginner basics” problem. I have L41G-2axD&FG621-EA on my hands and it seems that other devices with FG621-EA are affected as well.
Now we have .04 firmware but this does not solve the problem. It might be out of hands of Mikrotik as they do not make the firmware for a modem.
P. S. Mikrotik offered a scheduler script as workaround for now…
Mikrotik support gave me following scheduler script, that can be used as a workarround.
/system scheduler remove [find name=refresh_locked_SIM]
/system scheduler add name=refresh_locked_SIM start-time=startup interval=10s on-event="\
:local lteInterfaces [/interface print as-value where type=lte and disabled=no]\r\
\n:foreach lte in=\$lteInterfaces do={\r\
\n :if ([/interface/lte/monitor (\$lte->\"name\") as-value once]->\"status\"=\"sim locked\") do={\r\
\n /interface lte set (\$lte->\"name\") disabled=yes\r\
\n :delay 3s\r\
\n /interface lte set (\$lte->\"name\") disabled=no\r\
\n }\r\
\n }\r\
\n"
There’s more to it…
It looks like SIM gets locked even when LTE interfase is manually disabled before reboot and then manually enabled first time after reboot.
This implies that it might not be related to reboot process only.
Thanks for sending the script to Mikrotik support, it works… but it doesn’t seem very clean to me… I’m looking for another solution
It looks like script is checking if lte interface has status “sim locked”.
If this status is present then script disables lte interface, waits for 3 seconds and enables lte interface again. If “sim locked” status is not present, then script does not do anything. Script will run again after scheduled time (which seems to be 10 seconds in this case).
I don’t have an FG621-EA modem (e.g. most recent LTE6 devices) nor SIM locking enabled to know. But…I saw this in the release notes for 7.13.3 that seem to indicated this may problem may be fixed:
(edit: cut-and-paste error, see below)
This line might be more relevant 
*) lte - improved SIM PIN unlock event handling for MBIM FG621-EA;
Yes, ROS 7.13.3 really works. Comtrya 