RoS 7.18.2 (stable) rbm11g with modem em160quectel
I have to lock the bandwidth about every 12 hours because the isp halves the allowed bandwidth after 12 hours, but the scheduler does not work any more, either by writing the lock commands directly or by running the same script with this command /system scriptlockband
Running the script manually works everything works.
do you have any suggestions?
Anything in the logging?
Is the user frank admin ?
-no warning in the logs
-if the administrator is frank, the script works if I launch it from both the command line and webfig, I cannot programme it to do so automatically
I’m not 100% on why in this case… but does sound like a permissions problem.
The easy potential fix (or at least something to try) be to put that LTE code in a new /system/script and select “Do Not Require Permissions” & then in the /system/schedule use just the script name as “On Event”. The two-step action will avoid any permission checks.
15 ;;; vodaB3
name="vodaB3" owner="frank"
policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon
dont-require-permissions=yes last-started=2025-04-02 03:30:00
run-count=12 source=/interface lte at-chat lte1
input="at+qnwlock=\"common/4g\",1,1850,100"
add comment="Blocca banda LTE alle 3:00" interval=1d name=Nightly_LTE_Lock \
on-event=vodaB3 policy=\
ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon \
start-date=2025-03-25 start-time=03:30:00
I did what you suggested, I copied an extract of the script and that of the scheduler above.
Same problems, the script does not start at the set time, whereas it works when launched individually 
Weird. It does call it, since run-count is 12. I trust you know the AT command works at CLI, so IDK. My only guess was permissions since Mikrotik does mess them sometimes.
Perhaps a wait=yes on the LTE script. And/or adding more debug code to the script to get /log some AT command like /log [… input=“ATI”] just to confirm is sending something to modem. Similar you may want add more logging by adding “topics=lte” in /system/logging to see what’s going on around the schedule time.
I inserted the pause, activated logging for lte, rewrote the scheduler and script, always the same story, the scheduler starts and marks the values in the counter, but does not launch the script.
Lascia perdere gli script, metti direttamente nello scheduler questo, e guarda se funziona:
:execute "/interface lte at-chat [find where name=\"lte1\"] input=\"at+qnwlock=\\\"common/4g\\\",1,1850,100\""
He already tried putting in scheduler, I think. Perhaps wrapping in :execute might do something, IDK
If that doesn't work, look at the logs to see what's happening. It could be a script error, although the command looks right. Also possible the AT command is correct and but it's not doing what you think...so you may want to enable a topics=lte in /system/logging what is happening over AT in logs too.
@rextended I made a new entry in the scheduler and inserted your line, but it does not work.
@Ammo yes, I have enabled logging as you wrote but no AT command is launched; furthermore, all schedulers I have noticed no longer work, it must be a bug.
Yeah perhaps, it’s sounded weird from start. It might be worth trying the beta, or downgrading. Recent builds have good number of changes in LTE, which does have tendency to break something, somewhere.
not only the lte part, all the other scheduled scripts do not work either. but it is not possible that it is only me who has these problems.
Era un tentativo… non capisco perché non dovrebbe funzionare…
@rextended I don’t either, I have a lot of control scripts that no longer work when run from the scheduler, but do work when run manually or from the command line, I’ve read in other posts that the problem persists. I’m annoyed to downgrade from 7.18.2 (and I don’t even know if it’s possible)
RBM11G
[frank@RBM11g] > /user print
Columns: NAME, GROUP, LAST-LOGGED-IN, INACTIVITY-POLICY
# NAME GROUP LAST-LOGGED-IN INACTIVITY-POLICY
0 frank full 2025-04-06 15:12:23 none
[frank@RBM11g] > /user group print
0 name="read" policy=local,telnet,ssh,reboot,read,test,winbox,password,web,sniff,sensitive,api,romon,rest-api,!ftp,!write,!policy skin=default
1 name="write" policy=local,telnet,ssh,reboot,read,write,test,winbox,password,web,sniff,sensitive,api,romon,rest-api,!ftp,!policy skin=default
2 name="full" policy=local,telnet,ssh,ftp,reboot,read,write,policy,test,winbox,password,web,sniff,sensitive,api,romon,rest-api skin=default
[frank@RBM11g] >
Currently if I am forced to use v7 because the device does not support v6, for me the latest version of RouterOS that works is 7.16.2.
I switched to 7.18.1 and everything works again 
I'd recommend you still file a support ticket, otherwise it might still be there in future. And/or, perhaps try 7.19beta7 to see if it works there.
I'd also make sure all LTE and RouterBOARD firmware is updated, as mismatched versions is one sure fire way to have problems with LTE.
I forget how stable V6 is[/was]... if weren't for LTE MBIM support, I'd still be using V6 myself.
yes the firmware of the quectel modem is up to date from a few months ago and everything has always worked very well.
i had generated a supout.rif when i had problems with 7.18.2 i will forward it to mikrotik.
for now i have solved it by downgrading.
thank you all for the support
after a reboot, even with version 7.18.1 the scheduler no longer works with any scripts. I’m thinking it’s a problem with my rbm11 since no one on this forum complains of similar problems.