1. Attachments are working again! Check out this thread for more details and to report any other bugs.

Techstream cannot read HV Battery ECU data list

Discussion in 'Generation 1 Prius Discussion' started by Neil-London, May 25, 2015.

  1. Neil-London

    Neil-London New Member

    Joined:
    May 25, 2015
    5
    0
    0
    Location:
    London UK
    Vehicle:
    2000 Prius
    Model:
    I

    I have a Prius gen I Japanese import to the UK. It's a year 2000 according to the importer. It's recently been getting P3000-123 & P3006 DTC's, so I'm investigating getting a new HV battery.
    I'm using a Mini VCI with firmware 1.4.1 and have tried various versions of Techstream, but I always get a lost comms error (error code 0xA1050304) while trying to read the Data List from the HV Battery ECU.

    lost comms.png

    I can read the Freeze Frame Data when the DTC is active, just cannot read live data. All other 6 ECUs seem to communicate OK. I'm just not able to get live data from the ECU I'm most interested in!
    I wonder if anyone has any experience of this comms problem and hopefully a solution, or suggestions I could try.
    Thanks.
     
    #1 Neil-London, May 25, 2015
  2. bwilson4web

    bwilson4web BMW i3 and Model 3

    Joined:
    Nov 25, 2005
    27,134
    15,393
    0
    Location:
    Huntsville AL
    Vehicle:
    2018 Tesla Model 3
    Model:
    Prime Plus
    You might check with the New Zealand Prius owners. They have cracked a lot of the 'Gen 0' Prius functions.

    Bob Wilson
     
    #2 bwilson4web, May 25, 2015
  3. Neil-London

    Neil-London New Member

    Joined:
    May 25, 2015
    5
    0
    0
    Location:
    London UK
    Vehicle:
    2000 Prius
    Model:
    I
    Bob,
    Thanks for your reply. I'm not sure how to contact the New Zealand Prius owners & I still need to do the research as you suggest into the 'Gen 0' ECU's. My car is a Gen I, NHW11 first registered in Japan in June 2000. The later versions of Techstream automatically identify it as an NHW11 as well. I was thinking my comms problem could be a timeout issue. I understand that the HV battery ECU talks through the Hybrid ECU, is this correct? Maybe it's just I have a very very slow Mini VCI. Now the weekend is almost here I will have some more time to do research.
    Thanks
    Neil
     
    #3 Neil-London, May 29, 2015
  4. bwilson4web

    bwilson4web BMW i3 and Model 3

    Joined:
    Nov 25, 2005
    27,134
    15,393
    0
    Location:
    Huntsville AL
    Vehicle:
    2018 Tesla Model 3
    Model:
    Prime Plus

    Just to be sure, this one has the cylinder, "D" size cells in the traction battery?

    The last time I checked, the New Zealand group hangs out here:
    Yahoo! Groups

    GOOD LUCK!
    Bob Wilson
     
    #4 bwilson4web, May 29, 2015
  5. Neil-London

    Neil-London New Member

    Joined:
    May 25, 2015
    5
    0
    0
    Location:
    London UK
    Vehicle:
    2000 Prius
    Model:
    I
    Bob,
    My car is a NHW11 (Gen 1) with the prismatic batteries. I understand it was the NHW10 (Gen 0) that had the "D" cells and the battery case is quite different. Please see attached photos of my cars HV battery.
    HV Batt.png HV Batt label.png
    I assume that the NHW11 was produced from May 2000 when the production switched Toyota plants. The following quote (with the links removed) is from the Wikipedia page for Toyota Prius;
    "Production commenced in December 1997 at the Takaoka plant in Toyota, Aichi, ending in February 2000 after cumulative production of 37,425 vehicles. Production recommenced in May 2000 at the Motomachi plant in the same area, before XW10 manufacture ended in June 2003 after a further 33,411 vehicles had been produced"

    Thanks for the link to the NZ Yahoo group. The group description says they are a forum for the NHW10. Do you suggest I still pursue trying to get live data from the HV battery ECU using NHW10 comms? I've found a webpage ( Quick guide to scanning NHW10 ) which describes using a VAG COM K-line to USB adaptor and TECU 3 software application developed by a Russian enthusiast.

    Does anyone know how to extend the comms timeout on Techstream or should I buy another Mini VCI to see if it is just mine being very slow? The comms error I am seeing when trying to get live HV battery data appears after almost 1 minute.
    Regards
    Neil
     
    #5 Neil-London, May 30, 2015
  6. a_triant

    a_triant Member

    Joined:
    Mar 4, 2015
    83
    33
    0
    Location:
    Earth
    Vehicle:
    Other Hybrid
    Model:
    N/A
    Exactly same issue i has, on a Lexus GS450h, all ECU's was readable except the hybrid control ECU, when i tried to connect to it always it said connection lost, and as you say freeze data from that ECU was readable also, firstly i thought maybe that the MVCI cable problem, later about year after i got a new laptop and surprised that it started reading that hybrid control ECU, so my thoughts are that the problem is in slow computer, my old laptop was HP 6735s and it worked very slow...
     
    #6 a_triant, May 30, 2015
    Last edited: May 30, 2015
    bwilson4web and Patrick Wong like this.
  7. Patrick Wong

    Patrick Wong DIY Enthusiast

    Joined:
    Mar 8, 2008
    18,199
    6,464
    0
    Location:
    Green Valley, AZ
    Vehicle:
    2015 Prius
    Model:
    Two
    Do you recall the processor type and speed of the old laptop?
    Was the unit running on Windows Vista or Windows XP?

    Referring to the spec sheet, that laptop does not seem terrible - if it had one of the dual-core CPUs:
    http://www.hp.com/hpinfo/newsroom/press_kits/2008/connecting/ds_bn_6735s.pdf
     
    #7 Patrick Wong, May 30, 2015
  8. a_triant

    a_triant Member

    Joined:
    Mar 4, 2015
    83
    33
    0
    Location:
    Earth
    Vehicle:
    Other Hybrid
    Model:
    N/A
    The spec was:
    AMD Turion dual-core 2Ghz
    2Gb Ram(it has 2x1Gb and i remember one was 667Mhz and the other 800Mhz)

    I has installed Windows 7 64bit on it, later as Windows 8 64bit released i installed it
    some time earlier i runned techstream in Windows XP through VMware in Windows 7, that's because the driver installer for the cable did not worked on the systems above, but later i found how to install the driver manually on the systems above and stoped using the VMware method

    I know the spec looks fine enough to run a techstream, it's not a heavy application, that's why i did not expected before that this problem can cause the PC, my all thoughts was that the problem is in the cable.
     
    #8 a_triant, May 30, 2015
  9. Neil-London

    Neil-London New Member

    Joined:
    May 25, 2015
    5
    0
    0
    Location:
    London UK
    Vehicle:
    2000 Prius
    Model:
    I
    Thanks,
    I have generally been using a very old laptop a Sony Vaio, VGN-T30B which has a 900MHz Celeron M with 256MB RAM, running
    Windows XP Pro. I have tried this with versions 6, 7 & 8 of Techstream Recently I also found the 64 bit manual registry
    entries for the Mini VCI driver with Techstream, So I have tried a Dell Inspiron 15R SE with 2.5 GHz 3rd Gen Core i5, 6GB
    RAM, running Windows 7 Pro 64bit. This is running Techstream version 10. There doesn't seem to be any improvement in comms
    response reading from the ECU's. I still get the comms error after approx 1 minute of trying to read the live data from the HV Battery ECU.
    I didn't really know what I was doing as I hadn't spotted the Techstream DLC3 Cable Check utility before but after I found it I tried running it (with IG/Power on and Engine/ Ready off) this evening and got the following;
    Mini VCI cable check.png

    Is this normal with a Mini VCI?
    Regards
    Neil
     
    #9 Neil-London, May 30, 2015
  10. a_triant

    a_triant Member

    Joined:
    Mar 4, 2015
    83
    33
    0
    Location:
    Earth
    Vehicle:
    Other Hybrid
    Model:
    N/A
    Strange then, your Dell is very good, if no one will check the mini-vci with a DLC3 Cable Check utility then i will do it tomorrow, since almost for a year already i using a MFC Mongoose Pro cable, so i have to install the drivers to check the mini-vci with DLC3 Cable Check utility.

    Also while your cable is connected to PC, then go to Device Manager and find your cable there as USB Serial Port (COM3), then there press right-click and select properties and there you can find some settings like speed and some others, try changing them may it help, but as i remember by changing those settings did not noticed any difference.


    update:
    Checked my mini-vci with a DLC3 Cable Check utility the results are in the photo below, did the test on Toyota iQ 2010, after also checked with my MFC Mongoose Pro and it gave me exactly same result, maybe you should try your cable on another vehicle to see if the CAN-H, CAN-L will work or also a another cable on your vehicle.

    Снимок.PNG

    Alex.
     
    #10 a_triant, May 30, 2015
    Last edited: May 31, 2015
  11. Neil-London

    Neil-London New Member

    Joined:
    May 25, 2015
    5
    0
    0
    Location:
    London UK
    Vehicle:
    2000 Prius
    Model:
    I
    Alex,
    Thanks for trying and reporting the cable check with your Mini VCI.
    I did another cable check this time pressing the next button more quickly and got the following which is what I was expecting with the K-Line connected. The Gen I Prius doesn't use CAN bus.
    DLC3 cable check.PNG

    I think I'll buy another Mini VCI this time with the 2.0.4 firmware and see if that works any better. The Mongoose is very expensive and I'm trying to save up for the HV battery. I just really want to be able to read HV Battery ECU data before and after if I actually get a new battery.
    Regards
    Neil
     
    #11 Neil-London, May 31, 2015
    Last edited: May 31, 2015
  12. a_triant

    a_triant Member

    Joined:
    Mar 4, 2015
    83
    33
    0
    Location:
    Earth
    Vehicle:
    Other Hybrid
    Model:
    N/A
    Good luck Neil
    then that's in the link below is what you need maybe, but the price is x3 compared to the other mini vci's...
    I wonder if somehow is possible to update the older mini vci's to the fw 2.0.4
    2015 Original Mini VCI Diagnostic Cable for Toyota Lexus Tis Techstream FW 2 0 4 | eBay

    in description written:
    "You may not know Most of toyota and lexus vehicles before 2005 use K-Line protocol not CAN-BUS ! 99% of cheap mini vci cables on eBay don't support K-Line but CAN-BUS only."


    Alex.
     
    #12 a_triant, May 31, 2015
  13. bwilson4web

    bwilson4web BMW i3 and Model 3

    Joined:
    Nov 25, 2005
    27,134
    15,393
    0
    Location:
    Huntsville AL
    Vehicle:
    2018 Tesla Model 3
    Model:
    Prime Plus
    Now I'm wondering if there might be a loose or marginal connector? Check the connectors at the battery pack, perhaps even reseating them.

    Sorry about the NHW10 question. A by-product of the USA's weird model-year convention, I wanted to make sure of the model.

    The radio/cassette unit still works? The reason I ask is I replaced mine with a 3d party that does not have the OBD termination resistor. The MiniVCI works so I've not been terribly concerned. I need to verify the miniVCI is still working for the traction battery controller.

    Bob Wilson
     
    #13 bwilson4web, May 31, 2015
  14. vincent1449p

    vincent1449p Active Member

    Joined:
    May 24, 2004
    894
    331
    0
    Location:
    Singapore
    Vehicle:
    2012 Prius c
    P3000-123 : Input of abnormal signal from battery ECU (HV battery system malfunction)
    P3006 : Battery SOC Are Uneven
    If I were you, I would check the Battery ECU first.

    Freeze Frame Data is read from the HV ECU, not from the Battery ECU. The fact that you can read all other 6 ECUs tells me that the problem is probably not on the Mini VCI, Techstream or your laptop. Try open up your Battery ECU to see anything that is burnt or corroded (it happened to me before).

    Vincent
     
    #14 vincent1449p, Jun 1, 2015
(You must log in or sign up to post here.)