Hello, Thanks for your reply. Are you sure the modem is not already in QMI mode? MM is clearly using QMI to communicate with it (and I can also use qmicli -p), and also below URL states that this modem is a QMI raw-ip only modem.
https://sigquit.wordpress.com/2017/01/07/modemmanager-in-openwrt-take-2 Though I also admit I am not 100% sure, because the protocol relations and communication possibilities with the modem are not yet clear to me (I am quite new to this topic). Though I am a developer myself, I don't have much experience with different modems yet. So while I can gladly try to implement support for my modem's GNSS AT command set, it might end up being very model-specific. With some pointers though about which source files and APIs to start with (I don't have a clue yet about MM's code either), I might give it a go if you don't mind. Regards, Károly April 12, 2017 5:58 PM, "Dan Williams" <[email protected]> wrote: > On Wed, 2017-04-12 at 13:21 +0000, Karoly Pados wrote: > >> Hello, >> >> I have a MC7455 form Sierra Wireless. It is working fine for data >> communication, but ModemManager doesn't seem to be able to recognize >> the locations services (GPS and A-GPS) provided by the modem. >> >> mmcli -m 0 --location-status >> >> /org/freedesktop/ModemManager1/Modem/0 >> ---------------------------- >> Location | capabilities: '3gpp-lac-ci' >> | enabled: '3gpp-lac-ci' >> | signals: 'no' >> >> If I start ModemManager with the --debug flag and then issue AT- >> commands using --command by hand, I can get a GPS fix and retrieve >> the location using raw AT commands. (This also means that in my case >> there is no need to unlock location services using a password.) >> >> I read on this list that the modem needs to be in QMI-mode for MM to >> support location data. I think this is already the case because when >> I start MM in debug mode I can see it is using QMI to communicate. >> >> Is there anything else I can do or need to check to make location >> data in MM working? Or any way I can help to implement support for >> it? > > At the moment, no. The device is likely in MBIM mode which is why you > don't get location data. There are two options we are exploring for > ModemManager: > > 1) use the MBIM QMI passthrough to provide the location data that QMI > can provide, which will work with this device because it's a Qualcomm- > based one > > 2) if that fails, see if we can use the AT ports for GPS > > This is mainly just a problem for MBIM devices, because the MBIM > protocol specification does not contain any GPS-related options. That > is left to vendor proprietary methods, as you've discovered :) > > So TLDR; you can't do this yet but it's at least being thought > about/worked on. If you're interested in helping fix this, we can use > either code or testing... > > Thanks! > Dan > >> My software: >> # uname -a >> Linux a13-olinuxino 4.9.21 #2 SMP Mon Apr 10 10:29:48 CEST 2017 >> armv7l GNU/Linux >> # ModemManager --version >> ModemManager 1.6.2 >> ... >> # qmicli --version >> qmicli 1.16.0 >> ... >> >> Thank you for your help, greetings, >> >> Károly Pados >> >> tec4data >> finding of facts! >> thoerl 35; 8621 thoerl; austria >> mob +43 680 5577 310 >> uid atu44131505 >> mail [email protected] >> http://www.tec4data.at >> >> This email and any associated attachment are confidential. >> Unless you belong to the specified recipients, immediately notify the >> sender. >> The content may not be copied and given to third parties. >> ___________________________________________________________________ >> _______________________________________________ >> ModemManager-devel mailing list >> [email protected] >> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel > > _______________________________________________ > ModemManager-devel mailing list > [email protected] > https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel _______________________________________________ ModemManager-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
