+QMTOPEN: 0,-1 error

Please email to support@quectel.com to get the latest firmware and upgrade it to have a try. If it is still have such issue, please also email to such address to get the debug log catch tool and feedback the debug log to us.Then we will help to analyze it. Thanks!

I e-mailed support@quectel.com last friday and I still have not received an answer from you.
Also I sent one more email today

Do not worry about it. The FAE who in charge of your country will answer your email. Please be patient. Thanks!

@Kyson
Hi~~ I e-mailed support@quectel.comtwo weeks ago and I still have not received an answer from you.
Should I wait for a bit more?

@Maker_i
You need the latest firmware of EC25E, right?
If yes, please click the following link to download it. Thanks!
https://cnquectel-my.sharepoint.com/:u:/g/personal/asean-fae_quectel_com/EcpbVIk4FfhPqgjnoKfQSqoBYHM4L3jwVA8a-coPIk0hdw?e=fmbahT

About the support email, please provide the email screenshot that you have sent, and your country, your company name. I will notify the local FAE internal. Thanks!

Hello, I am testing with a EC25 mini PCIe module and getting similar results with +QMTOPEN: 0,-1 as a response to the command QMTOPEN. I am also using AWS IoT core with SSL setttings and certificates, and our code has been tested with BG96 module working, so there should not be an issue about the certificates.

The firmware version of our module is EC25AFFAR07A08M4G.

Has anybody solved this issue? IS EC25 capable of working with AWS IoT core through MQTT?

This is a Log with the commands we are using.

OK
AT+CPIN?
+CPIN: READY

OK
AT+CREG?
+CREG: 0,1

OK
AT+CEREG?
+CEREG: 0,1

OK
AT+QNWINFO
+QNWINFO: “FDD LTE”,“310260”,“LTE BAND 2”,775

OK
AT+QCSQ
+QCSQ: “LTE”,50,-78,188,-14

OK
AT+GSN
866834041644845

OK
AT+COPS?
+COPS: 0,0,“T-Mobile”,7

OK
AT+GMR
EC25AFFAR07A08M4G

OK
AT+QICSGP=1
+QICSGP: 1,“fast.t-mobile.com”,"","",0

OK
Performing AWS Provisioning
AT+QFDEL="*"
OK
AT+QFUPL=“RAM:cacert.pem”,1188,100
CONNECT
+QFUPL: 1188,2d13

OK
AT+QFUPL=“RAM:user_key.pem”,1679,100
CONNECT
+QFUPL: 1679,4b38

OK
AT+QFUPL=“RAM:client.pem”,1220,100
CONNECT
+QFUPL: 1220,3500

OK
AT+QIACT?
OK
AT+QIACT=1
OK
AT+QMTCFG=“SSL”,0,1,2
OK
AT+QSSLCFG=“clientcert”,2,“RAM:client.pem”
OK
AT+QSSLCFG=“clientkey”,2,“RAM:user_key.pem”
OK
AT+QSSLCFG=“cacert”,2,“RAM:cacert.pem”
OK
AT+QSSLCFG=“seclevel”,2,2
OK
AT+QSSLCFG=“sslversion”,2,4
OK
AT+QSSLCFG=“ciphersuite”,2,0xFFFF
OK
AT+QSSLCFG=“ignorelocaltime”,2,1
OK
AT+QMTOPEN?
OK
AT+QMTOPEN=0,“a1gfgsfcsg3p4-ats.iot.us-east-1.amazonaws.com”,8883
OK

+QMTOPEN: 0,-1

Regards

Hi, I also meet this issue. I write in C code. And I turn the certificate into hex file, and add \r to end of each line, fail. Then \r\n, then \n, all fail. So how do you fix this?

Open your aws certificates in Notepadd++. and choose the format windows(CR LF) from the right side down. Then check the length displayed in the Notepad++. This should match with the numbers of characters you have written in your code

Is this format right? Each and of line shoud be /r/n(CRLF)? Or just /r(CR)?Or just /n(LF)

I put them into a cha buffer. Here is my log, I think the length is same with what you said in this issue.
[12:23:24.873]收←◆AT+QMTCFG=“SSL”,0,1,2
OK

[12:23:27.837]收←◆AT+QMTCFG=“version”,0,4
OK

[12:23:30.801]收←◆AT+QFUPL=“ufs:cacert.pem”,1208,100
CONNECT

ready to write

[12:23:31.902]收←◆Write CA!

[12:23:36.797]收←◆+QFUPL: 1208,5769

OK

[12:23:39.760]收←◆AT+QFUPL=“ufs:clientcert.pem”,1244,100
CONNECT

ready to write

[12:23:40.868]收←◆Write certificate!

[12:23:45.761]收←◆+QFUPL: 1244,771c

OK

[12:23:48.724]收←◆AT+QFUPL=“ufs:clientkey.pem”,1702,100
CONNECT

ready to write

[12:23:49.871]收←◆Write private key!

[12:23:54.765]收←◆+QFUPL: 1702,2f24

OK

[12:23:57.730]收←◆AT+QSSLCFG=“cacert”,2,“ufs:cacert.pem”
OK

[12:24:00.694]收←◆AT+QSSLCFG=“clientcert”,2,“ufs:clientcert.pem”
OK

[12:24:03.657]收←◆AT+QSSLCFG=“clientkey”,2,“ufs:clientkey.pem”
OK

[12:24:06.621]收←◆AT+QSSLCFG=“seclevel”,2,2
OK

[12:24:09.585]收←◆AT+QSSLCFG=“sslversion”,2,4
OK

[12:24:12.548]收←◆AT+QSSLCFG=“ciphersuite”,2,0XFFFF
OK

[12:24:15.511]收←◆AT+QSSLCFG=“ignorelocaltime”,2,1
OK

[12:24:21.414]收←◆AT+QMTOPEN=2,"a2q1awzao9n7sa-ats.iot.cn-northwest-1.amazonaws.c
+QMTOPEN: 2,0

[12:24:26.378]收←◆AT+QMTCONN=2,“Rak_Wisblock_Mqtt”
OK

+QMTSTAT: 2,1

HI,
The Certificates size is ok. What is the hex value of CR and LF. it should be 0D and 0A.

if format is wrong the module will, return error
Can work only with /n

Right,CR and LF in the ASCII is 0x0D 0x0A. I put them in the a buffer, end of each line. But now I stuck here after

AT+QMTOPEN=2,"a2q1awzao9n7sa-ats.iot.cn-northwest-1.amazonaws.c
+QMTOPEN: 2,0

AT+QMTCONN=2,“Rak_Wisblock_Mqtt”
OK

+QMTSTAT: 2,1

hi…
please download the example code for MQTT with SSL from below link.
https://cnquectel-my.sharepoint.com/:u:/g/personal/india-fae_quectel_com/EQDRByaRx8pNvcsYbDY29ywBJdEibOlptCcTc0vRvgFgXQ?e=geR2Bw

Regards
Rahul

The connection seems to be closed by aws. Might be a client ID name issue or some policy issues with this ID. Check the aws configurations and ensure everything is right there

Hi All
Please find the below working AT logs for AWS SSL for EC2X. Hope so will help.

ATE1

OK
AT+CGREG?

+CGREG: 0,1

OK

+QIND: PB DONE
AT+COPS?

+COPS: 0,0,“IND airtel airtel”,0

OK
AT+QICSGP=1,1,“airtelgprs.com”,"","",1

OK
AT+QIACT=1

OK
AT+QIACT?

+QIACT: 1,1,1,“100.94.195.55”

OK
AT+QFUPL=“RAM:cacert.pem”,1206,100

CONNECT
+QFUPL: 1206,5a63

OK
AT+QFUPL=“RAM:clientcert.pem”,1220,100

CONNECT
+QFUPL: 1220,6118

OK
AT+QFUPL=“RAM:clientkey.pem”,1675,100

CONNECT
+QFUPL: 1675,1612

OK
AT+QMTCFG=“SSL”,0,1,2

OK
AT+QMTCFG=“recv/mode”,0,0,1

OK
AT+QSSLCFG=“cacert”,2,“RAM:cacert.pem”

OK
AT+QSSLCFG=“clientcert”,2,“RAM:clientcert.pem”

OK
AT+QSSLCFG=“clientkey”,2,“RAM:clientkey.pem”

OK
AT+QSSLCFG=“seclevel”,2,2

OK
AT+QSSLCFG=“sslversion”,2,4

OK
AT+QSSLCFG=“ciphersuite”,2,0xFFFF

OK
AT+QSSLCFG=“ignorelocaltime”,2,1

OK
AT+QSSLCFG=“ignoremulticertchainverify”,2,1

OK
AT+QMTOPEN=0,“a1twhjugwcsoyn-ats.iot.us-west-2.amazonaws.com”,8883

OK

+QMTOPEN: 0,0
AT+QMTCONN=0,“clientexample”

OK

+QMTCONN: 0,0,0
AT+QMTPUB=0,1,1,0,“test/topic”

this is the test

OK

+QMTPUB: 0,1,0

Hi Maker!, I’m getting the +QMTOPEN: 0,1 error in the bg96, How did you get rid of it? I’ve tried many different things but don’t work. :frowning: , I think it’s something when storing the certificates but I can not figure it out. These are the Commands I used:
QMTOPEN- 0,-1.pdf (18.0 KB)

Hi Azael ,

Please try your MQTT with MQTT.fx or some other application to check if your broaker is working fine .
If that is working then you can follow up example provided in BG96 MQTT application note .

How did you read the three files from memory?
You count last \r or not.

Hi,
If your file are stored in UFS,you can use the following command to query:
AT+QFLST=“UFS:*”