R-LINK 2 BLACK SCREEN REPAIR

Usually the R-LINK devices when you decided to raise the firmware version from 2.2.19.300 to 3.3.16.980, or in debug if you push something wrong there are some chances to block the navigation on black screen as bellow.

At the same time, the climate does not work, (it works somehow), there is no music, there are no parking sensors, well, and there are no other buns). True cruise, lane control, dead zone sensors, sign reading, auto-long distance – everything works. True, the panel is in ESO mode. But part of the functionality had to be taken over by the device.

But there are some solutions that you should try, like writing by PYREN all the parameters required.

Preliminary operations

What will we need, first of all?

•  An OBD2 interface ( ELM327 V1.5 mandatory with PIC 18F25K80) compatible, whether it is USB, Bluetooth or Wi-Fi, you can read about the versions here;
  • The correct driver for the interface in case of USB can be Prolific USB – SERIAL and can be download from the LINK
•  A laptop PC with Windows (tested with 7 and 10);
•  The python 2.7.x +pyren script files from DOWNLOAD LINK HERE or REVOLUT after BEER DONATION
•  A minimum of computer skills, otherwise it is better to leave it alone …

Step 1 : Launcher of pyren application

Inside of this great application is existing an MACRO section where

• choose COM port of your ELM or its IP address in case of WiFi
• press “Macro” button
• choose one of the next 4 files:
  rlink2-HIGH1-screen.cmd
rlink2-HIGH2-screen.cmd
rlink2-MID1-screen.cmd
rlink2-MID2-screen.cmd

* Options “Dump” and “Log” are highly recommended

The launcher saves their state in file settings.p for next use.

• Start pyren – launch the pyren
• Scan – rescan all ECUs
• Demo – launch the pyren in off-line (demo) mode
• Check ELM – launch the script intended to check your ELM
• Monitor – launch sniffer of system CAN frames
• Macro – launch terminal in command batch mode. You will be asked to choose command set from /macro folder
  

wait while the macro is executing as bellow ↓

13:712:CAN500# 
13:712:CAN500# 1003
50 03
13:712:CAN500# 
13:712:CAN500# # HIGH 1 768x1024
13:712:CAN500# 2E2303032802131303003C000004500014001E001E040011C5002C006967
6E 23
13:712:CAN500# 
13:712:CAN500# wait 2
13:712:CAN500# # reload rlink2
13:712:CAN500# 1101
61 01
13:712:CAN500# exit
****************************************
* 
*       ERRORS STATISTIC
* 
* error_frame      =  0
* error_bufferfull =  0
* error_question   =  0
* error_nodata     =  0
* error_timeout    =  0
* error_rx         =  0
* error_can        =  0
*
*       RESPONSE TIME (Average)
* 
* response_time    =  0.000
* 
****************************************

pyren $ 

The r-link 2 should go to reboot in the end.

If you are lucky and chosen the right macro file, then you will see a working screen, else wait a minute and repeat the process with another macro file.