-
Notifications
You must be signed in to change notification settings - Fork 2
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
ONE ERROR #7
Comments
"Initialising... The serial monitor keeps saying this." |
Hello.
|
"I am using pins 7 and 8, yes, my car's OBD has a pin 7. I am using the Basic Code, the one with the .ino file." |
"I was able to get a response when I connected the OBD2 device using the 'ISO9141' and 'ISO14230_Slow' protocols. There is no issue with the car." |
"I'm stuck in this loop with the messages: 'Initialising... Received Data: 55 8 8 Received Data: F7'. What could be causing this?" |
"I’m receiving the following responses when using the protocol String protocol = "ISO14230_Fast";: Live Data: Writing Data Received Data: C2 33 F1 1 D F4 Speed: 0 Writing Data Received Data: C2 33 F1 1 C F3 Engine RPM: 0 Writing Data Received Data: C2 33 F1 1 5 EC Coolant Temp: 0 Writing Data" |
Received Data: C2 33 F1 1 5 EC 83 F1 18 7F 1 12 1E |
If you get data like "C2 33 F1 1 5 EC 83 F1 18 7F 1 12 1E", it means your Arduino is connected to car ECU. This request code "C2 33 F1 1 5 EC" is written by Arduino and this "83 F1 18 7F 1 12 1E" is the response of the car, but this response means an error. Can you message me the console output in ISO9141 protocol. |
"Of course, buddy. The result with the 9141 protocol is as follows: Received Data: F7 |
Ops my bad your protocol is ISO14230_Slow but i dont know why your car response like this. What you receive here
after you Arduino is connected to your car? |
"Yes, the Arduino is currently connected to my car. Could there be an issue in the code?" |
Wait, I will modify the code and you will try with the modified code. |
"My friend, I’m waiting excitedly for your response. I’m so grateful for your help, I’ve been working on this for four days now." |
I think I had a bug in the Basic code. Try this code and send me serial output. |
Keep the protocol in automatic mode, don't change it and send me serial output. |
I'm encountering the following error in my new code: C:\Users\elato\AppData\Local\Temp\5631c5f7-2852-428a-a332-5a3985e80d62_Basic_Code.zip.d62\Basic_Code\Basic_Code.ino: In function 'void loop()': exit status 1 Compilation error: 'init_OBD2' was not declared in this scope |
Unzip all the files into one folder and it will work. |
Initialising... |
"I can only see these kinds of values in Fast mode: Speed: 0 (FAST PROTOCOL) |
I don't know why this happens to you. I have tested all the protocols and they worked for me. I guess it's due to the timing because all ECUs send the response at different times. I'll tell you a few things to change and try.
Try these steps separately. Keep the protocol in automatic mode. |
I dont know how you can receive data like this C2 33 F1 1 C F3 83 F1 18 7F 1 12 1E . This means you are initialised in ISO14230_Fast but your protocol is ISO9141. This is very strange. |
"Buddy, I translated it and here’s what happened: Live Data: |
After the last adjustment, the results turned out like this. |
Although a value has been read from the OBD, it's indicating 161 degrees Celsius (based on the conversion from hex C9), which seems to be incorrect. This suggests there's an issue either with how the data is being interpreted or a sensor error. Received Data: 68 6A F1 1 5 C9 |
That means it worked! |
No, this 68 6A F1 1 5 C9 is the request code that the arduino sends, not the response from the ECU. |
Ops my bad not in lines 66 and 70 in lines 99 and 103. if you changed in this lines and the response is this, change the time to 40 in line 99. and in line 103 the code should look like this "if (resultBuffer[1]) {" |
Unfortunately, the result is the same. Are there any other alternatives? |
Which pins do you have in your car's OBD2 port |
Do you still need help? |
Should I provide VCC to the L9637 from the ESP or 12V? |
From ESP |
Is there a 3V output on the ESP that can trigger? |
The ESP is providing 3V; will it be able to trigger the L9637? |
I didn't quite understand what you meant. |
Bro, the ESP8266 is providing a 3V output. Is this 3V enough for the L9637? |
Yes |
The result is still negative; there is no response from the vehicle again. I can't proceed without the serial monitor, so it seems I will have to wait for the ESP32. My only concern is that the L9637's datasheet states an operating voltage of 5V, but you operated it at 3V. |
I made a protocol change, but the result is still the same. While changing the protocol, the Wi-Fi connection keeps disconnecting and reconnecting. Is this normal? |
Where did you read that it says 5 volts see the picture. |
Yes it is normal. |
It was written on the website where I bought the chip; I didn't check the datasheet. My friend, what’s the plan now? What can we do? Should I wait for the ESP32? |
In my opinion, with ESP32 the result will be the same as with Arduino Nano. It does not depend on the microcontroller and with the simplest microcontroller that has a UART it should work. If I find something, I will write to you. |
Are you changing anything in the code at all? |
no |
Can you try this code with Arduino Nano. This code is for ISO9141 only and my first code that I tested in an ISO9141 car and it worked. |
This code doesn't have many features and is very short. |
It got stuck at initializing. |
If it’s working on your Uno like this, the only explanation is that there is an issue with my circuit. |
There was another friend having the same issue, and he recently started a new thread. I’m eagerly waiting for his results. |
Can you show me the schematics you made in detail. |
Received Data: C1 33 F1 81 66 |
I made it on a breadboard for better understanding. I also have the same version on a soldered PCB, and I'm using that one. |
|
The schematic looks good. Just change the protocol to İSO9141 because in this picture it only uses İSO14230 Fast and the car doesn't respond anything and with İSO9141 the car responds well and your car's protocol is İSO9141 |
Initialising ISO9141... |
Bro, I got this response in the short and simple code you gave me." |
"Hello my friend, I hope you're doing well. I made this project and connected everything according to the schematic you showed using Arduino Nano. I also added the code and connected it to the car, but I can't establish communication with the OBD no matter what I do. There's no communication, and I'm about to lose my mind. Can you give me some ideas?"
The text was updated successfully, but these errors were encountered: