Thales' cellular IoT products business is now part of Telit Cinterion, find out more.

You are here

Community > Forum > Cellular Hardware > PLS83-W QMI/RMNET Setup Problems

PLS83-W QMI/RMNET Setup Problems | Telit Cinterion IoT Developer Community

Like
1
9
Random Intern's picture
Random Intern

June 30, 2021 - 2:44pm, 3981 views

Hi,

I have been following this tutorial : PLS63/83 QMI/RMNET Setup and Linux qmi_wwan / ModemManager Integration | Thales IoT Developer Community (thalesgroup.com) to configure the PLS83-W module to operate in QMI/RMNET.

I have 2 LGA DevKits with PLS83-W module implemented. One seems to work just fine (only pinging from wwan0 isn't successful yet), but the second DevKit has its TXD0 LED lighting up in red, and that's what the datasheet says about red light :

Lighting: Overcurrent detected in module power pass, change module, restart LGA DevKit's power supply

Is the second DevKit defective?

You will find below the errors I encountered while trying to set up QMI on this second DevKit.

Every first sets of Linux commands seem to work. However, I am stuck to this following step : 

Once the wwan0 is up, connect the mobile network by changing the apn='YOUR_APN',username='YOUR_USERNAME',password='YOUR_PASSWORD' part of the line according to the information of your SIM & operator:

$ sudo qmicli -p -d /dev/cdc-wdm0 --wds-start-network="apn='YOUR_APN',username='YOUR_USERNAME',password='YOUR_PASSWORD',ip-type=4" --client-no-release-cid

Here is my output :

~$ sudo qmicli -d /dev/cdc-wdm1 -p --wds-start-network="ip-type=4,apn=yesinternet" --client-no-release-cid
error: couldn't start network: QMI protocol error (14): 'CallFailed'
call end reason (1): generic-unspecified
verbose call end reason (2,241): [internal] (null)
[/dev/cdc-wdm1] Client ID not released:
	Service: 'wds'
        CID: '3'

I am not really sure what this error corresponds to, and it might be related to this red light, but if someone has a solution other than changing the module, I am all ears ! 

 

Thank you in advance for your answer,

Best Regards

 

A Random Intern

9
Comment
Log in or register to post comments
Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Jul 1 2021 - 11:03am

Hello,

And what Linux system is it? I can see also the other way with udev for Ubuntu.

BR,

Bartłomiej

Random Intern's picture
Random Intern
Jul 1 2021 - 5:15pm

Hello Bartłomiej,

Thank you for your answer, I am using Ubuntu 20.04.1.

Also, I am having trouble with the last part of the tutorial, I am unable to ping from wwan0 like quoted below :

To verify if the wwan0 was up and running, you can ping an Internet host like below:

$ ping -I wwan0 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 100.89.179.219 wwan0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=227 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=114 time=47.6 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=114 time=44.8 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=114 time=42.0 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=114 time=42.3 ms
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/***/mdev = 41.990/80.642/226.516/72.964 ms

Here are my outputs :

dmesg :

[17607.715377] usb 1-2.2: new high-speed USB device number 21 using xhci_hcd
[17607.920779] usb 1-2.2: New USB device found, idVendor=1e2d, idProduct=006f, bcdDevice= 0.00
[17607.920788] usb 1-2.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[17607.920794] usb 1-2.2: Product: PLSx3
[17607.920798] usb 1-2.2: Manufacturer: Cinterion Wireless Modules
[17607.920802] usb 1-2.2: SerialNumber: b3806075
[17607.934215] cdc_acm 1-2.2:1.0: ttyACM0: USB ACM device
[17607.936131] cdc_acm 1-2.2:1.2: ttyACM1: USB ACM device
[17607.937856] cdc_acm 1-2.2:1.4: ttyACM2: USB ACM device
[17607.939606] cdc_acm 1-2.2:1.6: ttyACM3: USB ACM device
[17607.942859] qmi_wwan 1-2.2:1.8: cdc-wdm1: USB WDM device
[17607.944340] qmi_wwan 1-2.2:1.8 wwan0: register 'qmi_wwan' at usb-0000:00:14.0-2.2, WWAN/QMI device, 12:1e:c5:ce:5f:b8

 

~$ sudo qmicli -d /dev/cdc-wdm1 -p --dms-get-operating-mode

[/dev/cdc-wdm1] Operating mode retrieved:
	Mode: 'online'
	HW restricted: 'no'

 

~$ sudo qmicli -p -d /dev/cdc-wdm1 --wds-start-network="apn=yesinternet,ip-type=4" --client-no-release-cid

[/dev/cdc-wdm1] Network started
	Packet data handle: '2244892512'
[/dev/cdc-wdm1] Client ID not released:
	Service: 'wds'
	    CID: '2'

 

~$ sudo udhcpc -q -f -i wwan0

udhcpc: started, v1.30.1
udhcpc: sending discover
udhcpc: sending select for 10.10.20.125
udhcpc: lease of 10.10.20.125 obtained, lease time 7200
ip: RTNETLINK answers: File exists

 

~$ ip a

.
.
.
14: wwan0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/none 
    inet 10.10.20.125/30 scope global wwan0
       valid_lft forever preferred_lft forever
    inet6 fe80::179a:79cd:210c:69c9/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever

Here is the failed ping :

~$ ping -I wwan0 8.8.8.8

ING 8.8.8.8 (8.8.8.8) from 10.10.20.125 wwan0: 56(84) bytes of data.

--- statistiques ping 8.8.8.8 ---
5 paquets transmis, 0 reçus, 100 % paquets perdus, temps 4075 ms

 

I tried enabling Mobile Broadband Network through Network Manager but it doesn't work either. What could be the issues... ?

Best Regards

A Random Intern

 

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Jul 5 2021 - 2:05pm

Hello,

In your last post it looks like the connection is up - there is IP assigned similarly as in the tutorial.
So maybe the problem is now signal quality or something else in your system as ping does not go through.

Anyway I tried with my Ubuntu 20.04.02 LTS and was able to set it up in both ways. So at least I proved that in general this tutorial works.
For udev rules reloading didn't help and I rebooted the whole system. Then everything enumerated properly.

Best regards,
Bartłomiej

Random Intern's picture
Random Intern
Jul 7 2021 - 4:26pm

Hi Bartłomiej,

Thank you for your answer.

I tried everything again and now both my DevKits are facing similar problem. So my questions are :

- If the TXD0 Light on the LGA DevKit is Red (not blinking but lighting continuously), is it defective ? If not, what could be the problems I need to rectify ?

- I tried the tutorial again and now, even the LGA DevKit which was working till the "ping" command isn't reaching the network either. I still have this error, which I don't know how to solve :

~$ sudo qmicli -d /dev/cdc-wdm1 -p --wds-start-network="ip-type=4,apn=yesinternet" --client-no-release-cid
error: couldn't start network: QMI protocol error (14): 'CallFailed'
call end reason (1): generic-unspecified
verbose call end reason (2,241): [internal] (null)
[/dev/cdc-wdm1] Client ID not released:
	Service: 'wds'
        CID: '3'

Here is my 77-mm-cinterion-port-types.rules file, if needed :

# do not edit this file, it will be overwritten on update 

ACTION!="add|change|move|bind", GOTO="mm_cinterion_port_types_end"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1e2d", GOTO="mm_cinterion_port_types"
GOTO="mm_cinterion_port_types_end"

LABEL="mm_cinterion_port_types"
SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}=="?*", ENV{.MM_USBIFNUM}="$attr{bInterfaceNumber}"

# PHS8
ATTRS{idVendor}=="1e2d", ATTRS{idProduct}=="0053", ENV{.MM_USBIFNUM}=="01", ENV{ID_MM_PORT_TYPE_GPS}="1"

# PLS8
ATTRS{idVendor}=="1e2d", ATTRS{idProduct}=="0061", ENV{.MM_USBIFNUM}=="04", ENV{ID_MM_PORT_TYPE_GPS}="1"

# PLS83 family enumeration
# ttyACM0 (if #0): Modem port
# ttyACM1 (if #2): AT port
# ttyACM2 (if #4): AT port
# ttyACM3 (if #6): reserved
ATTRS{idVendor}=="1e2d", ATTRS{idProduct}=="0069", ENV{.MM_USBIFNUM}=="00", ENV{ID_MM_PORT_TYPE_AT_PPP}="1"
ATTRS{idVendor}=="1e2d", ATTRS{idProduct}=="0069", ENV{.MM_USBIFNUM}=="02", ENV{ID_MM_PORT_TYPE_AT_PRIMARY}="1"
ATTRS{idVendor}=="1e2d", ATTRS{idProduct}=="0069", ENV{.MM_USBIFNUM}=="04", ENV{ID_MM_PORT_IGNORE}="1"
ATTRS{idVendor}=="1e2d", ATTRS{idProduct}=="0069", ENV{.MM_USBIFNUM}=="06", ENV{ID_MM_PORT_IGNORE}="1"

ATTRS{idVendor}=="1e2d", ATTRS{idProduct}=="006F", ENV{.MM_USBIFNUM}=="00", ENV{ID_MM_PORT_TYPE_AT_PPP}="1"
ATTRS{idVendor}=="1e2d", ATTRS{idProduct}=="006F", ENV{.MM_USBIFNUM}=="02", ENV{ID_MM_PORT_TYPE_AT_PRIMARY}="1"
ATTRS{idVendor}=="1e2d", ATTRS{idProduct}=="006F", ENV{.MM_USBIFNUM}=="04", ENV{ID_MM_PORT_IGNORE}="1"
ATTRS{idVendor}=="1e2d", ATTRS{idProduct}=="006F", ENV{.MM_USBIFNUM}=="06", ENV{ID_MM_PORT_IGNORE}="1"


LABEL="mm_cinterion_port_types_end"

 

Best Regards,

A Random Intern

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Jul 8 2021 - 11:39am

Hello,

Please check ASC0 switch on DevKit and set USB. If you have more problems now please make sure if the USB cable is plugged to native USB.

BR,
Bartłomiej

Random Intern's picture
Random Intern
Jul 8 2021 - 2:51pm

Hello Bartłomiej,

ASC0 switch is already set on USB (POWER switch too), and USB cable is also already plugged to native USB... But it's not working. 

Still have this error when I try to connect to network through QMI Setup :

~$ sudo qmicli -d /dev/cdc-wdm1 -p --wds-start-network="ip-type=4,apn=yesinternet" --client-no-release-cid
error: couldn't start network: QMI protocol error (14): 'CallFailed'
call end reason (1): generic-unspecified
verbose call end reason (2,241): [internal] (null)
[/dev/cdc-wdm1] Client ID not released:
	Service: 'wds'
        CID: '3'

Do you know what could these errors mean ? And what does a TXD0 Red Light on one of the DevKit could mean ?

 

Thank you in advance,

Best Regards

 

A Random Intern

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Jul 8 2021 - 3:44pm

Hello,

As for the DevKit please paste a clear photo with all the board visible.
As for the error I just found on the internet that such error could be related to the MNO. In that case (Verizon MNO) IMEI was not loaded in their database as a valid device. This was a specifics of Verizon but maybe in your case there is something similar like you are using the wrong APN or so. Please also verify if the module is registered to the network. Try a SIM from some other MNO if possible. Or check some other type of connection like dialup. You might also look into AT spec and try a simple IP service over AT commands to check if the connection is possible.

Best regards,
Bartłomiej

Random Intern's picture
Random Intern
Jul 9 2021 - 3:07pm

Hi Bartłomiej,

Here is the picture of the first DevKit without any LED abnormalities.

Here is the picture of the second DevKit with its TXD0 LED lighting in red. 

 

As for the SIM cards we are using, they are meant for testing only so they connect to a private LTE mobile network only. We are trying to use QMI on this PLS83-W module in order to measure its performances.

Here are my AT ouputs, I am using the APN corresponding to our private network and it is registered to the network... 

at+cpin?
+CPIN: READY

OK
at+cops? //Checking the current status of network registration
+COPS: 0,0,"001 01",7

OK
at+creg? //Monitoring module's circuit mode network registration status
+CREG: 0,1

OK
at+cgdcont?  //Checking all the PDP contexts
+CGDCONT: 1,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,1,0
+CGDCONT: 2,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,1,0
+CGDCONT: 3,"IPV4V6","yesinternet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,0,0
+CGDCONT: 4,"IPV4V6","CMWAP","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,0,0
+CGDCONT: 5,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1,1,0

OK
at+cgact?  //Checking status of context : "yesinternet" (my APN) is up
+CGACT: 1,0
+CGACT: 2,0
+CGACT: 3,1
+CGACT: 4,0
+CGACT: 5,0

OK

As for qmicli commands, I noticed I am actually unable to use any qmicli network commands (wds and nas), and it returns the same following error : 

-Warning ** Error reading from istream
error: couldn't open the QmiDevice: Transaction timed out

I also tried looking up on Qualcomm Developer Network but unfortunately didn't find any documentation related to QMI to check those errors. 

Thank you for your help,

Best Regards,

A Random Intern

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Jul 9 2021 - 4:57pm

OK, thanks, I thought that there will be something abnormal we can change but everything looks standard. For now I don't know why the LED is on. Is there now a difference in dmesg output for these 2 devices? Any communication issues? You may try to remove jumpers in ASC0_A section.
If it is a private network it would be a good idea to test with some other and public network to verify if the solution works. There may be a problem in the network configuration. But your recent error suggest that either there is a new problem in your OS configuration or the modules do not work correctly (haven't you changed AT^SSRVSET?). Please check dmesg, try with other PC (maybe Windows OS) to verify in which component the problem is.

Regards,
Bartłomiej