PVS8 USB Enumeration Issue | Telit Cinterion IoT Developer Community
December 20, 2017 - 7:18pm, 3217 views
Hello,
We are building a custom health IoT hub that is using the PVS8 ****m for communication.
The device is running Android 4.4 and we are using PPP for the data connection.
However, we are seeing issues when we put the device into airplane **** and back to normal ****.
The data channel on ttyUSB3 will begin enumerating incorrectly on ttyUSB4 which causes the ****m to stop working.
The only way to get the ****m back on the correct usb channels is to reboot the device.
Below is our SCFG settings
AT< ^SCFG: "Audio/Ecfg","0"
AT< ^SCFG: "Audio/Loop","0"
AT< ^SCFG: "Call/Speech/Codec","0"
AT< ^SCFG: "CDMA/Priv****","0"
AT< ^SCFG: "CDMA/AutoAB","Any"
AT< ^SCFG: "CDMA/Operator/Store","Sprint"
AT< ^SCFG: "CDMA/System/CaiRev","9"
AT< ^SCFG: "CDMA/TetheredNai","disabled"
AT< ^SCFG: "Ident/Manufacturer","Cinterion"
AT< ^SCFG: "Ident/Product","PVS8"
AT< ^SCFG: "MEop****/Airplane","off"
AT< ^SCFG: "MEop****/CFUN","0","1"
AT< ^SCFG: "MEop****/PowerMgmt/LCI","disabled"
AT< ^SCFG: "MEop****/PowerMgmt/VExt","high"
AT< ^SCFG: "MEop****/PwrSave","enabled","0","50"
AT< ^SCFG: "MEop****/RingOnData","off"
AT< ^SCFG: "MEop****/RingUrcOnCall","on"
AT< ^SCFG: "MEShutdown/OnIgnition","off"
AT< ^SCFG: "Radio/Band","7168"
AT< ^SCFG: "Radio/Mtpl","0"
AT< ^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","0053","Cinterion","PH8",""
AT< ^SCFG: "Serial/USB/DeviceClass/RmNet","Vendor"
AT< ^SCFG: "Serial/USB/Instances/Audio","0","0"
AT< ^SCFG: "Serial/USB/Instances/RmNet","1","1"
AT< ^SCFG: "Serial/USB/Speed","high"
AT< ^SCFG: "Sms/Retrm",5
AT< ^SCFG: "Sms/Whitelist/****",0
AT< ^SCFG: "Sms/Whitelist/Acc"
AT< ^SCFG: "URC/DstIfc","app"
AT< ^SCFG: "URC/Data****/Ringline","on"
AT< ^SCFG: "URC/Ringline","local"
AT< ^SCFG: "URC/Ringline/ActiveTime","1"
Hello,
I remember the similar problem for Linux that USB interfaces were not always enumerated in the same way - it was depending on what else was plugged in. The solution was to create the proper udev rule.
Are you using RIL, what version you are using?
Maybe there's an update or some changes in RIL implementation might be required.
Please also check the module's firmware version with ATI1 command.
Regards,
Bartłomiej
I will look into the UDEV rules.
Here is the output from ATI1:
AT< REVISION 03.320
AT< A-REVISION 01.000.06
How about RIL from Gemalto? Are you using it?
Yes we are using the Gemalto RIL 1.7.0.0
From module side if you change configuration AT^SDPORT this could lead to change port enumeration but here it is not the case because rebooting device fix your issue.
So it must be Linux issue which make port ttyUSB3 locked and module is enumerated on next free ttyUSB4.