M66 problem with connecting to SPP device

Hello,
I have a problem with connecting to SPP device. Pairing is successful, but when I try to connect I get error, nevermind if I use AT+QBTCONN or AT+QBTCONND, still got errors.
The external device is working because I am able to connect with android device, PC, etc.

I’m using the last documentation that I found:
Quectel_GSM_BT_Application_Note_V1.2.pdf

This is the communication log:
->ATI
Quectel_Ltd
Quectel_M66
Revision: M66FAR02A05BT OK
-> AT+QBTSCAN
AT+QBTSCAN OK
+QBTSCAN: 1,“BarCode Scannerspp”,AAA8AC30A8FD
-> AT+QBTSCANC
AT+QBTSCANC
+QBTSCAN: 0 OK
-> AT+QBTPAIR=1
AT+QBTPAIR=1 OK
+QBTPAIR: “BarCode Scannerspp”,AAA8AC30A8FD
-> AT+QBTPAIRCNF=1,“0000”
AT+QBTPAIRCNF=1,“0000” OK
+QBTPAIRCNF: 1,1,1,“BarCode Scannerspp”,AAA8AC30A8FD
-> AT+QBTGPROF=1
AT+QBTGPROF=1
+QBTGPROF: 0,“SPP” OK
-> AT+QBTSTATE
AT+QBTSTATE
+QBTSTATE: 5
+QBTSTATE: 0,1,“BarCode Scannerspp”,AAA8AC30A8FD OK
-> AT+QBTCONND=AAA8AC30A8FD,0
AT+QBTCONND=AAA8AC30A8FD,0 OK
+QBTIND: “disc”,0,1,“BarCode Scannerspp”,AAA8AC30A8FD,“SPP”
+CME ERROR: 8018
-> AT+QBTCONND=AAA8AC30A8FD,1
AT+QBTCONND=AAA8AC30A8FD,1 OK
+QBTIND: “disc”,0,1,“BarCode Scannerspp”,AAA8AC30A8FD,“SPP”
+CME ERROR: 8018
-> AT+QBTCONND=AAA8AC30A8FD,2
AT+QBTCONND=AAA8AC30A8FD,2 OK
+QBTIND: “disc”,0,1,“BarCode Scannerspp”,AAA8AC30A8FD,“SPP”
+CME ERROR: 8018 CLOSED
-> AT+QBTCONN=1,0,0
AT+QBTCONN=1,0,0 OK
+QBTIND: “disc”,0,1,“BarCode Scannerspp”,AAA8AC30A8FD,“SPP”
+CME ERROR: 8018
-> AT+QBTCONN=1,0,1
AT+QBTCONN=1,0,1 OK
+QBTIND: “disc”,0,1,“BarCode Scannerspp”,AAA8AC30A8FD,“SPP”
+CME ERROR: 8018
-> AT+QBTCONN=1,0,2
AT+QBTCONN=1,0,2 OK
+QBTIND: “disc”,0,1,“BarCode Scannerspp”,AAA8AC30A8FD,"SPP
+CME ERROR: 8018 CLOSED

Any help will be appreciated.
Thanks.

Dear Sir,
Thanks for your inquiry in Quectel forums.Please check the following answers to your question.

  1. If you use AT+QBTCONND to connect, could you try to follow up the example to add password ?
    image
    image

  2. If you use AT+QBTCONN to connect it, whether the external device receive any indication information? How about use external device to connect the module to have a try ? Thanks!

Hello,
It seems that this was temporary problem with the module.
After rebooting everything is OK now.
Thanks.