Getting CME ERROR 13 with and without a SIM card inserted
Home › Forums › Conduit: AEP Model › Getting CME ERROR 13 with and without a SIM card inserted
Tagged: cellular
- This topic has 6 replies, 2 voices, and was last updated 5 years, 9 months ago by
Brandberg.
-
AuthorPosts
-
July 5, 2019 at 4:04 pm #28146
Brandberg
ParticipantHi,
I have trouble getting a cellular connection to work on my MTCDTIP-LEU1-266A unit. I have tried different sim cards, and also tried the sim in another 3/4G router and phone without a problem. I am sure it is in the correct way (contacts facing down & cut corner to the right). The nano sim is placed inside a sim kit to make sure it is the right micro sim size.
When I try to configure the cellular connection, I do receive an error message to say “Sim Card Locked Out”. The sim card has no pin and I verified this. The actual error message I receive is Connect script failed.Product Info
Product MTCDTIP-LEU1-266A
Serial XXXXXXXXXX
Provider Unknown
Phone Not Supported
IMEI XXXXXXXXXXXX
IMSI Not Supported
Firmware 1.7.4
Radio Firmware 17.00.523
Radio Model LE910-EUG****************Log detail***************
2019-07-03T21:57:39.307102+01:00 localhost chat[4259]: info: Attempting Basic Radio Communication
2019-07-03T21:57:39.308409+01:00 localhost chat[4259]: send (AT^M)
2019-07-03T21:57:39.341361+01:00 localhost chat[4259]: expect (OK)
2019-07-03T21:57:39.346392+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:39.346709+01:00 localhost chat[4259]: OK
2019-07-03T21:57:39.346922+01:00 localhost chat[4259]: — got it
2019-07-03T21:57:39.347169+01:00 localhost chat[4259]: info: Checking if SIM is inserted
2019-07-03T21:57:39.347390+01:00 localhost chat[4259]: send (AT#SIMDET?^M)
2019-07-03T21:57:39.461219+01:00 localhost chat[4259]: expect (#SIMDET: 2,1)
2019-07-03T21:57:39.461552+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:39.472170+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:39.473855+01:00 localhost chat[4259]: #SIMDET: 2,1
2019-07-03T21:57:39.474975+01:00 localhost chat[4259]: — got it
2019-07-03T21:57:39.476104+01:00 localhost chat[4259]: info: Checking if SIM is locked
2019-07-03T21:57:39.477234+01:00 localhost chat[4259]: send (AT+CPIN?^M)
2019-07-03T21:57:39.571002+01:00 localhost chat[4259]: expect (READY)
2019-07-03T21:57:39.571334+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:39.581848+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:39.583026+01:00 localhost chat[4259]: OK^M
2019-07-03T21:57:39.584415+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:39.585598+01:00 localhost chat[4259]: ERROR^M
2019-07-03T21:57:40.582277+01:00 localhost chat[4259]: alarm
2019-07-03T21:57:40.584640+01:00 localhost chat[4259]: send (AT+CPIN?^M)
2019-07-03T21:57:40.678420+01:00 localhost chat[4259]: expect (ERROR)
2019-07-03T21:57:40.683021+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:40.683355+01:00 localhost chat[4259]: ERROR
2019-07-03T21:57:40.683575+01:00 localhost chat[4259]: — got it
2019-07-03T21:57:40.683834+01:00 localhost chat[4259]: send (AT#SIMDET?^M)
2019-07-03T21:57:40.797402+01:00 localhost chat[4259]: expect (#SIMDET: 2,0)
2019-07-03T21:57:40.797734+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:40.802242+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:40.802631+01:00 localhost chat[4259]: #SIMDET: 2,1^M
2019-07-03T21:57:40.802898+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:40.803177+01:00 localhost chat[4259]: OK^M
2019-07-03T21:57:41.797912+01:00 localhost chat[4259]: alarm
2019-07-03T21:57:41.798216+01:00 localhost chat[4259]: info: No SIM Pin required
2019-07-03T21:57:41.798427+01:00 localhost chat[4259]: info: Waiting for minimum signal strength
2019-07-03T21:57:41.798639+01:00 localhost chat[4259]: send (AT+CSQ^M)
2019-07-03T21:57:41.870709+01:00 localhost chat[4259]: expect (+CSQ: )
2019-07-03T21:57:41.875195+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:41.875526+01:00 localhost chat[4259]: +CSQ:
2019-07-03T21:57:41.875819+01:00 localhost chat[4259]: — got it
2019-07-03T21:57:41.876082+01:00 localhost chat[4259]: expect (99,99)
2019-07-03T21:57:41.876418+01:00 localhost chat[4259]: 14,99^M
2019-07-03T21:57:41.876799+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:41.877079+01:00 localhost chat[4259]: OK^M
2019-07-03T21:57:42.876558+01:00 localhost chat[4259]: alarm
2019-07-03T21:57:42.877261+01:00 localhost chat[4259]: send (AT^M)
2019-07-03T21:57:42.908426+01:00 localhost chat[4259]: expect (OK)
2019-07-03T21:57:42.912697+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:42.913008+01:00 localhost chat[4259]: OK
2019-07-03T21:57:42.913234+01:00 localhost chat[4259]: — got it
2019-07-03T21:57:42.913498+01:00 localhost chat[4259]: send (AT^M)
2019-07-03T21:57:42.945193+01:00 localhost chat[4259]: abort on (NO CARRIER)
2019-07-03T21:57:42.945480+01:00 localhost chat[4259]: abort on (BUSY)
2019-07-03T21:57:42.945730+01:00 localhost chat[4259]: abort on (ERROR)
2019-07-03T21:57:42.945974+01:00 localhost chat[4259]: expect (OK)
2019-07-03T21:57:42.946277+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:42.949442+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:42.949759+01:00 localhost chat[4259]: OK
2019-07-03T21:57:42.949988+01:00 localhost chat[4259]: — got it
2019-07-03T21:57:42.950248+01:00 localhost chat[4259]: send (AT+CSQ^M)
2019-07-03T21:57:43.032541+01:00 localhost chat[4259]: expect (OK)
2019-07-03T21:57:43.032880+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:43.036962+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:43.037379+01:00 localhost chat[4259]: +CSQ: 14,99^M
2019-07-03T21:57:43.037655+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:43.037933+01:00 localhost chat[4259]: OK
2019-07-03T21:57:43.038149+01:00 localhost chat[4259]: — got it
2019-07-03T21:57:43.038421+01:00 localhost chat[4259]: send (AT+CGDCONT=1,\”IP\”,\”pp.vodafone.co.uk\”^M)
2019-07-03T21:57:43.436183+01:00 localhost chat[4259]: expect (OK)
2019-07-03T21:57:43.436525+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:43.440457+01:00 localhost chat[4259]: ^M
2019-07-03T21:57:43.440805+01:00 localhost chat[4259]: ERROR
2019-07-03T21:57:43.441026+01:00 localhost chat[4259]: — failed
2019-07-03T21:57:43.441326+01:00 localhost chat[4259]: Failed (ERROR)
2019-07-03T21:57:43.443400+01:00 localhost pppd[2329]: Connect script failed******PPP_Trace_*****
20:59:53: Connecting for 0 time
20:59:58: Physical link failed
21:0:29: Current timing 60
21:0:29: Sleeping 24 seconds before next attempt
21:0:53: Connecting for 1 time
21:0:58: Physical link failed**********************
AT+CPIN? consistently provides CME error 13 whether the SIM card is present in the socket or not.
Is it possible that this could be a physical sim socket issue or am I missing something? If so how can I get a replacement just for the sim socket connector of this unit?
Many thanks.July 8, 2019 at 12:56 pm #28159Steve Kovarik
ModeratorHi Brandberg
The log shows that the SIM card is physically detected (#SIMDET:2,1)
but the MTCDTIP can not read the SIM. The installation guide correctly
states “cut corner to the left and the SIM contacts facing towards the USB port”
Can you confirm that you have tried that SIM card orientation in the MTCDTIP?July 8, 2019 at 1:32 pm #28160Brandberg
ParticipantHi Steve,
Yes, I can confirm that this is the way the sim is inserted.
What I do receive is a consistent error messages of “SIM card is locked out” does not matter which sim card I insert ( I have one for Vodafone and one for EE here in the UK). If I stick both those in a 3/4G router or my iPad they work without any issues.
July 8, 2019 at 1:58 pm #28161Steve Kovarik
ModeratorHi Brandberg
If we consider this a possible physical SIM slot issue the next step would
be to open a support portal case at the link below. We would likely assign
a RMA and need the whole device shipped back for warranty service.
https://support.multitech.com/support/login.htmlJuly 8, 2019 at 2:09 pm #28163Brandberg
ParticipantHi Steve,
I have opened a case earlier today (I have the case number). Shall I wait for a response on the logged Support request for next steps?
Thanks very much for your assistance.
July 8, 2019 at 3:32 pm #28178Steve Kovarik
ModeratorLet me know the case number.
ThanksJuly 8, 2019 at 4:31 pm #28185Brandberg
ParticipantThanks Steve – I have just received your response in the case I have opened.
I have provided all needed information there.. -
AuthorPosts
- You must be logged in to reply to this topic.