Section: User Commands (8)
Updated: October 2012
mmcli - Control and monitor the ModemManager
ModemManager is a DBus-powered Linux daemon which provides a unified high level API for communicating with (mobile broadband) modems. It acts as a standard RIL (Radio Interface Layer) and may be used by different connection managers, like NetworkManager. Thanks to the built-in plugin architecture, ModemManager talks to very different kinds of modems with very different kinds of ports. In addition to the standard AT serial ports, Qualcomm-based QCDM and QMI ports are also supported.
The default mode is ERR.
All options below take a PATH or INDEX argument. If no action is provided, the default information about the modem, bearer, etc. is shown instead.
The PATH and INDEX are created automatically when the modem is plugged in. They can be found using mmcli -L. This produces something like (for modems only):
In this case, the INDEX is 4 and the PATH is the entire string above.
However, for the bearers, SIMs and SMS cases, the PATH is slightly different. The Modem is replaced with the object name in use, like Bearer. For example:
All of the modem options below make use of the --modem or -m switch to specify the modem to act on.
Some operations require a MODE. MODE can be any combination of the modes actually supported by the modem. In the perfect case, the following are possible:
'2G' - 2G technologies, e.g. EDGE, CDMA1x '3G' - 3G technologies, e.g. HSPA, EV-DO '4G' - 4G technologies, e.g. LTE 'ANY' - for all supported modes.
This powers the antenna, starts the automatic registration process and in general prepares the modem to be connected.
This disconnects the existing connection(s) for the modem and puts it into a low power mode.
The CODE provided is vendor specific. Without the correct vendor code, it's unlikely this operation will succeed. This is not a common user action.
An example would be: 'egsm|dcs|pcs|g850' to select all the GSM frequency bands.
The 3rd Generation Partnership Project (3GPP) is a collaboration between groups of telecommunications associations. These options pertain to devices which support 3GPP.
Included are options to control USSD (Unstructured Supplementary Service Data) sessions.
All of the 3GPP options below make use of the --modem or -m switch to specify the modem to act on.
This registers with the default network(s) specified by the modem,
For example, COMMAND could be '*101#' to give your current pre-pay balance.
All CDMA (Code Division Multiple Access) options require the --modem or -m option.
All simple options must be used with --modem or -m.
These options detail how to discover your location using Global Positioning System (GPS) or directly from your mobile network infrastructure (either 3GPP or 3GPP2).
All location options must be used with --modem or -m.
All messaging options must be used with --modem or -m.
Number to which the message is addressed.:
All time operations require the --modem or -m option.
All firmware options require the --modem or -m option.
The ID provided is a UNIQUE identifier for the firmware.
All OMA options require the --modem or -m option.
The given session type must be one of:
All bearer options require the --bearer or -b option.
All SMS options require the --sms or -s option.
You'll need first to know which the proper path/index is for the SIM in your modem:
$ mmcli -m 0 | grep SIM SIM | path: '/org/freedesktop/ModemManager1/SIM/0'
And after that, you can just use the SIM index:
$ mmcli -i 0 --pin=1234 successfully sent PIN code to the SIM
You can launch the simple connection process like:
$ mmcli -m 0 --simple-connect="pin=1234,apn=internet" successfully connected the modem
Then, you can disconnect it like:
$ mmcli -m 0 --simple-disconnect successfully disconnected all bearers in the modem
Scanning for 3GPP networks may really take a long time, so a specific timeout must be given:
$ mmcli -m 0 --3gpp-scan --timeout=300 Found 4 networks: 21404 - Yoigo (umts, available) 21407 - Movistar (umts, current) 21401 - vodafone ES (umts, forbidden) 21403 - Orange (umts, forbidden)
Using the “sm” (SIM), you can do this using:
$ mmcli -m 0 --messaging-create-sms="text='Hello world',number='+1234567890'" Successfully created new SMS: /org/freedesktop/ModemManager1/SMS/21 (unknown) $ sudo mmcli -s 21 --store-in-storage="sm" successfully stored the SMS $ sudo mmcli -s 21 SMS '/org/freedesktop/ModemManager1/SMS/21' ----------------------------------- Content | number: '+1234567890' | text: 'Hello world' ----------------------------------- Properties | PDU type: 'submit' | state: 'stored' | smsc: 'unknown' | validity: '0' | class: '0' | storage: 'sm' | delivery report: 'not requested' | message reference: '0' $ sudo mmcli -m 0 --messaging-status /org/freedesktop/ModemManager1/Modem/0 ---------------------------- Messaging | supported storages: 'sm, me' | default storage: 'me'
As you can see below, the important part is the --messaging-create-sms-with-data and the PATH provided.
$ sudo mmcli -m 0 \ --messaging-create-sms="number='+1234567890'" \ --messaging-create-sms-with-data=/path/to/your/file Successfully created new SMS: /org/freedesktop/ModemManager1/SMS/22 (unknown) $ sudo mmcli -s 22 --send successfully sent the SMS
When the receiver gets all the parts of the message, they can now recover the sent file with another mmcli command in their ModemManager setup:
$> sudo mmcli -m 0 --messaging-list-sms Found 1 SMS messages: /org/freedesktop/ModemManager1/SMS/0 (received) $> sudo mmcli -s 0 --create-file-with-data=/path/to/the/output/file
You first need to check whether the modem has GPS-specific location capabilities. Note that we’ll assume the modem is exposed as index 0; if you have more than one modem, just use --list-modems to check the proper modem index:
$ mmcli -m 0 --location-status /org/freedesktop/ModemManager1/Modem/0 ---------------------------- Location | capabilities: '3gpp-lac-ci, gps-raw, gps-nmea' | enabled: 'none' | signals: 'no'
The output says that the modem supports 3GPP Location area code/Cell ID, GPS raw and GPS-NMEA location sources. None is enabled yet, as we didn’t enable the modem, which we can do issuing:
$ sudo mmcli -m 0 --enable successfully enabled the modem $ mmcli -m 0 --location-status /org/freedesktop/ModemManager1/Modem/0 ---------------------------- Location | capabilities: '3gpp-lac-ci, gps-raw, gps-nmea' | enabled: '3gpp-lac-ci' | signals: 'no'
We can enable the RAW and NMEA GPS location sources using:
$ sudo mmcli -m 0 \ --location-enable-gps-raw \ --location-enable-gps-nmea successfully setup location gathering
If we do check again the status, we’ll see the GPS-specific locations are enabled:
$ mmcli -m 0 --location-status /org/freedesktop/ModemManager1/Modem/0 ---------------------------- Location | capabilities: '3gpp-lac-ci, gps-raw, gps-nmea' | enabled: '3gpp-lac-ci, gps-raw, gps-nmea' | signals: 'no'
You can query location source specific information with --location-get-3gpp, --location-get-gps-nmea and --location-get-gps-raw; but also for all at the same time:
$ sudo mmcli -m 0 --location-get /org/freedesktop/ModemManager1/Modem/0 ------------------------- 3GPP location | Mobile country code: '214' | Mobile network code: '3' | Location area code: '21071' | Cell ID: '7033737' ------------------------- GPS NMEA traces | $GPGGA,,,,,,0,,,,,,,,*66 | $GPRMC,,V,,,,,,,,,,N*53 | $GPGSA,A,1,,,,,,,,,,,,,,,*1E | $GPGSV,4,1,16,24,,,,29,,,,05,,,,18,,,*7A | $GPGSV,4,2,16,22,,,,14,,,,11,,,,17,,,*7B | $GPGSV,4,3,16,03,,,,12,,,,30,,,,13,,,*78 | $GPGSV,4,4,16,23,,,,15,,,,27,,,,07,,,*79 | $GPVTG,,T,,M,,N,,K,N*2C ------------------------- Raw GPS | Not available ------------------------- CDMA BS | Not available
An example of RAW GPS location information:
$ sudo mmcli -m 0 --location-get-gps-raw /org/freedesktop/ModemManager1/Modem/0 ------------------------- Raw GPS | UTC time: '155142.2' | Longitude: '-3.513941' | Latitude: '40.502603' | Altitude: '18.000000'
Martyn Russell <email@example.com>
Tutoriais de Tecnologia Web