Start vehicle engine, connect NexzDAS lite scanner to vehicle via OBD socket
The NexzDAS communication indicator turns on
Open NexzDAS App
Click Bluetooth icon on the top right-corner of the App
Problem:
I had problem connecting Bluetooth with the NexzDAS Lite obd2 code reader on my Android mobile phones. I have tried Sony xperia xa2 , Samsung Note9, Oppo and Samsung Note8 phones, all with latest Android operating system.
I removed older NexzDAS app 3.4 and install new 3.8 version. Only Note8 was able to make Bluetooth connection.
Possible reason:
The NexzDAS lite Bluetooth is not compatible with all Android mobile phones.
Besides, the App requires Android operating system above 5.0.
OBDII365 Solution:
Scan the QR code below to install the TTC-BLE App
(You can download TTC App on Google Play Store by search “TTC-BLE” as well.)
TTC-BLE is the third-party software App designed to connect data modules and module parameters through the mobile phone APP and Bluetooth module. The APP can set IO port, PWM input and other parameters through Bluetooth, and can also display the specific data content of the transmission.
After download TTC app, follow steps below to set up:
Exit the NexzDAS App.
Start vehicle engine, connect NexzDAS lite scanner to vehicle via OBD socket The NexzDAS communication indicator turns on Open NexzDAS App Click Bluetooth icon on the top right-corner of the App
Then open the TTC-BLE app, connect Bluetooth starts with H*********
Result:
Our customer has tested and successfully connected Bluetooth with his Sony xperia xa2 mobile phone.
Look here: What’s the difference between Benz eCOM DoIP diagnostic tool and MB Star diagnostic SD connect c4 multiplexer?
In summary,
New car: eCom DoIP
eCom – laboratory\development tool. Most cheap and light. Can’t be used with DAS\HHT vehicles. Need luck with kline communication. Need to be specially setup on any diag sw installation.
Normal: Clone SDConnect C4SDConnect – workshop\robust tool. Most universal in use. The only limitation is kline communication in Vediamo from ver5* Easy to setup. In most cases work as is.
Good to know:
Actia eCOM DoIP Box Multiplexer Kit supports DoIP for the latest E and S series, and it’s perfect for Mercedes COMAND NTG5, NTG5s1, NTG5s2, NTG5.5
ECOM is the diagnostic and swipe communication interface used by daimler-benz’s production and r&d department. It supports the after sales diagnostic software Xentry, Vediamo, and the Monaco DTS, the exclusive development software, with higher access rights than SDconnect (C4).
ECom supports the CAN/DoIP network, which CAN be used for the diagnosis and brushing of new car audio and video entertainment systems. Vediamo for Mercedes engineers is an engineering software used by Mercedes engineers to develop diagnostic software, that is, Xentry and DAS now in use is developed based on Vediamo and delivered to general after-sales dealers. For this reason, using the Mercedes super engineering version is open to all diagnosis /coding/retrofit/flashing programming features. It is possible to add or reduce SA codes freely without going through VEDOC(the process of the original factory applying for modifying the equipment code), so as to achieve the purpose of modifying the vehicle equipment, such as adding SA500 electric rearview mirror.
Xentry and DAS Developer mode, commonly known as: exploit data engineering version after 2010, has added many restrictions on functions. Therefore, people may encounter that the vehicle version is too new to enter the control unit, or they cannot make any special modifications after entering the control unit. For example, the w204/212 2012 meter may need to be configured in the regional language, or turn on other convenience functions.
The database of diagnosis /coding/retrofit/flashing for the Mercedes engineer version USES the Xentry database, so the Mercedes engineer version is dependent on the Xentry version. As long as the database is new, the Mercedes engineer version can use the V4.00 version on the new model, and compact3 & SDconnect does not support the ODX document. The latest V5.00 supports ODX files with eCom. It is recommended to use eCom with DoIP function, which is faster and more stable.
Have collected all about Audi a4 post-2004 RB8 cluster key learn/program using Xhorse VVDI2 or Abrites AVDI or Fly FVDI.
Look here:
Part 1: VVDI2 and Audi a4 RB8 2004+ key learn (all keys lost)
Part 2: AVDI and Audi a4 RB8 2004+ key program
Part 3: FVDI and Audi a4 RB8 2004+ key learn
in detail…
Tip:
With Xhorse vvdi2, the procedure to program a new key if all keys are lost is the same as for adding key, the only difference is that at some point you have to disconnect the BCM2 power and reconnect it. Just read the instruction below.
Recommendation:
take out BCM and read BDM file with VVDI2 BDM cable . Then load file, make dealer key and learn keys .
Steps:
1.Connect VVDI2 with computer and your car.
2.Put the new key into VVDI2 programmer.
3.Start VVDI2 software, and choose Audi.
4.Click on “Key Learn>>5th immobilizer system”.
5.Read BCM Data (OBDII).
6.Insert a working key to turn on ignition before continue.
If the key is already in car, you also need to remove it then insert it again.
If you lost all keys, you need to open car headlight and step on the brake before continue.
7.Read data success, save the eeprom bin file.
8.Make Dealer Key.
If car is A4/A5/Q5, press YES button to continue, no need working key.
If car is A6/A7/A8/VW Touareg, press NO button because it needs working key. Click on YES.
9.If you want to program an OEM key, make sure the new key support change ID. Click on YES.
Choose Program normal dealer key option, click Next and OK to load the BCM file.
10.OK and VVDI 2 start to program new key.
Wait a minute and VVDI2 make new dealer key successfully!
11.Change key number from 1 to 2.
Click on Key Learning then OK to load the BCM bin file.
VVDI2 start learn key.
Use the working key to turn on ignition then insert the new key to learn.
VVDI2 is able to program a new key to Audi A4 B8 successfully!
Here are steps of Audi a4 2004+ RB8 cluster key programming
Dealer key preparing and key learning on Audi a4 2004 onwards with abrites 7.4.
Open your Abrites vag commander programme and confirm that the programme finds your interface and your programmer. You should see the following screens if everything is connected.
Once open you should be prompted with the screen below. Under the special functions tab select key learning.
Once you have selected key learning you should be shown the following screen.
Select the down tab and select the Audi A4 2004+ [RB8 instrument cluster KW2000] selection.
Once you have selected this you should get the following screen.
Once you have entered your new key count then if you have a dealer key ordered to the vin number then select “Learn” this will start the key learning procedure follow any prompts that appear.
Once completed you will be prompted with a window saying all keys successfully programmed.
Key programming is now complete and you should turn ignition off and back on and now try to start the vehicle.
If you are using the special transponder chips to create a dealer key the follow this procedure. Enter your new key count as described above and then select “Program dealer key“.
It will now connect to the RB8 to retrieve the component security to prepare the dealer key.
Once it’s retrieved the component security then it will prompt you saying place a TA5 into the programmer to prepare the dealer key. Once you have done this select ok and at the bottom left of the window you will see the message communicating with the transponder (this may take some time).
Once this process is completed you will be prompted saying transponder is now prepared and can be learnt to instrument cluster. Select ok.
Make sure that the transponder is key blank and this is in the ‘On’ position in the ignition. Now you can learn the key as if you had bought it from the dealer to the vin number.
To programme the key follow the procedure above as if it is a dealer supplied key
It’s OviStar67’s story with Audi A6 2006 lost key situation:
The client had lost remote key and did tried to start the car with service plastic key (with id48 tp inside) and no success. Maybe somebody before did program other keys and forgot about the service key.
Dash shows “L7 2-2” instead of mileage.
I did precoded id48 for Audi with Tag Key tool from FVDI and did program again using both options standard/wizard learning option from VAG Commander v24. If not detected automatically select “Audi RB8 2004+ …” option, fill how many keys you want to program and hit learn without filling the PIN.
The system will work smooth and program the keys just follow on screen instructions.
Tip: Because RB4/RB8 is crypto even if you have good PIN is not accepting the code.
In this case after learning the system did not return to L6 state (normal mode) and immediately shows mileage.
In some cases “L0 2-2” it shows when accidental learning procedure is stopped (power lost etc).
To solve this read instrument cluster eeprom and change the state from 7 to 6 and hit update.
some advice
before do any key programming on any of the cars that need pre coded chips with component security then always make some backups first before playing.
Back up the eeprom in dash board and also the ecu config data . That way can go back to start and avoid having to fix def or L7 2-2 errors
That it.
Good luck and please excuse my rough language or my lack of technical details.
http://blog.obdii365.com/2019/05/05/audi-a4-rb8-2004-key-learn-with-vvdi2-or-avdi/
|
AuthorCategories |