I've converted my Pocket PC logger to run on the PC using the Tactrix cable using the FTDI drivers at the standard 15625 baud rate.

The logging items are hard coded and include JDM only MAT (inlet manifold air temp), MAP (in kPa), and all temp units are in celcius.

It logs to the same directory that the .exe is in.

It doesn't have good error checking and will easily crash, but I'd appreciate a few people testing it to see if it logs to the screen and file, and if the knock graphing works (plots a pixel for RPM vs knock sum - red if full throttle, blue if above 90 or 95% I can't remember, green if lift off) - may be difficult to see!! The scrolling graph doesn't scroll yet though.

The screens for map switching and live mapping of RAM fuel and timing work on a suitably modded ROM - since I've not posted these yet they can't be tested.

The aim is to have a completely open code base that we can modify to get live tuning going. It is not designed to compete with or replace existing loggers.

I have used FTDI based code for connecting to the ECU. I took a hint from Mitsubishilogger for latency timing to speed up the logging. Otherwise everything else is based on the previously released Pktlog.net I posted on here.

Using this app, I can read the fuel map in 2 seconds and the timing map in just under 3. Writing will take a bit longer.

I stress that the realtime stuff doesn't work yet!

Comments please.

Any volunteers to get the scrolling graphing working? It is the bitmap copy that doesn't work whereas it does with the same code on the Pocket PC.

Any volunteers to add xml features to take away the hard coding I've done for the realtime map sizes, axes, locations?

I will post the exe and the Visual Basic Express 2005 (free!) code in a following post if I can get it below the 100kb zip limit...

 

Here is the exe for datalogging. Note if you don't have MAT and MAP it will read funny, and the temps are degrees C, but with proper calibration curves.

 

I'm glad you decided to do this.. I'd like to see open source loggers and live tuning get more widely accepted. Its just too difficult to make mitsulogger as it sits an open source project.

FWIW Using FTDI calls has been a much better option than using serial comms, I've never been able to get really good performance using the com port emulation as compared to using the driver directly.

 

Thanks Jack, I've kept it really simple and small, trying to get the skeleton going to get a nice realtime mapping app that is really easy for end users to modify. I'm not scared by the FTDI stuff now, but was to start with. The example FTDI app is really good to show how to ID the chip etc, I see you used it as a model in Mitsubishilogger, so I took your lead.

I can't get the zip size down, but I can with a rar inside a zip!! I have archived the obj folder seperately, not sure if it is needed, but it goes in the tree at the same level as bin if you want it.

 

Obj file if you want to play with the source, not sure if needed though.

 

Yeh, definitely was easier than reinventing the wheel, I spent a few days before coding everything unsuccessfully, finally gave up and used the sample app as a model.

 

I'll certainly try to test it, thanks for the work on this and making it VB express compatible, I'm sure that will encourage more people to take a look.

MB

 

John - thanks for the great news on this. I tested on laptop - works fine. On monday I should get my usb host cable - so I will connect to PDA.
Can you possibly also direct me to the correct FTDI drivers and any adjustments that you have done to them?

 

Thanks evo828.

I used the example 4 from this page:
http://www.ftdichip.com/Projects/CodeExamples/VB.htm

I used the d2xx_unit_net.vb file virtually unchanged except for changing the c:\WINNT\System32 etc path for the dlls to no path at all. Then I just call the routines as you can see in my source.

Jack, please may I use snippets of your simplified xml processing code to read in the x,y,address of the RAM maps?

 

On PDA I am getting following error after I start the exe:
File or assembly name 'Microsoft.VisualBasic, Version=8.0.0.0, etc etc' or one of its dependencies, was not found - then the next page tells me to insert storage card or to reinstall NET framework. I tried to uninstall and install Net compact framework 2 and SP1 several times - still the same message. Have you experienced similar problems? I have windows moble 2003 SE.

I do not think it is because I do not have the FTD2xx driver and the cable connected - it should start and show the initial scree as it does on a laptop witout cable and drivers.

 

There are a few different apps here and we should probably keep each topic in the correct thread:

My RS232 based PDA logger
Galvitron's Tactrix PDA logger
My PC/Tactrix logger/live mapper which is what this thread is about.

If you are trying to run the app posted in this thread on a PDA it won't work!

 

This version allows the addresses used for the RAM fuel and timing maps as well as the RAM mapswitch variable to be manually altered in the program. Also the dimensions of the fuel and timing maps can be altered manually.

This now seems to be ready to produce a realtime mapping test ROM... Evo IX US first I think version 15? This is most like the one I started with (JDM IX).

This has been a codathon to get the PC stuff going. I'm going to have to remember how to do SH2 asm again LOL.

Anyone want to help?

 

Under setting... click setup tables to draw the fuel and timing tables and lock the values for the map sizes and locations. If you need to change them, the app needs to be closed and reopened, this was easier/safer.

Note that the axis info for the maps is still hard coded! You can manually type over it to see what you are doing.

I need some really tech savvy testers for this that aren't scared off by complication and can then help develop it.

 

Sorry - I've got confused.

Comming back to the right topic. What does the map switching address mean?

 

It is the address I write to in RAM to select map set 0 (ROM) or set 1 (RAM).