Ever since the Dashbox protocol was changed to RealDashCAN 2way, I cannot get a stable connection. It connects for a few seconds, then drops the connection, then connects and drops and so on. Works fine with the old xml file format on version 1.6.2. My dashbox uses a serial connection not bluetooth though.
There is a similar issue if I connect the Link ecu directly, it does show data but I get an error message in bottom left corner that the USB connection is not supported. This problem only exists with version that use RealDashCAN 2way protocol for Dashbox.
I do not believe this is related to RealDash CAN protocol. Around that time the Android USB-Serial library that we use was updated and we have heard some complaints with USB connections on Android after that. Seems to happen only on some Android-USB adapter combinations.
What is funny:
In the Arduino Example the MAP: value change until 100.00 and the stop.
Serial connection break, reconnect again and then count further…
170 b3 usb serial problems in RDCan protocol detected. It does not work stably when using several different usb devices(flash,airmouse,ARDUINO). I could not constantly show. Only chaotic. I don’t observe a binding to something. The equipment is the same.
Most likely a serial device conflict.
As always, however.
If I show a malfunction, I can send a log!
I have the same problem since today after updating to version 1.7 under Windows 10. After about 5 seconds there is a timeout and then it takes 2 seconds until it works again for the next 5 seconds.
How can I fix this error?
Greetings René
Hi, I just tested version 1.71. Unfortunately the bug is still there. Now the data is evaluated for about 4 seconds and then the timeout is about 20 seconds until it works again for 4 seconds.
