On the main screen choose the following options: Choose from Screens: 13 – ECU configuration ADAS.Select your interface, check the box as you are aware that you should not do anything and select “connected mode”.Īctivate the Expert mode (Einstein icon at the top), then select the after sales mode from the drop-down menu. To find out where your ODB socket is, you can visit this site. If the interface appears well, you can go to the vehicle and connect the probe to the ODB socket of the vehicle using the extension . Start DDT4all and check that the interface (connected) is detected by appearing on the first window. On Windows 8 and 10, you may use this method to install the drivers.Ĭopy the DDT2000 database to the C: \ Program Files (x86) \ ddt4all directory. Install the DDT4all application on your computer.ĭownload and install the drivers for the interface ( see this page ). So you have to change the extension to get the following situation: But the calculator of R-Link 1 is on a secondary CAN (12 and 13). Why? The interface is made to work on the classic CAN of the vehicle so pins 6 and 14. The very first thing to do is to modify the ODB extension. Modify an ODB extension like this one (the wires are apparent and easily modifiable):.Find a recent DDT2000 database (it’s up to you).Download the DDT4all software ( click here ), an open source program made by an enthusiast.You can also take a wireless one (I have not tested personally) which will allow later use with a smartphone:.Have an ELM interface (all are not compatible, those are recommended) with the 25k80 chip.Own the latest software version of R-Link 1 ( see this page ).To enable smartphone replication (Android Auto / Apple Carplay) on R-Link 1 there are some prerequisites: As it’s a little mess on the web, so I compiled all the info. No need to ask your garage Renault to do so, its computer equipment is not able to activate the function. Internet is incredible, smart guys have found a way to install Android Auto on all Renault R-Link 1 marketed even the first. This explains that even if it’s frustrating I grant you It was therefore necessary that Renault slightly change its hardware on the R-Link 1 released in 2017 knowing that the validation of the evolutions is a process much heavier in the automobile than in the world of the smartphone for example in particular because there is security issues. It was therefore not possible for Renault to integrate and deploy them on the first versions. But whether it’s Google or Apple, there are hardware requirements that are imposed on car manufacturers. Why the first R-Link 1 are not compatible with Android Auto? R-Link 1 was introduced in 2012, at that time neither Android Auto nor Carplay existed since they were presented in June 20.
0 Comments
Leave a Reply. |