Vag Tacho Download

Vag Tacho Download Windows 10
Vag Tacho Download 2.5

VAG TACHO V5.0
Vagtacho usb version 5.0，lastest version 5.0，support VDO with 24C32 or 24C64
our vagtacho usb version 5.0 includes the functions of vagtacho usb 4.52 ， vagtacho usb 4.0，and vagtacho usb 3.5

Download VAG Tacho files Drivers CAN bus scanner Download Vagtacho K+CAN How to install drivers: Connect OBD interface to any free USB port. This will start Windows procedure to install drivers for new hardware found. Show Windows where the drivers are on your hard disk. If Windows ask you for a file with extension '.cat', press 'Skip File'! Compatible Vehicles: Audi VW Seat Skoda. Version: Vag Tacho 3.01 + Opel Immo Airbag VAG TACHO USB 2.5 VAG Tacho USB 2.2. Recommend Mileage correction tool: Tacho Pro - More function and cheap price. VAG Tacho Function. Vag Tacho 3.01 + Opel Immo Airbag Latest update: VW Polo,Seat Ibiza Cordoba 2001 - 2005, Fabia 2004 ect. Software Vag Tacho Download. VAG-TACHO USB Vehicle OBD Cable With Software CD - Vag Software - Tacho - Vag-Com - VAG. Vag-Tacho USB is a Windows program that helps you install the Vag-Tacho drivers on you computer. Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

1.Main functions:
1.read ecu info
2.read pin
3.change mileage
4.read eeprom
5.programmer new key
6.write eeprom
7.clear ecu errors
8.viem memory buffer

VAG Kombiinstrument / Immo box eeprom programmer!
Windows 7, Vista, Win XP, Win 98 compatible software!
Support for some VDO dashes for VW from year 2009-2011 with NEC mcu and 24C32 or 24C64 eeprom memory. Important: These dashes requires ignition to be switched on with valid key of the car! Software version 5.0 works ONLY with interfaces which has got built-in programmer for Megamos ID48 transponders!
Built-in programmer for Megamos ID48 transponders! Pre-programming of TP2x transponders as dealer's keys with component security data which is read from immobiliser!
NEW key programming feature for VAG cars with VDO dashes on CAN bus! (TP2 and UDS protocols)

Note: TP22,23,24,25 transponders are required!

List of supported VAG cars:
Volkswagen
Golf 6, Jetta, Polo, EOS with VDO dash 2009 - 2011, note: not all dashes are supported!
Golf 5, Caddy, Touran, Jetta, EOS with VDO dash 2003 - June.2006
Golf 4, Bora with VDO or Motometer/Bosch dash: 1997-2003
Beetle with Marelli dash: 1998 - 2005
Passat, Jetta, with VDO, Marelli or Motometer dash: 1997-2004
Polo with VDO or Motometer dash: 1999-2006 (1999-2002 mileage change only)
Sharan with VDO dash: 2000-2004(mileage change only)
Caddy, Lupo with VDO or Motometer dash 1997 - 2002(mileage change only)
Transporter with VDO dash 1998 - 2000
LT35 ( Temic immo box) 1999-2003 (pin code read only)
Gol ( Kostal immo box) 1999-2003 (pin code read only)
Seat
Altea, Leon, Toledo with VDO 2003 - 6/2006
Leon, Toledo, Cordoba, Ibiza with VDO or Motometer dash 1997-2003
Alhambra with VDO 2000 - 2004(mileage change only)
Inca with VDO or Motometer 1997 -2000(mileage change only)
Skoda
Octavia II with VDO dash 2005 - 6/2006
Octavia, Fabia with VDO dash 1997 - 2004
Audi
A3 VDO dash 2003 - 2005
A3,A4,A6 VDO dash 1997 - 2000
A3,TT,A6 Magnetti Marelli dash 1998 - 2003
A4 Bosch dash 2000 - 2008 - Read/write of encrypted data with V4.5!
A4,A6,A8 1995-1999 (immo box - read pin code)

2.vag tacho usb version 4.52
Vagtcho 4.52 is upgraded from vag tacho usb4.0, Upgrade Vagtacho usb 4.0 interface with Programmer for Megamos ID48 chips, our vagtacho version 5.0 has upgraded directly ,includes the functions for vagtacho usb 4.52
The benefits with this upgrade are:
Your Vagtacho interface will works with software vesrion 5.0 for the new VDO dashes with UDS protocol from year 2009+
Programming of new keys to VAG cars which are into FAZIT database.
Works with cars which has got locked key programming channel, or pin code is not accepted.
No need to wait up to 30 minutes for the key programming procedure.
With this upgrade, Vagtacho can program the new key in one minute

.
3.Vagtacho version 4.0
VAG Kombiinstrument / Immo box eeprom programmer!
Windows 7, Vista, Win XP, Win 98 compatible software!
Works on any computer which has got USB port!
Most of VAG dashes from 1997 to 2006 are supported!
Direct programming of Megamos ID48 (JMA-TP08) chips
to VAG cars on CAN bus from November.2003 to June.2006
Transponder Maker Pro is required for pre-programming of these chips.
Note: TP22,23,24,25 transponders are NOT required!
1.Main functions:
1.read ecu info
2.read pin
3.change mileage
4.read eeprom
5.programmer new key
6.write eeprom
7.clear ecu errors
8.viem memory buffer
2.List of supported VAG cars:
Volkswagen
Golf 5, Caddy, Touran, Jetta, EOS with VDO dash 2003 - June.2006
Golf 4, Bora with VDO or Motometer/Bosch dash: 1997-2003
Beetle with Marelli dash: 1998 - 2005
Passat, Jetta, with VDO, Marelli or Motometer dash: 1997-2004
Polo with VDO or Motometer dash: 1999-2006 (1999-2002 mileage change only)
Sharan with VDO dash: 2000-2004(mileage change only)
Caddy, Lupo with VDO or Motometer dash 1997 - 2002(mileage change only)
Transporter with VDO dash 1998 - 2000
LT35 ( Temic immo box) 1999-2003 (pin code read only)
Gol ( Kostal immo box) 1999-2003 (pin code read only)
Seat
Altea, Leon, Toledo with VDO 2003 - 6/2006
Leon, Toledo, Cordoba, Ibiza with VDO or Motometer dash 1997-2003
Alhambrawith VDO 2000 - 2004(mileage change only)
Inca with VDO or Motometer 1997 -2000(mileage change only)
Skoda
Octavia II with VDO dash 2005 - 6/2006
Octavia, Fabia with VDO dash 1997 - 2004
Audi
A3 VDO dash 2003 - 2005
A3,A4,A6 VDO dash 1997 - 2000
A3,TT,A6 Magnetti Marelli dash 1998 - 2003
A4 Bosch dash 2000 - 2005
A4,A6,A8 1995-1999 (immo box - read pin code)

Vagtacho v5.0
How to program new transponder keys with Vagtacho!
This procedure works with VDO dashes on CAN bus (UDS protocol) from year 2009-2011
1.

Switch ON ignition with VALID key!
Start software, select 'VDO NEW - CAN - UDS protocol' from menu. Press 'Connect Selected ECU' button, after about 30 seconds software will get access to the dash.
Message 'Access Granted' must appears on screen, otherwise this is unsupported dash, or the key is not valid!
Important: copy-paste in a text file the information which is marked in blue! If you know this key, you can get access to the same dash in future without valid key of the car!
Press 'Disconnect' and see the next picture.
2.
Press 'Disconnect', turn OFF ignition, and remove the valid key. Insert the new key with new Megamos ID48 transponder and switch ON ignition with the new key. Do NOT close Vagtacho software ! Press 'Connect Selected ECU' button, after about 5 seconds software will get access to the dash again. Press 'Program New Key', a new window will be open, see the picture. Check 'Erase all old keys' if you wish. In this case all keys will be erased. If you left this unchecked, the new key will be added to the existing keys. No need to program all available keys again. Press 'Continue' , the new key will be programmed in 5 seconds. Wait while the immobiliser accepts the new key, a message will be on the dashboard's display: '2-2' '3-3' ect. for every next key. Turn off/on ignition, and start engine. If the immobiliser's shows on display '1-2' or '2-3' this means that the type of the transponder key is not correct, or this key is already programmed to the car! Do NOT repeat the programming procedure if immobiliser shows different digits '1-2' or '2-3'! Just switch ON ignition with NEW Megamos ID48 transponder key! If you want to program more than one new key, repeat again the same procedure for every next key.

This procedure works with VDO dashes on CAN (TP2 protocol) MY2003-2007, and Audi A4 MY2005-2008!
1.
Switch ON ignition with the new key. Be sure that the type of transponder key is correct, use TP23 for VW, TP25 for Audi, TP22 for Seat, TP24 for Skoda! Start software, select 'VDO NEW - CAN bus' from menu. Press 'Connect Selected ECU' button, after 5 seconds the data of the dash will be shown on screen. Press 'Program New Key', software will open a new window. See the picture.
Check 'Erase all old keys' if you wish. In this case all keys will be erased. If you left this unchecked, the new key will be added to the existing keys. No need to program all available keys again. Press 'Continue' , the new key will be programmed in 5 seconds. Wait while the immobiliser's warning lamp is turned off. Turn off/on ignition, and start engine. If the immobiliser's warning lamp starts flashing faster, this means that the type of the transponder key is not correct, or this key is already programmed to the car! Do NOT repeat the programming procedure if immobiliser's warning lamp is flashing faster! Just switch ON ignition with right type TP2x transponder key! If you want to program more than one new key, repeat again the same procedure from the beginning for every next key.
The next procedure works with K-Line cars ONLY!

Switch ON ignition with the new key. Start software, and press 'Connect Any Tacho' for all cars with immobiliser inside dashboard. If the car has got separate immo box, select immo box from 'Select ECU' menu and press 'Connect Selected ECU'
Important! VW Polo, Skoda Fabia, Seat Ibiza from year 2007+ has got immo inside dash board, but these cars are programmed like VW Immo box! Turn on ignition for 10 minutes before to start the programming procedure!
5 seconds after the connection the data of the dash will be shown on screen. Press 'Program New Key', software will open a new window. See the picture. Enter correct PIN code , and the number of all keys which has to be programmed to the car. Select 'Channel 21' for cars with immo2 or 3. Select 'Channel 1' for cars with immo1. Press 'OK' , and read messages on the screen. The new key will be programmed to the car in 5 seconds. Wait while the immobiliser's warning lamp is turned off and turn ignition OFF. If you have to program more than one key, turn ON ignition with the next key, and wait until the immo's warning lamp is turned off. If the immobiliser's warning lamp starts flashing faster, this means that the type of the transponder key is not correct, or this key is already programmed to the car! For some old cars, before year 2000, trun off ignition after programming of the last key, and wait 3 minutes before to start engine.

vag tacho usb 2.40 problem

Witam. Mam vag tacho usb w wersji 2.40 do tej pory dzialal jak potrzeba. Ale gy podlaczylem go ostatnio do kompa zainstalowalem sterowniki i odpalilem program to od samej gory w prgramie mam komunikat ' USB to K-line Interface Not Found' - poprustu nie widzi mi go program. Sterowniki sa zaintalowane, i komp widzi go w manadzerze urzadzen jako zaintalowane urzadzenie USB io ... Co moze byc powodem, uszkodzenie samego interfacu czy moze zla wersja programu ( mam oczywiscie wersji 2.40) Mash tu komplekt

VAG-TACHO-USB_2.4.RAR
- VAGTACHO 2.0.exe
- vagtacho_good2.2.rar
- dumps.zip
- vagtacho2.2.rar
- EditEEPROM.exe
- Array
- vagtacho 2v4.exe
- fuses.JPG
- UA 2.4.txt
- 2.4.bin
- SCHEMATIC VAG Tacho USB.pdf

Download file - link to post

VAG-TACHO-USB_2.4.RAR > FTD2XX.H

/*++
Copyright (c) 2001-2005 Future Technology Devices International Ltd.
Module Name:
ftd2xx.h
Abstract:
Native USB device driver for FTDI FT8U232/245
FTD2XX library definitions
Environment:
kernel & user mode
Revision History:
13/03/01 awm Created.
13/01/03 awm Added device information support.
19/03/03 awm Added FT_W32_CancelIo.
12/06/03 awm Added FT_StopInTask and FT_RestartInTask.
18/09/03 awm Added FT_SetResetPipeRetryCount.
10/10/03 awm Added FT_ResetPort.
23/01/04 awm Added support for open-by-location.
16/03/04 awm Added support for FT2232C.
23/09/04 awm Added support for FT232R.
20/10/04 awm Added FT_CyclePort.
18/01/05 awm Added FT_DEVICE_LIST_INFO_NODE type.
11/02/05 awm Added LocId to FT_DEVICE_LIST_INFO_NODE.
--*/
#ifndef FTD2XX_H
#define FTD2XX_H
// The following ifdef block is the standard way of creating macros
// which make exporting from a DLL simpler. All files within this DLL
// are compiled with the FTD2XX_EXPORTS symbol defined on the command line.
// This symbol should not be defined on any project that uses this DLL.
// This way any other project whose source files include this file see
// FTD2XX_API functions as being imported from a DLL, whereas this DLL
// sees symbols defined with this macro as being exported.
#ifdef FTD2XX_EXPORTS
#define FTD2XX_API __declspec(dllexport)
#else
#define FTD2XX_API __declspec(dllimport)
#endif
typedef PVOID FT_HANDLE;
typedef ULONG FT_STATUS;
//
// Device status
//
enum {
FT_OK,
FT_INVALID_HANDLE,
FT_DEVICE_NOT_FOUND,
FT_DEVICE_NOT_OPENED,
FT_IO_ERROR,
FT_INSUFFICIENT_RESOURCES,
FT_INVALID_PARAMETER,
FT_INVALID_BAUD_RATE,
FT_DEVICE_NOT_OPENED_FOR_ERASE,
FT_DEVICE_NOT_OPENED_FOR_WRITE,
FT_FAILED_TO_WRITE_DEVICE,
FT_EEPROM_READ_FAILED,
FT_EEPROM_WRITE_FAILED,
FT_EEPROM_ERASE_FAILED,
FT_EEPROM_NOT_PRESENT,
FT_EEPROM_NOT_PROGRAMMED,
FT_INVALID_ARGS,
FT_NOT_SUPPORTED,
FT_OTHER_ERROR
};
#define FT_SUCCESS(status) ((status) FT_OK)
//
// FT_OpenEx Flags
//
#define FT_OPEN_BY_SERIAL_NUMBER 1
#define FT_OPEN_BY_DESCRIPTION 2
#define FT_OPEN_BY_LOCATION 4
//
// FT_ListDevices Flags (used in conjunction with FT_OpenEx Flags
//
#define FT_LIST_NUMBER_ONLY 0x80000000
#define FT_LIST_BY_INDEX 0x40000000
#define FT_LIST_ALL 0x20000000
#define FT_LIST_MASK (FT_LIST_NUMBER_ONLY|FT_LIST_BY_INDEX|FT_LIST_ALL)
//
// Baud Rates
//
#define FT_BAUD_300 300
#define FT_BAUD_600 600
#define FT_BAUD_1200 1200
#define FT_BAUD_2400 2400
#define FT_BAUD_4800 4800
#define FT_BAUD_9600 9600
#define FT_BAUD_14400 14400
#define FT_BAUD_19200 19200
#define FT_BAUD_38400 38400
#define FT_BAUD_57600 57600
#define FT_BAUD_115200 115200
#define FT_BAUD_230400 230400
#define FT_BAUD_460800 460800
#define FT_BAUD_921600 921600
//
// Word Lengths
//
#define FT_BITS_8 (UCHAR) 8
#define FT_BITS_7 (UCHAR) 7
#define FT_BITS_6 (UCHAR) 6
#define FT_BITS_5 (UCHAR) 5
//
// Stop Bits
//
#define FT_STOP_BITS_1 (UCHAR) 0
#define FT_STOP_BITS_1_5 (UCHAR) 1
#define FT_STOP_BITS_2 (UCHAR) 2
//
// Parity
//
#define FT_PARITY_NONE (UCHAR) 0
#define FT_PARITY_ODD (UCHAR) 1
#define FT_PARITY_EVEN (UCHAR) 2
#define FT_PARITY_MARK (UCHAR) 3
#define FT_PARITY_SPACE (UCHAR) 4
//
// Flow Control
//
#define FT_FLOW_NONE 0x0000
#define FT_FLOW_RTS_CTS 0x0100
#define FT_FLOW_DTR_DSR 0x0200
#define FT_FLOW_XON_XOFF 0x0400
//
// Purge rx and tx buffers
//
#define FT_PURGE_RX 1
#define FT_PURGE_TX 2
//
// Events
//
typedef void (*PFT_EVENT_HANDLER)(DWORD,DWORD);
#define FT_EVENT_RXCHAR 1
#define FT_EVENT_MODEM_STATUS 2
//
// Timeouts
//
#define FT_DEFAULT_RX_TIMEOUT 300
#define FT_DEFAULT_TX_TIMEOUT 300
//
// Device types
//
typedef ULONG FT_DEVICE;
enum {
FT_DEVICE_BM,
FT_DEVICE_AM,
FT_DEVICE_100AX,
FT_DEVICE_UNKNOWN,
FT_DEVICE_2232C
};
#ifdef __cplusplus
extern " C " {
#endif
FTD2XX_API
FT_STATUS WINAPI FT_Open(
int deviceNumber,
FT_HANDLE *pHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_OpenEx(
PVOID pArg1,
DWORD Flags,
FT_HANDLE *pHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_ListDevices(
PVOID pArg1,
PVOID pArg2,
DWORD Flags
);
FTD2XX_API
FT_STATUS WINAPI FT_Close(
FT_HANDLE ftHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_Read(
FT_HANDLE ftHandle,
LPVOID lpBuffer,
DWORD nBufferSize,
LPDWORD lpBytesReturned
);
FTD2XX_API
FT_STATUS WINAPI FT_Write(
FT_HANDLE ftHandle,
LPVOID lpBuffer,
DWORD nBufferSize,
LPDWORD lpBytesWritten
);
FTD2XX_API
FT_STATUS WINAPI FT_IoCtl(
FT_HANDLE ftHandle,
DWORD dwIoControlCode,
LPVOID lpInBuf,
DWORD nInBufSize,
LPVOID lpOutBuf,
DWORD nOutBufSize,
LPDWORD lpBytesReturned,
LPOVERLAPPED lpOverlapped
);
FTD2XX_API
FT_STATUS WINAPI FT_SetBaudRate(
FT_HANDLE ftHandle,
ULONG BaudRate
);
FTD2XX_API
FT_STATUS WINAPI FT_SetDivisor(
FT_HANDLE ftHandle,
USHORT Divisor
);
FTD2XX_API
FT_STATUS WINAPI FT_SetDataCharacteristics(
FT_HANDLE ftHandle,
UCHAR WordLength,
UCHAR StopBits,
UCHAR Parity
);
FTD2XX_API
FT_STATUS WINAPI FT_SetFlowControl(
FT_HANDLE ftHandle,
USHORT FlowControl,
UCHAR XonChar,
UCHAR XoffChar
);
FTD2XX_API
FT_STATUS WINAPI FT_ResetDevice(
FT_HANDLE ftHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_SetDtr(
FT_HANDLE ftHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_ClrDtr(
FT_HANDLE ftHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_SetRts(
FT_HANDLE ftHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_ClrRts(
FT_HANDLE ftHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_GetModemStatus(
FT_HANDLE ftHandle,
ULONG *pModemStatus
);
FTD2XX_API
FT_STATUS WINAPI FT_SetChars(
FT_HANDLE ftHandle,
UCHAR EventChar,
UCHAR EventCharEnabled,
UCHAR ErrorChar,
UCHAR ErrorCharEnabled
);
FTD2XX_API
FT_STATUS WINAPI FT_Purge(
FT_HANDLE ftHandle,
ULONG Mask
);
FTD2XX_API
FT_STATUS WINAPI FT_SetTimeouts(
FT_HANDLE ftHandle,
ULONG ReadTimeout,
ULONG WriteTimeout
);
FTD2XX_API
FT_STATUS WINAPI FT_GetQueueStatus(
FT_HANDLE ftHandle,
DWORD *dwRxBytes
);
FTD2XX_API
FT_STATUS WINAPI FT_SetEventNotification(
FT_HANDLE ftHandle,
DWORD Mask,
PVOID Param
);
FTD2XX_API
FT_STATUS WINAPI FT_GetStatus(
FT_HANDLE ftHandle,
DWORD *dwRxBytes,
DWORD *dwTxBytes,
DWORD *dwEventDWord
);
FTD2XX_API
FT_STATUS WINAPI FT_SetBreakOn(
FT_HANDLE ftHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_SetBreakOff(
FT_HANDLE ftHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_SetWaitMask(
FT_HANDLE ftHandle,
DWORD Mask
);
FTD2XX_API
FT_STATUS WINAPI FT_WaitOnMask(
FT_HANDLE ftHandle,
DWORD *Mask
);
FTD2XX_API
FT_STATUS WINAPI FT_GetEventStatus(
FT_HANDLE ftHandle,
DWORD *dwEventDWord
);
FTD2XX_API
FT_STATUS WINAPI FT_ReadEE(
FT_HANDLE ftHandle,
DWORD dwWordOffset,
LPWORD lpwValue
);
FTD2XX_API
FT_STATUS WINAPI FT_WriteEE(
FT_HANDLE ftHandle,
DWORD dwWordOffset,
WORD wValue
);
FTD2XX_API
FT_STATUS WINAPI FT_EraseEE(
FT_HANDLE ftHandle
);
//
// structure to hold program data for FT_Program function
//
typedef struct ft_program_data {
DWORD Signature1; // Header - must be 0x00000000
DWORD Signature2; // Header - must be 0xffffffff
DWORD Version; // Header - FT_PROGRAM_DATA version
// 0 = original
// 1 = FT2232C extensions
WORD VendorId; // 0x0403
WORD ProductId; // 0x6001
char *Manufacturer; // " FTDI "
char *ManufacturerId; // " FT "
char *Description; // " USB HS Serial Converter "
char *SerialNumber; // " FT000001 " if fixed, or NULL
WORD MaxPower; // 0 & lt; MaxPower & lt; = 500
WORD PnP; // 0 = disabled, 1 = enabled
WORD SelfPowered; // 0 = bus powered, 1 = self powered
WORD RemoteWakeup; // 0 = not capable, 1 = capable
//
// Rev4 extensions
//
UCHAR Rev4; // non-zero if Rev4 chip, zero otherwise
UCHAR IsoIn; // non-zero if in endpoint is isochronous
UCHAR IsoOut; // non-zero if out endpoint is isochronous
UCHAR PullDownEnable; // non-zero if pull down enabled
UCHAR SerNumEnable; // non-zero if serial number to be used
UCHAR USBVersionEnable; // non-zero if chip uses USBVersion
WORD USBVersion; // BCD (0x0200 = & gt; USB2)
//
// FT2232C extensions
//
UCHAR Rev5; // non-zero if Rev5 chip, zero otherwise
UCHAR IsoInA; // non-zero if in endpoint is isochronous
UCHAR IsoInB; // non-zero if in endpoint is isochronous
UCHAR IsoOutA; // non-zero if out endpoint is isochronous
UCHAR IsoOutB; // non-zero if out endpoint is isochronous
UCHAR PullDownEnable5; // non-zero if pull down enabled
UCHAR SerNumEnable5; // non-zero if serial number to be used
UCHAR USBVersionEnable5; // non-zero if chip uses USBVersion
WORD USBVersion5; // BCD (0x0200 = & gt; USB2)
UCHAR AIsHighCurrent; // non-zero if interface is high current
UCHAR BIsHighCurrent; // non-zero if interface is high current
UCHAR IFAIsFifo; // non-zero if interface is 245 FIFO
UCHAR IFAIsFifoTar; // non-zero if interface is 245 FIFO CPU target
UCHAR IFAIsFastSer; // non-zero if interface is Fast serial
UCHAR AIsVCP; // non-zero if interface is to use VCP drivers
UCHAR IFBIsFifo; // non-zero if interface is 245 FIFO
UCHAR IFBIsFifoTar; // non-zero if interface is 245 FIFO CPU target
UCHAR IFBIsFastSer; // non-zero if interface is Fast serial
UCHAR BIsVCP; // non-zero if interface is to use VCP drivers
} FT_PROGRAM_DATA, *PFT_PROGRAM_DATA;
FTD2XX_API
FT_STATUS WINAPI FT_EE_Program(
FT_HANDLE ftHandle,
PFT_PROGRAM_DATA pData
);
FTD2XX_API
FT_STATUS WINAPI FT_EE_ProgramEx(
FT_HANDLE ftHandle,
PFT_PROGRAM_DATA pData,
char *Manufacturer,
char *ManufacturerId,
char *Description,
char *SerialNumber
);
FTD2XX_API
FT_STATUS WINAPI FT_EE_Read(
FT_HANDLE ftHandle,
PFT_PROGRAM_DATA pData
);
FTD2XX_API
FT_STATUS WINAPI FT_EE_ReadEx(
FT_HANDLE ftHandle,
PFT_PROGRAM_DATA pData,
char *Manufacturer,
char *ManufacturerId,
char *Description,
char *SerialNumber
);
FTD2XX_API
FT_STATUS WINAPI FT_EE_UASize(
FT_HANDLE ftHandle,
LPDWORD lpdwSize
);
FTD2XX_API
FT_STATUS WINAPI FT_EE_UAWrite(
FT_HANDLE ftHandle,
PUCHAR pucData,
DWORD dwDataLen
);
FTD2XX_API
FT_STATUS WINAPI FT_EE_UARead(
FT_HANDLE ftHandle,
PUCHAR pucData,
DWORD dwDataLen,
LPDWORD lpdwBytesRead
);
FTD2XX_API
FT_STATUS WINAPI FT_SetLatencyTimer(
FT_HANDLE ftHandle,
UCHAR ucLatency
);
FTD2XX_API
FT_STATUS WINAPI FT_GetLatencyTimer(
FT_HANDLE ftHandle,
PUCHAR pucLatency
);
FTD2XX_API
FT_STATUS WINAPI FT_SetBitMode(
FT_HANDLE ftHandle,
UCHAR ucMask,
UCHAR ucEnable
);
FTD2XX_API
FT_STATUS WINAPI FT_GetBitMode(
FT_HANDLE ftHandle,
PUCHAR pucMode
);
FTD2XX_API
FT_STATUS WINAPI FT_SetUSBParameters(
FT_HANDLE ftHandle,
ULONG ulInTransferSize,
ULONG ulOutTransferSize
);
FTD2XX_API
FT_STATUS WINAPI FT_GetDeviceInfo(
FT_HANDLE ftHandle,
FT_DEVICE *lpftDevice,
LPDWORD lpdwID,
PCHAR SerialNumber,
PCHAR Description,
LPVOID Dummy
);
FTD2XX_API
FT_STATUS WINAPI FT_StopInTask(
FT_HANDLE ftHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_RestartInTask(
FT_HANDLE ftHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_SetResetPipeRetryCount(
FT_HANDLE ftHandle,
DWORD dwCount
);
FTD2XX_API
FT_STATUS WINAPI FT_ResetPort(
FT_HANDLE ftHandle
);
FTD2XX_API
FT_STATUS WINAPI FT_CyclePort(
FT_HANDLE ftHandle
);
//
// Win32-type functions
//
FTD2XX_API
FT_HANDLE WINAPI FT_W32_CreateFile(
LPCSTR lpszName,
DWORD dwAccess,
DWORD dwShareMode,
LPSECURITY_ATTRIBUTES lpSecurityAttributes,
DWORD dwCreate,
DWORD dwAttrsAndFlags,
HANDLE hTemplate
);
FTD2XX_API
BOOL WINAPI FT_W32_CloseHandle(
FT_HANDLE ftHandle
);
FTD2XX_API
BOOL WINAPI FT_W32_ReadFile(
FT_HANDLE ftHandle,
LPVOID lpBuffer,
DWORD nBufferSize,
LPDWORD lpBytesReturned,
LPOVERLAPPED lpOverlapped
);
FTD2XX_API
BOOL WINAPI FT_W32_WriteFile(
FT_HANDLE ftHandle,
LPVOID lpBuffer,
DWORD nBufferSize,
LPDWORD lpBytesWritten,
LPOVERLAPPED lpOverlapped
);
FTD2XX_API
DWORD WINAPI FT_W32_GetLastError(
FT_HANDLE ftHandle
);
FTD2XX_API
BOOL WINAPI FT_W32_GetOverlappedResult(
FT_HANDLE ftHandle,
LPOVERLAPPED lpOverlapped,
LPDWORD lpdwBytesTransferred,
BOOL bWait
);
FTD2XX_API
BOOL WINAPI FT_W32_CancelIo(
FT_HANDLE ftHandle
);
//
// Win32 COMM API type functions
//
typedef struct _FTCOMSTAT {
DWORD fCtsHold : 1;
DWORD fDsrHold : 1;
DWORD fRlsdHold : 1;
DWORD fXoffHold : 1;
DWORD fXoffSent : 1;
DWORD fEof : 1;
DWORD fTxim : 1;
DWORD fReserved : 25;
DWORD cbInQue;
DWORD cbOutQue;
} FTCOMSTAT, *LPFTCOMSTAT;
typedef struct _FTDCB {
DWORD DCBlength; /* sizeof(FTDCB) */
DWORD BaudRate; /* Baudrate at which running */
DWORD fBinary: 1; /* Binary Mode (skip EOF check) */
DWORD fParity: 1; /* Enable parity checking */
DWORD fOutxCtsFlow:1; /* CTS handshaking on output */
DWORD fOutxDsrFlow:1; /* DSR handshaking on output */
DWORD fDtrControl:2; /* DTR Flow control */
DWORD fDsrSensitivity:1; /* DSR Sensitivity */
DWORD fTXContinueOnXoff: 1; /* Continue TX when Xoff sent */
DWORD fOutX: 1; /* Enable output X-ON/X-OFF */
DWORD fInX: 1; /* Enable input X-ON/X-OFF */
DWORD fErrorChar: 1; /* Enable Err Replacement */
DWORD fNull: 1; /* Enable Null stripping */
DWORD fRtsControl:2; /* Rts Flow control */
DWORD fAbortOnError:1; /* Abort all reads and writes on Error */
DWORD fDummy2:17; /* Reserved */
WORD wReserved; /* Not currently used */
WORD XonLim; /* Transmit X-ON threshold */
WORD XoffLim; /* Transmit X-OFF threshold */
BYTE ByteSize; /* Number of bits/byte, 4-8 */
BYTE Parity; /* 0-4=None,Odd,Even,Mark,Space */
BYTE StopBits; /* 0,1,2 = 1, 1.5, 2 */
char XonChar; /* Tx and Rx X-ON character */
char XoffChar; /* Tx and Rx X-OFF character */
char ErrorChar; /* Error replacement char */
char EofChar; /* End of Input character */
char EvtChar; /* Received Event character */
WORD wReserved1; /* Fill for now. */
} FTDCB, *LPFTDCB;
typedef struct _FTTIMEOUTS {
DWORD ReadIntervalTimeout; /* Maximum time between read chars. */
DWORD ReadTotalTimeoutMultiplier; /* Multiplier of characters. */
DWORD ReadTotalTimeoutConstant; /* Constant in milliseconds. */
DWORD WriteTotalTimeoutMultiplier; /* Multiplier of characters. */
DWORD WriteTotalTimeoutConstant; /* Constant in milliseconds. */
} FTTIMEOUTS,*LPFTTIMEOUTS;
FTD2XX_API
BOOL WINAPI FT_W32_ClearCommBreak(
FT_HANDLE ftHandle
);
FTD2XX_API
BOOL WINAPI FT_W32_ClearCommError(
FT_HANDLE ftHandle,
LPDWORD lpdwErrors,
LPFTCOMSTAT lpftComstat
);
FTD2XX_API
BOOL WINAPI FT_W32_EscapeCommFunction(
FT_HANDLE ftHandle,
DWORD dwFunc
);
FTD2XX_API
BOOL WINAPI FT_W32_GetCommModemStatus(
FT_HANDLE ftHandle,
LPDWORD lpdwModemStatus
);
FTD2XX_API
BOOL WINAPI FT_W32_GetCommState(
FT_HANDLE ftHandle,
LPFTDCB lpftDcb
);
FTD2XX_API
BOOL WINAPI FT_W32_GetCommTimeouts(
FT_HANDLE ftHandle,
FTTIMEOUTS *pTimeouts
);
FTD2XX_API
BOOL WINAPI FT_W32_PurgeComm(
FT_HANDLE ftHandle,
DWORD dwMask
);
FTD2XX_API
BOOL WINAPI FT_W32_SetCommBreak(
FT_HANDLE ftHandle
);
FTD2XX_API
BOOL WINAPI FT_W32_SetCommMask(
FT_HANDLE ftHandle,
ULONG ulEventMask
);
FTD2XX_API
BOOL WINAPI FT_W32_SetCommState(
FT_HANDLE ftHandle,
LPFTDCB lpftDcb
);
FTD2XX_API
BOOL WINAPI FT_W32_SetCommTimeouts(
FT_HANDLE ftHandle,
FTTIMEOUTS *pTimeouts
);
FTD2XX_API
BOOL WINAPI FT_W32_SetupComm(
FT_HANDLE ftHandle,
DWORD dwReadBufferSize,
DWORD dwWriteBufferSize
);
FTD2XX_API
BOOL WINAPI FT_W32_WaitCommEvent(
FT_HANDLE ftHandle,
PULONG pulEvent,
LPOVERLAPPED lpOverlapped
);
//
// Device information
//
typedef struct _ft_device_list_info_node {
ULONG Flags;
ULONG Type;
ULONG ID;
DWORD LocId;
char SerialNumber[16];
char Description[64];
FT_HANDLE ftHandle;
} FT_DEVICE_LIST_INFO_NODE;
FTD2XX_API
FT_STATUS WINAPI FT_CreateDeviceInfoList(
LPDWORD lpdwNumDevs
);
FTD2XX_API
FT_STATUS WINAPI FT_GetDeviceInfoList(
FT_DEVICE_LIST_INFO_NODE *pDest,
LPDWORD lpdwNumDevs
);
FTD2XX_API
FT_STATUS WINAPI FT_GetDeviceInfoDetail(
DWORD dwIndex,
LPDWORD lpdwFlags,
LPDWORD lpdwType,
LPDWORD lpdwID,
LPDWORD lpdwLocId,
LPVOID lpSerialNumber,
LPVOID lpDescription,
FT_HANDLE *pftHandle
);
#ifdef __cplusplus
}
#endif
#endif /* FTD2XX_H */

VAG-TACHO-USB_2.4.RAR > D2XX Release Info.txt

FTDI - D2XX Driver Release Information
Version No. Date Changes
1.06.20 15 Oct 2004 Fixed disconnect delay on WinXP.
1.06.18 30 Sep 2004 Supports modem control signals in FT_SetState.
1.06.17 23 Sep 2004 Supports FT232R.
1.06.16 23 Jun 2004 Fixed initialization bug in WinXPSP1.
Fixed WHQL EEPROM compatibility problem.
1.06.14 01 Mar 2004 Supports serial numbers up to 16 chars in length.
Fixed bug in staged write requests.
1.06.12 30 Jan 2004 Fixed synchronization problem between open and first read.
1.06.11 23 Jan 2004 Fixed problems with driver verifier.
Fixed disconnect with open port problem.
Added open by location capability.
1.06.08 24 Nov 2003 Fixed problem with FT_W32_ClearCommError not reporting errors.
Fixed serial number problem in library.
1.06.07 17 Nov 2003 Complete outstanding wait-on-event request on surprise removal.
1.06.06 30 Oct 2003 Fixed bug that limited write requests to 64Kbytes.
1.06.05 27 Oct 2003 Fixed bug in FT_W32_SetCommMask.
Added FT_ResetPort.
1.06.02 18 Sep 2003 Fixed bug in FT_W32_WaitCommEvent.
Added FT_SetResetPipeRetryCount.
1.05.12 12 June 2003 Fixed power management so that laptops can suspend.
Fixed bug in event notification.
Added FT_StopInTask and FT_RestartInTask.
1.05.09 21 Mar 2003 Fixed problem with write timeout when setup by FT_W32_SetCommTimeouts.
1.05.08 19 Mar 2003 Fixed power management problems.
FT_W32_PurgeComm purges read queue.
Added FT_W32_CancelIo.
1.05.04 08 Nov 2002 Added FT_GetDeviceInfo.
1.05.03 08 Nov 2002 Supports BM devices.
1.05.01 04 October 2002 Supports USB transfer sizes up to 64Kbytes
Works with USB2.0 host controllers
1.04.01 07 August 2002 Suspend / Resume Problem fixed with Open Devices ( Win2000 / WinXP )
1.03.20 29 July 2002 Improved Support for surprise removal ( Win2000 / WinXP )
Version Number updated in INF file

Vag Tacho Download Windows 10

VAG-TACHO-USB_2.4.RAR > Vag_USB_User_guide.doc

VAGTACHO USB for WINDOWS SOFTWARE USER
GUIDE
1. AGREEMENT
By using this software you agree the following:
THIS SOFTWARE IS PROVIDED BY ITS AUTHORS ``AS IS' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS
BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION;
DAMAGE TO ANY CAR MODULE OR DEVICE ) HOWEVER CAUSED AND ON ANY
THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
2. System requirements:
VAGTACHO.EXE is a Windows based program that will work on
any PC or laptop
that has instaled Microsoft Windows 98, 2000, ME, XP.
Hardware requrements:
Any PC or laptop with Pentium / 300MHz processor or
greater, and a free USB port.
2.1 USB Drivers instalation
Caution: This hardware interface requires drivers
instalation to work!
Please use only drivers that are supplied with this product.
There are no other or better drivers.
For all Windows XP users:
Please disconnect your PC or laptop from Internet before
install drivers!
Don't use Windows 'original' drivers! This is important!
2.2 How to install drivers:
Connect OBD interface to any free USB port. This will start
Windows procedure to install drivers for new
hardware found. Tell to Windows where the drivers are on your
harddisk.
If Windows ask you for a file with extention " .cat " , press
" Skip File " !
2.3 Uninstall drivers
If you wish to uninstall drivers, go to control panel and
uninstall drivers with standart procedure.
3. How to work with software
Connect OBD connector to car diagnostic socket.
Then connect hardware interface to any free USB port of your PC
or laptop.
Start program VagTacho.exe. Select ECU from menu. If you don't
know type of kombiinstrument,
press 'Connect Any Tacho' button. Program will try to connects
any kombi and will display type
of kombiinstrument. Then press disconnect, and select
appropriate ECU from menu. There is no
problem if you do wrong selection, but all other functions will
work only if you select right ECU.
After selecting ECU, press " Connect Selected ECU " button.
If everything is OK after 5 seconds you will see kombi info on
display and program will try
to log in to the ECU. After successful procedure, all useful
buttons on screen will be enabled.
4. Commands
4.1 Select ECU from Menu
This option selects type of ECU that user will try to connect.
* (There is selections for VW/Seat/Skoda immo box. It is
usefull only if you have an alredy working key,
and switch ignition ON with this key. Works only for Immo1
type immobilizers! )
4.2 File
User can save and read files to / from program memory buffer.
4.3 Connect Any Tacho button
By pressing this button user can connects to kombi, and read
info for any car's kombiinstrument.
This is usefull when type of kombi is unknown.
4.4 Connect Selected ECU
By pressing this button user will connects kombi or immo box
which is selected from menu.
4.5 Read Info
After pressing this button, program will shows ECU info. Press
it twice to read whole information.
4.6 Read PIN
Program will try to read PIN code for log in to the selected
ECU. If the operation was successful,
PIN code will be shown on display.
4.7 Change Mileage
This will change mileage counter on kombi display. After
pressing, program will try to read actual
mileage, then user may enter 'new' mileage and press 'Continue'
button. For some kombiinstruments,
it is required to disconnect and reconnect car battery after
this procedure.
4.7 Stop Action
Pressing this button will cancel any command that is in
progress. Not all commands can be stopped,
it is usefull only for some of them.
4.8 Read eeprom
This will read ECU eeprom memory and store data into memory
buffer.
It is usefull if program is logged in to the tacho, but can't
read PIN code automatically.
User can save whole eeprom data to a file.
4.9 Program New Key
This will open a new window. User must enter correct PIN code ,
and number of
new keys to program. Then press OK , and read messages from
software.
The number of all programmed keys must be greater than zero,
otherwise there
are some error.
Note: If you have read PIN code before this procedure, you have
to disconnect,
turn OFF ignition, then ON and connect again with " Connect
Any tacho " for tacho,
or " Connect selected ECU " for immo box.
4.10 Disconnect
End of communication command.
4.11
View memory buffer
This will show memory data on screen in another window.
4.12
Write eeprom
Same as its name. Upload file in memory first!
4.13
Clear ECU errors
This command will erase all trouble codes that are stored in
ECU memory.
5. Error Messages
In case of receiving any error message, user can try to repeat same
operation again.
If error message continue to appear on screen, this means that
there are some fatal error,
or kombiinstrument or ECU is unknown or program can't log in.
------------------------------------------------------------------------
-------------
Caution:
This software may not works on some types
kombiinstruments.
Also some automated functions also may not be executed due
to
variety of types and software versions. The autors of
this software
has no ability to test all exsiting types and models of
kombiinstruments,
and therefore there is no any guarantee that desired
actions will be executed.
Warning:
For all Motometer dashes:
There is some very important information in eeprom memory
of this types
kombiinstruments. If you erase eeprom, or corrupt original
data,in some
cases you may not be able to write or read eeprom at all !
Message
" ACCESS DENIED " will be show when you select tacho !
------------------------------------------------------------------------
-------------
For more info please write an e-mail to: kiti@maltchev.com or
see: www.opelinfo.com
Also you can contact to our distributor for United Kingdom:
www.automotiveecu.co.uk
and for USA: Mr. John Stainer e-mail:
Sumpoorguy@aol.com

VAG-TACHO-USB_2.4.RAR > UA 2.4.txt

Íq[?

VAG-TACHO-USB_2.4.RAR > SCHEMATIC VAG Tacho USB.pdf

Vag Tacho Download 2.5

1
2
3
4
5
6
R3
470R
SCK
RESET
RXF#
D3
R14 10 K
VCC
27R
1k5
D0
D0
D0
24
D1
D1
23
D2
D2
D3
22
D3
D3
21
D4
MISO
D5
20
D5
D6
19
D6
18
D7
USBDM
7
R6
25
D7
R5
D0
D4
8
27R
3V3OUT
5
27
USBDP
RSTOUT#
XTIN
12
13
14
SCK
PB0(ICP)
PB1(OC1A)
PB2(SS/OSC1B)
15
16
17
PB3(MOSI/OC2)
PB4(MISO)
PB5(SCK)
27 pF
TXE#
RESET#
93C46/56/66
( Optional )
R7
1
R8
2k2
EESK
2
1
2
3
4
EEDATA
31
TEST
PD1(TXD)
PD0(RXD)
12
RXF#
SI/WU
PC6(RESET)
28
27
PC3(ADC3)
PC2(ADC2)
PC1(ADC1)
PC0(ADC0)
26
25
24
23
PB7(XTAL2/TOSC2)
VCC
10
29
RESET
18
20
19
22
AVCC
AREF
ADC6
ADC7
RXF#
RX
WR
RD#
D7
D6
D5
ATMega8-TQFP32
D4
11
PWREN#
TX
PWREN#
GND
GND
D3 1N4007
V Bat
FT245BM
K Line
VCC
R9
680
U4
10k
TX
R12
1K
1
2
3
4
VDD
TX
CS
FAULT
SI9241
V Bat
Q1
BC807
3
1
D2
R11 1K
2
U3
CS
SK
DIN
DOUT
9
17
VCC
NC
NC
GND
TXE#
TXE#
31
30
PB6(XTAL1/TOSC1)
VCC
AGND
8
7
6
5
14
EECS
29
32
WR
9
2
1
32
3
5
21
VCC
4
15
RXF#
VCC
RD#
11
10
PD3(INT1)
PD2(INT0)
27 pF
16
WR
XTOUT
PD5(T1)
PD4(XCK/T0)
Y1
6 MHz
C13
RD#
PD7(AIN1)
PD6(AIN0)
PC5(ADC5/SCL)
PC4(ADC4/SDA)
7
C12
8
28
IC1
4
6
AVCC
U2
D2
R4
R13 10 K
MISO
D1
6
WR
VCC
J2
C6
0.1uF
30
5
C4
33nF
R15 10 K
RESET
GND
GND
GND
C5
10nF
1
2
3
4
VCC
CON6
3
26
13
CN1
CN-USB
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC-IO
USB
K Line
R1 1K
LED BI-COLOUR
RX
VBAT
K
GND
8
7
6
5
RX
Car diagnose port
1
2
3
4
J1
V Batt (+12V)
K Line
L Line
GND