Live mapping PC side app - progress yes and no!
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
Live mapping PC side app - progress yes and no!
I took my Pocket PC application and migrated it to the laptop PC. Fairly quickly I had logging running with live display of values, live knock display, although the scrolling live graphs I had on the Pocket PC don't scroll. I was pleased to see that using a virtual com port with the Tactrix cable I could also connect at the standard 15625 baud. I was further pleased to quickly get a live mapping going of the high octane fuel and timing maps.
My future plan was to try to get an xml configurable setup going or just releasing the logger's code so that live tuning can be released to many ECUs with the production of modified ROMs.
HOWEVER, the logging performance using the same code on the high spec laptop PC is very oddly less than HALF that of Evoscan or the Pocket PC. There must be something fiddly working with the virtual com port and the serial port drivers in .net 2.0, but using lots of ways of reading and writing it just won't go faster. Whilst logging at 60 items per second it is not a disaster until you find that writing the ignition map back to the RAM in the ECU takes 14 seconds, which is just too long, even though you can do it as the car is being driven. It can go much faster so I need full speed!
With a very simple setup that simply writes 300 bytes to the port and waits for the echo it is taking about 5 seconds at 19200 baud! It should take about 0.15 seconds. The instructions being delayed seem to be reading a byte or string from the serial port. Very irritating when the same code on the steam powered Pocket PC absolutely flies!
So I'll have to access the FTDI stuff directly, my first attempt doesn't work though!
It was frustrating to make such rapid initial progress to be hit by technicalities.
You can see the sort of table that gets read or written when the buttons are clicked and it all works. Presently you make changes and then they are only made when you click write. There is a similar map for the high octane ignition timing.
My future plan was to try to get an xml configurable setup going or just releasing the logger's code so that live tuning can be released to many ECUs with the production of modified ROMs.
HOWEVER, the logging performance using the same code on the high spec laptop PC is very oddly less than HALF that of Evoscan or the Pocket PC. There must be something fiddly working with the virtual com port and the serial port drivers in .net 2.0, but using lots of ways of reading and writing it just won't go faster. Whilst logging at 60 items per second it is not a disaster until you find that writing the ignition map back to the RAM in the ECU takes 14 seconds, which is just too long, even though you can do it as the car is being driven. It can go much faster so I need full speed!
With a very simple setup that simply writes 300 bytes to the port and waits for the echo it is taking about 5 seconds at 19200 baud! It should take about 0.15 seconds. The instructions being delayed seem to be reading a byte or string from the serial port. Very irritating when the same code on the steam powered Pocket PC absolutely flies!
So I'll have to access the FTDI stuff directly, my first attempt doesn't work though!
It was frustrating to make such rapid initial progress to be hit by technicalities.
You can see the sort of table that gets read or written when the buttons are clicked and it all works. Presently you make changes and then they are only made when you click write. There is a similar map for the high octane ignition timing.
Last edited by jcsbanks; Dec 5, 2007 at 02:36 PM.
Thread Starter
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
Yes I wrote it and posted it here. There are threads in this forum on it. No one else is running it because it needs a Pocket PC 2003 SE with a real serial port, and you need to change the ECU's MUT rate from 15625 to 19200 baud to suit the Pocket PC which you connect to the ECU using a VAG COM RS232 cable and whatever adaptor your Pocket PC needs to connect to 9 pin D RS232. So in other words there needs to be a "q" in the month for it to work 
Works great for me though.
We really need a program to live edit on a PC that is completely open hence why I need to write something, although having done the Pocket PC stuff it is easier, although new problems arise as discussed which are really frustrating.
Works great for me though.We really need a program to live edit on a PC that is completely open hence why I need to write something, although having done the Pocket PC stuff it is easier, although new problems arise as discussed which are really frustrating.
Thread
Thread Starter
Forum
Replies
Last Post
jcsbanks
ECU Flash
17
Dec 11, 2007 05:36 AM
