Leccy61
Well-Known Member
- Joined
- Nov 18, 2024
- Threads
- 4
- Messages
- 311
- Reaction score
- 231
- Location
- United Kingdom
- Vehicles
- Taycan Cross Turismo, 986 Boxster S, VW ID.3 Pro S
Great explaination @D00notD00d .
I’ve come to know more than I wanted having had a few VW group EVs, but the Taycan actually works OK with IO. From an ARB6 limiting perspective haven’t had need to charge beyond 80% since the orange triangle.
EDIT: It just happily charged to 85% under Octopus control ?
PS off-topic: Our VW ID.3 uses the 23:30-05:30 window, but I did briefly connect it to IO, it uses enode same as the Taycan. I suspect enode is where the gremlins are, our Tesla worked flawlessly with IO. Octopus support indicated they were looking to move away from it, but my understanding is enode is how VW does 3rd party access. Regardless, I‘d rather IO controlled our Podpoint, but it isn't supported.
I’ve come to know more than I wanted having had a few VW group EVs, but the Taycan actually works OK with IO. From an ARB6 limiting perspective haven’t had need to charge beyond 80% since the orange triangle.
EDIT: It just happily charged to 85% under Octopus control ?
PS off-topic: Our VW ID.3 uses the 23:30-05:30 window, but I did briefly connect it to IO, it uses enode same as the Taycan. I suspect enode is where the gremlins are, our Tesla worked flawlessly with IO. Octopus support indicated they were looking to move away from it, but my understanding is enode is how VW does 3rd party access. Regardless, I‘d rather IO controlled our Podpoint, but it isn't supported.
Sponsored
Last edited:
