Asus 4G-AX56 not yet supported

Well, I tried those commands first having this modem in "disabled" state.

Then I enabled it using "mmcli -e -m 0" and drove those commands again and noticed differencies. It did not help. Putting those different settings to the same position as they are while modem is "registered" did not change anything.

Giving it AT+GCAP gives this list. I suppose it's a list of all commands this model supports:

+GCAP: AT,D,Q,V,A,H,Z,E,and_F,and_D,and_C,and_W,W,and_K,+CPAS,+CPIN,
+CBC,+CLIP,+CLIR,+CCFC,+CCWA,+CREG,+CRC,+VTS,+CHLD,+CLCC,+COPS,
+CSSN,+SIND,+SBCM,+CSQ,+CESQ,+CIMI,+CGMI,+CGMM,+CGSN,+CGMR,
+CMEE,+CSCS,+SMUX,+CPOF,S0,S2,S3,S4,S5,S6,S7,S8,S10,+CGDCONT,
+CGPCO,+CGQREQ,+CGQMIN,+CGATT,+CGACT,+CGPADDR,+CGCMOD,
+CGDATA,+CGAUTO,+CGANS,+CGCLASS,+CGEREP,+CGREG,+CGSMS,+SDATACONF,
+SDATASTART,+SDATASEND,+SSTRSEND,+SDATAREAD,+SDATARXMD,+CSMS,+CSDH,
+CRES,+CPMS,+CMGF,+CMGR,+CMGL,+CMGD,+CMGS,+CMSS,+CSMP,+CMGC,+CMGW,
+CSCA,+CSAS,+SMSC,+SUSS,+CSCB,+CNMI,+CPBR,+CPBF,+CPBW,+CPBP,+CPBN,
+CNUM,+SSMP,+CSVM,+CPBS,+COLP,+COLR,+CPUC,+CUSD,+CCUG,+CAOC,+CACM,
+STSF,+STIN,+STGR,+CAMM,+CCLK,+XX,+VTD,+CCID,+VGR,+CRSL,+CMUT,+VGT,
+SEQT,+SSEA,+SBAND,+SDTMF,+ECHO,+CLCK,+CPWD,+SSAM,+SSAP,+SADM,+CICB,
+CFUN,+IPR,+CIND,+CCED,+STONE,+CRMP,+SCDM,+SAC,+SSST,+SATT,+RFNVCHKS,
+S32K,+STMF,+CEER,+CR,+SAUTOATT,+SGPRSDATA,+SDCP,+SRWD,+SNVM,+SBOOT,
+SMGF,+SMGV,+SMGD,+SDMUT,+SLOG,+SUPS,+SSGF,+SSGS,+CPLS,+CPOL,xor_SYSINFO,
+CBST,+CMOD,DL,+CHUP,+CGDSCONT,+CGEQREQ,+CGEQMIN,
+CGTFT,+CMUX,xor_HVER,xor_SYSCONFIG,xor_SPN,+CSTA,xor_SCPBR,xor_SCPBW,
+ARMLOG,+SECMODE,+PSCUSTOMVER,xor_CARDMODE,+CRSM,+CNMA,+STED,
+CHUPVT,+TRACE,+OFF,+RESET,+CGEQNEG,+ECMMB,+ECMMBSTS,+ECMMBEER,
+EUICC,+ESQOPT,+CMMS,+ECPIN2,+ECIND,+EVTS,+CCWE,+BOOT,+CLVL,+CMER,
STAR_SPNTRG,+GMM,+FCLASS,+GCI,xor_DSCI,+PSRABR,+RRDMPARAM,
+TDMEASSWTH,+TRRPARAM,xor_SPEDGE,+L1PARAM,+ERGA,+ERTCA,+DMPARAMRESET,
+SMTIMER,+GRRTDNCELL,+GRRFDDNCELL,+NVOPERATE,
+SCPFRE,+PCCOTDCELL,STAR_SPPRAS,STAR_SPCSCN,STAR_SPENGI,STAR_SP3GPBR,
STAR_SPVTCS,+SIPCONFIG,xor_MBAU,xor_MBCELLID,+SFUN,+SADC,+CUFP,+CTZR,
+SMMSWAP,xor_FTDHO,xor_CURC,+WRRCPARAM,+SGMR,+TPCN,STAR_FDY,
+2GNCELL,+Q2GNCELL,+3GNCELL,+Q3GNCELL,+ALS,+SIPMODE,+NVSYNLINK,+SGFD,
+CSIM,+CCHC,+CCHO,+CGLA,+XMODEMACT,+CAGPS,+AGPSMR,+AGPSMER,
+SECUREBOOT,+SADMDSP,+SSYS,+SMS,+CPBCAPA,+TFSTAT,+XVOLLEV,+CVMOD,
+CUSATR,+CUSATW,+EMGONLYMODE,+GCAP,+GMI,+GSN,+BGLTEPLMN,+CEREG,
+CGCONTRDP,+CGSCONTRDP,+CGTFTRDP,+CGEQOS,+CGEQOSRDP,+ERSRP,
+CEMODE,+CSCON,+SCSFB,+CSSSFB,+AUTPWRON,+CPNER,+CSSAC,+RSIMRSP,
+VIRTUALSIMINIT,+COPSCSG,+LTESETRSRP,+LTEBGTIMER,+CEUS,+CGAUTH,
+CUSATT,+CUSATE,+CEVDP,+CAVIMS,+CMTLRA,+CGPIAF,+CASIMS,+CMMIVT,+CNAP,
+CPINR,+CPOS,+CTFR,+CPOSPARAM,+CMTLR,+CPOSR,xor_CMDVER,xor_RFSW,
+CNEM,+CEN,+ENGDISPLAY,+RRTMPARAM,+GRRLTEFREQ,+INSTANCEID,+IMEIURL,
+IMPU,+IMPI,+DOMAIN,+PCSCF,+IMSEN,+CIREG,+CLSSPDT,+CMCCS,+CLCCS,
+EMBMSIM,+CCMMD,+ISIM,+CMOLR,+MODECHAN,+FDDWRED,+PSISMSC,+CIREP,
+CISRVCC,+BSF,+XCAPRTURI,+CONFURI,+CCFCU,+APPSAUTHTYPE,+CGU,
+KEYSHORT,+FACTORST,+HEADINFO,+SYSSLEEP,+MAXPOWER,+FCBTTEST,
+FCMPTEST,+FCEPTEST,+TEMPTEST,+LOOPTEST,+SIMDETEC,+EMEMTEST,
+BATTTEST,+MSLSECUR,+IMEITEST,+AKSEEDNO,+CALIDATE,+LVOFLOCK,+DETALOCK,
+SERIALNO,+RSTVERIF,+LOCKREAD,+KSTRINGB,+SETTESTNV,+GETTESTNV,
+ARMLOGEVT,+LOGERASE,+SETFDATA,+GETFDATA,+GETFULLTESTNV,
+GETFULLHISTNV,+SETFULLFDATA,+GETFULLFDATA,+READRSSI,+BANSELCT,+SALRM,
+DTIME,+CDAT,+RTCCTEST,+VERSNAME,+CALLCONN,+DBGSCRN,+FACTOLOG,
+IMSITEST,+CDU,+XCAPIP,xor_SPDATAENCRYPT,xor_SPSIMLOCKDATAWRITE,
xor_SPSIMLOCKIMEI,
xor_SPHUK,xor_SPFACAUTHPUBKEY,xor_SPIDENTIFYSTART,xor_SPIDENTIFYEND,
+LTEPOWER,mod_MBMSCMD,mod_MBMSEV,+CEMBMSCNT,+CEMBMSCFG,+CDEFMP,
+VOWIFIEN,+IMSHO,+IMSHORST,+IMSHOWFINF,+IMSHOCALLEND,+VOWFREG,
+IMSWFATT,+IMSHODATAROUTER,+WIFIPARAM,+IMSCOUNTCFG,+CRLA,
+WRRDMPARAM,+VOWIFCALLINF,+COPN,+VOWIFIPCSCF,+MBMSEREG,+CSCM,
+IMSHONWINF,+PRENWINF,xor_LVDSDUMP,+ZCGMR,+ZRSSI,+ZPAS,+ZDON,
+ZCELLINFO,+HALOINFO,+GSMRXLEVELDBM,+WCDMARXLEVELDBM,
+LTERXLEVELDBM,+SMMFULL,+GTCGMR,+MHUP,+GTVTS,+GTCCINFO,+CMGLEX,
+NVRW,+COPNEX,+GTDTMF,+SMSREADY,+CALLBREAK,+GTSIMCNT,+CGCONTRDPEX,
+DUMPEN,+GTSDMUT,+GTRATPRIO,+GTBANDWIDTH,+PDPRETRY,+GTROAMST,
+GTCAINFO,+GTENMEASURE,+GTCELLLOCK,+GTPLMNLOCK,+GTMCSCQI,
+GTDATASTAT,+GTMTUEN,+GTANTINFO,+GTBWLIMIT,+ADVINFO,+GTDATATHROT

Any idea what to try next?

Or is there something else? Is it Luci that needs some kind of resetting/refreshing and not the modem?

What commands refresh Cellular Network WebUI?

I don“t think ModemManager is the best choice if your modem does not support QMI or MBIM. You have to use AT commands. The challenge with AT commands is that it“s modem specific. Maybe you can create a plugin to MM and add support for the FG621 modem.
I have created an AT command script for the Fibocom FM350 modem, and a LuCI app, so maybe we can create one for the FG621 as well. Then LuCI will be updated. A script for the RSSI LEDs would be easy to add.

Or if you just want to activate the RSSI LEDs you can create a script that reads the signal quality with AT+CSQ and turns on the LED according to the RSSI level.

Response to AT+CSQ:

+CSQ: <rssi>,<ber>
<rssi>: integer type
0 -113 dBm or less
1 -111 dBm
2...30 -109... 53 dBm
31 -51 dBm or greater
99 not known or not detectable

<ber>: integer type; channel bit error rate (in percent)
0...7 as RXQUAL values in the table in 3GPP TS 45.008 subclause 8.2.4
99 not known or not detectable

It responds this, but gives only:

AT+CSQ

+CSQ: 23,99

but how about this:

AT+ZRSSI?

+ZRSSI: -97,-10,0,-5

I have been trying to find how to update modem FW. It should have FOTA upgrade, but I have not found the right command.

34: ECM+AT+DIAG+LOG
35: ECM+AT+DIAG+LOG+ADB
36: NCM+AT+MODEM+DIAG+LOG
37: NCM+AT+MODEM+DIAG+LOG+ADB
38: RNDIS+AT+MODEM+DIAG+LOG
39: RNDIS+AT+MODEM+DIAG+LOG+ADB

Regarding FOTA you can try:

AT+GTOTA=?

+GTOTA=<type>,<"url">[,<"filenamefilename">,< "usernameusername">,< "passwordassword">]

You need to have access to a server with the firmware.

FW is available on Mikrotik server, but do you know what the "type" setting should be?

+GTOTA=<type>,<"url">[,<"filename">,< "username">,< "password">]

<type>: integer type and range s from 0-1.
  0: FOTA upgrade through HTTP
  1: FOTA upgrade through FTP
<"url">: string type; Address of HTTP or FTP server.
<"filename">: string type; The file name of OTA package.
<"username">: string type; User name for FTP server.
<"password">: string type; FTP password for <"username">.

When <type> is 0, parameters <"filename">, <"username">, and <"password"> can’t be used.
When <type> is 1, parameters <"filename">, <"username">, and <"password"> must be given given.

When using HTTP, the file name and path of the OTA package must be included in in <"url">.
When using FTP, <"url"> is the address of FTP server, while filename is given by parameter <"filename">.

Do you have the url to Mikrotik server?

You can find links to those FW files here:
https://forum.mikrotik.com/viewtopic.php?t=204276

At least link;
https://upgrade.mikrotik.com/firmware/FG621-EA/16121.1034.00.01.01.03/image
seems to work fine.

Latest .05 version seems to have some trouble and is not recommended to use by Mikrotik users.

Do you have one of these devices yourselves?

No, I don“t have any Fibocom FG621. I“m just curious how MikroTik manage the different FWs and how FOTA is working.

Was it possible to upgrade your modem with AT+GTOTA?

AT+GTOTA=0,"https://upgrade.mikrotik.com/firmware/FG621-EA/16121.1034.00.01.01.03/image"

If you run

wget https://upgrade.mikrotik.com/firmware/FG621-EA/16121.1034.00.01.01.03/latest

or

wget https://upgrade.mikrotik.com/firmware/FG621-EA/16121.1034.00.01.01.04/latest

you get file latest in response.
Ii contains 16121.1034.00.01.01.04 in both cases, so it looks like MikroTik recommend 16121.1034.00.01.01.04.

It gives immediatelly message "ERROR"

Maybe the FW packages on MikroTiks server are not FOTA packages.
It looks like MikroTik has a special tool to perform the FW upgrade of the modem.

Propably just that.

There seems to be a shell script in that package but it does not tell is it run by modem processor or host device.

Just FYI:

This device has a nice culprint. Default boot environment setting end up in CRC error. Bootloader uses then default settings and it boots OK.

There are some other settings in environment and now if OpenWrt is booted and then fw_setenv is used to change something, it fixes the CRC error.

Unfortunatelly most of the settings are incorrect. It does not boot again.

Those settings don't bring up possibility to tftp boot it. Neither does it allow Asus recovery to work correct.

So - it's better to have some way to put correct boot environment in it to make it boot again.

Here they are if someone needs it. First take everythin away and then set these back:

setenv baudrate 115200
setenv bootcmd mtkautoboot
setenv bootdelay 2
setenv bootmenu_0 "Startup system (Default)=tftpd"
setenv bootmenu_1 "Upgrade firmware=mtkupgrade fw"
setenv bootmenu_2 "Upgrade bootloader=mtkupgrade bl"
setenv bootmenu_3 "Upgrade bootloader (advanced mode)=mtkupgrade bladv"
setenv bootmenu_4 "Load image=mtkload"
setenv fdtcontroladdr 8ffe3610
setenv ipaddr 192.168.1.1
setenv mtdids "nmbm0=nmbm0"
setenv mtdparts "mtdparts=nmbm0:896k(u-boot),1024k(u-boot-env),1024k(factory),1024k(factory2),-(firmware)"
setenv netmask 255.255.255.0
setenv serverip 192.168.1.2
setenv stderr uartlite0@1e000c00
setenv stdin uartlite0@1e000c00
setenv stdout uartlite0@1e000c00

I got the modem properly up now. There was some part of ModemManager missing. Now it's normally enabled after booting.

AT+CESQ gives now this:

+CESQ: 99,99,255,255,22,44

AT+CSQ:

+CSQ: 23,99

and AT+ZRSSI?:

+ZRSSI: -95,-9,0,5

can those values be used to drive RSSI-leds?

Now everything else works but those LTE related leds.

There are two kinds of them. One for indicating if WAN/internet is available and an other to tell if connection strength is low/medium/high.

Can you help how to do these?

Hi
Has anyone used the TFTP method, via U-Boot, to roll back to OEM sw?

I tested it some months ago and TFTP method did not work using original FW. Asus rescue is working.

1 Like

Does anybody know how to reconnect this Fibocom modem if it drops out?

I have a script to detect missing connection using mmcli and I can reboot the whole router if it happens, but is there any more delicated means to just bring modem up again without rebooting whole device?

Resetting modem using

echo -e "AT+CFUN=15\r\n" > /dev/ttyUSB0

or

echo -e "at+cfun=1,1\r\n" > /dev/ttyUSB0

does not end up with connection. It seems to need something more.

mmcli -m -e

ends up in "registered" state and it does get signal strength and everythin. Still not connected.

What's the magic command to give? It uses cdc_ether protocol if it matters.

How did you manage to tear down the router?

I can find one screw but it's not enough to open it.

Just take the sticker off. You'll find it all bellow it. There are no more "hidden" screws, but the case is quite tight to open.

1 Like

I have created a device page for this nice router.

1 Like