Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some information about my wifi dongle problems #52

Closed
brainfoolong opened this issue Dec 25, 2020 · 0 comments
Closed

Some information about my wifi dongle problems #52

brainfoolong opened this issue Dec 25, 2020 · 0 comments
Assignees

Comments

@brainfoolong
Copy link

Hi maintainers. This is just a short information about my previous wifi obd dongle problems. Hope this help someone out, for further debugging and tests. The root cause is not ELMduino, this library work as expected.

I've submitted a pull request for the connected state problem a while ago. And what i can say, WIFI_MODE doesn't fix anything :) Sorry for the wrong input last time.

Here is my summary of what is going wrong on the side of Wifi. I've debugged days with a lot of different adapters.

ESP32 and ESP8266 both have unreliable wifi network

This is the base problem. All ESP32 and ESP8266 modules i've tested (5 different) have the same issues. Sending a raw AT Command works fine. Like for example AT @1. Receiving the answer as difficult.

  1. Most of the time, you get back what you have sent. For example AT @1 including some weird characters at the end, mostly ?.
  2. Once in a while, you get the correct answer, in the case of the example AT command, this is something like OBDII RS232 to xxx Interpreter. You can improve this behaviour when setting setNoDelay(true) on the WifiClient -> https://arduino-esp8266.readthedocs.io/en/latest/esp8266wifi/client-class.html#setnodelay
  3. I wrote a testscript that just send this one command in a interval of 1 second. 76 of 100 received trash data. Only 24 received correct data.
  4. It doesnt matter how long you wait for data to be received, after the trash data is received, which curiously correctly is terminated with an >, there is no more data the comes down the line. Only after sending another AT command, you get back data.

ESP32 BluetoothSerial

Same code as above for Wifi (Except the wifi client changes with BT Serial), work without problems and 100 of 100 requests receive correct data.

Testscenario - All show similar results

  • 3 different ESP32 and 2 different ESP8266 modules
  • 7 different OBD2 Wifi dongles, from cheap to more expensive
  • I have also tested all wifi adapters with a smartphone app that can send serial messages. Here it work without any problems. So all tested wifi adapters are generally fine and work as expected.

Conclusion

Don't use OBD2 WIFI adapters on ESP32 or ESP8266. You will have troubles.

I wanted to write down my testing hell of the last days, to help others with my experience.

Have nice holidays. Cya.

@brainfoolong brainfoolong added the bug Something isn't working label Dec 25, 2020
@PowerBroker2 PowerBroker2 removed the bug Something isn't working label Dec 25, 2020
@PowerBroker2 PowerBroker2 pinned this issue Mar 14, 2021
@PowerBroker2 PowerBroker2 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants