openecu.org

the product 'TARI DL1' is available off my website - www.tari.co.za

it is free and will be free forever! check out the website and view the screen-shots, download the app, try it...

calvin.

Sweet. I'm definitely going to have to check this out.

Would I be able to use my AccessPORT cable to connect the OBDII port to my laptop's serial port? Or will I need a different cable?

hi,

i dont have access to an AccessPORT so i can't confirm that just the cable will work, it should though. just be careful because the accessport may have the neccessary shielding built into the unit and not the cable. let me know how your tests go.

calvin.

Ok, after a few very quick tests, I can confirm that my AccessPORT cable (OBDII thingy to serial) does work.

Now it's time to go and capture some logs!

whoa...slow down there skippy...

the dl1 application currently does not allow for recording of your own log files. you can view the realtime data and you can view saved log files - from another application.

the next release (available soon) will have the ability to record your own log files. its not in the app yet because i havent coded in the switches addresses.

calvin.

Hehehehe....that probably explains why I couldn't get the app to save any log files today.

My initial testing involved me plugging in the computer to the car, and verifying that the software was recognizing the ecu's output.

Either way, it's cool.

-- Tom

tom,

did some of the switches last night so it shouldnt be too much longer. quite alot of stuff to add into the next release though...

please send me the ecuassist file it creates, along with a pic of your ecu cover. its the only way i can build a database of the different ecu's and their supported parameters, etc. also i'm sure you would like it to be able to recognise your ecu type?

calvin.

I'll get you that file and pic hopefully by this weekend for you.

- tom

calvinc wrote: its the only way i can build a database of the different ecu's and their supported parameters, etc.
calvin.

look here :
http://forums.openecu.org/viewtopic.php?p=182#182

it's not difficult to know how parameter are supported (or not supported) when ecu reply to 80 10 f0 01 bf 40

maybe you what build only an db to know what type of ecu are connected, but if i am in my car, i knok what car is it so this is a useful feature

sorry for bad english, if i can help in your soft i have some free time

thanks for the comments nemis,

dl1 already parses byte 9 .. x for the supported parameter types. those are the most 'generic' and there are alot of missing bit definitions. there are also others that are not listed and seem to change between ecu variants - advance multiplier, engine load, etc.

maybe you what build only an db to know what type of ecu are connected, but if i am in my car, i knok what car is it

this software is built for all levels of the 'enthusiast'. not everybody knows what ecu type they have. its as basic and simple as you want it to be and yet it can offer ecu information only the well informed will understand.

calvin.

The software looks great. Cannot wait to use it.

I look forward to a GUI like Delta Dash and AP Street Tuner

Hi Calvin,

I have visited your website, and I'm keen to start using your software.

Congratulations, you already have a great product, and with exellent potential.

I am in Australia with a 2001 Subaru Forester GT - can you advise what brand of connector I will need to interface to my laptop??

Many thanks,
Andrew

If you have a serial, you can use the openport generic one.

If you are turbo, the WRX version may work.

Just install the USB-Serial drivers and you will be good.

Hi calvin,

The software is now working good with the rpm. I have to replace the pci.exe file since the program was extracting it to c:\winnt\system32 when my XP uses c:\windows\system32

My ecu still needs to be supported by the software, but now the rpm is looking good.

ok, i made a post on nasioc about that yesterday so hopefully more with the problem can correct it. it was a stupid descision by me to put it in the System32 folder, it should have gone into the application folder.

version 2 will be a single executable so problem solved there.

calvin.