MS908P VCI – J2534 ECU Programming Device

25-1  25-4

1.Functional Description

1.  Ethernet Port

2.  USB Port

3.  Power LED – illuminates solid green when powered on

4.  Error LED – illuminates solid red when serious hardware failure occurs

5.  Bluetooth LED – illuminates solid green when connected with the MaxiSys display tablet through Bluetooth communication

6.  Ethernet LED – illuminates solid green when connected with the Autel Scan Tool MaxiSys display tablet or an existing LAN via the Ethernet serial cable

7.  USB Status Light — illuminates solid green when the device is properly connected and communicating with the MaxiSys display tablet or the PC via the USB cable

8.  Vehicle LED – flashes green when communicating with the vehicle’s network

IMPORTANT: Do not disconnect the reprogramming device while this status light is on! If the flash reprogramming procedure is interrupted while the vehicle’s ECU is blank or only partially programmed, the module may be unrecoverable.

9.  Bluetooth Antenna

10. DC Power Supply Input Port

11. Vehicle Data Connector (DB26-Pin MVCI)

12. External Programming Voltage Output Port

13. A/D Input Port

J2534 Reprogramming Capability

The J2534 ECU Programming Device is a SAE J2534-1 & -2 compliant PassThru reprogramming interface device. Using the updated OEM software, it is capable of replacing the existing software/firmware in the Electronic Control Units (ECU), programming new ECUs and fixing software-controlled drivability issues and emission issues.

Communication

The J2534 ECU programming device supports Bluetooth, Ethernet and USB communication. It can transmit vehicle data to the MaxiSys display tablet with or without a physical connection. The working range of the transmitter through Bluetooth communication is 755 feet (about 230 m). A signal lost due to moving out of range automatically restores itself when the display tablet unit is brought closer to the VCI unit.

Power Sources

The J2534 programming device can receive power from both of the following

Sources:

Vehicle Power
AC/DC Power Supply

Vehicle Power

The J2534 programming device operates on 12-volt vehicle power, which it receives through the vehicle data connection port. The MS908P powers on whenever it is connected to an OBD II/EOBD compliant data link connector (DLC). For non OBD II/EOBD compliant vehicles, the device can be powered from a cigarette lighter or other suitable power port on the test vehicle using the auxiliary power cable.

AC/DC Power Supply

The J2534 programming device can be powered from a wall socket using the AC/DC power adapter.

Technical Specifications

25-3

The Tech 2 hardware initial installation steps

1.  Remove the RS-232 loopback adapter (P/N 02001606) from the storage case (P/N 02002971). Plug it into the RS-232 port.

20-1

2.  Attach the Tech 2 DLC cable (P/N 02002952) to the VCI connector.

20-2

3.  Locate the DLC loopback adapter (P/N 02002953) in the storage case. Attach it to the DLC cable.

20-3

4.  Locate the NAO (P/N 02002972) power supply and appropriate power cord in the storage case. Insert the power jack into the Tech 2 DLC cable or into the bottom of the Tech 2 next to DLC cable connector.

20-4
20-5

5.  Turn on power by pressing the PWR button located on the GM Tech 2 key pad.

6.  Car diagnostic scanner Tech 2 hardware is verified automatically by the POST Test.

20-6

7.  Disconnect the RS-232 loopback adapter, the power supply, and the DLC loopback adapter and return to the Tech 2 storage case.

20-7

Super Dprog5 PROG2 IMMO Odometer Airbag 3 in 1 Reset Tool

10-1

To fully support the cars instrument calibration, security immo key match, airbag repair, and other functions. Support ISO9141, CANBUS, and J1850 protocols. Perfect self-diagnosis function, can automatically identify and diagnose system faults.

 Super Dprog5 Highlights:
-Support all CAS (including CAS3-9S12XDP512) programming.
-Support all M35080 instrument no dismantled adjustment (including M35080 V6 instrument);
-Support  transmission computer OBD setting; E38/ E39/ E46/ E53 instrument, EWS/ LCM and EWS4 adjustment.
-Support Be ignition module adjustment (912/ 9S12 series ignition module doesn’t have to disassemble CPU), W211/ W203/ W164 and before year 2000 OBD adjustment. Support Mercedes-Benz Gateway (CGW) adjustment.
-Support  from 2009.
-Support MCU calibration,

Device parameters:
This Odometer Correction Tool is based on the latest CORTEX technology handheld devices, internal embedded dual CORTEX ARM processor, clocked at up to 200 MHz; SD card for data storage or upload; USB2.0 for software and firmware upgrades; 320×240 TFT true color display and 256K color resolution to display help files and pictures; Support CAN-BUS, J1850, CCD-BUS, ISO9141, SPI, UDS and other protocols; just an OBD connector which can complete all the automatic switching of the protocols by multiple relay intelligent control.

The 5th VW A-u-di IMMO software:
1. New BCM2 adapter to pre-read and write chip data.
2. OBD2 key match (no password, no need online)
3. For the V-W, Audi 5th security system models.

The 4th V-W IMMO software:
1. Write the V-W key with the new Meg-am-os48 chip
2. OBD2 key match ((no password required), no need online)
3. For Vol-kswa-gen, Sk-o-da, S-e-at 4th security system models (the instrument use NEC+24C64 or NEC+24C32 or Macrons (CDC) or 9s12xhz512 (1M80F) microcontroller)

10-2

How to use SD connect C4 + Xentry/DAS on Macbook Pro

I’m running Xentry/DAS 2015.12 (not OpenShell) on my MacBook Pro together with SD Connect C4 via LAN cable and VMware. Works without problems.
Need bridged networking in VMware. And adjust the network settings/IP addresses.

VMware:

Use VMware Fusion Professional and and allocate enough resources to the VM.

Mac hardware specification:

MacBook Pro, Core i7, 16GB RAM, 512 SSD, 15″ 1GbE, SuperDrive, Mid-2012

Virtualization:

That is the magic of virtualization. If you can locate a copy of Star Diagnosis that was intended for the IBM ThinkPad T30 running Windows NT 4.0 Workstation, you could easily install Windows NT 4.0 in a virtual machine and replicate that environment with near native performance. If you prefer to use a Windows XP-based version, that is easily done as well, up to and including Windows 10 1709 or Windows Server 2016. Almost any computer you purchase now will not have drivers available for Windows XP, so either an old PC such as a Dell D630/D830 will allow you to install Windows XP natively and make it work, but virualization takes the headache out of that. OS X us built on UNIX, so it is a very stable host OS and can run nearly any version of Windows was a guest with easy, stability and performance. The only think I would refrain from doing at this point in time, is if you are using OS X 10.13 High Sierra, do not use APFS just yet. It still is not as stable IMO as HFS+. You certainly don’t want to introduce system instability when programming a control module!

Battery:
The battery life is good when running Windows in a VM, as OS X has excellent power management. Allocate at 2 cores to the Windows VM, and if using an XP-based version, 2048GB of RAM should be sufficient.

In detail…How to setup Xentry/DAS on a Mac OS X

It is very straight forward. I elect to not use the automated installation of Windows, as it automatically configures the partition sizes, formats them, etc. Instead, do a custom installation and select your ISO. It will then determine the contents of the OS ISO and select your low-level hardware components automatically, such as CD-ROM bus, HDD bus, etc.

For the network cable, it defaults to NAT, so it shares the IP of OS X, but cannot receive unsolicited network traffic due to the nature of NAT. You can select Bridged, and it can have an IP on the same subnet as OS X.

I think I would prefer to install my installation from scratch, as the pre-built images that are distributed have an unknown product key, and also could contain malware or other unwanted applications.

If you are installing the XP version of DAS/Xentry, specify your virtual disk to be about 120GB, and when Windows XP asks you to specify your partition size, instead of pressing Enter and allowing it to consume the disk specify 20GB and quick format as NTFS. Create the remaining three partitions in Disk Management after XP completes installation.

Also, the first thing you will want to do is install VMware Tools after XP installs. If you want to install all available updates for Windows XP, and download WSUS Offiline version 9.2.3 and it will get your all of the available updates that were released when XP reached EOL.

I have used 12.2015, but if I still used it, I would revert back a few months to avoid the hard-coded timebomb that was implemented at the end of 2015.

Result:

I have used this setup for many years for control module programming and SCN coding with no issues from OBD2TOOL.

What’s Tech2 TIS2000 hardwaresecurity key used for

I have a question about the gm tech2 hardware/security key. What exactly is the purpose of it? I don’t have one, and was wondering if I can still use the TIS software without it.

Reply:

There are three versions of the hardware key:

the original green parallel port key,

the newer white Rainbow Technologies parallel port key

and now the USB key also made by Rainbow Technologies.

Normally the Car Scanner GM SPS software (TIS2000) as supplied by GM requires a hardware key for its SPS functions.

However most GM dealers now use a web based SPS system that links directly to GM’s database via a password protected secure GM website which do not a hardware key.

Some dealers still use a standalone SPS terminal which does require a key.

Without this key the software and its programming system is inoperative unless you have a hack for it.

All other functions of the TIS program will work without the key, if you have full blown TIS package it will include software that can download and playback data recordings done with the tech2 scanner for sale, it will also update a TECH2 with the latest software from GM.

Obdstar x300 pro3 vs Xtool x100 pro vs Skp900

OBDSTAR X300 PRO3, xtool x100pro, SKP900.
Which of this tool is fantastic for get started in essential programming?

Appear here… all facts integrated

Obdstar x300 pro3 vs Xtool x100 pro vs Skp900

27-1

OBDSTAR X300 PRO3 Important Master Feedback:

Client 1:
I’ve bought two of there newest programmer (Crucial Master X300 Pro 3) claim to have the same plan as the SKP900. Not correct it lacks the newest protcal, all thou the F100 does possess the newest protocol.

Buyer 2:
For the price tag and its function more than Skp900 (€549.00) looks to become the superior obtain.
mileage is further bonus, much more funds & something different. (New story’s)
obd2 scanning is limited but further bonus on rewriting vin # on donor Ecu.

Consumer 3:

OBDSTAR F100 Ford/Mazda essential pro and OBDSTAR?X300M is the separate program out from X300 PRO3 Important Master, while if you are a master working at workshop/garage, you are advised to own one OBDSTAR X300 PRO3 Key Master which include all vehicle models and function including: essential programming, odometer adjustment, PIC function (read write CPU data on a part of car computer) and EEPROM function (read out password from EEPROM chip and restore data), EPB, oil service reset, battery matching etc.

OBDSTAR X300 Pro-3 Test Report:

Crucial programming:

“OBDSTAR X300 PRO3 covers SKP900 and OBDSTAR X100 Pro function”

Toyota 4Runner (2006): add new keys->ok
Lexus RX400H (2005): plan a new key->ok
Honda: edit vin-> great

Nissan: smart crucial programming-> awesome
Kia Ria 2014 with I4D60: programmed essential with pin (pin ready be another tool)->ok
Hyundai i10 2012: Read Pin and programmed 7936 (ID46)->Quick and easy.
Volex c30 2012: read pin code program key-> ok
K13 worked perfect
Insignia 2011: read security code + system keys-> OK

Odometer correction:

OBD2TOOL technicians have a fantastic success with km change using X300 pro3. The VAG group vehicles are what we tested most. Also, some Hyundai, Kia, Opel, Chevrolet, Range Rover, Ford, Fiat, Porsche, Jeep, etc are tested. Here are VAG test reports.

Audi A3 2008 monocolore: OK
Audi A4 2007: in 20 seconds by OBD-> ok
Audi normal a6 2009: ok

Audi a8 2006: OK
Audi Q5 2013: via obd-> ok
Volkswagen Tiguan 2013: TFT color dash nec+24C64-> ok
Volkswagen caddy 2014: white meter NEC24C64 via obd-> ok
Seat Ibiza 2014: Via obd -> ok
Volkswagen Polo 2014: with NEC24C64-> ok
Golf 2013with black/white screen: OK (with latest update)
Golf 6 2012 white color: write 2 sec !!
Tiguan 2012 tft color NEC24C64 ok
Volkswagen Polo 2014: White Meter NEC24C64 using golf menu-> OK
Passat 2009: mileage nec+24c32-> OK
kia sportage r 2014: d70f423 mileage-> tested ok
Skoda Octavia 2010: nec+24c32 VDO mileage OK
Skoda Superb 2012: via obd-> mileage ok
Polo 2004: VDO k Line-> mileage OK
Volkswagen Amarok 2014 ok: chose golf NEC 24C64 white meter 2013-> ok

The last, XTOOL X100 PRO vs OBDSTAR X100 PRO

27-2

In summary,

1.Bothis original makes ofhigh quality, but come from different factory:

OBDSTAR X100 pro is designed by the OBDTAR factory

Xtool X100 pro is designed by the Xtool factory

2.Update online on different website:

OBDSTAR X100 Pro update on:http://www.obdstar.com/ three years for free

Xtool X100 update on:http://www.xtooltech.com/, with serial number and register password

3.Different function:

OBDSTAR X100 pro: support EEPROM function, but you need to invest in EEPROM Adapter additionally.

Xtool X100: do not support EEPROM function

4.Support different vehicles:

OBDSTAR X100 pro: do not support Proton

Xtool X100: support Proton

5.Different main board:

X100 pro odometer with new design of PCB hardware, greatly improved configuration

(Solved) ODIS-S 4.3.three Error ODS9011E on Windows 7

Download VAS 5054AODIS-S 4.three.three on Windows 7 but had a problem:

Update file missing

ODS9011E

Infrastructure VW on-line connection. MirrorServer2:

The update just isn’t complete.

All required updates will not be obtainable.

Please speak to assistance.

22 22-1

I located a answer to resolve it by editing the lic. file – so that just vag “basic” merchandise are valid/active…. but you have got to provide this file to the installer in the course of the procedure, just swapping inside the offboard folder hasn’t solved my issue…

And after that, obviously there’s no full activation and not all brands but it appears you could run odis four.3.3 using the “basic vag brands” and with this installer plus the existing postsetups

Hopefully, guss could resolve this “problem” for us, to ensure that we’re totally activated with all the brands then

22-3

How to Update Digimaster 3 EBOOT and Kernel

Update kernel of yanhua digimaster 3 was newly added (one key through updating kernel by SD card), we made some modification on EBBOT program.

Digimaster 3 EBOOT Update:

Click button “8” and “OK” together, then “Press OK to confirm, and if the button “continue update Firmware” appears, it means your device EBOOT program is old version, you need to firstly update EBOOT program and choose a convenient way to update Digimaster 3 kernel.

Digimaster III update kernel

After update EBOOT, it is necessary to update kernel.

Tips: Before update EBOOT, please instal D3 TOOL first.

Step 1: Click button “8” and “OK” together, then power on. The indication of “Press OK to continue and ESC to cancel” will appear on the screen. Press “OK” into Renovation.

Step 2: “Found new hardware” is found in the system when you connect USB cable with the PC.

15-1
Step 3: choose “install the software automatically”, click “next”.

Step 4: If DIGIMASTER 3 has been installed already, choose the second “SEC SOC SMDK Board” in dialog box, and click “Next” to complete driver installation.

15-2

Step 5: Double-click Digimaster 3 PC Tools and choose “Kernel Update”.

15-3

15-4

Step 6: Indication ” USB connect succeed “will appear as below after the USB is connected.

15-5

Step 7: click “Kernel Update”, choose “EBOOT_20110427.bin” then click “OK” to start digimaster 3 price program update.

Step 8: After 10sec. the DIGIMASTER 3 screen appears a twinkling red ‘YH’ logo which means EBOOT update is complete.

After update obd2 odometer correction EBOOT successfully, please turn the power off and choose an appropriate way to update the kernel.

TIPS: Please unload the anti-virus software and firewall temporarily in order to run the software normally.

VAS6154 ODIS 4.23 driver for VW Audi Skoda WIN7 free download and install

VAS6154 ODIS 4.23 for VW Audi Skoda diagnostic tool WIN7 free download and install procedure.

VAS6154 driver free download:

http://www17.zippyshare.com/v/PlA2J9Ho/file.html

I only share here, please try it at your own risk.

Source: mhhauto.com

VAS6154 driver for VW Audi Skoda WIN7 download

http://www.obd2tool.com/goods-6919-Newest+VAS6154+Diagnostic+Tool+with+ODIS+413+Software+for+VW+Audi+Skoda.html

Compatible with ODIS 4.23

Works on the interface like:

VAS6154 ODIS-S 4.2.3 test reports:

DTC memory…works

Identification… works

Output Diagnostic Test Mode… works

Basic setting … works

Coding … works

Coding bus master …works

Measured values … works

Adaptation … works

Access authorization … works

Guide:

Right click on “VAS6154 Driver” and choose “Run as administrator”

9-1

Click on “Next”

Complete VAS Driver Setup Wizard.

9-2

Connect the VAS6154 interface to the computer and receive the windows message “Your device is ready to use”.

9-3 9-4

Right click on the “VAS Config” and choose “Run as administrator”.

9-5

Click on “Firmware+”

Click on “Upgrade”.

9-6
9-7

9-8
Exit VAS Config.

Delete the folder of “VAS6154 Driver”.

9-9

One more time, right click on the “VAS Config” and choose “Run as administrator”.

Click on the “License”, you can see Passthru, PDU, VW are all available.

9-10

Click on “Diagnostic”, then “VW ODIS”, then “Install”.

9-11

Setup complete.

9-12

Option 1: The way to use VAS6154 Diagnostic Tool via USB.

Back to click “Configure”, then connection type “USB” and save.

9-13

Open “Wolkswagen”

9-14

Receive the warning and notes.

9-15

Welcome to Diagnosis, click on “OBD” then “Start self diagnosis”.

9-16

Make sure the ignition is on.

9-17

Here fault codes.

9-18

Go to option “Identification”.

9-19

If the ignition is off, you will get the message shown as below, just follow it to do.

9-20

OBD starting..

9-21

You can achieve more functions incl. Output professional diagnostic tool Test Mode, basic setting, coding, coding bus master, measured values, adaptation, Access authorization etc.

9-22

Exit ODIS-S.

VAS6154 connect to the network.

9-23

Work network

9-24

Network location is now work, click on “Close”.

9-25
Option 2: use VAS6154 via Wlan connection.

Again, open “VAS Configure”, choose the connection type “Wlan”.
9-26

Repeat the same procedure as the USB connection type to diagnose.

9-1

End.

Cars & Computers The History of Diagnostic Tools

One common factor to be found in every decade’s ideal future is a sense of comfort and reassurance, and in this regard car diagnostic tools could not be more modern. For example, each successive generation of products and software from Launch Tech not only allows for more extensive diagnostics of a vehicle’s performance; they also make the task more effortless and less time consuming as you go through the various generation models.
car start problems

But exactly how far has this technology come in the last few decades? In this entry of the Launch Tech UK blog, we’ll go from creation to current day with this history of diagnostic tools:

As a brief description, an car diagnostic is an electronic device that can be used to diagnose, interface and even partially reprogram a vehicle’s control module. Scanners in particular perform the same functions as a diagnostic code reader, except they also give the user additional diagnostic information, and can perform functional tests on the vehicle. They’re designed to function in tandem with your car’s on-board computer system, which itself monitors engine emissions controls and systems whilst your car is in use. The first generation of On-board diagnostic (OBD) tools were developed in the 1980’s, originally as an expensive diagnostic option only really available for professional mechanics.

Throughout the decade, automotive scanners were produced in the United States, using various cables and adaptors that would be compatible with certain car models, makes and their respective years. The first commercially available code readers hit car part stores in and around 1989, but it was only in 1996 that the automotive industry lost their exclusive ability over vehicle on-board diagnostic systems, with further standardization of the technology caused by stricter federal regulations.

The presence of two generations of on-board diagnostic systems, OBD-I and OBD-II, are intrinsically linked to this change in regulations, and a combined effort to clean up our air. The “gas attack” in Los Angeles during the summer of 1943, as well as the proliferation of lethal smog in London in 1952 were two environmental episodes that turned the business culture of voluntary emissions regulations into one of national requirement. The autel scanner in use at the time served fine in letting drivers know if their vehicle had a malfunction, but from an emissions point of view there were some serious flaws, to the point where your vehicle could be spitting out raw unburned fuel out of its tailpipe and neither you nor the computer would have any idea! This lead to the creation and required implementation of auto key programmer; the same technology monitored and read by today’s Launch OEM level diagnostic tools and aftermarket products.

Speaking of, the Launch Tech Co LTD itself was founded in 1992, developing their first generation of LE100 scanners two years later. Now global leaders in the automotive diagnostics market with a range that includes the C Reader VI, CRP123 and the CRP129, the Launch parent company has 13 branches in and amongst Europe, North America, Central and South America, Africa, Middle East, China and Asia Pacific, and has supplied to the UK market since 2003.