What's the point of changing the APN in the TPU?

[Chaoscontrol]

I've set up OCW with the Hologram SIM, and updated the APN in the navigation unit.

I was able to insert the new SIM, but I wasn't able to update the APN in the TPU, because my OBD2 reader is BLE and not supported by the app.

However, since the SIM was in, I could do the OCW set up, and surprisingly it could get all the info from the car! And from the navigation unit as well (once I logged in from the car).

So, if everything can be received without the TPU having the correct APN, what is that setting for? I'm sure I'm missing something, and that's my question.

Thanks!

PS. I am AMAZED at the INSANE amount of info that we get in OCW. This product you've created is INCREDIBLE. Thank you so much.

[developerfromjokela]

I've set up OCW with the Hologram SIM, and updated the APN in the navigation unit.

I was able to insert the new SIM, but I wasn't able to update the APN in the TPU, because my OBD2 reader is BLE and not supported by the app.

However, since the SIM was in, I could do the OCW set up, and surprisingly it could get all the info from the car! And from the navigation unit as well (once I logged in from the car).

So, if everything can be received without the TPU having the correct APN, what is that setting for? I'm sure I'm missing something, and that's my question.

Thanks!

PS. I am AMAZED at the INSANE amount of info that we get in OCW. This product you've created is INCREDIBLE. Thank you so much.

The APN change is needed for remote AC and EV battery info. TCU and navigation unit have separate connection settings, only changing navigation unit will enable carwings while in-car, doing anything outside of car should not work without APN change.

Do these commands and refresh data command work though?

[developerfromjokela]

Uhhh, I don't feel that confident. 😂 I just leave that info with you for now.

Tomorrow I'll test the A/C and charge commands and see if they work.

Any idea why the A/C might not have worked? Prob there wasn't any timer or setting about it.

What conditions have to be fulfilled for the charge to work? Obv cable connected, but usually the charge starts instantly when connected. So I guess I should set a timer so it does NOT start immediately, and then try to send the command to start? Is that the only use (to start a charge earlier than programmed)? It feels a bit strange tbh.

Charging will start immediately via the app command, no timers. And AC will start always with cable plugged in. It will start also without it but until 30 or 20% if I remember. If the battery is too low it won't start

[Chaoscontrol]

Yeah but I mean, how to make the car NOT charge immediately when plugged in? So I can trigger it with the command later.

[developerfromjokela]

Yeah but I mean, how to make the car NOT charge immediately when plugged in? So I can trigger it with the command later.

Oh. I just set a timer to like, Sunday or somewhere far in the future. That way it doesn't start charging after being plugged in

[Chaoscontrol]

That's what I meant.

Any idea why the A/C failed? Oh maybe because the SoC is 22%? Probably yes. I will charge tomorrow and test that.

[Chaoscontrol]

I can now confirm, all commands work without updating the TPU APN.

I just tested, the car started charging, and also started and stopped the A/C while plugged. I did it from the Android app. Worked wonderful.

So I'm not entirely sure of the point of the TPU APN at this point.

I guess I will still change it when BLE are available for the app.

Also, I've seen a strange quirk about the location.

• When reading the data remotely: Ok
• In the Navi: Ok
• Whenever the car starts -> OCW gets a wrong location. Some remote place in the middle of nowhere (about 50km from my location).

If I read data again it updates to my Home (when doing the tests). But whenever I turn off and back on the car, that same location pops up again in OCW. Any idea what might that be?