Nissan ECU Tuning

NewKleer · Joined: 09 Oct 2004 Posts: 159 Location: Sydney

ECUTalk v1.2 - http://www.ecutalk.com/

Combined Standard and Pocket PC versions into the single unified executable (single .exe also), based off the last Pocket PC release.

Added auto connect back in - it will connect on the given com port, select the sensors, and view gauges fullscreen on startup (after its set up).

Added in injector duty cycle % sensors, and added MPH and degrees F sensors (for speed/temp).

Left: Running on PC/Laptop
Right: Running on Pocket PC

More screenshots: http://www.ecutalk.com/screenshots.aspx

NewKleer · Joined: 09 Oct 2004 Posts: 159 Location: Sydney

ECUTalk v1.3 Released - http://www.ecutalk.com

Added ability to log sensors without showing them on gauges (when logging is enabled, checkboxes have a greyed out checkstate, indicated logging only)
Logging changed so it logs all packets (only gauges will drop packets/not update when cpu is falling behind, but all packets will be logged)
Colour setup for gauges added. Hard bit for you is coming up with a colour theme that looks ok!
Added Instant Fuel Economy Sensor - requires RPM, Injector and Speed kph selected to work
Changed DutyCycle/RH Sensors to calculate values from RPM and Injector/RH sensors (therefore requires them to be logged at least to work)
Fixed Timestamps when milliseconds are less than 100 (3 digits). Previously they would not have leading zeroes
Simplified gauges such that they will only display values within their range (however, logging will show the calculated value) and will no longer auto change their range to suit the values (as occasionally a weird value may be read which causes a unco gauge to be drawn).
Added an option to allow the full-screen mode to only use the "working area" of the screen. Eg, it wont cover taskbar in a normal windows desktop, and for carpc users with special frontends, it may mean gauges display properly if running ECUTalk from within your frontend.
Improved the saving of settings to .ini file. Note that the order of items in this .ini file matters - their names (what is shown before the ":") does not. Eg autoconnect, logging, selected sensors, working area option, injector size, gauge colours, etc are all stored in here.
Removed EGT sensor (it's useless, only ever reads 4.98v)

See screenshots below to better understand difference between selecting sensors for gauges (batt, duty, econ, temp) which you check once, and for logging (rpm, injector, speed) which are checked a second time to make them grey. Also shown is how you can set the colour of the gauges yourself.

RomChip200 · Joined: 27 Nov 2003 Posts: 196 Location: France

Big up !
_________________
200SX CA18DET S13 '92.
300ZX TT '91.

mookistar · Joined: 06 Feb 2007 Posts: 3

Hi,
It's Mookistar from the GTR register.

I got my cables and things tonight to hook up to my
R33 GTR.

if i use ver 1.31 it registers "reading ECU part
number" then just closes the programme.

if i use version 1.2, it connects and looks for
sensors.

but each time it only finds 2 or 3 sensors, a/f,
timing etc, and none of the gauges update/register
any readings. each time i connect it find different
sensors.

the car has been "chipped" as far as i know, by Abbey
motorsports, running a 1 bar map.

have you any ideas?

i'm using a blazt cable, null modem adaptor and
serial sync cable, on an orange SPV M2000

i hope you don't mind me asking.

Mike

NewKleer · Joined: 09 Oct 2004 Posts: 159 Location: Sydney

generally if it doesnt work, it can be any of these reasons:

1) pocket pc itself isnt good enough - confirm whether it works on a normal laptop
2) intermittent connection - ensure proper physical connection.
3) messed up remap - im not definite that consult code is included in the ecu rom, but on the assumption it is, you should probably try the setup in a car without a remap (but same model car if possible)
4) software itself is problem - obviously this is a possibilty. you could confirm if its by trying other software, eg free conzult. it may be timing differences (ie how long you wait for a response, etc) that mean one version works but another doesnt.

v1.3.2 will be released soon, give it a shot, although nothing much will have changed on the setup side of things (ie before showing gauges)

mookistar · Joined: 06 Feb 2007 Posts: 3

thanks again for the above, and the email. its been snowing here and bitterly cold so not had another chance to test it, but i "think" i got it working...

will post result when it thaws a little

lol

thanks again

mook

NewKleer · Joined: 09 Oct 2004 Posts: 159 Location: Sydney

ECUTalk v1.3.2 Released - http://www.ecutalk.com

This version fixes a few bugs and has some pretty big performance improvements.
Users of v1.3 and v1.3.1 should update to this version.
v.1.3.1 added a MPG sensor for Imperial users (and an option to switch between Imperial/Metric sensors).

Fixed issue in v1.3 and v1.3.1 which meant data packets weren't being dropped when CPU couldn't keep up
Increased performance of gauge drawing by ~250% (on my PPC, time to draw a gauge went from ~30ms down to around ~12ms).
Changed code to always draw gauges (even if data hasnt changed) in order to result in consistent amount of packets being logged per second.
Added option to specify minimum gauge update speed - higher value means more packets are logged due to less gauge updates (and hence more time for logging). Eg on my 568 Jornada PocketPC 2002, 10ms = ~5 packets logged/second, whereas 1000ms = close to full 50 packets). The setting ignored when not logging (it will just update as quickly as possible).
Improved consult streaming to allow more data to be read in and processed (rather than lost). Probably the best program for data logging due to the sheer amount of data able to be read in. On my desktop PC, setting minimum gauge refresh to 0ms (ie never skip a gauge redraw, hence uses most CPU), can log 35 packets/second of all sensors. Setting minimum refresh to just 50ms gives the full 50 packets/second. I compared this to Nissan Datascan, which can only log 16 packets/second on the same PC (and thats without gauges shown at all) with the same sensors.
Changed options controls to dropdowns rather than textboxes (i didnt realise id disabled the use of the soft input panel on PPC, so you couldnt change settings). If you want to enter a value other than shown, edit the .ini file.
Fixed logging time output, both to add in the missing leading zeros (eg it would show 7:5:7 for 7:05:07), and also added in a interpolated millisecond value for PPC users (which doesnt have a millisecond capability in standard time object).
Minor changes to individual sensors to better display on gauges, and slight changes to change config (units shown next to sensor rather than down bottom as often the units would overlap gauge).
Added a hidden option for CarPC users with frontends (eg Centrafuse) to manually edit .ini file to set custom top/bottom/left/right co-ordinates for full-screen mode. Example: FullScreenBounds_L|T|R|B:10|20|1000|900. Setting all to 0 will use default method.

mookistar · Joined: 06 Feb 2007 Posts: 3

hmmm

it's definetly not working.

i have no way of eliminating my Serial-PDA cable, but i've tested my Consult cable on a laptiop and it works fine

on my PDA it still has trouble finding all the sensors everytime Sad

mook

NewKleer · Joined: 09 Oct 2004 Posts: 159 Location: Sydney

yeh since it works on your laptop, im guessing something weird with ur pda. check that version i sent and we'll try work out what ur pda doesnt like if possible (and might be able to work around that)

NewKleer · Joined: 09 Oct 2004 Posts: 159 Location: Sydney

ecutalk 1.3.3 beta - http://www.ecutalk.com/downloads/ECUTalk_v1.3.3_beta2.exe

has auto-reconnect when in gauges/logging mode (ie for carpc/pda users, u can just turn car off then back on later and it should resume itself).

also has 3 new sensors, distance, trip fuel usage, trip fuel economy.

as my car is out of action i cant test it myself - need people to test the new sensors and see if they seem accurate. You'll will need RPM, Injector and Speed to be at least logging (or shown on gauges) for these new sensors to work

edit: only issue found so far is distance resets after 6.6km. will be fixed in next beta

Chri · Joined: 28 Aug 2004 Posts: 68 Location: Austria, Europe

I just tried it a short run.

which sensors need to be activated for the trip/economy values ?
I`m having 100% cpu utilization von my Celeron 500mhz Laptop Sad

I don`t understand the Trip/ L/100km complete ?, it was showing me a value of 2,2-4?

Can you please add the 197 cc injector size, my euro GA16DE should have this value Rolling Eyes

there would also be a speed/tyre adaptation value necessary Question

mfg Chri

NewKleer · Joined: 09 Oct 2004 Posts: 159 Location: Sydney

NewKleer · Joined: 09 Oct 2004 Posts: 159 Location: Sydney

added 197cc in this one:
-----
http://www.ecutalk.com/downloads/ECUTalk_v1.3.3_beta3.exe

New features in beta3 below, along with a fix for distance sensor resetting after 6.6km.
#14 Add offset option timing so US users can get correct timing readings
#24 Derived sensors should select dependent sensors automatically
#26 Priority option for ECUTalk (eg so mp3 etc play fine)

Also minor change to delays in between commands, may help people who dont always get all sensors detected? Also minor change to consult reading for gauges, to reduce chances of corrupt data being accepted, eg you see all gauges flick to weird values for a second

Chri · Joined: 28 Aug 2004 Posts: 68 Location: Austria, Europe

Hy Newkeeler.

It seem that the software is now producing correct values on my car Cool

Great jop

mfg Chri

NewKleer · Joined: 09 Oct 2004 Posts: 159 Location: Sydney

good to hear Smile