# EM7565 "no network service"

**URL:** <https://forum.sierrawireless.com/t/em7565-no-network-service/25959>\
**Category:** IoT Modules\
**Created:** [January 13, 2022, 10:06pm UTC](https://forum.sierrawireless.com/t/em7565-no-network-service/25959 "2022-01-13T22:06:21Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![greg.wood](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@greg.wood](https://forum.sierrawireless.com/u/greg.wood)\
**Post date:** [January 13, 2022, 10:06pm UTC](https://forum.sierrawireless.com/t/em7565-no-network-service/25959/1 "2022-01-13T22:06:21Z")

</div>

I’m trying to get a new EM7565 module up and running. I’ve had it working in the development board in windows, I’ve also had my custom carrier board working with a different EM7565. With the problem unit when I do at!scact=1,1 I get :

"at!scact=1,1  
+CME ERROR: no network service  
"

On the other EM7565 module it works just fine.

I tried updating the firmware, but had no effect. Is there some other settings I need to change to make this work? It seems to connect under windows just fine so the module is obviously capable of working on my network.

---

<div class="post-metadata">

**Author:** ![Donald](https://avatars.discourse-cdn.com/v4/letter/d/ac8455/32.png) [@Donald](https://forum.sierrawireless.com/u/Donald)\
**Post date:** [January 14, 2022, 12:32am UTC](https://forum.sierrawireless.com/t/em7565-no-network-service/25959/2 "2022-01-14T00:32:51Z")

</div>

Hi greg.wood,

Can you please provide the log files of the following commands on working EM7565 and not working EM7565?

```auto
ATI3
AT+CCID?
AT+CIMI
AT!ENTERCND="A710"
AT!SKU?
AT!HWID?
AT!IMPREF?
AT!PRIID?
AT!USBCOMP?
AT!GSTATUS?
AT+COPS?
AT+CGDCONT?
AT!UIMS?
AT!BAND?

```

---

<div class="post-metadata">

**Author:** ![greg.wood](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@greg.wood](https://forum.sierrawireless.com/u/greg.wood)\
**Post date:** [January 14, 2022, 1:58pm UTC](https://forum.sierrawireless.com/t/em7565-no-network-service/25959/3 "2022-01-14T13:58:21Z")

</div>

Here you are:

Working unit:

ati3  
Manufacturer: Sierra Wireless, Incorporated  
Model: EM7565  
Revision: SWI9X50C\_01.08.04.00 dbb5d0 jenkins 2018/08/21 21:40:11  
IMEI: 353533101687104  
IMEI SV: 8  
FSN: UF043201540210  
+GCAP: +CGSM

OK

at+ccid?  
+CCID: 89302780201326768169

OK  
at+cimi  
302780002735351

OK  
at!entercnd=“A710”  
OK  
at!sku?  
SKU: 1104207

OK  
at!hwid?  
Revision: 1.0

OK  
at!impref?  
!IMPREF:  
preferred fw version: 01.08.04.00  
preferred carrier name: GENERIC  
preferred config name: GENERIC\_002.011\_000  
current fw version: 01.08.04.00  
current carrier name: GENERIC  
current config name: GENERIC\_002.011\_000

OK

at!priid?  
PRI Part Number: 9908685  
Revision: 002.004  
Customer: Generic-M2M

Carrier PRI: 9999999\_9907259\_SWI9X50C\_01.08.04.00\_00\_GENERIC\_002.011\_000  
Carrier PRI: 9999999\_9907258\_SWI9X50C\_01.07.02.00\_00\_ATT\_002.008\_004  
Carrier PRI: 9999999\_9908609\_SWI9X50C\_01.09.04.00\_00\_DOCOMO\_002.015\_000  
Carrier PRI: 9999999\_9908789\_SWI9X50C\_01.08.04.00\_00\_SIERRA\_002.001\_000  
Carrier PRI: 9999999\_9908607\_SWI9X50C\_01.09.04.00\_00\_SOFTBANK\_002.017\_000  
Carrier PRI: 9999999\_9909446\_SWI9X50C\_01.08.04.00\_00\_SPRINT\_000.001\_001  
Carrier PRI: 9999999\_9909335\_SWI9X50C\_01.07.02.00\_00\_TELUS\_001.000\_000  
Carrier PRI: 9999999\_9907257\_SWI9X50C\_01.08.04.00\_00\_VERIZON\_002.015\_001

OK

at!USBCOMP?  
Config Index: 1  
Config Type: 3 (Generic)  
Interface bitmask: 0000010D (diag,nmea,modem,rmnet0)

OK

at!gstatus?  
!GSTATUS:  
Current Time: 325 Temperature: 33  
Reset Counter: 1 Mode: ONLINE  
System mode: LTE PS state: Attached  
LTE band: B7 LTE bw: 20 MHz  
LTE Rx chan: 2850 LTE Tx chan: 20850  
LTE SSC1 state:ACTIVE LTE SSC1 band: B4  
LTE SSC1 bw : 20 MHz LTE SSC1 chan: 2200  
LTE SSC2 state:ACTIVE LTE SSC2 band: B7  
LTE SSC2 bw : 10 MHz LTE SSC2 chan: 3000  
LTE SSC3 state:NOT ASSIGNED  
LTE SSC4 state:NOT ASSIGNED  
EMM state: Registered Normal Service  
RRC state: RRC Connected  
IMS reg state: No Srv

PCC RxM RSSI: -80 PCC RxM RSRP: -110  
PCC RxD RSSI: -76 PCC RxD RSRP: -104  
SCC1 RxM RSSI: -84 SCC1 RxM RSRP: -115  
SCC1 RxD RSSI: -80 SCC1 RxD RSRP: -110  
SCC2 RxM RSSI: -78 SCC2 RxM RSRP: -113  
SCC2 RxD RSSI: -71 SCC2 RxD RSRP: -104  
Tx Power: – TAC: 0014 (20)  
RSRQ (dB): -8.7 Cell ID: 0116f205 (18280965)  
SINR (dB): 17.6

OK  
at+cops?  
+cops: 0,0,“SaskTel”,7

OK  
at+CGDcont?  
+CGDCONT: 1,“IPV4V6”,“inet.stm.sk.ca”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0

OK  
at!uims?  
!UIMS: 0

OK  
at!band?  
Index, Name, GW Band Mask L Band Mask 1 TDS Band Mask L Band Mask 2 L Band Mask 3 L Band Mask 4  
00, All bands 100600000EC00000 0000A700BA0E19DF 0000000000000000 0000000000000002 0000000000000000 0000000000000000

OK

Failing unit:

ati3  
Manufacturer: Sierra Wireless, Incorporated  
Model: EM7565  
Revision: SWI9X50C\_01.14.02.00 2e210b jenkins 2020/08/19 14:18:39  
IMEI: 353533100115214  
IMEI SV: 12  
FSN: UF904586700215  
+GCAP: +CGSM

OK

at+ccid?  
+CCID: 89302780201327989426

OK

at+cimi  
302780002857457

OK

at!entercnd=“A710”  
OK

at!sku?  
SKU: 1104207

OK

at!hwid?  
Revision: 1.0

OK

at!impref?  
!IMPREF:  
preferred fw version: 01.14.02.00  
preferred carrier name: GENERIC  
preferred config name: GENERIC\_002.035\_003  
preferred subpri index: 000  
current fw version: 01.14.02.00  
current carrier name: GENERIC  
current config name: GENERIC\_002.035\_003  
current subpri index: 000

OK

at!priid?  
PRI Part Number: Unknown  
Revision: Unknown  
Customer: Unknown

Carrier PRI: 9999999\_9907259\_SWI9X50C\_01.14.02.00\_00\_GENERIC\_002.035\_003

OK

at!usbcomp?  
Config Index: 1  
Config Type: 1 (USBIF)  
Interface bitmask: 0000100D (diag,nmea,modem,mbim)

OK  
at!gstatus?  
!GSTATUS:  
Current Time: 192 Temperature: 27  
Reset Counter: 1 Mode: ONLINE  
System mode: LTE PS state: Attached  
LTE band: B7 LTE bw: 20 MHz  
LTE Rx chan: 2850 LTE Tx chan: 20850  
LTE SCC1 state:NOT ASSIGNED  
LTE SCC2 state:NOT ASSIGNED  
LTE SCC3 state:NOT ASSIGNED  
LTE SCC4 state:NOT ASSIGNED  
EMM state: Registered Normal Service  
RRC state: RRC Idle  
IMS reg state: No Srv

PCC RxM RSSI: -81 PCC RxM RSRP: -112  
PCC RxD RSSI: -86 PCC RxD RSRP: -117  
Tx Power: – TAC: 0014 (20)  
RSRQ (dB): -10.8 Cell ID: 0116f205 (18280965)  
SINR (dB): 8.8

OK  
at+cops?  
+cops: 0,0,“SaskTel”,7

OK  
at+cgdcont?\>  
+CGDCONT: 1,“IPV4V6”,“inet.stm.sk.ca”,“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0  
+CGDCONT: 2,“IPV4V6”,"",“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0  
+CGDCONT: 3,“IPV4V6”,"",“0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0”,0,0,0,0

OK  
at!uims?  
!UIMS: 0

OK  
at!band?  
Index, Name, GW Band Mask L Band Mask 1 TDS Band Mask L Band Mask 2 L Band Mask 3 L Band Mask 4  
00, All bands 100600000FC00000 0000A700BA0E19DF 0000000000000000 0000000000000002 0000000000000000 0000000000000000

OK

Thanks for the help.

---

<div class="post-metadata">

**Author:** ![anon56110884](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@anon56110884](https://forum.sierrawireless.com/u/anon56110884)\
**Post date:** [January 14, 2022, 5:59pm UTC](https://forum.sierrawireless.com/t/em7565-no-network-service/25959/4 "2022-01-14T17:59:49Z")

</div>

Issue is probably because problem modem is set to MBIM.

> at!usbcomp?  
> Config Index: 1  
> Config Type: 1 (USBIF)  
> Interface bitmask: 0000100D (diag,nmea,modem,mbim)  
> OK

Change it to rmnet like the other modem:

> AT!ENTERCND=“A710”  
> AT!USBCOMP=1,1,10D  
> AT!RESET

After reset, AT!SCACT=1,1 should work.

---

<div class="post-metadata">

**Author:** ![greg.wood](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@greg.wood](https://forum.sierrawireless.com/u/greg.wood)\
**Post date:** [January 14, 2022, 7:04pm UTC](https://forum.sierrawireless.com/t/em7565-no-network-service/25959/5 "2022-01-14T19:04:50Z")

</div>

Brilliant! It’s working now. Thanks.

One small issue remains. On the original EM7565 the control port ( the one I send AT commands to) enumerated as /dev/ttyUSB2, on this one it is /dev/ttyUSB0. On both cards I get USB0 through USB2, but the ordering seems to have changed.

I have a script that runs on boot and sends the at!scact=1,1 command to the radio. Right now this script assumes the control port is the last of the /dev/ttyUSB devices added by the GobiSerial driver. Is there a way to determined which port is which without need to open and test each port?

---

<div class="post-metadata">

**Author:** ![Donald](https://avatars.discourse-cdn.com/v4/letter/d/ac8455/32.png) [@Donald](https://forum.sierrawireless.com/u/Donald)\
**Post date:** [January 19, 2022, 4:51am UTC](https://forum.sierrawireless.com/t/em7565-no-network-service/25959/6 "2022-01-19T04:51:12Z")

</div>

Hi greg.wood,

Please change it to AT!USBCOMP=1,3,10D same as a working module:

```auto
<Config Type> : 3 Generic
<Interface bitmask>: 0000010D (diag,nmea,modem,rmnet0)

```

```auto
AT!ENTERCND="A710"
AT!USBCOMP=?
AT!USBCOMP=1,3,10D
AT!RESET
AT!ENTERCND="A710"
AT!USBCOMP?                                                                     
Config Index: 1                                                                 
Config Type: 3 (Generic)                                                       
Interface bitmask: 0000010D (diag,nmea,modem,rmnet0)                            
                                                                                
OK    

```

/dev/ttyUSB2 is AT port.

---

<div class="post-metadata">

**Author:** ![greg.wood](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@greg.wood](https://forum.sierrawireless.com/u/greg.wood)\
**Post date:** [January 19, 2022, 1:47pm UTC](https://forum.sierrawireless.com/t/em7565-no-network-service/25959/7 "2022-01-19T13:47:10Z")

</div>

That did the trick, thanks.

---

<div class="post-metadata">

**Author:** ![Donald](https://avatars.discourse-cdn.com/v4/letter/d/ac8455/32.png) [@Donald](https://forum.sierrawireless.com/u/Donald)\
**Post date:** [January 21, 2022, 12:23am UTC](https://forum.sierrawireless.com/t/em7565-no-network-service/25959/8 "2022-01-21T00:23:44Z")

</div>

Closed on January 21, 2022, 12:23am UTC


