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