ECUTalk USB Consult Cable LCD Display ECUTalk Software
Skip Navigation Links
News
ECUTalk Consult Cables
ECUTalk Consult LCD Display
V2 Firmware Updates
V2 User Guide
Feature/Bug Tracker
V1 Display Info
V1 Firmware Revisions
ECUTalk Consult Software
Screenshots
Version History
Feature/Bug Tracker
Pocket PC Compatibility
Diesel Compatibility
Donate
Contact
 

ECUTalk Consult LCD Back in Stock! (2014-07-08 23:55)

The parts for the next batch of ECUTalk LCD Displays have unexpectedly arrived early, so the displays are back in stock and available to be ordered from the website.

To purchase, just visit the ECUTalk LCD Display page.

ECUTalk LCD Quick Reference Guide (2014-02-25 12:52)

Patrick Adams, one of the user's of the LCD display, has written a quick reference guide for navigating around the display. It is written for his diesel engine Elgrand, so some of the features/sensors will be different for other vehicles, but the core of the displays features and how to get to each of them is shown. You can view it here. Many thanks to Patrick for taking time to make this.

ECUTalk LCD v2.06 Firmware Update (2013-10-17 09:27)

There has been a firmware update for the ECUTalk LCD Display to add a fuel temp reading to the display for diesels only, in the otherwise blank area due to diesels not supporting fuel economy. Updating the firmware can be done for displays used in petrol vehicles, but it wont show any difference for them unless used in a diesel.

Visit the firmware update page to update.

New batch of ECUTalk Consult LCD displays (2012-05-08 20:44)

The changes for this batch are (see below for new display and size comparison with old):
  • Enclosure slimmer - reduction of depth, from 33mm to 26mm
  • The onboard alerts buzzer is louder now
  • MicroSD slot is easier to access (but still not used yet, reserved for future use
  • Change of USB socket to be the smaller A type (note - port is solely for connection to laptop, not for any USB devices)
To purchase one, go to the Consult LCD page on this website.

ECUTalk Consult LCD Slim ECUTalk Consult LCD Slim Comparion

ECUTalk USB Cable Resellers (2011-04-20 10:50)

For those purchasing ECUTalk USB Consult cables from UK/Europe or America, we have 2 distributors in these regions:

UK/Europe buyers, you may wish to buy from H-Dev - £69.37 shipped to UK (next day), £77.78 shipped to Europe (3-4 days).
American buyers, you may wish to buy from Nismotronic - $80USD shipped to USA, $90-95 estimated to Canada/Mexico.

They currently only sell the USB consult cables.

ECUTalk LCD v2.04 Firmware Update (2010-11-06 08:35)

A firmware update is available for the V2 LCD Displays. This firmware update has the following changes:

#92 - Speedo Correction: Allows speedo correction for people running a non-standard rolling diameter tyre/wheel combination. Accessible from Options -> Units -> Speedo%

#102 - Diesel ECU Support: The display now supports all tested diesels with ECU's - ZD30DDTi, TD42Ti, RD28ETi (and TD27Ti tested with ECUTalk software and should be supported, but no user yet has tried with ECUTalk LCD). If the Diesel doesn't have an ECU (e.g. TD42 non Ti version), it will not work.

#107 - Remove Unsupported Sensors: This change is with respect to earlier v2.04 beta firmwares for diesel support, which still showed petrol sensors that weren't supported.

ECUTalk v1.3.5 Final Software (2010-10-15 00:18)

An updated ECUTalk software has been released, download ECUTalk v1.3.5. This release is likely the final version supporting .NET 1.0/1.1. Changes are shown below:

Features/fixed bugs in v1.3.5 Final compared to v1.3.5 Beta7
#113 Make log files .csv rather than .txt
#114 Provide minimum log update functionality
#115 Attempt ED connection if EF fails
#119 Support unlisted serial port names via ini file
#120 Add dec points to Height sensor (inches)/MPG

Other features/bugs fixed in v1.3.5 compared to v1.3.4
#3 User definable warning levels for sensors
#99 TB45E engine does not have bank1 injectors, swap with bank2
#109 Add basic compatibility for diesels
#105 Add extra sequential index column to logging
#108 Russian language has trouble changing alert values
#110 Differentiate between petrol/diesel (as some sensors are shared)
#111 Update error codes (for both petrol and diesel)
#18 Display switch/solenoid etc sensors
#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)

ECUTalk v1.3.5 Beta7 Software (2010-08-02 15:38)

An updated ECUTalk software beta has been released, download ECUTalk v1.3.5 Beta 7. This release adds support for Active Suspension control unit (sensors and fault codes). The control unit is selectable via the Options -> Settings -> Control Unit option.

Normal_ECU is for normal ECU dianostics ECUTalk has had previously, ECU_ED is for the few newer vehicles (99 A32 Maxima) that do things slightly differently, and Active Suspension is if your car has active suspension control unit, e.g. Infinity Q45a.

Features/fixed bugs in v1.3.5 Beta7 compared to v1.3.5 Beta6
#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)

The images below show all possible sensors (not all may be applicable to your car), click to see example gauges.

ECUTalk Active Suspension Sensors 1 ECUTalk Active Suspension Sensors 2

ECUTalk v1.3.5 Beta6 Software (2010-07-15 23:16)

Edit: Beta4 had a bug in it, all the DBR registers would have read as 0. Beta5 didn't have readings for individual switches, get Beta6.

An updated ECUTalk software beta has been released, download ECUTalk v1.3.5 Beta 6. This release adds heaps of switch (on/off, open/closed, etc) sensors, and a couple of switch registers that have unknown usage at the moment. If you ever see a sensor with a question mark (e.g. DBR2C?) have a value that changes, let me know.

Features/fixed bugs in v1.3.5 Beta6 compared to v1.3.5 Beta3
#18 Display switch/solenoid etc sensors

There is a total of 8 switch sensors added common to petrol/diesel, 39 added which are specific to diesel engines, and another 39 added which are specific to petrol engines. Each specific engine will only have a small subset of these (around 10-20 is common), however.

ECUTalk v1.3.5 Beta3 Software (2010-05-16 21:57)

An updated to ECUTalk software has been released, download ECUTalk v1.3.5 Beta 3. This update adds proper compatibility for diesels (RD28, ZD30, TD27Ti, and maybe others). Please contact us if you have a diesel (with an ECU) that isnt listed above, whether the software works for you or not, as you may be able to help us add proper compatibility for any of the sensors specific to your car.

Features/fixed bugs in v1.3.5 Beta3 compared to v1.3.5 Beta2
#105 Add extra sequential index column to logging
#108 Russian language has trouble changing alert values
#110 Differentiate between petrol/diesel (as some sensors are shared)
#111 Update error codes (for both petrol and diesel)

Below is two screenshots, the first showing all possible diesel sensors (you will never get all of these on any given engine), and the second shows sample gauges (showing units etc) the more common of the new diesel sensors.

ECUTalk Diesel All Possible Sensors ECUTalk Main Diesel Specific Sensors

ECUTalk v1.3.5 Beta2 Software (2010-04-27 00:15)

An updated ECUTalk software beta has been released, download ECUTalk v1.3.5 Beta 2. This should add basic compatibility for diesels (RD28, ZD30, TD42Ti). Note however some sensors may appear (particularly injector/duty cycle/fuel used/economy) that arent actually those sensors but readings of other sensors.

Features/fixed bugs in v1.3.5 Beta2 compared to v1.3.5 Beta
#109 Add basic compatibility for diesels

The final v1.3.5 will most likely aim to differentiate between petrol/diesel sensors (i.e. #110). Also, the final v1.3.5 will probably be the last release for .NET Framework 1.1/.NET Compact Framework 1.0.

ECUTalk v1.3.5 Beta Software (2010-02-28 10:34)

An updated to ECUTalk software has been released, download ECUTalk v1.3.5 Beta. This adds alerts for RPM, Air Flow, Temperature, Speed, Injector Duty Cycle and Voltage. It should also fix compatibility with TB45E engines.

Features/fixed bugs in v1.3.5
#3 User definable warning levels for sensors
#99 TB45E engine does not have bank1 injectors, swap with bank2

The final v1.3.5 will most likely aim to add support for RD28 Diesel Patrol engines, and perhaps other diesels that are compatible. Also, the final v1.3.5 will probably be the last release for .NET Framework 1.1/.NET Compact Framework 1.0.

V2 Firmware & Userguide Update (2010-01-31 23:52)

A firmware update is available for the V2 LCD Displays. This firmware update has the following changes:

#74 - Save Trip Meter Statistics: There is now a 3rd trip meter screen, only distinguished from the existing one by it saying 'All' at start of second line rather than 'Trip'. That new screen is for all trip data since last clear, rather than only current trip (as the existing trip meter screen is).

#98 - Full TB45E Engine Support: This patrol engine reports 'RH'/'Secondary' Injector banks, and therefor trip meter readings etc didn't work as the primary injector bank is always 0 as it doesnt exist. So this is fixed by the display using the second bank readings if first is unavailable. Also added an option to injector options page to disable use of bank1 (this is really only useful for cars with 2 banks, where you dont really care about seeing both banks, and rather simpler view of just single bank reading).

#100 - Allow Adjustments on Main Screens: Now the adjustments set in the adjustments page are applied whilst on the main display/trip meter screens. Use at own risk, and please, dont use if you dont know what you're doing!!! If you dont know what these adjustments can do for your car, or have to ask someone (including me - I am not a tuner), then do NOT use them. As with any ECU alterations, you should monitor AFR with a wideband O2 sensor, and monitor knock levels to prevent detonation/pinging (and if you are using the adjustments, you would already know this).

#101 - Change Main Sensors: Water temp has moved to the start of the second line, and Ignition timing has moved to the end of the third line.

Head on over to the firmware page to download the latest firmware.

USB Consult Cables Back In Stock (2009-09-10 21:50)

USB Consult Cables are back in stock. See the consult cable page for more info.

Group buys of 5 or more consult cables are welcome, contact us for pricing/logistics.

ECUTalk USB Consult Cable

Firmware Update for V2 Displays (2009-09-06 23:30)

A firmware update is available for the V2 LCD Displays. This firmware update has the following changes:

#64 - Alerts: User definable alerts utilising the onboard buzzer on all V2 displays. Alerts are available for water temperature, injectory duty cycle, speed, air flow, RPM and voltage (voltage is the only one which alerts at or below the specified level, the others alert at or above the specified level). The alerts are only active on the main sensor/trip meter display screens. There are also options to set the pitch level, the buzzer length, and repeat interval. When an alert is triggered, the buzzer will sound and the sensor triggering the alert will flash on the sensor screen (for 10 seconds). The buzzer will continue to sound after each buzzer interval set in the settings.

#86 - Bug displaying ATDC timing: Fixed a bug where if the timing is occuring after TDC it will show it as degrees A, rather than showing a negative degrees B value.

#88 - Timing retard added to peak values: The lowest (most retarded) timing value will be shown on the max values screen along with existing most advanced timing.

#96 - Temporary Fuel/Ignition Adjustments: Temporary adjustments can now be made to fuel percent and ignition timing from the adjust screen. These adjustments are only active whilst on the adjust screen. These utilise the consult 'active tests' to alter the fuelling and/or ignition timing, and are in no way saved into the ECU or alter the ECU fuel/ignition maps in any way (as they are read-only).

CAREFUL: YOU CAN DAMAGE YOUR ENGINE IF YOU DO NOT KNOW WHAT YOU ARE DOING WITH THESE. USE AT YOUR OWN RISK.

If you dont know what these adjustments can do for your car, or have to ask someone (including me - I am not a tuner), then do NOT use them. As with any ECU alterations, you should monitor AFR with a wideband O2 sensor, and monitor knock levels to prevent detonation/pinging (and if you are using the adjustments, you would already know this).

Head on over to the firmware page to download the latest firmware.

LCD Displays Back In Stock (2009-08-19 21:12)

The ECUTalk Consult LCD Displays are back in stock. If you wish to purchase one, head on over to the LCD page and click one of the Buy links (depending on your LCD colour preference and location).

Note that the displays no longer come with the glossy polcarbonate enclosure, but come with a matte black enclosure (like what the original ones used to), which dont scratch easily (but is still polycarbonate so still has high temperature resistance).

ECUTalk v1.3.4 Software (2009-06-20 15:57)

An updated to ECUTalk software has been released, download ECUTalk v1.3.4. This allows you to edit the ini file and use another ECU ID if you have one of the few cars that doesnt use the default id EF. E.g. some cars it is ED instead of EF. Also fixed a bug which didnt allow ports COM10-COM19 to be used.

Features/fixed bugs in v1.3.4
#90 Allow user to edit ECU ID for initialisation
#93 COM10 and above dont work in ECUTalk

Next Batch of V2 LCDs in Stock! (2009-04-06 20:57)

There is stock again of the V2 displays! See the V2 LCD page for more information and to place an order. Also there is an extremely unrehearsed demonstration of it here: 19MB divx avi.

ECUTalk Consult LCD V2 Display

LCD V2.01 Firmware Update (2008-09-22 15:41)

The first update to the V2 display firmware is available on the firmware page.

This update fixes a few minor issues (#75, #77, #82, #85) along with adding these features:
  1. #83 - MicroSD card info/speed test page added to options
  2. #79 - Added Ignition Timing offset option for US users as some cars timing reads 35 more than it should
  3. #76 - Added "Ref Time" option to LCD options, controls the time (in ms) between each LCD line update. Higher value may be useful for blue screen users due to its slower response time
Users who had their displays sent out before September 3, 2008, who wish to log to MicroSD card (in the future when firmware that supports logging is released), will require a modification (adding a resistor) to the display to lower the voltage going to the MicroSD card slot. Users who had their displays sent after September 3, 2008, will already have this modification done.

Note: Existing data on a MicroSD card will be lost if used in the display - the card is written to in a lower level format than a PC will be able to read. Retrieving logs off the card in future will be done via USB, you wont remove the card from the slot, so just buy one for use in the display.

Consult LCD V2 Available & Compatibility (2008-08-26 11:51)

Everyone who has previously expressed interested in the display has been contacted with payment details and have had sufficient time to make payment - so now the remaining displays (currently around 30) are available for purchase. I've also noticed that I havent put up a compatibility list/guide anywhere, so here's the brief checklist for if the display will work in your car:
  1. Your car is a Nissan that is still running the stock ecu. Piggybacks/remaps are generally fine, but aftermarket ECUs wont work (PowerFC, Motec, etc).
  2. Your car was a model produced somewhere between 1989-2001 (but not all models in that range support consult)
  3. You can locate the consult port near the incabin fuse box.
  4. Most likely your car DOESNT have the OBD2 port (16 pin trapezoid). Some cars, esp US/Euro, lost consult when they gained OBD2 after 1996. On the other hand, most AUS/JAP cars didnt rush in OBD2.
Off the top of my head, all these cars should support consult: S13 (not CA18 engines), S14, S15, N14/B13/GTiR, N15/B14, Z32, R32(9/89+), R33, R34, C34, A32 (not A31), NX/NXR (SR20), U12/U13/U14/U15 (SR/KA), W10/W11, Q45, G20, K11, P10, some P11.

Note that if the display doesn't work with your car, you can send it back if its in original condition for a refund (minus postage).

If you would like to purchase a display, send an email, and a few more details and payment info will be sent. Price is $220 + postage ($7 in Australia, $15 outside), add $5 for blue screen.

Consult LCD V2 Finished (2008-08-12 16:02)

The ECUTalk Consult LCD V2 Displays are finally finished. There is a first batch of around 90 (100 minus ones 'consumed' by the different enclosure manufacturers and other testing) which are pretty much all reserved for people on the interest list for getting a display. These people will be contacted over the next few days to organise payment and shipping.

Once this first batch are sold, a second batch (of probably 100) may be started if sufficient demand.

Pictures of Blue Screen Prototype (2008-07-31 12:26)

Here are some pictures of a blue screen version, showing the sensor display screen (previous green screen shows the trip meter display). The first is better quality but blueness is washed out a bit. Second shows the blueness a bit better (but worse quality, taken at night without flash). They both have the black buttons which will be on final displays

blue v2 prototype
blue v2 prototype

Enclosure Update (2008-07-09 10:08)

Just received a prototype enclosure from the place that will be making enclosures for the first batch of V2 displays. Will probably have them ready around the start of August.

Here's a picture of it. Looks better in person but you get the idea. Dimensions are 144mm wide, 48mm high, 33mm deep (buttons protrude 3mm). So it will fit inside a DIN slot. Will try add a shot of the blue screen later on.

plastic v2 prototype

Final Firmware for V1 LCD Displays (2008-05-26 22:17)

The last firmware version (v1.0) for V1 lcd displays is available. It adds a basic trip meter screen to the display, accessible by pressing the left/right buttons whilst on the main data display. It pretty much has the same content as the prototype picture for the V2 display is showing.

This firmware update is available at no charge. The main chip in the display must be reprogrammed. Simply post your display to me, along with a paid self-addressed return satchel (eg 500g express/standard satchel). Make sure its reasonably packaged. Contact us for address details.

V1 firmware version is displayed on the device info screen. Information on V1 firmware versions, and for those interested in how firmware updates will work for the V2 displays, I've updated the Firmware page.

V1 displays will be able to be traded in for a $100 discount off the cost of a V2 display.

ECUTalk v1.3.3 Final (2008-05-12 00:33)

Edit: Whoops! The first upload of the file was broken - this has been fixed as of 2008-05-12 17:10 GMT+10.

The final beta build of ECUTalk v1.3.3 has been completed. Still need to update the ECUTalk Software page, but in the meantime you can download it from the above link. Currently we're unable to test it on any car so as usual lettuce know if there is any problems. Planning for probably one more release, v1.3.4, before the move is made to .NET Compact Framework 2.0.

Features/fixed bugs in v1.3.3 final (from 1.3.3 beta4):
#42 Removed console output for few users who have a console setup on their PPC
#55 Trip meter sensors shouldn't keep 'counting' while car is turned off
#58 Prevent 'clicking' show gauges button with keyboard when gauges already shown
#69 PPC users can now utilise the 'working area' option and the LTRB option (ini setting)
#70 Changed default 100ms max refresh to 40ms (equivalent of 25fps)

Features/fixed bugs in beta4 and previous (from 1.3.2):
#10 Put font size/scaling for gauges in options
#31 When value exceeds gauge maximum, the actual value should be on digital readout
#32 When you read fault codes without having connected to ecu, ecutalk exits
#33 Gauge colour preview doesnt update till you restart ECUTalk
#35 Save long term trip sensor statistics
#36 Clear trip statistics from sensors
#37 Option dropdown lists are editable on laptop/PC (shouldn't be)
#38 check for port open when reconnecting when gauges showing
#39 Put option in for data flush wait time
#41 If using L|T|R|B settings in the ini file, the gauges arent displayed properly if L is far from 0.
#1 Automatically attempt reconnection to ECU after connection lost
#5 Other Trip Meter Sensors (Fuel Used, Trip Fuel Economy, Trip Distance)
#14 Add offset option timing so US users can get correct timing readings
#22 imperial (etc) option in the options is cutoff with japanese font
#24 Derived sensors should select dependent sensors automatically
#25 Options might not be saved if you dont select another tab before closing
#26 Priority option for ECUTalk (eg so mp3 etc play fine)

Consult LCD V2 Progress (2008-04-28 09:35)

Manufactured and assembled PCBs have been received, now we are primarily waiting on the production of the enclosure before the final displays are ready for sale.

The status of each of the new features for the display has been updated on the consult lcd display page. Additionally, ordering and draft pricing details have been added to that page. Basically contact us and you'll be added to a interest list and be contacted when displays are available.

Consult LCD V2 Progress (2008-01-13 12:14)

Over the holidays a prototype was constructed which has been used for feature development. The trip meter screen has just been completed, which is accessed by pressing the right/cursor button whilst on the main display. Depending on whether you've chosen KM or Miles in the options, you'll get one of the two screens below.

From left to right, top to bottom, you have: current speed, instant fuel economy, trip average speed, overall trip fuel economy, trip fuel used, average fuel used per hour, distance travelled, and time elapsed.

kph v2 prototype
mph v2 prototype

Consult LCD Version 2 Update (2007-12-01 19:37)

We're a couple weeks away from finishing a prototype design (minus enclosure) for the next LCD display. We're aiming to get the prototypes done before Christmas so work can be on the firmware/features etc over the Christmas break.

If all goes well, enclosures etc will be designed and perhaps some local users will get a beta version to help out with final testing.


Consult LCD Version 2 Update (2007-10-01 20:26)

The next version of the consult lcd display is still being worked upon, though progress is a bit slow, and a few key components needed for the display are still unavailable.

We've decided upon and ordered a batch of lcd modules that will be used in v2. They are the 20x4 low profile modules from Crystalfontz. One is positive (sunlight assists viewing) yellow/green module. The other is a negative (direct sunlight makes it harder to read) white on blue module.

yellow/green lcd
white/blue lcd

In other news, Beta 4 of ECUTalk v1.3.3 seems to be working well for most users, with only one confirmed bug found.


ECUTalk v1.3.3 Beta 4 (2007-08-21 23:10)

The 4th and most likely final beta build of ECUTalk v1.3.3, beta4 has been completed and put on the website. We're fairly sure all the functionality introduced in these betas now works as intended, though we haven't had much if any feedback from Imperial sensor (Mi/Gal/MPG etc) users. If there are no problems with this build, it will become final v1.3.3.

New features/fixed bugs in beta4 below:
#10 Put font size/scaling for gauges in options
#31 When value exceeds gauge maximum, the actual value should be on digital readout
#32 When you read fault codes without having connected to ecu, ecutalk exits
#33 Gauge colour preview doesnt update till you restart ECUTalk
#35 Save long term trip sensor statistics
#36 Clear trip statistics from sensors
#37 Option dropdown lists are editable on laptop/PC (shouldn't be)
#38 check for port open when reconnecting when gauges showing
#39 Put option in for data flush wait time
#41 If using L|T|R|B settings in the ini file, the gauges arent displayed properly if L is far from 0.

Additional notes:
1) For Flush Wait option, 100ms is default, lower values will give quicker startup times, but higher values might help with some connection problems, eg sensors not showing up, ECU part number not being read, gauges not moving when showing gauges, etc. Eg I can use 20ms on my desktop and 50ms on my 568 Jornada.
2) For Font Base Size and Increment, this allows you to specify a font size, and then the amount of pixels which the font size will be incremeneted depending on gauge size. Eg 6pt + 50px increment on a 200px wide gauge = 10pt font.
3) Also a minor fix to heading names in logs so distance/fuel used have units (KM/Mi,L/Gal)

Features/fixed bugs in beta3 and previous:
#1 Automatically attempt reconnection to ECU after connection lost
#5 Other Trip Meter Sensors (Fuel Used, Trip Fuel Economy, Trip Distance)
#14 Add offset option timing so US users can get correct timing readings
#22 imperial (etc) option in the options is cutoff with japanese font
#24 Derived sensors should select dependent sensors automatically
#25 Options might not be saved if you dont select another tab before closing
#26 Priority option for ECUTalk (eg so mp3 etc play fine)

If you find any problems with any features in this beta, if you could send me an email, or sign up to the bug tracker and add a note to the ticket.

Future version v1.4 of ECUTalk is likely the time when the software will move over to the .NET Framework 2.0. Therefore, depending on whether any minor releases are done after v1.3.3 before v1.4, this may be the last version of ECUTalk that will work on Pocket PC 2000 and 2002 devices, depending on how hard it is to maintain a .NET 1.0/1.1 version alongside a .NET 2.0 version.

Anyone buying a PDA for the purposes of using ECUTalk should try and get one with Windows Mobile 2003 (and up), which supports .NET 2.0. iPAQ's tend to be the best to use, particularly due to the standard connector and being popular.


Feature/Bug Tracker (2007-07-20 22:12)

We've put together a (largely uncustomised) feature/bug tracker which can be found here. This will take over from the previous featurerequests list, and will be used eventually for both the ECUTalk Software and the ECUTalk Consult LCD Display. If you have previously contacted us about a bug or potential feature that is not shown as an issue in this bug tracker, either email us again about it, or register for an account (which allows you to submit issues) and create a new issue for it.


Update (2007-05-23 23:51)

Next ECUTalk LCD Display will probably have design started be towards the end of the year, possibly being redesigned into a squarer shape (20x4 instead of 40x2 LCD). We're hoping to get a fair few fundamental changes made, potentially setting it up to enable firmware upgrades to be downloaded off the website and upgraded with a laptop - but this will be difficult to accomplish, but we'll see how it goes. Of course current displays are still "upgradable", just requires the main chip being replaced (and not able to be performed by users due to custom hardware needed to write to the chip).

ECUTalk v1.3.3 will probably be out towards end of July, and will have a fair few improvements, especially for Pocket PC users. This may be the last release for .NET 1.0/1.1 before the move to .NET 2.0 - this means that Pocket PC 2000 and Pocket PC 2002 users will not be able to use any versions made for .NET 2.0 (only Windows Mobile 2003+), because they do not support the newer .NET 2.0.


ECUTalk v1.3.2 (2007-02-10 13:44)

We've released a (rather major) minor update to ECUTalk, v1.3.2. It's primary purpose was to fix the issues with not dropping packets if CPU can't keep up, but we ended up doing a significant overhaul of the consult reading, gauge performance, and logging aspects. The end result is much more data is able to be processed, especially the capability for amount of data packets that can be logged per second.

Changelog:
  1. Fixed issue in v1.3 and v1.3.1 which meant data packets weren't being dropped when CPU couldn't keep up
  2. Increased performance of gauge drawing by ~250% (on our PPC benchmark, time to draw a gauge went from ~30ms down to around ~12ms).
  3. Changed code to always draw gauges (even if data hasnt changed) in order to result in consistent amount of packets being logged per second.
  4. 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 a 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).
  5. 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.
  6. 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.
  7. 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).
  8. 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).
  9. 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.
ECUTalk v1.3.2 can be downloaded from this page.


ECUTalk v1.3.1 (2007-02-05 10:24)

Edit: Use v1.3.2. This version has a bug which means the gauges dont drop packets when falling behind. If you have a slow laptop or most Pocket PCs, then the data will lag.
We've released a minor update to ECUTalk, v1.3.1, which has a Economy MPG sensor added for those stuck in the dark ages in the US and affiliated imperialists. There is also now an option under "options->other" to choose imperial sensors (miles, F, MPG, etc) or not (not checking the option means the normal metric ones).

Changelog:
  1. Added option to choose imperial/metric sensors under options->other. A restart is required for setting to change effect (setting is saved once you choose a different tab other than "options" from memory).
  2. Added Economy MPG sensor for the imperialists
  3. Re-added EGT sensor, as there is now more room on sensor setup screen for it after removal of both imperial/metric sensors being shown
  4. Changed max timing shown on gauge from 40 to 50
ECUTalk v1.3.1 can be downloaded from this page.


ECUTalk v1.3 (2007-02-04 01:34)

Edit: Use v1.3.2. This version has a bug which means the gauges dont drop packets when falling behind. If you have a slow laptop or most Pocket PCs, then the data will lag.
v1.3 of ECUTalk has been completed, which has seen Feature Requests numbers 8-12 implemented, as well as a fair few other fixes. Fair amount of work has gone into it (taken over a month which is a bit more than usual).

Changelog:
  1. Added ability to log sensors without showing them on gauges (when logging is enabled, checkboxes have a greyed out checkstate, indicated logging only)
  2. 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)
  3. Colour setup for gauges added. Hard bit for you is coming up with a colour theme that looks ok!
  4. Added Instant Fuel Economy Sensor - requires RPM, Injector and Speed kph selected to work
  5. Changed DutyCycle/RH Sensors to calculate values from RPM and Injector/RH sensors (therefore requires them to be logged at least to work)
  6. Fixed Timestamps when milliseconds are less than 100 (3 digits). Previously they would not have leading zeroes
  7. 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).
  8. 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.
  9. 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.
  10. Removed EGT sensor (it's useless, only ever reads 4.98v)
ECUTalk v1.3 can be downloaded from this page.

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.

ECUTalk SensorsColour Setup


LCD Display compatibility with 300ZX/Q45 fixed (2007-01-16 23:09)

Over the last week we've corrected an issue causing the main display not to work with 300ZX/Q45 users (and any other cars with V6/V8 engines with 1 AFM). This is fixed in v0.9 of firmware and beyond. The 2 users with 300ZX/Q45 cars as their primary car have been contacted for an update - everyone else can probably be updated whenever we get the trip meter functionality finalised. Thanks to Karl and Chan for helping to resolve this issue.


ECUTalk LCD Displays Delayed (2007-01-07 15:56)

Due to other commitments in the coming 6 months, we've decided to delay the redesign of next lot of Consult LCD Displays until after mid-year. Only one remains from the first batch, so we're pleased they've done so well. We'll be working on updates to ECUTalk Consult software from time to time until then. With any luck we may have time to add trip meter functionality for current users, but can't really guarantee anything at the moment.


Update + Injector Duty Cycle Issue (2006-12-11 22:40)

Current plans are for availability of ECUTalk Consult LCD Displays in January or February. The first batch (mainly limited to Australian users to help with testing) is almost complete, with 3 displays left. If you would like one of these remaining displays, send me an email (may not last long - overseas buyers are OK).

I've discovered an issue with calculation of Injector Duty Cycle in ECUTalk v1.2 and the ECUTalk LCD Display (v0.7).

The calculation was based on the assumption that the injector opening time was per engine revolution, but it is per power stroke of a cylinder (which in a 4 stroke engine, is every 2 revolutions). This will be fixed in the next release of ECUTalk software (v1.3) and ECUTalk Display (v0.8).


ECUTalk v1.2 (2006-10-17 03:14)

I've completed v1.2 of ECUTalk, which has seen a few functional improvements as well as a significant change architecturally. From v1.2 and onwards, there will be no seperate Standard/Pocket PC versions - the same version can be run on both.

ECUTalk v1.2 is based upon the Pocket PC version, with changes to allow the gauges to be displayed full screen on whatever size screen you have (previous PPC versions would only show the 320x240 screen size when viewing gauges).

It is also a single standalong .exe file, so run it from wherever you want (of course you still need the .NET Framework or .NET Compact Framework). I've updated the page for this release. The previous Standard and Pocket PC sections are now obsolete.

ECUTalk v1.2 can be downloaded from this page.


Video Demonstration Consult LCD (2006-09-05 00:40)

The Consult LCD is getting close to completion, so we've uploaded a video demonstration of the Consult LCD Display. We've also written up a commentary of the use of the device.

We've also updated the Consult LCD Display with a couple of pictures of possible mounting positions. The device is slim enough to make a steering column mount perfect.

Prototype Display


[Updated] Information on LCD Display (2006-05-10 12:01)

Update (2006-08-11 12:01:51): The display should be finalised within the month. The following features are under development or already finished:
  1. Sensor Display
  2. Read Error Codes
  3. Clear Error Codes
  4. Peak Values
  5. Configuration options: kmh/mph, tps volts/%, deg C/F
  6. Time Trials
See here for more info: Consult LCD Display


ECUTalk Pocket PC Compatibility (2006-03-12 23:11)

We're compiling a list of setup's users have got the PPC version of ECUTalk working on. It should support any Pocket PC that can host the .NET Compact Framework and has support for a Serial COM port, but these are confirmed cases of it working (and the hardware used).

See the Pocket PC Compatibility list.