PROD - OBD application for Win32 and WinCE (OttoNavi)

Been working on a WinCE OBD reader for my OttoNavi unit...

Developing under Lazarus which allows for win32 and winCE builds... Lazarus is a rather nice FREE visual pascal program platform... it's a free, open source, version of Delphi.

Have a working Win32 application (both GUI and OBD interface)
Have a almost working WinCE application (Gui is running, OBD interface need debugging)

Both applications use a "FTDI FT232RL OBDII USB Interface" from eBay. Less than $30. Prolific will work on Win32 but does not have drivers for WinCE. The FTDI does support WinCE and was rather easy and straight forward to install on my OttoNavi. Putty for CE (terminal program) is working communicating through Com6...

Thank you to vincent1449p for allowing me to import his Standard and Custom PID files. These allow for super easy decoding of the HEX data from the PIDs.... I have the application able to decode the HEX and use standard mathmatical equations from within the CSV file... IE ICE RPM PID 01c0 is ((A*256)+B)/4

Here is what the first pass looks like on my OttoNavi...

Not going to promise quick programming... This is a labor of love, and free time... Program as often as I can from my couch in the evening...

Still working through the com decoding on the WinCe version... The ports connect but I think the trouble may be missing something simple like a missing or extra ctrl character that is messing with my packet logic... I have just hacked together a test program... I will be testing the com with it shortly... I hope to have the WinCE version not only looking good, but running the numbers as well reall soon...

-steve

 

Ok.. Now that the cat is out of the bag..

What information would on your ideal data screen and what would it look like?

 

Tested the winCE com port logic this am. Yep. Missing a Ctrl character that my simulator didn't have. Gonna correct that tonight.

 

Woooo Hoooo.
Enabled OBD headers and Linefeeds. The Application is now reading data.
Now to fix some formatting errors and speed up requests.

 

WinCE version is running... Win32 version is running... Going though PID list and checking received values with actual reading and comparing with other OBD applications.

Data requests have been increased but threading out the readport. This also greatly improved the reliabilty of reading the multiline return strings.

Stay tuned for more...

 

WinCE version working good on my OttoNavi..... Currently looking into Math Expression Parsing issues..... Win32 reports the correct values... WinCE is giving me slightly different results....

 

Math Parsing issues was not an issue with the Calculating routine, but a bug in the FormatFloat function in the Lazarus compiler that I chose to use. Hmmppp. I guess that's what you can expect for a free pascal compiler

Win32 and WinCE now calculating correctly... Working on information displays.

Anyone have any favorite group of PID information that could be used as a display? Open to suggestions. Thanks.

 

Ahhhh, sweet success....
I believe I have the floating point and Lazarus issues corrected. Updated my Lazarus version to the most current, changed my Calculating object to a basic math one, and changed my double/floaing point variable to Currency as described in many WinCE Lazarus application forums.
I will be posting some pictures in the near future...

 

Thought I'd post a few pictures of my Prod application running on my OttoNavi.

Main OttoNavi menu.


Start and connection screen.


PID list, values, and equations.


RPMs.


Temperatures.


Gauges. For RPM and MPH.


MG1 and MG2 statuses.

 

I will check to see if the genIII has those PIDs available, if so ill see if I can add the calculations.

I also have the application compiled under win32. Lazarus is great in that sense, but still has a few bugs in the CE compiler that I have had to work around.

 

Thanks to GasperG I have started a new feature. Adding in the ability to include custom equations. I have a basic equation feature coded and working. Basic, meaning as long as all of the PID parameters in the equation come from the same ECU the calculation is good. Working on making it ECU independant, so I can have mixed ECU equation paramters. Should have the multiple ECU code finished by tomorrow.

 

Mixed ECU equations are now working. Basic Testing completed on my ICE OBD simulator. Some of the more involved equations that I have use Toyota Custom PIDs which I will need to test in the WinCE in my Prius.

GasperG - waiting to see how your equations work out on the actual ECUs. Thanks again.

 

Been looking into the kW for the ICE.... can't seem to find an active one for the ICE on my 2010 Prius Gen III...
MG1 and MG2 kW was straighforward... thou torque was in ft/lbs that was easy to convert....

Anyone have another way to calcualate ICE kW on a 2010 Gen III?

 

I found my issue with the PID 2137 not returning a value in my code. It actually was sending a response. The issue was that the first data byte was a 7F which I misinterpreted as a failure packet (03 7F). I now check for more of the failure packet including the size byte.

I will be testing more tonight. When I get this ironed out I will be posting the executable for others to enjoy and help me test.

 

Ok. Here y'all go.... V0.99 beta versions Win32 WinCE and the data files....
WinCe is optomized for the OttoNavi.
Win32 and WinCE GUI are currently created with the GenIII Prius in mind... I'll work later in a configurable GUI...
But hey... I made it for MY car ... and sharing it with you all...

You will need to save the data files a CSV in the same directory as the EXE for them to load.

I had to comiple with Debug turn off so PriusChat would allow me to upload... The file was too large with it...

I use TrackBars for ProgressBars because in the Lazarus compiler the WinCE ARM compiled code did not graph correctly..

 

Oh... Use the Debug mode sparingly.... It is quite a CPU hog....

You can right click on the Received Data List, PID Status List, and Debug List to Export them for examination..