Jun 16, 2012 - I wrote a lot of the 29Bit stuff in MonoDevelop / C# / GTK+, which meant that the software could be run on Windows. 29Bit Can / ALDL / 11Bt Can is all the same, just the syntax of the commands and data sent to the Logger changes. The MSVBxxx.dll is just the visual basic run time library mate. Feb 26, 2014 Hi all, this question is on the use of the aldl cable and a vt v6 ecotec. Now I recently purchased a aldl to USB cable. The reason I got it was to read. ALDLdroid is an application for OBD1 GM (ALDL) ECMs. It is currently compatible with both 160 baud and 8192 baud protocols. The application has also been used beyonds GM ECMs such as BMW N54, DSM, etc etc. Endnote Keygen X7 Corel here. OBD-II support is in there but has not been extensively tested. It is compatible with TunerPro files (ADX),.

Prodad Mercalli V4 Serial Killers. Hi all, this question is on the use of the aldl cable and a vt v6 ecotec. Now I recently purchased a aldl to USB cable. The reason I got it was to read code errors on the vt.it came with efilive v4 evaluation version, I recently obtained a key for use till 2020 on it. The pro version is still some 199.00.

A little dear, I also purchased recently toad software. Now I like to do other things as well as read error codes and wipe error codes. Like read the vin and radio code and security remote code and any other info data. Would like to learn how to do this from a fellow user of aldl cable and similar software or maybe other software, at present just interested in vt v6.can anyone assist me please.ty phil. Hi all, this question is on the use of the aldl cable and a vt v6 ecotec. Now I recently purchased a aldl to USB cable. The reason I got it was to read code errors on the vt.it came with efilive v4 evaluation version, I recently obtained a key for use till 2020 on it.

The pro version is still some 199.00. A little dear, I also purchased recently toad software. Now I like to do other things as well as read error codes and wipe error codes. Like read the vin and radio code and security remote code and any other info data. Would like to learn how to do this from a fellow user of aldl cable and similar software or maybe other software, at present just interested in vt v6.can anyone assist me please.ty phil.

I bought a scanguageII, only after I asked the buyer if it would fit my 90series. This was there answer:. 'According to the Manufacturer if your vehicle was made after 1996 (which your was), it has an OBDII connector that ScanGaugeII will fit. It also works on the Toyota Land Cruiser 1995 and above. The only significant difference with the Prado is the steering is on the right side. They also state that it will fit all vehicles except the Jeep Liberty with the diesel engine that does not report fuel use or trip functions and some of the gauges.' I fitted the unit but certain feature don't work, like scan.guage.trip functions.

Has anyone else fitted this unit to there 90 Series and did it work for you or did you have problems as well, and were thet fixable???? Does anyone have any information relating to the data format used in the 90 series? That is if there even is a data interface, I assume toyota have a scan tool that can read the ECU vitals? I was looking at making a small unit to monitor the ECU functions, I currently make them for pre OBDII commodores (also logs to a SD card so can playback recordings) so can adapt the ALDL interface to suit the Toyota. Having no information on what the ECU has in terms of data interface makes it hard to start this project!

I hope this help: 1990 - 1996 Toyota (like the other manufactures) came up with their own ECM digital data stream called TDCL (Toyota Diagnostic Comm Link). This transmits a few basic engine parameters at a snail's pace (taking 1 sec!). 1996 USA forced Toyota to be OBDII compliant.

Toyota did, but only for USA models. The rest of the world Toyota continued with it's TDCL snails pace serial data protocol. OBDI (TDCL) = 100baud = 1.25secs data refresh OBDII = 10,400baud = 0.2secs data refresh 2006 Australia force Toyota to be OBDII compliant So an American 1996 4Runner / Tacoma / T100 / Colarado with a 5VZ-FE engine is OBDII. It has a OBDII port (TDCL3) in the driver's footwell area, and the ECM Pin19 = 'SDL' So an Australian 1996 Prado with a 5VZ-FE engine is not OBDII.

It has a OBDI (TDCL1) 'Diagnostic' port in it's engine bay and requires counting the CEL. The ECM Pin19 = 'VF1' serial data stream if TE2 is shorted = SNAIL's PACE LIMITED DATA It is possible to digitally read the fault codes & digitally read the OBD1 (TDCL1) Serial Data. You can home make something (Arduino or CarTester8000). Info see here: DIY for $8 see here: Many v. Expensive scantools state they will read OBDI fault codes too. But all these just digitally count the CEL light flashes (via W pin) and take the same time as if a human were doing it. They do offer the benefit of looking up the code for you and presenting it + info nicely, but google is much more powerful than a library hard coded by a software programmer (not mechanic).