Re: Telit FN990: MM 1.20.4: mmcli --location-enable-gps-nmea reporting error
Hi Amol, Il giorno mar 3 gen 2023 alle ore 06:36 Amol Lad ha scritto: > > Hi, > > I get the following error when enabling NMEA in FN990 with MM 1.20.4 (It > comes with 1.18.6 as well). I do not recall seeing this with Telit LN920 so > looks like this is something FN990 specific. Please advise. (I'm using MBIM) > > # mmcli -m "$modem" --location-enable-gps-nmea > error: couldn't setup location gathering: > 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.GeneralError: Couldn't > enable location 'gps-nmea' gathering: Couldn't start GPS engine: QMI protocol > error (46): 'GeneralError'' > [1672723268.345371] [/dev/cdc-wdm0] sent generic request > (translated)... > << QMUX: > << length = 19 > << flags = 0x00 > << service = "loc" > << client = 1 > << QMI: > << flags = "none" > << transaction = 4 > << tlv_length = 7 > << message = "Set NMEA Types" (0x003E) > << TLV: > << type = "NMEA Types" (0x01) > << length = 4 > << value = 0D:00:02:00 > << translated = gga, gsv, gsa > > [1672723268.345445] [/dev/cdc-wdm0] sent message... > << RAW: > << length = 68 > << data = 03:00:00:00:44:00:00:00:3A:00:00:00... > > [1672723268.345621] [/dev/cdc-wdm0] sent message (translated)... > << Header: > << length = 68 > << type= command (0x0003) > << transaction = 58 > << Fragment header: > << total = 1 > << current = 0 > << Contents: > << service = 'qmi' (d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3) > << cid = 'msg' (0x0001) > << type= 'set' (0x0001) > << Fields: > << QmiMsg = > '01:13:00:00:10:01:00:04:00:3e:00:07:00:01:04:00:0d:00:02:00' > > [1672723268.376601] [/dev/cdc-wdm0] received message... > >> RAW: > >> length = 68 > >> data = 03:00:00:80:44:00:00:00:3A:00:00:00... > > [1672723268.376810] [/dev/cdc-wdm0] received message (translated)... > >> Header: > >> length = 68 > >> type= command-done (0x8003) > >> transaction = 58 > >> Fragment header: > >> total = 1 > >> current = 0 > >> Contents: > >> status error = 'None' (0x) > >> service = 'qmi' (d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3) > >> cid = 'msg' (0x0001) > >> Fields: > >> QMUX = '01:13:00:80:10:01:02:04:00:3e:00:07:00:02:04:00:01:00:73:00' > > [1672723268.376877] [/dev/cdc-wdm0] received message... > << RAW: > << length = 20 > << data = 01:13:00:80:10:01:02:04:00:3E:00:07... > > [1672723268.376982] [/dev/cdc-wdm0] received generic response > (translated)... > << QMUX: > << length = 19 > << flags = 0x80 > << service = "loc" > << client = 1 > << QMI: > << flags = "response" > << transaction = 4 > << tlv_length = 7 > << message = "Set NMEA Types" (0x003E) > << TLV: > << type = "Result" (0x02) > << length = 4 > << value = 01:00:73:00 > << translated = FAILURE: NoPermission > > [1672723268.377384] [modem0] couldn't setup required NMEA traces: QMI > protocol error (115): 'NoPermission' I can't check right now on the target, but this and the start error are probably related to the control point not registered as the master client. I suggest to file a ticket with Telit technical support to deal with this. Regards, Daniele > [1672723268.377493] [/dev/cdc-wdm0] sent message... > << RAW: > << length = 38 > << data = 01:25:00:00:10:01:00:05:00:22:00:19... > > [1672723268.377685] [/dev/cdc-wdm0] sent generic request > (translated)... > << QMUX: > << length = 37 > << flags = 0x00 > << service = "loc" > << client = 1 > << QMI: > << flags = "none" > << transaction = 5 > << tlv_length = 25 > << message = "Start" (0x0022) > << TLV: > << type = "Minimum Interval between Position Reports" (0x13) > << length = 4 > << value = E8:03:00:00 > << translated = 1000 > << TLV: > << type = "Intermediate Report State" (0x12) > << length = 4 > << value = 02:00:00:00 > << translated = disable > << TLV: > << type = "Fix Recurrence Type" (0x10) > << length = 4 > << value = 01:00:00:00 > << translated = periodic-fixes > << TLV: > << type = "Session ID" (0x01) > << length = 1 > << value = 10 > << translated = 16 > > [1672723268.377846] [/dev/cdc-wdm0] sent message... > << RAW: > << length = 86 > << data = 03:00:00:00:56:00:00:00:3B:00:00:00... > > [1672723268.378097] [/dev/cdc-wdm0] sent message (translated)... > << Header: > << length = 86 > << type= command (0x0003) > <<
Telit FN990: MM 1.20.4: mmcli --location-enable-gps-nmea reporting error
Hi, I get the following error when enabling NMEA in FN990 with MM 1.20.4 (It comes with 1.18.6 as well). I do not recall seeing this with Telit LN920 so looks like this is something FN990 specific. Please advise. (I'm using MBIM) # mmcli -m "$modem" --location-enable-gps-nmea error: couldn't setup location gathering: 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.GeneralError: Couldn't enable location 'gps-nmea' gathering: Couldn't start GPS engine: QMI protocol error (46): 'GeneralError'' # mmcli -m 0 --- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: d04794b2e195986e2087001f45f6a4b81d1e3f16 --- Hardware | manufacturer: Telit Wireless Solutions | model: FN990 | carrier config: default | h/w revision: FN990A40 | supported: gsm-umts, lte, 5gnr |current: gsm-umts, lte, 5gnr | equipment id: 35917239176 --- System| device: /sys/devices/platform/soc/soc:internal-regs/f10f.usb3/usb3/3-1 |drivers: option1, cdc_mbim | plugin: telit | primary port: cdc-wdm0 | ports: cdc-wdm0 (mbim), ttyUSB0 (ignored), ttyUSB1 (gps), | ttyUSB2 (at), ttyUSB3 (at), ttyUSB4 (ignored), wwan0 (net) --- Numbers |own: 918660286965 --- Status| lock: sim-pin2 | unlock retries: sim-pin2 (3) | state: connected |power state: on |access tech: lte, 5gnr | signal quality: 24% (recent) --- Modes | supported: allowed: 3g; preferred: none | allowed: 4g; preferred: none | allowed: 3g, 4g; preferred: none |current: allowed: any; preferred: none --- Bands | supported: utran-1, utran-4, utran-6, utran-5, utran-8, utran-2, | eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, eutran-7, eutran-8, | eutran-12, eutran-13, eutran-14, eutran-17, eutran-18, eutran-19, | eutran-20, eutran-25, eutran-26, eutran-28, eutran-29, eutran-30, | eutran-32, eutran-34, eutran-38, eutran-39, eutran-40, eutran-41, | eutran-42, eutran-43, eutran-46, eutran-48, eutran-66, eutran-71, | utran-19, ngran-1, ngran-2, ngran-3, ngran-5, ngran-7, ngran-8, | ngran-20, ngran-25, ngran-28, ngran-30, ngran-38, ngran-40, ngran-41, | ngran-48, ngran-66, ngran-71, ngran-75, ngran-77, ngran-78, ngran-79 |current: utran-1, utran-4, utran-6, utran-5, utran-8, utran-2, | eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, eutran-7, eutran-8, | eutran-12, eutran-13, eutran-14, eutran-17, eutran-18, eutran-19, | eutran-20, eutran-25, eutran-26, eutran-28, eutran-29, eutran-30, | eutran-32, eutran-34, eutran-38, eutran-39, eutran-40, eutran-41, | eutran-42, eutran-43, eutran-46, eutran-48, eutran-66, eutran-71, | utran-19, ngran-1, ngran-2, ngran-3, ngran-5, ngran-7, ngran-8, | ngran-20, ngran-25, ngran-28, ngran-30, ngran-38, ngran-40, ngran-41, | ngran-48, ngran-66, ngran-71, ngran-75, ngran-77, ngran-78, ngran-79 --- IP| supported: ipv4, ipv6, ipv4v6 --- 3GPP | imei: 35917239176 | enabled locks: fixed-dialing |operator id: 405861 | operator name: Jio | registration: home | packet service state: attached --- 3GPP EPS | ue mode of operation: csps-2 | initial bearer apn: jionet | initial bearer ip type: ipv4v6 --- 3GPP 5GNR | mico mode: unsupported | drx cycle: unsupported
