Tiger 800 / 900 - Main Discussion Section > ECU Re-Mapping and Tuning

Unauthorised ECU Modifications and Warranty Claims

<< < (10/11) > >>

Stevie.P:
No engine faults detected using bike switch method equals just the same in Tigertool. The 'deeper bit' is that Tigertool allows additional things like 'service due' light reset and throttle body vacuum balancing.

Dont_Stop:
I think the smart thing to do would be, to live with your Tiger's ECU Map as is, until the warranty runs out.  If you can't do that, then realize you might be buying a new ECU yourself if your modified map runs amuck while being added. 

I myself, have a 2014 Tiger 800 and just remapped it with my own custom map using TuneECU a few days ago.  I bought it in 2013 on the showroom floor.  The remap provided a nice improvement to responsiveness at low throttle I must say.  However, after having the improvement, I'm glad that I didn't risk my warranty.  I learned to live with the hesitation.  Now the hesitation is gone and I'm enjoying it.   Having the improvement, if I could do it again, I still would not risk it. 

On another note, my DealerTool software and OBD II Connection often will not connect and often can't be located by DealerTool when I open I open the software.  This causes DealerTool to shut down.  So, I needed Tune ECU anyway. I know one of the problems with DealerTool is the drivers.  I've reloaded the drivers over and over and I get it to work for a short period then it quits again next time I try to use it. 

I bought a new $15 USB OBD II connection for TuneECU that works great with TuneECU but does not seem to work with DealerTool.  Any thoughts?  Seems to have something to do with the comms port and serial vs USB.  The OBD reader that came with DealerTool is recognized through a serial comms port.  The one I just bought is recognized as a USB device by the computer and TuneECU.  Both are USB but, recognized differently based on the drivers I would guess. 

KildareMan:
A "normal" cable that'll work with tuneecu won't work with dealer tool as you've found because the dealer tool cable has custom hardware in the plug.

T800XC:
Originally Posted by Dont_Stop On another note, my DealerTool software and OBD II Connection often will not connect and often can't be located by DealerTool when I open I open the software.  This causes DealerTool to shut down.  So, I needed Tune ECU anyway. I know one of the problems with DealerTool is the drivers.  I've reloaded the drivers over and over and I get it to work for a short period then it quits again next time I try to use it. 

I bought a new $15 USB OBD II connection for TuneECU that works great with TuneECU but does not seem to work with DealerTool.  Any thoughts?  Seems to have something to do with the comms port and serial vs USB.  The OBD reader that came with DealerTool is recognized through a serial comms port.  The one I just bought is recognized as a USB device by the computer and TuneECU.  Both are USB but, recognized differently based on the drivers I would guess.

One of the issues with the DealerTool interface is that they don't necessarily (in my experience) use genuine FTDI USB interface chips. From what I've seen the V2 DT interface is one of the better quality far eastern copies of an ELM327-based OBD2 interface, although they have since changed again to the V2.5 interface using the Prolific PL2303 USB interface chip.

Occasionally when Windows runs an update it will also update the USB driver for the interface chip which can cause issues. A couple of years back things went awry slightly when FTDI released a new driver that bricked some of the cloned chips, and therefore many 1000s of cheap OBD2 interfaces. Although it was possible (but tricky) to resolve this, FTDI lost a lot of friends over this action, particulary in the OBD market since very few interfaces use genuine FTDI chips. If you get the interface working successfully you can instruct Windows not to update the driver if/when a new one is released and this should stop it from failing again.

You can download all of the latest DealerTool USB drivers here, including those for 64-bit Win8 onwards.

http://dealertoolcouk.ipage.com/downloads17.htm


As Kildareman has said, a standard TuneECU lead will never work with DealerTool. TuneECU uses discrete components and their own software control to drive the necessary OBD lines to talk to the ECU whereas the DealerTool interface uses the ELM327 chip (or a clone of it) to handle all of the logic and line driving making coding more simple, so you just need to use the correct commands and let the ELM327 chip worry about the rest.

Gasman:
Originally Posted by paul_o Easy fix - fit a PC5

Simples

What's a PC5?  :084:

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version