Hi. I am trying to connect to an ELM327 Bluetooth dongle which is an OBD interpreter using the EC200UEUAA module’s Bluetooth and SPP profile, but when the connection is established, the EC200U module crashes and resets when I run api bt.sppSend(‘ATI\r’). I am using the latest firmware version of this module (V0005) and of course I tested it with version V0004 but the problem still exists. There is no problem in connecting the EC200U to my mobile phone, and the connection is completely established and data is sent and received. On the other hand, there is no problem in connecting my mobile phone to the ELM327. I must say that when I want to connect to the ELM327 with my mobile phone, I need to enter the correct PIN code to pair it, otherwise the pairing will not be done. So we can conclude that probably because the initial communication between EC200U and ELM327 is not established properly, executing bt.sppSend(‘ATI\r’) causes EC200U to crash. (Any data I put in the input argument of bt.sppSend() crashes.) I was able to connect to ELM327 with ESP32 and send and receive data, but we need EC200U to connect to ELM327 in our project. I am using the SPP demo code in the classic bluetooth API Reference to communicate with the mobile and ELM327, which communicates perfectly with the mobile, but with the ELM327 it encounters the problem I mentioned. Even to make sure that a crash occurs when executing bt.sppSend() I used this API after the connection was successful. When communicating with the mobile phone, the API input argument is sent to the mobile phone and the program continues to work. However, when communicating with the ELM327, the EC200U module crashes when the program reaches bt.sppSend(), and it is most likely due to the same PIN code that the ELM327 requires for pairing. I have tested this with several ELM327 Bluetooth dongles and I am having the same problem with all of them (ELM327 Bluetooth module’s is SPP_C or HC_05). Please follow up on this issue and resolve the issue and let me know so that we can move forward with our project using your company’s good module. Thank you very much.
Dear @Amir_Reza_Bahrami ,
Thank you for reaching out with your query,
Im seeing duplicate issue as also this link : Problem communicating between the EC200UEUAA module and the ELM327 (spp_c and hc05 modules) dongle via classic Bluetooth and Quecpython
Could you please confirm whether this is the same inquiry? I understand that my colleague is already handling this via mail.
Thank You and Have a Great Day!
Hi Alvin.
Yes, this is the same inquiry. But unfortunately, because the problem has not been solved, I created another topic to raise my problem to speed up the process of solving the problem, but the problem has not been solved yet. I would like to thank you for following up and solving my problem as soon as possible. Your colleagues @gyc were also very persistent and I thank them. But so far, no results have been achieved.
Dear @Amir_Reza_Bahrami ,
I understood your point,
We actually have reproduce the issue and no issue on our side as per the mail from @gyc .Can you confirm on your side as well?
I tink the main issue here is that we needed is the log files as we need to analysed on our side to get the root couse on the as you mentioned here "However, when communicating with the ELM327, the EC200U module crashes when the program"
At the same time, we need the following details for our records:
- Company full name.
- From where you bought Quectel
module? - Project name (for reference):
- How many modules have you bought?
Thank You and Have a Great Day!
I sent all this information including logs to @gyc and he is following up. Do I need to send it here too?
Dear @Amir_Reza_Bahrami ,
Good Day,
Kindly send the logs here, because this is a new thread of the issue you created. Kindly send all the relevant logs here for us to check internally.
Thank you!
Log.zip (6.1 MB)
SPP_DemoMain.txt (8.7 KB)
Log file uploaded.
Script file uploaded. Note that the script I am running is exactly the same as #SPP Demo Program that is in the bt API reference and I only added bt.sppSend(‘ATZ\r’) on line 175 to send “ATZ\r” immediately after establishing the connection. When connecting EC200u to ELM327 which uses the SPP_C Bluetooth module inside, executing bt.sppSend(‘ATZ\r’) crashes the EC200u module but when connecting to mobile and ESP32, the EC200u module does not crash and sends the phrase “ATZ\r” and continues executing the program.
I have prepared a Bluetooth SPP_C module used in the ELM327 dongle and I have done some experiments by manually executing the Bluetooth APIs in the REPL and I will tell you the results:
The EC200U module can establish SPP communication with the target Bluetooth module with any Pin_code (“0000”, “1234” …) and the problem is not the Pin_code challenge but the EC200U module crashes when communicating with SPP Bluetooth modules and calling bt.SPPSend when the EC200U sends the first data packet. When the target Bluetooth module sends the first data packet to the EC200U, the EC200U module does not crash by calling bt.SPPSend and sends the data to the target Bluetooth module and the connection remains completely healthy until one of the communication elements is disconnected normally. When the connection is established again, the above conditions apply.
The thing is that I can’t do what I did for the Bluetooth module for the ELM327, and in connection with this dongle using the EC200U, the first data packet must be sent by the EC200U to receive a response from the ELM327 (just like the ATCommand mechanism of your company’s modules). I hope this was useful for the troubleshooting process.
This means that when connecting the EC200U to a mobile phone or ESP32, the module will not crash even if the EC200U sends the first data packet.
Dear @Amir_Reza_Bahrami ,
Thank you for the logs.
I have also followed up with my colleagues regarding the analysis conducted on our side. I understand that you mentioned SIMCom modules are able to connect to the ELM327. Let me further consult with our internal team to determine whether there is any available patch or solution to resolve this connection issue.
We will get back to you as soon as possible.
Thank you!