AT commands via MM

Martin Anderseck Martin.Anderseck at ni.com
Thu Nov 14 00:25:57 PST 2013


Aleksander Morgado wrote on 14.11.2013 08:58:07:

> Not enabling the Command() method in the Modem interface when not in
> --debug is mainly to prevent the user from playing with the AT port in a
> manner which would be incompatible with MM's behaviour, and to avoid
> users putting 'quirks' themselves where a proper fix would be to fix the
> plugin in use. The AT command. The Command() interface is currently just
> used for debugging purposes (e.g. when testing out new commands to
> implement in plugins, so that there's no need to run them in minicom).

Okay, I totally get your point.

> Do you have a use case where it would be useful to have it enabled?

I still struggle with IPv6 and simple-connect [1]. I have to admit that 
I'm not deep enough into QMI to completely understand what is going on 
behind the scenes but at least with +cgdcont I'm able to connect to my v6 
apn. Therefore sending an AT command seemed a good way to do that. But of 
course that totally fits your explanation "users putting 'quirks' 
themselves where a proper fix would be to fix the plugin in use". This is 
the main purpose for me to use the AT commands at the moment. Possibly 
there will be other special use cases in the future. 

Martin

[1] 
http://lists.freedesktop.org/archives/modemmanager-devel/2013-September/000268.html
 
Signalion GmbH; Geschäftsführer (Managing Directors): Dr. Tim Hentschel, Dr. Thorsten Dräger; Sitz (Registered Office): Dresden; HRB (Commercial Register No.): 22081; Registergericht (Registration Court): Dresden

This email and any attachments are intended only for the person to whom this email is addressed and may contain confidential and/or privileged information. If you received this email in error, please do not disclose the contents to anyone, but notify the sender by return email and delete this email (and any attachments) from your system.


More information about the ModemManager-devel mailing list