2002/2003 Alphard 2.4L : Techstream Error Code 0xA1050308

[Geralt]

I bought Techstream v18 with MVCI cable off eBay and wanted to share my (rather limited) success.

 

I am able to connect by selecting 0205-0401 (May 2002 to Jan 2001). It reads DTCs and live data* from only 3 ECUs: Engine, ABS and Immobilizer. This in itself is not surprising for a 20 year old car where there is no CAN bus. I think diagnostics for anything other than emissions related ECUs was in its infancy.

 

*Even with the Engine ECU, I can read data but only one snapshot. After a few seconds I get a dialogue saying lost communication with vehicle with error code 0xA1050308:

 

 

The error logs don't really give much detail.

 

1) Has anybody encountered this "Lost comms with vehicle" for any Alphard MY? Have you solved it please?

2) Has anybody with an 2002/2003 2.4L vehicle been able to communicate with ECUs other than the ones listed above?

 

Thank you very much.

[PaulE]

You might try earlier versions - I use v14.30.23 for 2005 hybrid- could just be a case of finding the correct version that suits your vehicle.

[Geralt]

1 hour ago, PaulE said:

You might try earlier versions - I use v14.30.23 for 2005 hybrid- could just be a case of finding the correct version that suits your vehicle.

Many thanks. I'll certainly give that a try.

[charlaph]

How did you get on? I'm having similar issues with my 2004 Alphard, I've got techstream working, the cable is functioning, drivers loaded and the vehicle is recognised, but I can't connect to most ECUs, getting the ECU not recognised message and can't make and changes. I only bought it to turn off the reverse beeps so it's not life or death but I've tried techstream 10 and 12 and they're both the same so I'm wondering if it's the cable or the software that's causing my issue 

[Geralt]

An earlier version (v17) made no difference.

 

I could be wrong but I think the diagnostic options are very limited on the 2003 - 2004 Alphards to those ECUs which can affect tailpipe emissions via K-Line i.e. Engine/Transmission and ABS and that's why you can't connect to other ECUs on your 2004.

 

According to your profile you have a 2007 model (too) so how do you get on with that? If you can talk to loads more ECUs I think this probably proves my theory.

 

I haven't solved my issue yet but I have a plan to use an Arduino to log the K-Line comms and see who's at fault. Techstream or Engine ECU. Whether it gets to the top of my To Do list we shall see.

Edited June 18, 2023 by Geralt

[Geralt]

I tried Techstream v12 today using the Virtual Machine (Win XP) method but I get identical results. So I'm further convinced it's either the vehicle or the MVCI cable. Looks like I'll have to try debugging with the Arduino after all.

[charlaph]

I've edited my profile, only got a 2004, not sure why I put a 2007 down.

 

So far I've tried techstream 10,12,16 and 17 using virtual machines with xp and I did the method for loading drivers into win10 so you can use it with a 64 bit machine directly, it's the same with all of them so I'm thinking it's the cable or the vehicle. I'm loathe to spend ~£60 on the 'guaranteed' cable when it might be a vehicle issue.

Guess I'll live with the beeps for now, I was planning on taking it to an Alphard specialist for a full going over at some point so when I do I'll ask them to take a stab at it.

[Geralt]

On 7/2/2023 at 9:21 AM, charlaph said:

so I'm thinking it's the cable or the vehicle.

I'm fairly convinced your vehicle (and mine) doesn't support diagnostics for ECUs other than Engine, ABS and immoblizer. Switching off the reverse beeps therefore won't be possible by diagnostics.

 

[Geralt]

I happened to use Techstream v17 (same laptop, same MVCI cable) on a 2004 hybrid and it worked without an issue. This problem must be confined to my model year (2002) or my vehicle. Again, I'd appreciate if anybody who has got Techstream to work with a 2002 or 2003 model to confirm please.

Edited October 10, 2023 by Geralt

[MonsterS]

On 6/25/2023 at 7:00 PM, Geralt said:

I tried Techstream v12 today using the Virtual Machine (Win XP) method but I get identical results. So I'm further convinced it's either the vehicle or the MVCI cable. Looks like I'll have to try debugging with the Arduino after all.

It's the virtual machine. Never works correctly. Try a physical hard drive and in a laptop. I had the same and as soon as I put it 9n the laptop it worked.

[Geralt]

23 minutes ago, MonsterS said:

Try a physical hard drive and in a laptop.

Thanks but that's how I started the topic: V18 with Win 10. The VM was just an experiment.

In my latest post, I explain that my laptop and cable works with a 2004 hybrid so most likely it's the specific 2002/2003 2.4L ECM software that's at fault.

[Chris.ac]

those early alphards were based on the granvia, there is not really a canbus to be spoken of, so not much can be accessed via techstream beyond engine.

any customisation would probably be accessible via the toyota head unit, or voodoo turning of the ignition key whilst holding a button or flicking a lightstalk.