Notices
ECU Flash

Need help w/ECUFlash 1.40 - Not responding

Thread Tools
 
Search this Thread
 
Old Dec 6, 2008 | 10:53 AM
  #1  
deathtracks's Avatar
Thread Starter
Newbie
iTrader: (4)
 
Joined: Sep 2006
Posts: 73
Likes: 0
From: Utah
Need help w/ECUFlash 1.40 - Not responding

I have used EcuFlash 1.29a for a quite a while now but wanted to utilize the periphery bits so I upgraded to 1.40 and it won't connect or respond. I have the original Taxtrix cable and uninstalled all the old drivers, 1.29a and then upgraded to the new drivers with 1.40 but still nothing.

EcuFlash 1.40 just ends up saying not responding but 1.29a works fine with the new drivers and so does Mitsulogger and EVOScan so it seems to be EcuFlash 1.40. I tried EcuFlash 1.35 and it doesn't respond either.

Does anyone have any suggestions to get EcuFlash 1.40 working? I'm out of ideas. This is installed on an HP ZD7000A laptop with XP SP2 if that helps.

Thanks for any ideas.
Reply
Old Dec 6, 2008 | 03:13 PM
  #2  
evo4mad's Avatar
Former Sponsor
iTrader: (4)
 
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
Originally Posted by deathtracks
I have used EcuFlash 1.29a for a quite a while now but wanted to utilize the periphery bits so I upgraded to 1.40 and it won't connect or respond. I have the original Taxtrix cable and uninstalled all the old drivers, 1.29a and then upgraded to the new drivers with 1.40 but still nothing.

EcuFlash 1.40 just ends up saying not responding but 1.29a works fine with the new drivers and so does Mitsulogger and EVOScan so it seems to be EcuFlash 1.40. I tried EcuFlash 1.35 and it doesn't respond either.

Does anyone have any suggestions to get EcuFlash 1.40 working? I'm out of ideas. This is installed on an HP ZD7000A laptop with XP SP2 if that helps.

Thanks for any ideas.
There is already threads on here that discussed this when it was first released. you just have an older cable. but ecuflash 1.40 doesn't have any extra features for evo8 anyway. so just stick to v1.29a
Reply
Old Dec 6, 2008 | 03:14 PM
  #3  
evo4mad's Avatar
Former Sponsor
iTrader: (4)
 
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
just keep an eye on the Endian settings, I can't remember what version it changed in.
Reply
Old Dec 6, 2008 | 05:16 PM
  #4  
deathtracks's Avatar
Thread Starter
Newbie
iTrader: (4)
 
Joined: Sep 2006
Posts: 73
Likes: 0
From: Utah
Thanks but the endian settings didn't seem to matter as I had changed those when putting back my mods to the XML files. I wanted to use the blob bits (periphery bits) functionality of the new version to get rid of the timing variances (which 1.29a doesn't do).

Any other ideas?

Thanks for any tips/pointers to resolve.
Reply
Old Dec 6, 2008 | 06:35 PM
  #5  
dan l's Avatar
Account Disabled
iTrader: (3)
 
Joined: Apr 2006
Posts: 1,029
Likes: 0
From: USA
Email tactrix. You may have an issue with the serial number on your cable that needs to be updated. 1.40 is confused by your serial # when it looks at it to confirm it is a legit cable and it pegs the processor. tactrix will help you change the serial # on your cable so that 1.40 is compatible with it.
Reply
Old Dec 6, 2008 | 11:28 PM
  #6  
deathtracks's Avatar
Thread Starter
Newbie
iTrader: (4)
 
Joined: Sep 2006
Posts: 73
Likes: 0
From: Utah
Thanks for the pointer. I've e-mailed them and will see if there is a firmware update for the ealier cables.

Thanks again!
Reply
Old Dec 31, 2008 | 06:34 PM
  #7  
GTijoejoe's Avatar
Evolved Member
iTrader: (25)
 
Joined: May 2008
Posts: 2,110
Likes: 12
From: Ohio
Originally Posted by dan l
Email tactrix. You may have an issue with the serial number on your cable that needs to be updated. 1.40 is confused by your serial # when it looks at it to confirm it is a legit cable and it pegs the processor. tactrix will help you change the serial # on your cable so that 1.40 is compatible with it.
I had the same issue, got tractrix to help me reserialize my cable.

My issue was with 1.40, it would always freeze when you tried to communicate with the ecu. Now after reserializing the cable it gives me an error and the data log says:

[20:20:03.706] Using interface OpenPort 1.3 Universal TX29HmBS7366b6c553611ea15b277e98b33ff49180f428ae

So it still doesn't work......yet
Reply
Old Dec 31, 2008 | 06:43 PM
  #8  
evo4mad's Avatar
Former Sponsor
iTrader: (4)
 
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
If it is a cable you purchased from me at limitless.co.nz you can return it to me and I will provide a fully tested working cable, i test all my cables individually on ecuflash v1.40 and I test them on new unreleased versions of ecuflash also.
Reply
Old Dec 31, 2008 | 07:42 PM
  #9  
GTijoejoe's Avatar
Evolved Member
iTrader: (25)
 
Joined: May 2008
Posts: 2,110
Likes: 12
From: Ohio
Originally Posted by evo4mad
If it is a cable you purchased from me at limitless.co.nz you can return it to me and I will provide a fully tested working cable, i test all my cables individually on ecuflash v1.40 and I test them on new unreleased versions of ecuflash also.
YES! I do believe I got my cable from Limitles.co.nz.
You have PM.
Reply
Old Dec 31, 2008 | 07:43 PM
  #10  
evo4mad's Avatar
Former Sponsor
iTrader: (4)
 
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
please do not use PM, please use my website to contact me, because the support call messages pop up on my screen when I'm online via my website, its a lot easier too because I have my address and other preloaded responses, thanks.
Reply
Old Jan 1, 2009 | 12:43 PM
  #11  
deathtracks's Avatar
Thread Starter
Newbie
iTrader: (4)
 
Joined: Sep 2006
Posts: 73
Likes: 0
From: Utah
Update: reserializing the cable did the trick. Thanks for the help
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
s.lamoureux
ECU Flash
3
Dec 12, 2010 04:11 PM
GTijoejoe
ECU Flash
7
Apr 12, 2009 04:23 PM
Boltz.
ECU Flash
2
Dec 22, 2008 03:15 PM
HOSTILE_EVO
ECU Flash
18
Feb 11, 2008 11:47 AM




All times are GMT -7. The time now is 02:53 PM.