I spoke to him online for a few and he was supposed to email me some code & instructions on what he needed done.

Nothing in my indbox yet though. I am going to make a more concentrated effort to be online this evening to help out.

 

Thanks for your wonderfull insight.

 

Glad to see you had even a small amount of intelligence to add.


What we really need is a way to see what load column the car is using. It would also be nice to see it real time and have it leave a ghost track of cells behind that it passes through. I wrote software to do this for the UTEC and it made my tuning job a heck of a lot easier.

I spend a lot of time messing with Corvettes and, at the end of the day, it would be really awesome if we could get a package that is as complete as, say, HP Tuners. This way you could log and see those logs over your maps and other tracked variables. I know that LM/LC-1 support is getting added into the software, and I am certain its only a matter of time before we end up with really great logging support built into the software. It seems that we will need to, at bare minimum, get the data directly from the sensors though, instead of OBD-II, since the OBD-II port is operating so slow.

 

Listen bro, what I was pointing out was you were dissing the guy who is writing the EVOScan software (the "stupid" comment in case you forgot).

I just think it is better to keep on topic and air your gripes about languages in some other thread.

BTW I'm sure you are way more intelligent than I am...

 

Bump For Topic

 

ok back on topic lol, hoping this week the scan datalogger software will be out and we all can start using it since last week was said it was a few days from done, im so exsided for this. and also this will help al a huge amount with all the e flashes he is geting order i think will make his work load down and also he can get them out faster to us who are inpasiont woot woot.

 

I need to apologize for my previous statement. It wasnt meant to be read as "You are stupid for using VB.", understanding of course, that its easy to read it that way. What was meant by stating VB is for stupid people, is that its a very simple language and requires little, to no, training to use. After spending the last 13 years of my life coding you come to learn all about the negatives of using a high level language, especially once the compilers start to mash things up.

Back on topic... Like I said earlier in this thread, this is one of the better, most useful, threads I have seen in quite sometime. There is a lot of good information here. I hope that we will have a solution that can work straight from the OBD-II port, but given what we know about the sampling rate, Im not all that optimistic. Not that I cant think of a few ways to possibly speed it up, but I havent played in this area all that much, so I dont really have the knowledge needed to risk damaging some internal components.

I ordered the LM-1 + aux box, so I will be sharing how that goes with logging and the built in accelerometer. Obviously its not really worth $600 to most everyone, potentially even myself, but you only live once so spend that money now before its too late To MJ and whomever else was offended by my VB statement; sorry guys / gals.

 

EVO4Mad claims that his EVOScan software will have a sampling rate of at least 140-200 samples per second. I am not sure how many parameters he is logging for that rate. I think he has figured out the MUT protocol???

 

The Default OBDII protocol is definitely SLOW, but after talking to Evo4Mad he mentioned he was able to get a much higher speed and that the ECU itself is capable of running a faster speed, only the OBD-II protocol (for the US market) is standardized at a particular speed. He determined most of this by analyzing the functions of the MUT tool with an oscilliscope to see how fast the data exchange is in monitoring mode, and also how each function is communicated and responded to, though I think he said he needs some more time with the tool to get the rest of the data he needs.

Keep in mind he told me he did this data gathering on 2-3 seperate occasions of about 1 hour of analysis with his computer and oscilliscope.. Thats pretty damn impressive..

I'm pretty sure VB.net was chosen as the host language because it is the easiest to use and get a User interface that people won't ***** about.

 

From my experience, I have never seen an OBD-II port go as slow as the one on the EVO. With the 2000 Vette, we can get 3 data items at 72 s/ps. The Subarus also provide a much much faster OBD-II connection. The ECU may be intentionally limited so that its not used for "Tuning" purposes, but Im not sure how likely that really is. It would definitely be a great thing if he can figure out how to get the ECU to update over the OBD-II port quicker. If I had the *****, I would pull the ECU apart and find the component thats limiting it. Anyone got a wrecked ECU?

 

I logged a Subaru this weekend using ecuexplorer and my 1.3m cable. 3rd gear pull 3k to redline logging 8 data items resulted in samples every 50 rpm's. Very impressive. If the Evo is anywhere close to this I will be blown away.

Girlie

 

Good choice on the LM-1 and aux box. I have the LM-1 and the LMA-2 (RPM Convertor). If I had to do it all over again I will get the LM-1 and the DL-32 instead of the Aux Box. The DL-32 has the ability to log timing and AFAIK the Aux Box does not. So far with the LM-1 and the LMA-2 I have been able to log AFR, RPM and Boost. EGT is next. The nice thing about the LM-1 is the Logworks software that allows you to creat so many diiferent table combinations. Look at the one below. It shows AFRs by RPM and PSI. It includes 12 3rd gear pulls. The AFR numbers can be shown in average, max, min, stddev. In brackets are the number of data points displayed in each category.

 

You arent able to log timing with the Aux box nj1266? According to the innovate web site (http://www.innovatemotorsports.com/p...s/MTS_grid.php) the aux box supports Ign timing sensing. Were you not able to do this?

 

I do not have the Aux Box. I have the LMA-2. You are right, according to the grid the Aux Box logs timing, but they do not mention that here http://www.innovatemotorsports.com/products/lma3.php

T be safe, give them a call and make sure that the Aux Box has the INTERNAL ability to log timing.

 

Read here (http://www.innovatemotorsports.com/s...MA3_Manual.pdf) on page 18. Actually gives you a nice lesson on how to determine timing.