Tweaking the software XC90

[Whippy]

Originally Posted by Quacker

Don't forget the critical adjustment of the sprangleweaver spring, otherwise the frogliodingle capacitor might blow.

Hah! Not so smart are you? That's what the intermediary flange is for! Connect that through a double din to the frogliodingle before applying any current. Simple.

[Quacker]

Originally Posted by Whippy

Hah! Not so smart are you? That's what the intermediary flange is for! Connect that through a double din to the frogliodingle before applying any current. Simple.

Thanks, that's what I always wanted to know but was too embarrassed to ask.

[chocko]

Originally Posted by berrymanuk

you can't tinker with the SPA cars like you could with the older ones. The VIDA app is now cloud based, and requires authentication every time its hooked up to a PC.

I'm gutted too, as there's a few things I could do with enabling on my S90..

If you had access to their domain, QNX Car2 development kit and knew Linux/BSD inside out, pretty sure tinkering would be a breeze! Customisable DIM displays and everything

So if I could handle requirements 1 and 3 how would I get my hands on the required software to setup a server to get my car talking to? I like a challenge.

[Philip Fisher]

Originally Posted by berrymanuk

LOL! Haven't had a chuckle within a forum for a while.

The long story short - VIDA app used to be available on DVD so you could find hooky versions of it, and a volvo-specific OBD-II adapter (big plastic thing tied to a laptop via USB or left free to roam via Bluetooth - but now its fully internet based, with a change in the connection too.

QNX Car2 is the software platform that most car manufacturers - JLR/Volvo/Ford/GM/ - all use for their infotainment and driver information module displays as it stands currently. The actual bit you see - the pretty digital dials, Sensus - is written on AutomotiveLinux (an alternative to Windows/MacOS) which is secure and extensively customisable, within certain constraints of the underlying software.

So does the car run Linux then? I am sure I read it was running Windows behind the interface?

[Philip Fisher]

Originally Posted by chocko

So if I could handle requirements 1 and 3 how would I get my hands on the required software to setup a server to get my car talking to? I like a challenge.

Whilst you are at it, if you could find a way to reprogram it so that it says "bonnet open" rather than the irritatingly american "hood ajar" then I would be most interested

[FooMan]

Originally Posted by chocko

So if I could handle requirements 1 and 3 how would I get my hands on the required software to setup a server to get my car talking to? I like a challenge.

Requirement 1b - their private SSL key and certificate (hopefully)

[berrymanuk]

Originally Posted by Philip Fisher

So does the car run Linux then? I am sure I read it was running Windows behind the interface?

yeah, QNX uses Qt5 on the front of it (framework) and is unix-based at its core. Manufacturers don't use standard Linux, its a flavour called AutomotiveLinux.. https://www.automotivelinux.org/

Android Auto and Apple CarPlay are nothing more than virtual applications that sit on top of AGL/QNX, and interface with appropriate phones/tablets via standard technology such as MirrorLink etc.