Gemalto is now part of the Thales Group, find out more.

You are here

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

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


I have been following this tutorial : PLS63/83 QMI/RMNET Setup and Linux qmi_wwan / ModemManager Integration | Thales IoT Developer Community ( 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