Hello everyone. Have you updated the units via PF? If so, did you connect an external power supply or is the battery power sufficient? I wanted to update the units, but PF says I need to connect an external power supply just in case.
I've updated most of mine without an external battery maintainer. There was one where I was too scared, so I added a battery charger to it.
Don't talk nonsense, even BMWs won't even start updating until your laptop is connected to an external power supply.
They do update without external chargers. I've done it a few times. Ha!
Thank you for the detailed explanation. I don't understand what all the fuss is about. I initially simply asked/contacted those who had done it and how they did it (I wanted to know how someone had done it in practice). In the end, I'm completely confused. Is it possible to update the batteries by connecting the battery charger, the photo of which I attached above, and connecting the laptop, which has been using its battery for 3.5 hours without 220V?
I've messed around with most if not all modules. I did it with poor battery, charged battery, plugged in, and not plugged in. Car charger and no car charger. Sometimes, there were restrictions, like "the car battery isn't charged enough", "the engine isn't warm enough" and so on.
One time, the laptop freaked out and lost power while communicating with a module. The module was fine. Another module also went crazy, and did stuff without permission. All in all though, they were all successful. I think sometimes, they err on the side of caution to make you take extreme safety measures.
By the way, thanks so much for this amazing thread! Very nice work!
I have no idea what the guy is saying about looking in the logs though. I've looked through hundreds of logs and nothing stands out to me (at the moment).
I've spent HOURS on this and I'm almost there. For those who are interested, there's potentially quite a bit more that needs doing than is mentioned in the thread.
I had a problem where Pathfinder simply could't see the "JLR - JLR-DoIP, D-PDU API by Bosch" device in the settings/configuration menu. It took about 5hrs for me to fix. Basically, to fix that, remove the device, uninstall "MTS633_Setup_R2_4_22_62" and also uninstall the DoIP driver in VX Manager. Restart the PC, install MTS633_Setup_R2_4_22_62, insert the usb device, then install VX Manager JLR DoIP (in VX Manager). It might be related to the VCX mode, as I noticed that after install, it appeared to be in LAN mode rather an USB mode (The VCX device is actually a USB to ethernet device).
There's also an app called vpro.exe and vci-new.exe that you may need those but I'm not 100% sure.
Yu dont need to flick the DoIP switch for it to work. It can do itself.
VIN not supported - it can happen randomly. I think it's something to do with VCI resetting.
I've sort of rambled through a lot of things trying to get it to work.
On Wednesday (with a configuration that I no longer remember), I noticed that DFSM was reachable in the status thing. It's no longer available after all the changes I've made (or maybe it's not available for another reason).
A bit of feedback; The instructions and info is very scattered throughout the thread. It's not a case of saying "Have you not worked it out yet". It's like giving someone a 100 page manual and expecting that someone clueless is able to pick out 20 relevant sentences - some of which conflict!
"VIN not compatible" or whatever it says. Don't think that it's telling the truth, because it's not. This message can come randomly and I think it's something to do with the VCI manager. If it says this, just fiddle around with the VIN placement. Try a different screen, etc.
You can get right the way into PF, and further without connecting the VCX to the OBD port. You can even find vehicle info, and a few other bits. It's good for basic diagnostics.