Hi,
Do you have a download link of “EPAT.exe” tool to capture log from BC660K-GL-TE board ?
Thanks
JF
hi,jea-francois:
Please download the file from the link below to see if it works.
https://quectel123-my.sharepoint.cn/:u:/g/personal/ae-fae_dom_quectel_com_cn/ETwCJAFaYfxFulqql-AHhPIBoPfRvBHsDmQA5zl1jIRdtA?e=QbgNru
thanks for the link. No exe file found though do you know the link for that?
I have sent it to your email,pls check
Please send me link to epat.exe
I have sent it to your email,pls check
1 Like
Can you please share me
the link for epat.exe.
I have sent it to your email,pls check
thans for your quick reply. I am following EPAT tool giude to capture the logs but I am not getting proper logs at Unilogviewer screen. logs looks as followes.
F âþþþþÿþÿFfþÿüÿÿüÀ¡àPøÿýŠ€ÿÿÿÿüþ²‘Nðþÿÿ
Can you tell me where I am making mistake.
Quectel_EPAT User Guide_BC260Y&BC660K&BC28F&BC95GF&BC300Y&BC950K.pdf (1.9 MB)
please refer to the doc.
Hi,
we are trying attach quectel UE with our eNB we see cell camp success and msg1 and also successfully detected in eNB. some times reached till msg5 also.
But inbetween after msg1 we are seeing phy escape is being triggered most of the time, respective logs are attached here need help in understanding why this is seen. where as same UE is verifed with third party eNB, attach complete will happen consistently their.
20240112_114356_Phy_Escape.zip (2.6 MB)
According to Log analysis, the SNR and some RSRP signals received by the current module are poor. Please confirm whether there is any abnormality in RF or antenna, or you can try again at another location
Hi Herbert, we are using SIMCOM SIM7022, and should need EPAT tool, can you please share it with us? Thank you so much. Salvatore
I have sent it to you
Hello, we also using SIMCOM SIM7022, and for debugging in need of EPAT log tool. Can you please share it. Thank you.
I have sent it to you
HI @herbert.pan-Q ,
I am using SIMCOM_SIM8202G-M2, can you share the EPAT log tool for linux environment?
Thank you
Hi herbert,
I’m using the module BC660K-GL, can you please share the link to EPAT to debbug a problem I have with MQTTS?
I suggest that you send the debug log obtained to me for analysis and provide the complete AT log
I have been trying to connect to my broker through MQTTS following the tutorial in the file: BC660K-GL&BC950K-GL MQTT Application Note.
But when I try to open the connection (AT+QMTOPEN) I get -1 Failed to open network connection.
This happens only when I try to do it through MQTTS, because when I connect only through MQTT (port 1883) I can send messages normally. I have also created a python client to verify that it is not a problem linked to the broker and it is not, the certificates are correct, and the connection works. This is why I am requesting access to the EPAT program to see what is happening and why I can’t connect to my broker.
Here is the procedure I have followed:
AT+QSCLK=0
OK
AT+QSCLK=0
OK
AT+QSSLCFG=0,0,“seclevel”,1
OK
AT+QSSLCFG=0,0,“cacert”
-----BEGIN CERTIFICATE-----
MIICEDCCAZagAwIBAgIUSIuG8XfJU0ArgEut2Ycpr4zlBtswCgYIKoZIzj0EAwMw…
-----END CERTIFICATE-----
+QSSLCFG: 0,0,“cacert”,2783
OK
AT+QSSLCFG=0,0,“clientcert”
-----BEGIN CERTIFICATE-----
MIIEZDCCA0ygAwIBAgIRAIlUVTBqBGkQ9gstjp+4CTQwDQYJKoZIhvcNAQELBQAw…
-----END CERTIFICATE-----
+QSSLCFG: 0,0,“clientcert”,1583
OK
AT+QSSLCFG=0,0,“clientkey”
-----BEGIN RSA PRIVATE KEY-----
MIIEpAIBAAKCAQEAvy4IAgX40TekwTa4QqoH+cQDodrN1r8vEKe+yb4lBrvOPXAB…
-----END RSA PRIVATE KEY-----
+QSSLCFG: 0,0,“clientkey”,1681
OK
AT+QMTCFG=“ssl”,2,1,0,0
OK
AT+QMTCFG=“version”,2,1
OK
AT+QMTOPEN=2,“iot.fr-par.scw.cloud”,8883
OK
+QMTOPEN: 2,-1