PLS83-W QMI/RMNET Setup Problems | Thales IoT Developer Community
June 30, 2021 - 2:44pm, 3431 views
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,
A Random Intern
And what Linux system is it? I can see also the other way with udev for Ubuntu.
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 :
Here are my outputs :
~$ sudo qmicli -d /dev/cdc-wdm1 -p --dms-get-operating-****
~$ sudo qmicli -p -d /dev/cdc-wdm1 --wds-start-network="apn=yesinternet,ip-type=4" --client-no-release-cid
~$ sudo udhcpc -q -f -i wwan0
~$ ip a
Here is the failed ping :
~$ ping -I wwan0 18.104.22.168
I tried enabling Mobile Broadband Network through Network Manager but it doesn't work either. What could be the issues... ?
A Random Intern
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.
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 :
Here is my 77-mm-cinterion-port-types.rules file, if needed :
A Random Intern
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.
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 :
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,
A Random Intern
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.
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...
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 :
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,
A Random Intern
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.