Yep.

Silly bytes

 

Yep yep.

Want to know a silly tidbit on bytes?

Even Addresses need 2 bytes. (A, C and E are even)

 

Yeah, I assumed it was 2 byte in looking at the value it was spitting out, but my original equation for 2 byte was assuming x/65535 instead of x/1023... so it had me really confuzzled. All good now though!

 

FYI, my current logcfg is here for anyone that wants to use it:

http://thefrost.net/randomfiles/tuni...810.logcfg.txt

 

I know this is a terrible question, but is there any way to get the remote logger to work for the IX. I have the 2.0 cable and a SD card. I was going to try and set this up for logging in a week or so.... Also, if this will work, what WBO2 are you using fostyou?

 

The trigger would work the same, you just need to know the address of a memory location to trigger on. The 8's have an IC cooler sprayer button. The X has a cruise control button. I'm not sure what you could key off of for the 9. (Never driven one)

 

I would be content with just logging it 24/7 and not needing a trigger. I have a 4 GB SD card so that should last for a while...

 

Sweet, serial datastream added (for UEGO, etc). Now I just have to find out how to build the cable!

 

Excellent. I meant to do some work on this, but it slipped my mind completely...

 

I have a diagram made, but I think it may be incorrect. I'll test my roommate's LC-1 conversion cable when he gets home and try to match up to that...

 

Looks like my diagram was correct according to my mulimeter, but I couldn't confirm because the LC1 cable and my AEM cable are both female-side cables and I couldn't find one of the 20 gender benders I have

I'll try to build a cable when I get back from Deal's Gap this weekend.

 

Does anyone know if it is possible to get the standalone logging to have a more precise time scale like in the Evoscan logs, i.e., LogEntrySeconds? I wired up my ECU ADC to my wideband and everything works great but Virtual Dyno cannot plot the run worth **** because the only time scale in the logs is <time> which doesn't provide a smooth graph at all due to the lack of resolution. It looks like a set of bear teeth when plotted.



Thanks!

 

the time is accurate...

how many things are you logging?

 

Yeah, it's probably due to logging too much stuff. The standalone does not log very fast. The drive could limit it too... I say could, because it's not writing that much data, so I don't know how fast it needs to be, but if the flash has to erase a sector, it could cause some good lag.

 

Colby limits the number of requests to the ECU, it should only be *slightly* slower than EvoScan...