I’m running v7b8 with a Sierra 7455 LTE card in MBIM mode without too much trouble, things are working as expected. However I would like to be able to monitor cellular information using commands like “at!gstatus?”
However, the command "/interface lte at-chat lte1 input=“at!gstatus?” returns “failure: unsupported”
Is there another method to perform this action?
At this time the only way I’ve found to issue such commands is to move the modem out of MBIM mode.
In my opinion OS7 has great potential as far as USB modems go.
I have tried both a Quectel RM500Q and a Sierra Wireless EM9190 (both are 5G modems) and both have been immediately recognized and work well.
This lack of at-chat capability is serious because when using such modems there is a lot of tuning needed before committing to a configuration, and having
to move the modem out of the mikrotik device and into a cheap chinese router (which can talk to the modem just fine) is a real nuisance.
Please, PLEASE Mikrotik, fix the at-chat for modems in MBIM mode and you’ll be rewarded with a lot of new customers.
I am still looking forward for a solution to this issue, which prevents me from using a non quectel modem on my RB3011.
Support replied to change the lte mode to serial and check the serial ports that should show up under /port, to find which one will work with AT command,
however the usb port that appears when I do is in inactive state:
[admin@MikroTik] > /port/print
Flags: I - INACTIVE
Columns: NAME, CHANNELS, USED-BY, BAUD-RATE
# NAME C USED-BY BAUD
0 serial0 1 Serial Console auto
1 I usb2 4 9600
[admin@MikroTik] > /system serial-terminal port=usb2 channel=0
failure: port is inactive
[admin@MikroTik] > /system serial-terminal port=usb2 channel=1
failure: port is inactive
[admin@MikroTik] > /system serial-terminal port=usb2 channel=2
failure: port is inactive
[admin@MikroTik] > /system serial-terminal port=usb2 channel=3
failure: port is inactive
I did not test on the RB3011 (because that is running my entire home) but on a spare HEX S that I have.
Without a working at-chat command there is no way to use a MBIM modem with RouterOS.
no response from MikroTik ? You can share that case with me ? At support portal you have a share button, use info@sibex.it .
Some person must isolate usb3.0 pings, enable usb3.0 via at and then communication start work.
I not have experience with sierra and not use that cards.
One note, you used to need to escape “?” like ?. But in rc1 and rc2, at-chat has worked with Siera MC7455 in LTE at-chat no problem. I did have an issue MC7354 in PPP mode not liking at-chat (tried to use that switch it to MBIM using USBCOMP) in beta6 or rc1.
In fact, it now pretty easy use scripting “functions” to issue the AT commands with at-chat and the Sierra etc modems. If you put it into a scheduler script, with an interval, it can poll the modem and store the detailed LTE info. See below:
In theory, one could use :toarray and the new MQTT function (in IOT v7.1 extra package) to store persist these values in something like AWS. That gets more complex, but seemingly possible.
So there may be bug in the at-chat hanging… I’ve only seen that with the PPP at-chat. But have to say this is night and day with the Sierra modems from v6 where PPP mode only has 1 AT channel, so you can’t even get RSSI with the MC7354/MC7455 modems while there running.
[admin@Mikrotik] > /interface/lte/at-chat lte1 input="AT+QCAINFO"
output: +QCAINFO: "pcc",3300,50,"LTE BAND 7",1,371,-105,-7,-81,16
+QCAINFO: "scc",1301,100,"LTE BAND 3",1,449,-101,-8,-83,6
OK
But most of times it stucks:
[admin@Mikrotik] > /interface/lte/at-chat lte1 input="AT+QCAINFO"
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
And I have to wait or Ctrl+C and try again and again till it works fine once.
You can try to add a “wait=no” to the commands. The default (wait=yes) waits for an “OK” to be received, but it can timeout.
If you add adding logging for topics=lte,!packet, the log may show the results too.
Alternatively, you may be able to use something like “/system/serial-terminal usb1 channel=1” to get to directly to the AT serial line of the modem (& adjust port and channel as needed in the command)
I have try “wait=no”, but it didn’t fix the problem, stucks as well.
And something like “/system/serial-terminal usb1 channel=1” I found correct usb port and tried different channels, but it didn’t answer for AT command, no OK response.
Logging lte didn’t show my stucked request, like I didn’t send it at all.