# Configuring WP7702 for NB-IoT
**URL:** https://mangoh.discourse.group/t/configuring-wp7702-for-nb-iot/1088
**Category:** Uncategorized
**Created:** [January 17, 2018, 12:59pm UTC](https://mangoh.discourse.group/t/configuring-wp7702-for-nb-iot/1088 "2018-01-17T12:59:55Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@basti](https://mangoh.discourse.group/u/basti)
#### Post date: [January 17, 2018, 12:59pm UTC](https://mangoh.discourse.group/t/configuring-wp7702-for-nb-iot/1088/1 "2018-01-17T12:59:55Z")
Hi,
I was informed there is no AT command reference yet for the WP7702 module, but that WP76xx has basically the same commands. I am looking through the reference, but cannot find a way to force it to use NarrowBand IoT.
I need to use either LTE Band 3 or Band 20. But for example when trying `AT!GETBAND?` it throws: `!GETBAND: Unknown`
Any input on this is appreciated! Thanks.
---
### Author:  [@dfrey](https://mangoh.discourse.group/u/dfrey)
#### Post date: [January 17, 2018, 10:54pm UTC](https://mangoh.discourse.group/t/configuring-wp7702-for-nb-iot/1088/2 "2018-01-17T22:54:01Z")
I spoke with someone on the WP77 team and they had this to say:
> Yeah there isn’t a way to force the device into NBIOT mode only right now, that’s still in progress. But we can ask which Release this customer is using. If he’s using Release 7 FW, then he can use AT!SELACQ=LTE-NB1 to force the UE into scanning the LTE NB1 bands first.
> and AT!RESET afterwards to apply the setting
---
### Author:  [@basti](https://mangoh.discourse.group/u/basti)
#### Post date: [January 18, 2018, 6:45am UTC](https://mangoh.discourse.group/t/configuring-wp7702-for-nb-iot/1088/3 "2018-01-18T06:45:17Z")
Thanks for the answer @dfrey. The firmware I am using is version `02.13.02.00`. Not sure what Release it is since it is a custom release provided to us.
Commands returned OK, but I guess there is no way of knowing what network one is using right now? Could you check with the team if there is a AT command reference (other than the WP76xx which states stat !SELACQ is removed) that is up to date for WP77? Thank you again!
---
### Author:  [@mohamid](https://mangoh.discourse.group/u/mohamid)
#### Post date: [January 18, 2018, 11:56pm UTC](https://mangoh.discourse.group/t/configuring-wp7702-for-nb-iot/1088/4 "2018-01-18T23:56:24Z")
Based on my conversation with SW sales team, don’t expect full NB-IOT support until Q2 of 2018
---
### Author:  [@basti](https://mangoh.discourse.group/u/basti)
#### Post date: [January 19, 2018, 11:57am UTC](https://mangoh.discourse.group/t/configuring-wp7702-for-nb-iot/1088/5 "2018-01-19T11:57:23Z")
Okay. But just something I thought about. What if you were to put the modem in LTE mode only, and then set `AT!SELACQ=LTE-NB1`. Wouldn’t that force it to use NB-IoT in theory?
---
### Author:  [@dfrey](https://mangoh.discourse.group/u/dfrey)
#### Post date: [January 19, 2018, 3:56pm UTC](https://mangoh.discourse.group/t/configuring-wp7702-for-nb-iot/1088/6 "2018-01-19T15:56:27Z")
I received another response from the WP77 team member:
> they can use AT+COPS? to check what RAT they are currently registered on, after they have successfully registered on the network.
>
> If the RAT shows as 7, it’s LTE CAT-M1. If it’s 9, then it’s LTE NB1 network. From 3GPP specs 27.007 AT+COPS documentation:
>
> : integer type; access technology selected
> 0 GSM
> 1 GSM Compact
> 2 UTRAN
> 3 GSM w/EGPRS (see NOTE 1)
> 4 UTRAN w/HSDPA (see NOTE 2)
> 5 UTRAN w/HSUPA (see NOTE 2)
> 6 UTRAN w/HSDPA and HSUPA (see NOTE 2)
> 7 E-UTRAN
> 8 EC-GSM-IoT (A/Gb mode) (see NOTE 3)
> 9 E-UTRAN (NB-S1 mode) (see NOTE 4)
---
### Author:  [@basti](https://mangoh.discourse.group/u/basti)
#### Post date: [January 23, 2018, 8:03am UTC](https://mangoh.discourse.group/t/configuring-wp7702-for-nb-iot/1088/7 "2018-01-23T08:03:33Z")
Thanks @dfrey!
With AT+COPS? I got:
> at+cops?
> +cops: 0,0,“244 12 DNA”,9
> OK
So I am guessing it is on NB-IoT now. I also forced RAT to LTE (as I mentioned in the previous comment) just to avoid it switching to GSM.