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

You are here

Community > Forum > Cellular Hardware > EHS5-E no carrier

EHS5-E no carrier | Thales IoT Developer Community

Like
0
11
jannenivala's picture
jannenivala

July 31, 2014 - 2:00pm, 9695 views

Hi, We have a Windows CE 7 device that has EHS5-E device. ASC0 and USB are connected, but we don't have USB drivers yet. We can communicate via ASC0 using a terminal. When we try establish a RAS connection (dial-up), it dials but after ~20 seconds we get RAS error 679 ("Cannot detect carrier."). When we dial using terminal ("ATDT *99***1#") we get "CONNECT", then some content and then "NO CARRIER". That is similar as with dial-up. We have tested that - signal is ok (+CSQ: 13,99) - modem is attached to network - SIM is fine Any ideas? Regards, Janne
11
Comment
Log in or register to post comments
1 - 10 of 11 Comments

Pages

Michał - Gemalto Moderator's picture
Michał - Gemalt...
Jul 31 2014 - 4:59pm
Hi Janne, Please let us know if you are using RIL driver. Do you have any logs?
Walking on water and developing software from a specification are easy - if both are frozen.
jannenivala's picture
jannenivala
Aug 1 2014 - 12:42pm
Hi, We're not using a RIL driver. I'll post RAS dialer console output asap. I'm not aware of any other log available for us. Is there something that I can get from modem or OS that you are aware of? Edit: Microsoft RIL driver is loaded but RIL driver configuration does not point to correct serial port. There is no Cinterion USB driver for modem. => RIL does not interact with the modem and thus does not contribute to this case. When modem is started we get a notification of a new USB device without a driver. Regards, Janne
jannenivala's picture
jannenivala
Aug 1 2014 - 12:22pm
This is what is printed to CE device debug port: AUTORAS:: Dialer notifies: [1] [Dialer Start] RASCS_Disconnected: Ecode=679 Posting WM_NETCONNECT(FALSE) message, ErrorCode = 679(0x2A7) AUTORAS:: Dialer notifies: [2] [Dialer Terminate]
jannenivala's picture
jannenivala
Aug 4 2014 - 7:50pm
AT+CEER outputs: +CEER: "CC setup error",50,"Requested facility not subscribed" Could that have anything to do with this?
jannenivala's picture
jannenivala
Aug 4 2014 - 7:54pm
We have a DSB75 evaluation board with EHS5-E attached, too. When trying to connect from PC terminal using AT commands, we get the same result as with the CE device (CONNECT... content... NO CARRIER). When we setup a dial-up connection in Windows 8, we get "Connection failed with error 651". RAS error 651 is "Your modem (or other connecting device) has reported an error."
Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Aug 4 2014 - 2:09pm
Hello, have you installed the modem using generic windows driver or used .inf descriptor file supplied with the module? Regards Jedrzej
jannenivala's picture
jannenivala
Aug 4 2014 - 7:54pm
Thanks. Our goal is not desktop but I will test that. Is it expected to get NO CARRIER after a while when you dial from a terminal? This was the behavior on both device and evaluation board modems.
Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Aug 5 2014 - 1:19pm
Yes, it is. After calling ATD PPP protocol is expected. If DTE doesn't answer properly (and you don't answer as you only call it using terminal and do nothing) the connection is dropped with NO CARRIER result code.
jannenivala's picture
jannenivala
Aug 6 2014 - 4:21pm
Found the cause: Windows CE 7 prefixed the specified RAS connection phone number with "9," and it became "9,*99***1#". That ruined dialing-up. After dialing such number modem AT+CEER was: +CEER: "CC setup error",50,"Requested facility not subscribed".
Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Aug 6 2014 - 5:12pm
Good to see you've found the root of the issue. Did you finally got it working?
1 - 10 of 11 Comments

Pages