Thread: ECUTalk v1.3 Released (Pocket PC/Laptop Consult Software for pre-OBDII Nissans)

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.

see point 9

what do u mean MPG wont work? you need injector, speed mph, and RPM selected for it to work. and naturally, your economy will be 0 unless car is moving

as for mixing metric/imperial, bad luck for the time being, maybe down the track ill add ability to select C/F seperate from M/KM

will it not just allow us to list the units we want in the ini file

RE: 1.3.2
Still resets pc when click to exit dials, but only if I click the area outside of the actual area the dials fill.

For screen bounds settings in .ini file are they in the format xpos,ypos,xsize,ysize in pixels
If so that doesn't seem to make any difference in the car

what langauge is ECUTalk written in?

Any chance you could donate the code to be ported to java? Would a donation be an incentive to do so?

Then we could make a plugin for JDash!

Since both are free currently, why not ECUTalk plugin for JDash. Would look great on the ECUTalk Homepage!

I would be willing to donate my Blazt.biz consult->usb cable to the appropriate resource to code the jDash java plugin. Or I might try to tackle it w/ Sama's help.

http://www.mp3car.com/vbulletin/show...81#post1011881

from the ecutalk website:

Running ECUTalk on a PC/Laptop requires the .NET Framework 1.1
It can be downloaded via Windows Update. Or to download it manually, get and install the:
.NET Framework 1.1
and then (optionally) get and install SP1:
.NET Framework 1.1 Service Pack 1

Hopefully that means C# as it is similar to java.

-ikon

Originally Posted by ShawJohn

will it not just allow us to list the units we want in the ini file

RE: 1.3.2
Still resets pc when click to exit dials, but only if I click the area outside of the actual area the dials fill.

For screen bounds settings in .ini file are they in the format xpos,ypos,xsize,ysize in pixels
If so that doesn't seem to make any difference in the car

the ini file only has a setting for imperial/metric.
try run it without centrafuse and see if clicking outside dials will crash
like i said in point 9, its left/top/right/bottom, not width and height. modify the example given: L|T|R|B:10|20|1000|900 - left and top are values closest to 0, right/bottom are closest to screen res (ie, 0 is top/left of screen)

its written in .net which means you may be able to get it working under mono in linux - id be interested helping in getting that working rather than doing a lot of work to get jdash working for nissans, as id rather spend the time i dont have adding plenty of things that arent currently in ecutalk (active tests, graphs, rom downloading, etc)

the code is c#, but the hard part isnt converting to java, its all the .net libraries etc that are used wont be compatible with java equivalents...so your only option really is mono.net or some other .net framework for linux.

performance meters would be nice too

0-30
0-60
0-100
30-70
60-0
1/4 mile
standing km etc...



Just a though whilst you mention future features.


What I meant about the sensor settings in the .ini was to be able to just change kph for mph in the display list and it just show that dial, instead of having a global metric/imperial switch.

The pc reseting thing happens even when run standalone BTW. might be something specific to my pc thought

So if I want the screen boundry setting typed in the ini to be used do I disbable the full screen option in the other tab?

I was under the impression that if you made the code available, others would be doing all the work to get it ported to java and into jDash. thoughts?

-ikon

oh yeah, if i was to make code available then someone else could - but i wont be for a few reasons, one of which is ive done some of this work for a project of mine at uni which means i cant make it open source

but it sounds like jdash already has the guts set up - if all you need to do is to get the communications work, plms host a few documents on the protocol which should be all you need: http://www.plmsdevelopments.com/consult_if.shtml