Command timeouts

[Chaoscontrol]

This is probably not a server issue, but I'm asking for support.

When I send any command to the car, I just get timeouts. I'm using Hologram SIM, and I have checked the dashboard and the SMS gets sent and delivered.

But I get no data from the car.

Here's my vflash file:

I was using the 2nd connection at some point as I was testing my private sever on the HA addon, and weirdly it was still sending the data to the public server. That stopped working at some point.

I changed the connection in the car to the Public server. It gets connection, because on every car start I get a TTS message about OCW release notes (a bit annoying as it happens always). It means it is connecting fine.

But when sending a command (any), it gets a timeout.

I have also tried removing the car from OCW and adding it again.

Anything I can do to debug this?

[wados77]

I had the same issue and can't understand why 'carwings' in the navi unit can get data from my server, but TCU has timeouts during send the commands and I didn't have any data in "Overview", "EV Status", "TCU Configuration" tabs and on main screen.
After some research, I found that configuration with LeafSDTools related to configuration navi unit, but to be able to communicate with TCU, this device must be configured with tcu-configurator-1.0.0.4.apk, after configuration has been done, I've got a fully working opencarwings server, be sure that your server can provide access to TCP 55230 port as well.

[Chaoscontrol]

Thanks. I'm using the public server.

It's true I've never configured the TCU using the apk (as my OBD is BLE and it's not supported yet) but even without it, I got OCW commands working at some point.

It was only after flashing a second connection and some tests I did with a private server that it stopped working I think. Now Idk how to fix it. :S

[Chaoscontrol]

After trying 2 more OBD2 adapters, the 3rd one finally worked. It connected fine, and I could finally read some TCU values. I could read VIN and one or two more. Most others returned an error about length mismatch.

https://xfiles.s-ul.eu/tK8xv9X2

Still I tried writing the APN Name and the Write worked. After that I tried sending a command again from OCW, and it FINALLY worked. So it seems to confirm my TCU was somehow stuck on an old APN (no clue how it worked on my first days with OCW).

Now I have different questions.

1. What might be the issue in the app for the length mismatch and reading all the other values?
2. What is the difference between the "Refresh data" and the "Read configuration" commands?
3. When using both, the coloured "LED" changes to green, confirming connection (finally). I got some information in the "Basic info" tab, and the "Vehicle journal". But nothing in the "Overview", "TCU Configuration" or other tabs. Any idea why?
4. When trying for example the A/C On command, I don't get a timeout anymore. The LED turns to green, but I don't get confirmation of the A/C turning On, and I've waited in the car and it doesn't turn on. So the server is receiving something, but the car is not running the command. What might be wrong?

Thanks.

[Chaoscontrol]

@developerfromjokela Sorry for pinging. It's just I feel stuck with this.

[wados77]

It seems TCU still not configured or not correctly configured.

1. During configuration via "TCU Configurator" use 3 dots, uncheck "Data integrity check", after this, you'll be able to write data into TCU. After writing some fields into TCU, try to read it, the value needs to be as you wrote before (sometimes it's not, at least I have such behavior).
2. "Refresh data" seems to refresh all data from TCU, "Read configuration" seems related to read "TCU configuration" only, IMHO
3. Related to 1.
4. Related to 1.

You can check the link below there use english subtitles
https://www.youtube.com/watch?v=syjwgkja03s

Regards.

[Chaoscontrol]

Thanks, I hadn't thought of trying to remove the "Data integrity check". Removing it I was able to read from all fields.

APN Name is correct, and Server hostname is correct as well. I have wrote both of them again to make sure. See video.

Then I turn the car off, I send a "Refresh data" command, and the LED turns green, but no data shows up in OCW. No toast notification of successful command.

I honestly don't understand what's wrong and would like to understand why the LED turns green.

The "Basic data" tab does have data, and also shows updated to my last attempt.

[micvppl]

I have some kind same situation with Leaf ZE0.

• SIM tested on 2G phone, works without issues (SMS, DATA)
  Polish pre-paid SIM from Play GSM
• Navi flashed and connecting (info present in OCW)
• TCU (2G) reconfiguration with android app 1.04
  Write probably works as i got confirmation in app that data was written
  Read does not work, got errors
  Disconnected and connected TCU few times
  Will try other ODBII as Im using cheep blue ELM327 which btw. has no problem working with LeafSpy and Torque
• TCU commands timeout, no basic info
  when i send command it sometimes shows green toast Connection established! but no data update and i see only errors Refresh data timed out after 5 minutes in Recent Alerts on OCW

BTW. great two video instructions I followed with PL and EN audio:

• https://www.youtube.com/watch?v=dJCob1zvT-c (TCU configuration)
• https://www.youtube.com/watch?v=SAIx7u6rNuc (NAVI flashing)

[Chaoscontrol]

See my comment above. My OBD2 works and writes fine, like yours. I could even read all the values too. After updating the APN Name I saw a difference, which is that the commands don't timeout anymore. They now change LED to green. But still no data is received except the "Basic info" tab which shows updated data.

[micvppl]

Hi, yes i saw Your post.
Mine ODB can only write, but i didn't tried to update host URL yet as I have EU version.
Sometimes when I execute commands they give me toast green Connection established! but dot is not turning green.
I believe in my case dot turns green when Navi connects when car is on, because it turned green when i flashed Navi and successfully connected with user/pass in Navi Carwings config.
What can be important, Im not using hologram, just simple pre-paid SIM from Polish operator.

[Chaoscontrol]

Whatever the LED means, it confirms the server is receiving some data from the car. So the SIM Data (APN Name and Server hostname) connection is working.
The issue is either:

• It's sending the wrong or incomplete data.
• Server is not interpreting the data correctly.

Some better log to debug would be helpful. I'll try asking AI about the code to see if I can find something in the meantime till the dev replies.

[Chaoscontrol]

Some findings from AI analyzing the OCW code and my command responses:

{
  "command_result": 1,           // ❌ 1 = Error (from COMMAND_RESULTS)
  "command_result_display": "Error",
  "command_type": 1,             // Refresh data command
  "ev_info": {
    "last_updated": null,        // ❌ Never updated - all zeros
    "soc": 0, "gids": 0, ...
  },
  "tcu_configuration": {
    "last_updated": null         // ❌ Never updated
  }
}

The command_result: 1 means the TCU server sent the command to your car, but the car responded with a failure status.

✅ SIM card works (car connects)
✅ SMS delivery works (last_connection updates)
❌ Command execution fails (command_result: 1)
❌ EV data never populates (ev_info.last_updated: null)

[Chaoscontrol]

Sent! Thanks.

I've also submitted a PR to add a tab showing server logs for our cars. That way we have some better tools to debug ourselves. :) I hope it helps.

[developerfromjokela]

and just as a reminder, have you sent the sms to tcu for wakeup after each command is sent on the website? "NISSAN_EVIT_TELEMATICS_CENTER" must be sent after pressing send command for the TCU to actually make the connection. with hologram this is done using the api key, on other operators you will take care of this happening, either by sending it yourself or making an automation with webhook

[Chaoscontrol]

Yes. It's being sent. I get an email confirmation as well when it happens, and double checked the log in my SIM dashboard too. I use Monogoto, and that's working as I mentioned. The car gets the command, but responds an error. Otherwise the car wouldn't wake up at all to respond.

One thing I realised today was that I hadn't updated my SIM ID after switching SIMs from Hologram to Monogoto. That was dumb. I was expecting that to fix everything, but it really didn't. :( So when checking logs, check the latest ones, as those will have an updated SIM ID.

[developerfromjokela]

Yes. It's being sent. I get an email confirmation as well when it happens, and double checked the log in my SIM dashboard too. I use Monogoto, and that's working as I mentioned. The car gets the command, but responds an error. Otherwise the car wouldn't wake up at all to respond.

One thing I realised today was that I hadn't updated my SIM ID after switching SIMs from Hologram to Monogoto. That was dumb. I was expecting that to fix everything, but it really didn't. :( So when checking logs, check the latest ones, as those will have an updated SIM ID.

I checked the logs, it says TCU reporting SIM ID ending 9979, while the car is configured in settings with one ending 997. So one digit short :D

But how is it that you don't get any errors about this mismatch? I've recently implemented a mechanism to notify these mismatches for diagnosing connection purposes.

[developerfromjokela]

Yes. It's being sent. I get an email confirmation as well when it happens, and double checked the log in my SIM dashboard too. I use Monogoto, and that's working as I mentioned. The car gets the command, but responds an error. Otherwise the car wouldn't wake up at all to respond.
One thing I realised today was that I hadn't updated my SIM ID after switching SIMs from Hologram to Monogoto. That was dumb. I was expecting that to fix everything, but it really didn't. :( So when checking logs, check the latest ones, as those will have an updated SIM ID.

I checked the logs, it says TCU reporting SIM ID ending 9979, while the car is configured in settings with one ending 997. So one digit short :D

But how is it that you don't get any errors about this mismatch? I've recently implemented a mechanism to notify these mismatches for diagnosing connection purposes.

Errors should be visible in recent alerts tab as error notifications with descriptions also.

[Chaoscontrol]

I checked the logs, it says TCU reporting SIM ID ending 9979, while the car is configured in settings with one ending 997. So one digit short :D

Huh? That's really strange. You're right the navi indeed reports that final 9. But my SIM dashboard ends in 7! That's why I was using that.

I added the final 9... and it worked. 😨😨😨😨😨😨😨😨😨😨😨😨 I can't believe it.

Thank you so much.

But how is it that you don't get any errors about this mismatch? I've recently implemented a mechanism to notify these mismatches for diagnosing connection purposes.

Errors should be visible in recent alerts tab as error notifications with descriptions also.

No, nothing showed in "Recent alerts". Only timeouts were showing there. No other message.

[micvppl]

Unfortunetly it does not resolves my situation. I have had same SIM Id in OCW and in TCU a the time.
@developerfromjokela can You please check logs for me also? I have sent VIN on priv

[developerfromjokela]

Unfortunetly it does not resolves my situation. I have had same SIM Id in OCW and in TCU a the time.

@developerfromjokela can You please check logs for me also? I have sent VIN on priv

Hi, I checked the logs but it shows no connection attempts. Are connection parameters correct in the obd configuration app?