# Example of succesfull output status command of WP7702 connected to LTE-NB1

**URL:** https://mangoh.discourse.group/t/example-of-succesfull-output-status-command-of-wp7702-connected-to-lte-nb1/9295
**Category:** mangOH Red
**Created:** [June 7, 2021, 6:50am UTC](https://mangoh.discourse.group/t/example-of-succesfull-output-status-command-of-wp7702-connected-to-lte-nb1/9295 "2021-06-07T06:50:59Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![rickvanderzwet](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/rickvanderzwet/32/1881_2.png) [@rickvanderzwet](https://mangoh.discourse.group/u/rickvanderzwet)
#### Post date: [June 7, 2021, 6:51am UTC](https://mangoh.discourse.group/t/example-of-succesfull-output-status-command-of-wp7702-connected-to-lte-nb1/9295/1 "2021-06-07T06:51:00Z")

</div>

I am trying to connect an WP7702 connected to an LTE-NB1 network, using an Vodafone NB-IoT simcard. MangOH is [not listed as one of their preferred devKits](https://www.vodafone.com/business/iot/managed-iot-connectivity/nb-iot#devkits) so I am not 100% sure if NB-IoT is supposed to work at all.

Looking at the forums I cannot see successful connections being made to the LTE-NB1/NB-IoT network, leaves me wondering, is this supported? If so, would anybody be so kind to provide me with a sample output of `cm info`, `cm radio`, `cm data` & `AT!GSTATUS?` (and any other status which is useful). I am very interested how a success established connection looks like.

Thanks in advance!

---

<div class="post-metadata">

### Author: ![jyijyi](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/jyijyi/32/997_2.png) [@jyijyi](https://mangoh.discourse.group/u/jyijyi)
#### Post date: [June 7, 2021, 7:10am UTC](https://mangoh.discourse.group/t/example-of-succesfull-output-status-command-of-wp7702-connected-to-lte-nb1/9295/2 "2021-06-07T07:10:03Z")

</div>

Here i am Ok to register NB network with WP77 module:

```auto

root@fx30:~# microcom /dev/ttyAT
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7702
Revision: SWI9X06Y_02.32.02.00 c2e98c jenkins 2019/08/30 07:28:21
IMEI: 352653090002874
IMEI SV: 4
FSN: VU735370521401
+GCAP: +CGSM

OK
at!selciot?
Current Operating Mode: 0x6

Supported Operating Modes:
LTE WB: 0x01
LTE M1: 0x02
LTE NB1: 0x04

OK
at!gstatus?
!GSTATUS:
Current Time: 537 Temperature: 36
Modem Mitigate Level: 0 ModemProc Mitigate Level: 0
Reset Counter: 1 Mode: ONLINE
System mode: LTE PS state: Attached
IMS reg state: UNKNOWN IMS mode: Not Support
IMS Srv State: UNKNOWN SMS,UNKNOWN VoIP
LTE band: B3 LTE bw: 1.4 MHz
LTE Rx chan: 1486 LTE Tx chan: 19486
LTE CA state: INACTIVE
EMM state: Registered Normal Service
RRC state: RRC Idle

PCC RxM RSSI: -80 RSRP (dBm): -79
PCC RxD RSSI: 0 RSRP (dBm): 0
Tx Power: 0 TAC: 058E (1422)
RSRQ (dB): -3 Cell ID: 06745D1C (108289308)
SINR (dB): -31.0

OK
at+cgdcont?
+CGDCONT: 1,"IP","nbiotdirect","0.0.0.0",0,0,0,0
+CGDCONT: 10,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 11,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 12,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 13,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 14,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 15,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 16,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","nbiotdirect","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
+CGDCONT: 4,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 6,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 7,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 8,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 9,"IPV4V6","","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0

OK
root@fx30:~# cm info
Device: WP7702
IMEI: 352653090002874
IMEISV: 4
FSN: VU735370521401
Firmware Version: SWI9X06Y_02.32.02.00 c2e98c jenkins 2019/08/30 07:28:21
Bootloader Version: SWI9X06Y_02.32.02.00 c2e98c jenki[553.276275] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
ns 2019/08/30 07:28:21
[553.296108] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1300c8 OPER:0x00000090
MCU Version: 002.013
PRI Part Number (PN): 9907365
PRI Revision: 001.001
Carrier PRI Name: GENERIC
Carrier PRI Revision: 001.055_000
SKU: 1103530
Last Reset Cause: Power Down
Resets Count: Expected: 862 Unexpected: 257
root@fx30:~#
root@fx30:~#
root@fx30:~# cm radio
Power: ON
Current Network Operator: CSL
Current RAT: LTE network (LE_MRC_RAT_LTE)
Status: Registered, home network (LE_MRC_REG_HOME)
Signal: Strong signal strength (4)
PS: Packet Switched Registered, home network (LE_MRC_REG_HOME)

root@fx30:~#
root@fx30:~# cm data
Index: 1
APN: nbiotdirect
PDP Type: IPV4
Connected: no
root@fx30:~#

```
