PDA

View Full Version : Weired LS1 Passthrough Log



swingtan
July 1st, 2010, 06:17 PM
Hi All,
I have a long, curly question for those that have done a lot of logging. Last night I logged a friends LS1 ( Holden VY Auto) that had been tuned with HPT. I logged with the laptop as I wanted to see the charts in real time and it all worked well. Initial connection of the V2 and power on of the ignition saw Tune tool do a validation and scan of modules, nothing exciting there.

Starting the log worked fine, until the auto was put into gear. At this point the WB went lean, really lean. I'm used to seeing it go to 25:1 for DFCO, but at times it was reading 60:1, which is just plain wrong. As soon at it was put in neutral or went into "over run" down a hill, the WB returned to normal operation.

I know what you are thinking, the WB is playing up, which is what I thought. But I tried replicating the problem by moving the cables and applying some pressure to the sender, but nothing would replicate the problem except putting it in any gear. As soon as it went into gear, it went lean on the WB. It was running in CL and the STFT's did indicate a slight lean out, but nothing compared to the WB.

Another thing I found was that after saving the log file, the time stamps were completely messed up in the log. The data displayed OKL, but the time stamps were all over the place. So I closed TuneTool and attempted to reopen the same log file. At this point I was met with a completely corrupted log. Nothing displayed correctly, even after a reboot.

What I then found was that the log file had been corrupted just after the metadata header. For those that care, this is what it looked like....




Source file: Log_0001.efi
Source size: 419069
Source Meta size: 1934


Source Metadata as follows...
[FILE],2
VERSION=7.5
DECSEP=.
[VEHICLE],22
VIN=6G1YK54F34Lxxxxxx
TAG=
REGO=xxxxxx
DIFF_RATIO=
TRANSMISSION=Manual 5 speed
AUTO=0
INJECTORS=
GVM=1650000
DISPLACEMENT=0
MOD_COLDAIR=0
MOD_THROTTLE=0
MOD_CAM=0
MOD_VALVE=0
MOD_TRACTION=0
MOD_IGNITION=0
MOD_PCMCAL=0
MOD_MAF=0
MOD_HEADERS=0
MOD_EXHAUST=0
MOD_N2O=0
MOD_HEADS=0
OS=1271001
[DTEXT],1
COMMENTS=
[PID],24
EXT.WO2AFR1=0
EXT.WO2AFR2=2
EXT.WO2LAM1=4
EXT.WO2LAM2=6
EXT.WO2ST1=8
EXT.WO2ST2=10
GM.AFR=12
GM.ASPARK=14
GM.DYNCYLAIR=0
GM.HO2S11=16
GM.HO2S21=17
GM.IBPW1=18
GM.KR=20
SAE.ECT=21
SAE.IAT=22
SAE.LONGFT1=23
SAE.LONGFT2=24
SAE.MAP=25
SAE.RPM=26
SAE.SHRTFT1=28
SAE.SHRTFT2=29
SAE.SPARKADV=30
SAE.TP=31
SAE.VSS=32
[DTC],1
COUNT=0
[LTFT],4
MAP=$00,$00,$00,$00,$00,$00
RPM=$00,$00,$00,$00,$00,$00
0-15=$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00 ,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$ 00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00 ,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$ 00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00 ,$00,$00
16-23=$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00 ,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$ 00,$00,$00,$00,$00,$00,$00,$00
[SHIFT],3
1-2=$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00
2-3=$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00
3-4=$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00,$00, $00,$00,$00,$00,$00
[MISC],20
GM.ENGSIZE_DMA=
GM.TRANS_DMA=
GM.DIFF_DMA=
GM.4WD_DMA=
GM.VSSLIMIT_DMA=
SAE.O2SLOC=
GM.MAFHIGHFAIL_DMA=
GM.MAFLOWFAIL_DMA=
GM.MAFRATFAIL_DMA=
GM.MAFRATCOMP_DMA=
GM.ESCFAIL_DMA=
GM.FANTYPE_DMA=
GM.FAN1OFF_DMA=
GM.FAN1ON_DMA=
GM.FAN2OFF_DMA=
GM.FAN2ON_DMA=
SAE.OBDSUP=
GM.RAMFAIL_DMA=
GM.ROMFAIL_DMA=
GM.ROMCHKSUM_DMA=
[DATA],6
DASHBOARD=Default LS1 Metric.vdb
PIDCOUNT=24
CHANNELCOUNT=35
FRAMECOUNT=9677
STARTDATE=40360
STARTTIME=74147890
[End_Of_Meta_Data],0

Channel Count: 35
Frame size: 43
Data length: 416111
Frame Data:



All that looks pretty good.... But then the actual frame data starts.....




C:\data\apps\EFILive\V7.5\Logged data\Log_0001.efi

00000000 5b 44 41 54 41 5d 2c 36 0d 0a 44 41 53 48 42 4f 41 52 44 3d 44 65 66 61 75 6c 74 20 4c 53 31 20 4d 65 74 72 [DATA],6..DASHBOARD=Default LS1 Metr
00000024 69 63 2e 76 64 62 0d 0a 50 49 44 43 4f 55 4e 54 3d 32 34 0d 0a 43 48 41 4e 4e 45 4c 43 4f 55 4e 54 3d 33 35 ic.vdb..PIDCOUNT=24..CHANNELCOUNT=35
00000048 0d 0a 46 52 41 4d 45 43 4f 55 4e 54 3d 39 36 37 37 0d 0a 53 54 41 52 54 44 41 54 45 3d 34 30 33 36 30 0d 0a ..FRAMECOUNT=9677..STARTDATE=40360..
0000006c 53 54 41 52 54 54 49 4d 45 3d 37 34 31 34 37 38 39 30 0d 0a 5b 45 6e 64 5f 4f 66 5f 4d 65 74 61 5f 44 61 74 STARTTIME=74147890..[End_Of_Meta_Dat
00000090 61 5d 2c 30 0d 0a 54 41 09 c4 06 a5 06 a5 00 01 00 00 34 35 37 30 33 0d 0a 5b 45 6e 64 5f 4f 66 5f 4d 65 74 a],0..TA.Ä.¥.¥....45703..[End_Of_Met
000000b4 61 5f 44 00 00 00 00 4e 5c 43 04 16 6a 09 c4 06 a5 06 a5 00 01 00 00 00 00 10 00 66 68 00 00 00 7d 58 80 80 a_D....N\C..j.Ä.¥.¥........fh...}X€€
000000d8 66 00 00 80 80 80 00 00 00 00 00 00 28 5d 43 04 16 6a 09 c4 06 a5 06 a5 00 01 00 00 00 00 10 00 67 64 00 00 f..€€€......(]C..j.Ä.¥.¥........gd..
000000fc 00 7d 58 80 80 66 00 00 80 80 80 00 00 00 00 00 00 02 5e 43 04 16 6a 09 c4 06 a5 06 a5 00 01 00 00 00 00 10 .}X€€f..€€€.......^C..j.Ä.¥.¥.......
00000120 00 67 68 00 00 00 7d 58 80 80 66 00 00 80 80 80 00 00 00 00 00 00 ee 5e 43 04 16 6a 09 44 06 a5 06 a5 00 01 .gh...}X€€f..€€€......î^C..j.D.¥.¥..


Note the repeated "[End_Of_Meta_D" tag in there.... So something is very wrong.

Checking the frame data I could pick the time stamps, so I I did a BYTE count between them and got 41. Taking away the note and time data, that gave 33 bytes, but the Metadata says the Channel count is 35, so that's going to mess things up.

I giot into the log file with a HEX editor and found that if I changed the Channel count, deleted the first frame and dropped the last 2 PID descriptors in the Metadata, I could now read the log, though it's still a tad weird.

Any takers on what's going on here?

The original corrupt log (click here ---> )8381

The "some what fixed" log sowing the WBas the car goes in / out of gear (click here ---> )8382


Simon.

Blacky
July 2nd, 2010, 10:48 AM
Don't know what's going on with the wideband - it could be a symptom of the data corruption in the log file.

The log file is very much corrupted, again I don't know why.

The two PIDs GM.ASPARK and GM.DYNCYLAIR are both messed up in the [PID] meta data.
GM.ASPARK is only allocated 1 byte (should be 2)
GM.DYNCYLAIR has an offset of 0, I don't know why.

Sorry I can't be of much help but there's too many things wrong with that log file to try and work out the cause.
Is the corruption problem repeatable? Can you log more files and always get a corrupt file?

Based on the limited data I have it may be something to do with EFILive confusing a previous log file's PIDs with the current log file's PIDs.
Other than that I can't help much.

Regards
Paul