In the last 4 updates I have had problems with the OBD2 Elm327 communication and it has been getting worse, it doesn’t connect, communication drops, incomplete data, do you have any idea what could be happening?
Not much attanetion paid here to OBD2 Elm327 support or impreovement I am afraid.
The latest updates have worsened the obd2 communication and automatic connection, you could see what is happening, before I rarely had this problem.
I think it’s a problem with REALDASH’s bluetooth, now even my hc05 is having connection problems, sometimes it starts to connect and I need to exit the app and return.
The option “connect with ancestors” was removed from realdash? I think that might be the problem.
I have never heard of such an option. What was it called exactly in English version of RealDash?
We have not forgotten the OBD2. True, I personally do not like to work on it because its a terrible mess with all different adapters and vehicles, but we do use it daily with two vehicles and had no issues with connection.
I believe connection issues with OBD2 are related to custom XML. With custom XML there is so many error situations that its not a surprise for me that RealDash cannot handle all of them. And in case of that, RealDash just does disconnect->connect and tries again. I believe that is what you are experiencing.
Without debug logs I can do nothing. I hope you understand that “IT DOES NOT WORK!” doesn’t help. You need to describe the issue in detail, provide steps how the issue can be re-produced, send debug log along with your custom XML file; as a minimum set for analysis.
It would just be nice for RD to see as many sensors (ex. accelerometer) as Torque does with the SAME recomonded OBD (Mx plus), NON XML use.