ECUTalk v1.3 Released (Pocket PC/Laptop Consult Software for pre-OBDII Nissans)
(makes sense to create a new thread rather than using the other one meant for something else).
ECUTalk v1.3 Released - http://www.ecutalk.com
ECUTalk was originally made so that people would have an alternative to the only available Pocket PC software for Consult, which cost $600. It's free, although donations often result in it actually being updated
It was also made with widescreens in mind (eg CarPCs) with its ability to arrange/size gauges to maximise screen area used.
- 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. Couple of older screenshots of fault codes/gauges also.
Nice one fella, been waiting for the next edition for ages
You should start a new thread about this with a more apt tittle
PS. there are definate improvements with 1.3 with regards to the ability to change the gauge colours and especially the fuel economy thingy, but the screen fill size is still playing up
I wish I was able to post you a screenie but right at the moment, mid moving house, I haven't got the hardware available to do it.
It definately behaves differently when standalone (in which case it tried to fit all the dials in the PPC sized window, but when embedded in CF it still tries to display dials beyond the available app space. Could you add a user option to set the window size manually? And make sure dials fill all the available space.
And how about sussing out some calcs to also get mpg worked out for us who still believe in Engilsh units
My brain doesn't work in km/h and litres... I need UK gallons and good old miles per hour
Another function which has suddenly struck me as essential is way to decide the order of the dials because for them to be useable when driving you need to be able to look straight at the dial you're interested in rather than having to stare at the LCD looking for what you want to see.
I appreciate your efforts, and would love to help you but my programming skills are lacking to say the least Keep up the good work Mr.
EDIT: Hang on a minute, first time I downloaded the PPC version And I may be confusing some of the problems that the PPC one produced when run on a PC, and the car is in the garage now, 150ft away and its -2C outside So we will have to wait till tomorrow to be sure
I'm now wondering how hard it would be to have this app as a CF Plugin
Things like this, and skinning are taken care of then
i already tried making a cf plugin, but it simply would not show up in cf no matter what i did.
it looks that most likely we'll just have to set x/y/width/height manually
ive added MPG in next minor revision (as well as an option for metric vs imperial sensors in options, so that u dont have two versions of each sensor). see here
there is only the one version now - one that works on both ppc and normal pc/laptop - are you talking about the older v1.0 non-ppc version?
how are u closing the program? just with the X? works for me without leaving it open in background. or was that after a resume from hibernate? if u can work out when it does hang around, and when it doesnt, i might be able to fix it
cant really know what u mean with screen issues without screenshots.
ill have to have a think about how to do the connecting stuff (i assume u mean u just want to hibernate when gauges were on, and then on resume, it would drop out of gauges if no connection, then do the normal reconnect, as if u just started it?)
for the checkboxes, u only have to set them up once, so i wont be changing them just for carpc's (u know u can click the text of the checkbox right? not just the checkbox itself)
yeh if you could do that (email me, contact link on site) ill check it out when i get the chance...probably would mean screenshots arent as important (assuming i can get it working)
here are some screenies
In car at the moment. keyboard is a real PITA
Will post up coments on each pic later
For now you can see how it behaves
CF must do some really unco stuff to the window area to make it look like that. is that using the "working area" option? ecutalk isnt made to account for changes to the window size whilst in full screen mode either