Hello,
I successfully let the BC95-G “autoconnect” with the network. Everything looks good, AT+CGATT? returns 1.
The module also has assigned an IP address.
The next step in order to send a CoAP message is to create a CoAP context:
AT+QCOAPCREATE=56830
But this returns an ERROR with code 4 “Operation not supported”
What’s wrong?
Could ATI please check the bc95-g firmware version number?
‘ATI’ returns
Quectel
BC95-G
Revision:BC95GJBR01A04
‘AT+CGMR’ returns
SSB,V150R100C10B200SP1
SECURITY_A,V150R100C20B300SP2
PROTOCOL_A,V150R100C20B300SP2
APPLICATION_A,V150R100C20B300SP2
SECURITY_B,V150R100C20B300SP2
RADIO,Hi2115_RF0
‘AT+NCONFIG?’ returns
+NCONFIG:AUTOCONNECT,TRUE
+NCONFIG:CR_0354_0338_SCRAMBLING,TRUE
+NCONFIG:CR_0859_SI_AVOID,TRUE
+NCONFIG:COMBINE_ATTACH,FALSE
+NCONFIG:CELL_RESELECTION,TRUE
+NCONFIG:ENABLE_BIP,FALSE
+NCONFIG:MULTITONE,TRUE
+NCONFIG:NAS_SIM_POWER_SAVING_ENABLE,TRUE
+NCONFIG:BARRING_RELEASE_DELAY,64
+NCONFIG:RELEASE_VERSION,13
+NCONFIG:RPM,FALSE
+NCONFIG:SYNC_TIME_PERIOD,0
+NCONFIG:IPV6_GET_PREFIX_TIME,15
+NCONFIG:NB_CATEGORY,1
+NCONFIG:RAI,FALSE
+NCONFIG:HEAD_COMPRESS,FALSE
+NCONFIG:RLF_UPDATE,FALSE
+NCONFIG:CONNECTION_REESTABLISHMENT,FALSE
Your version supports the COAP protocol.
Can you provide the AT process you operate?Or provide me with the UEMonitor log extracted from the lower module DBG port.
Thanks for your support, there is the sequence of AT commands:
For initialization:
AT+NCONFIG=AUTOCONNECT,FALSE
AT+NRB
AT+NBAND=8
AT+QLEDMODE=1
AT+CMEE=1
Some informations:
ATI
Quectel
BC95-G
Revision:BC95GJBR01A04
AT+CGMR
SSB,V150R100C10B200SP1
SECURITY_A,V150R100C20B300SP2
PROTOCOL_A,V150R100C20B300SP2
APPLICATION_A,V150R100C20B300SP2
SECURITY_B,V150R100C20B300SP2
RADIO,Hi2115_RF0
AT+NCONFIG?
+NCONFIG:AUTOCONNECT,FALSE
+NCONFIG:CR_0354_0338_SCRAMBLING,TRUE
+NCONFIG:CR_0859_SI_AVOID,TRUE
+NCONFIG:COMBINE_ATTACH,FALSE
+NCONFIG:CELL_RESELECTION,TRUE
+NCONFIG:ENABLE_BIP,FALSE
+NCONFIG:MULTITONE,TRUE
+NCONFIG:NAS_SIM_POWER_SAVING_ENABLE,TRUE
+NCONFIG:BARRING_RELEASE_DELAY,64
+NCONFIG:RELEASE_VERSION,13
+NCONFIG:RPM,FALSE
+NCONFIG:SYNC_TIME_PERIOD,0
+NCONFIG:IPV6_GET_PREFIX_TIME,15
+NCONFIG:NB_CATEGORY,1
+NCONFIG:RAI,FALSE
+NCONFIG:HEAD_COMPRESS,FALSE
+NCONFIG:RLF_UPDATE,FALSE
+NCONFIG:CONNECTION_REESTABLISHMENT,FALSE
AT+NBAND?
+NBAND:8
Manually connect to the network:
AT+CFUN=1
AT+CEREG=2
AT+CGDCONT=0,“IP”,“iot.1nce.net”
AT+COPS=1,2,“26201”,9
Then I repeatedly do a
AT+CEREG?
Results over time:
+CEREG:2,2,0000,00000000,9
+CEREG:2,2,D325,01D6DF09,9
+CEREG:2,2,D325,01D6DF09,9
+CEREG:2,2,D325,01D6DF09,9
+CEREG:2,2,D325,01D6DF09,9
+CEREG:2,2,D325,01D6DF09,9
+CEREG:2,2,D325,01D6DF09,9
+CEREG:2,5,D325,01D6DF09,9
Yeah … Registered (Roaming) = 5
Again some informations
AT+CGPADDR
+CGPADDR:0,100.68.216.2
AT+CGATT
+CGATT:1
AT+COPS?
+COPS:1,2,“26201”
AT+CGDCONT?
+CGDCONT:0,“IP”,“iot.1nce.net”,0,0,0
Try to create CoAP Context
AT+QCOAPCREATE=56830
+CME ERROR: 4
The AT + QREGSWT?Under the query.
AT + QREGSWT=1 if 2 is returned
What do you mean?
Do you want to try out a AT+QREGSWT?
After AT+QREGSWT=1 instruction, AT+NRB restarts the module and tries again.
hi Wklenk
Has the problem been solved?
I think you mixed it up:
I found some information in the “BC95&BC95-G Difference Introduction” manual that states for BC95-G:
When the Huawei IoT platform is not
used, the platform registration function
needs to be disabled through
AT+QREGSWT=2.
Actually, AT+QREGSWT? returned 1, which indicates that the module is in a mode where it uses the Huawei IoT platform, which I don’t want to.
The solution is to send a AT+QREGSWT=2 followed by a AT+NRB to reboot.
Now, creating a CoAP context with AT+QCOAPCREATE no longer results in an error.
The issue seems to be solved.
Thanks for pointing into this direction.