Alcatel X500D: unable to retrieve ICCID or SIM operator info
Hi all,
I am using an Alcatel X500D USB modem and ModemManager is unable to retrieve ICCID or SIM operator info (name and identifier). The debug logs show that the AT commands fail systematically.
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.458158] loading SIM identifier...
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.458202] (ttyUSB4) device open count is 3 (open)
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.458246] (ttyUSB4) device open count is 2 (close)
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.458287] (ttyUSB4): --> 'AT+CRSM=176,12258,0,0,10<CR>'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.493816] (ttyUSB4): <-- '<CR><LF>ERROR<CR><LF>'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.494031] Got failure code 100: Unknown error
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.494124] loading SIM identifier...
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.494210] (ttyUSB4) device open count is 3 (open)
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.494295] (ttyUSB4) device open count is 2 (close)
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.494379] (ttyUSB4): --> 'AT+CRSM=176,12258,0,0,10<CR>'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.529565] (ttyUSB4): <-- '<CR><LF>ERROR<CR><LF>'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.529667] Got failure code 100: Unknown error
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <warn> [1551964085.529711] couldn't load SIM identifier: 'Unknown error'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.529762] loading IMSI...
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.529791] (ttyUSB4) device open count is 3 (open)
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.529834] (ttyUSB4) device open count is 2 (close)
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.529932] (ttyUSB4): --> 'AT+CIMI<CR>'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.544769] (ttyUSB4): <-- '<CR><LF>208011400352762<CR><LF><CR><LF>OK<CR><LF>'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.544860] loaded IMSI: 208011400352762
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.544942] loading Operator ID...
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.544969] (ttyUSB4) device open count is 3 (open)
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.545000] (ttyUSB4) device open count is 2 (close)
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.545031] (ttyUSB4): --> 'AT+CRSM=176,28589,0,0,4<CR>'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.579403] (ttyUSB4): <-- '<CR><LF>ERROR<CR><LF>'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.579521] Got failure code 100: Unknown error
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <warn> [1551964085.579617] couldn't load Operator identifier: 'Unknown error'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.579660] loading Operator Name...
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.579714] (ttyUSB4) device open count is 3 (open)
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.579786] (ttyUSB4) device open count is 2 (close)
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.579853] (ttyUSB4): --> 'AT+CRSM=176,28486,0,0,17<CR>'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.614570] (ttyUSB4): <-- '<CR><LF>ERROR<CR><LF>'
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <debug> [1551964085.614746] Got failure code 100: Unknown error
Mar 07 14:08:05 SGX-CMP-486 ModemManager[3259]: <warn> [1551964085.614827] couldn't load Operator name: 'Unknown error'
I have also tested with ModemManager 1.10.0 and the problem remains. Is it a modem limitation for this model or can something be fixed ?
Regards,
Attached logs for ModemManager 1.8.0: modemmanager_debug.log mmcli_output.log