Jump to content
SAU Community

Recommended Posts

ECUTalk v1.3.5 final has been released (along with beta 7 before it), which mainly just adds support for Active Suspension control unit (on Q45 Infiniti and similar) amongst other minor changes:

ECUTalk v1.3.5 final - Changes from v1.3.5 beta6 below:

  • #113 Make log files .csv rather than .txt
  • #114 Provide minimum log update functionality
  • #115 Attempt ED connection if EF fails
  • #116 Add support for Active Suspension control unit
  • #117 Fix 'Code 55' for Diesel to say 'No Errors Detected'
  • #118 Remove Flush Wait Time option (still in .ini)
  • #119 Support unlisted serial port names via ini file
  • #120 Add dec points to Height sensor (inches)/MPG

ECUTalk v1.3.5 can be downloaded from here.

  • Replies 149
  • Created
  • Last Reply

Top Posters In This Topic

Just bought one of your cables cheers Peter. Would be awesome if you could write ECUtalk for android especially considering it comes with a handy USB plug such as on the samsung galaxy s :D.

as far as im aware, no FTDI drivers for android? once there are, assuming android devices have USB host, and assuming mono for android works well (in early stages - http://tirania.org/blog/archive/2011/Jan-04.html) then ECUTalk v1.4.0 out soon, will have a fair few changes which will improve chances of it working with mono.

but FTDI would be the first hurdle - http://www.ftdichip.com/Drivers/VCP.htm

email FTDI if you want to add an extra request for android drivers. and perhaps google FTDI android drivers and see what's doing. i think some people are trying to port drivers to android or something.

ipaq, a windows mobile pocket pc. something with the 22pin connector (not new ones with just mini usb).

bigcol on aus300zx had a thread with his installation but all the pictures are down. here's another.

http://www.ecutalk.com/compatibility.aspx

  • 3 years later...

Here is how to make an Ipaq serial cable so you can connect your Ipaq to your Consult serial cable so you can use Ecutalk on your PocketPC. This will work on all IPAQ 1900, 2200, 2400, 3800, 5400 and 5500 Series models. I made one for my HP IPAQ h5550 and it works perfect

IPAQcon.pdf

Does anyone actually have EcuXtend?

doubt many people actually bought it considering they were charging $600 before ecutalk came out, and perhaps $200 which is still way too much, after it came out.

about the only one who may have any idea would be caz from cazracing (no longer in business) who tried it herself (as she was a reseller i imagine). aus300zx forums might be best place to find her if she's still active

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Similar Content

  • Latest Posts

    • Well, yes, every CU on the bus is available via the Consult port, but whether the scanner you are using is capable of talking to the TCU, the ABS/TCS modules, etc etc, is what is at question here. Many of them are only for engine codes. So, if you have one of those, you won't know if the ABS is having a bitch.
    • That's now. R chassis Skylines come from a time when the tolerance in the ADRs was a bit more....slack. My car, on 235/35-17, which is damn near the exact same size as the original 205/55-16, is pretty much bang on correct indicated speed across the whole legal range. That's demonstrated with constant speed run over 5km, and GPS speed. It's just the luck of the draw. My particular speedo head has to be the thing that is "calibrated" that way, because everything else (the diff ratio, the gearbox and the speedo drive**) are all same same as most other Skylines. **OK, so the speedo drive is a Navara unit to drive the R32's cable, not the electronic unit than an R33/4 would normally have with teh same gear on it. Otherwise, I applaud your OCD tendencies, and I would do the same if I needed to.
    • Not too sure, I believe the Nissan consult port does everything? Also just filled up the reservoir to full and the light is still on. The float seems to move up and down fine.
    • The speedo's can be very conservative, when my Mazda NC MX5 speedo is showing 118kph, the GPS, and a calibrated radar.... cop mate.....hits me at around 110kph +/- 1 or 2 kph, and that is on a 215/45 17, stock tyres size is 205/45 17 as well, so weirdly conservative with stock tyre size When my Commodore speedo red 116kph GPS had me at 110kph on 255/40 17, so again conservative Google says manufacturers need to set the speedo from 4 to 10% slower than actual road speed.....for safety.....and compliance  After doing some offset and clearance measurements to see what can fit the NC on 17x8 +40, without guard rolling or rubbing anything at my current ride height, I've decided that when my tyres are toast, I'm going to fit 225/45 17 and see where that gets me IRT actual speed of my speedo and GPS/radar From the online calculator I should be still be doing around 5kph under an actual 110kph when the speedo is showing 110kph My ADHD requires that when I'm doing 110kph on the speedo, that the actual road speed is actually really close to that, and not alot slower And going from 205 to 225 still keeps the car within the %/mm allowable in the NSW vehicle rules and regulations, which is nice, as long as I'm looking at the latest version that is.....LOL https://www.nsw.gov.au/sites/default/files/2021-02/RMS-13.464-Light-vehicle-modifications-Vehicle-Standards-Information-No-6-November-2013.pdf
    • Take the value it measured as, and pick the closest range available that is above the reading on the screen.   Also, no point just testing the coils. Read what has been said again. You need to test all your wiring, everything.
×
×
  • Create New...