Openport Stand-Alone Logging Beta

[cboles]

I don't think it is the patch, because logcfg.out is written by the OP2 before it tries to communicate with the ECU and do any logging. You could have no ECU in the car and still get a logcfg.out file when you plug the OP2 into the OBD port.

The card is a 2GB Sandisk, formatted fat32, and while it is very possible that it is an issue with the card, it was working before applied the patch. I will try reformatting the card on a different computer and try it again if the k-line logging doesn't work. After that perhaps I can re-flash with an unpatched ROM.

Thanks
Matthew

What size / make is the SD card? What filesystem is it formatted with (FAT16, FAT32, etc)? I'm wondering if the OP2 is having some trouble writing to that card for some reason.

[mshoemaker]

No problem, I just thought it was strange that the logcfg.out was empty, and I noticed it not working after the patch. I think you may be on to something with the format of the SD card however, because I did recently install Windows 7. I will try everything from my other WinXP or Linux machine and see how it goes.

Thanks
Matthew

I don't think it is the patch, because logcfg.out is written by the OP2 before it tries to communicate with the ECU and do any logging. You could have no ECU in the car and still get a logcfg.out file when you plug the OP2 into the OBD port.

[cboles]

I wonder if the FAT on the card is somehow corrupted. Assuming you don't have anything important on the card, try quick formatting it and putting the logcfg.txt back on it. Also try FAT16 (although both should work).

c

[mshoemaker]

Hm, ok I reformatted, then took MY logcfg.txt file setup for CAN and tried it again, still no luck. So I just copied the k-line file from the samples directory and tried it and it works fine. I didn't get a chance to try the CAN sample again, but I will soon.

Thanks
Matthew

I wonder if the FAT on the card is somehow corrupted. Assuming you don't have anything important on the card, try quick formatting it and putting the logcfg.txt back on it. Also try FAT16 (although both should work).

c

[cboles]

can you post the exact CAN logcfg.txt file you are using to this thread so I can see what might be wrong? i know you copied it from the installation, but it just want to be extra sure there is nothing funny in the file.

thanks.

Hm, ok I reformatted, then took MY logcfg.txt file setup for CAN and tried it again, still no luck. So I just copied the k-line file from the samples directory and tried it and it works fine. I didn't get a chance to try the CAN sample again, but I will soon.

Thanks
Matthew

I wonder if the FAT on the card is somehow corrupted. Assuming you don't have anything important on the card, try quick formatting it and putting the logcfg.txt back on it. Also try FAT16 (although both should work).

c

[mshoemaker]

Well I did get a chance to try out the sample CAN file, and it worked. This was the first try with the RAM parameters. I will try again without them.

Matthew

can you post the exact CAN logcfg.txt file you are using to this thread so I can see what might be wrong? i know you copied it from the installation, but it just want to be extra sure there is nothing funny in the file.

thanks.

[cboles]

- I thought you had said the sample CAN file was not working?

Well I did get a chance to try out the sample CAN file, and it worked. This was the first try with the RAM parameters. I will try again without them.

Matthew

can you post the exact CAN logcfg.txt file you are using to this thread so I can see what might be wrong? i know you copied it from the installation, but it just want to be extra sure there is nothing funny in the file.

thanks.

[mshoemaker]

It did not work before the format, it did after.

Matthew

:?: - I thought you had said the sample CAN file was not working?

[cboles]

I wonder if the OP2 might have corrupted your filesystem at some point. Even though I do it all the time, you generally want to wait for the OP2 to stop logging before disconnecting it from the car, just in case it happens to be writing the FAT right when you yank it. If you leave it plugged into the car, and then just connect via USB, it closes out the files before connecting to your PC.

It did not work before the format, it did after.

Matthew

:?: - I thought you had said the sample CAN file was not working?

[ahagge]

start and stop conditions apply to any type of logging. i could also make a "new file" action. take a look at the subaru samples - i just didn't bother copying those examples into the mitsu samples yet. you might consider using some sort of switch on your dash such as the defogger to trigger logging since i imagine there are also times when you are at WOT that you are just driving and don't want your file chopped up.

Is there a list of switch bitfield items for Mitsubishis anywhere (specifically, for a 2006 Evo IX MR)? I'd like to make a start/stop based on some dashboard switch (most likely the rear defroster), but I can't find the paramid and offsetbits for it. The only switch I've been able to locate is the A/C switch, via the EvoScan files, which claims it's paramid=4A offsetbits=5 (can anyone confirm?).

For that matter, is there a list of all possible parameters for an '06 IX MR? Again, my only source has been the EvoScan program, which seems to be pretty complete, but I'm not sure if they're missing anything that might be useful.

Lastly, I've generated a log file using the sample "mitsubishi k-line.txt" config file, but I had to do some significant tweaking to get it to be read by EvoScan for graphing. Might it be possible for the logger to automatically include the "LogEntryDate" and "LogEntryTime" fields that EvoScan requires? I know that real time & date can't be used due to lack of clock hardware, but a date of "2000-01-01" and a time of "00:00:00" plus the LogEntrySeconds could be put into those to fields to allow EvoScan to read the .CSV file correctly.

[cboles]

I don't know the Mitsu bitfields, but I should be able to make a time format parameter that supports the EvoScan format. Could you post a few sample lines of EvoScan data?

start and stop conditions apply to any type of logging. i could also make a "new file" action. take a look at the subaru samples - i just didn't bother copying those examples into the mitsu samples yet. you might consider using some sort of switch on your dash such as the defogger to trigger logging since i imagine there are also times when you are at WOT that you are just driving and don't want your file chopped up.

Is there a list of switch bitfield items for Mitsubishis anywhere (specifically, for a 2006 Evo IX MR)? I'd like to make a start/stop based on some dashboard switch (most likely the rear defroster), but I can't find the paramid and offsetbits for it. The only switch I've been able to locate is the A/C switch, via the EvoScan files, which claims it's paramid=4A offsetbits=5 (can anyone confirm?).

For that matter, is there a list of all possible parameters for an '06 IX MR? Again, my only source has been the EvoScan program, which seems to be pretty complete, but I'm not sure if they're missing anything that might be useful.

Lastly, I've generated a log file using the sample "mitsubishi k-line.txt" config file, but I had to do some significant tweaking to get it to be read by EvoScan for graphing. Might it be possible for the logger to automatically include the "LogEntryDate" and "LogEntryTime" fields that EvoScan requires? I know that real time & date can't be used due to lack of clock hardware, but a date of "2000-01-01" and a time of "00:00:00" plus the LogEntrySeconds could be put into those to fields to allow EvoScan to read the .CSV file correctly.

[ahagge]

I don't know the Mitsu bitfields, but I should be able to make a time format parameter that supports the EvoScan format. Could you post a few sample lines of EvoScan data?

Thanks for the offer. Here you go (this is from a sample of theirs included with the program, not an actual run):

Code: Select all

LogID,LogEntryDate,LogEntryTime,LogEntrySeconds,LogNotes,TPS,RPM,InjPulseWidth,I
njDutyCycle,MAP,AccelEnrich,TimingAdv,FuelTrim_Low,FuelTrim_Mid,FuelTrim_High,O2
FeedbackTrim,O2Sensor,O2Sensor2,Speed,CoolantTemp,AirFlow,AirTemp,Battery,AFRMAP
,LoadCalc,WideBandAF,AirVol,Baro,KnockSum,ISCSteps,Load11bit4,ECULoad,InjectorLa
tency,LoadMUT2Byte,RPMMUT2Byte,TestE1,TestE4,OctaneFlag,TargetIdleRPM,Knock,knoc
k_adc,knock_base,knock_var,knock_change,knock_dynamics,knock_flag,EGRTemp,WGDC,Z
TXEGT,ZTXBoost,ZTXRPM,ZTXTPS,ZTXUser1,ZTXConfig,LC1RPM,LC1Battery,LC1Aux1,LC1Aux
2,LC1Aux3,LC1Aux4,LC1Aux5,Custom
1,2007-10-03,19:37:15.40915,0.36052,,13.7254901960784,1000,1.792,1.4933333333333
3,-6.96467,36.8627450980392,7,100,108.59375,120.3125,110.15625,0.195,0.702,0,193
.7586232,37.74,109.651523824,14.0003,128,27.1395191460937,,248,101,0,,49,32.5,18
,32.5,1000,,,100,990.6,,,,,,,,,,,,,,,,,,,,,,,17: 35
2,2007-10-03,19:37:15.84978,0.80115,,13.7254901960784,1000,1.536,1.28,-6.96467,3
6.8627450980392,7,100,108.59375,120.3125,113.28125,0.624,0.624,0,193.7586232,37.
74,109.651523824,13.927,128,21.8588137734375,14.9058,8,101,0,,48,31.875,19,31.56
25,992.1875,,,100,990.6,,,,,,,,,,,,,,,,,,,,,,
3,2007-10-03,19:37:16.37053,1.3219,,13.7254901960784,1000,1.536,1.28,-6.96467,36
.8627450980392,7,100,108.59375,120.3125,110.15625,0.702,0.507,0,193.7586232,37.7
4,109.651523824,13.927,128,21.8588137734375,14.9646,16,101,0,,48,32.5,18,32.1875
,968.75,,,100,990.6,,,,,,,,,,,,,,,,,,,,,,


I'm hoping that someone (tephra perhaps?) might be able to comment on the bitfields.

[cboles]

"17: 352"

any idea what this weird field value is at the end of the first line?

I don't know the Mitsu bitfields, but I should be able to make a time format parameter that supports the EvoScan format. Could you post a few sample lines of EvoScan data?

Thanks for the offer. Here you go (this is from a sample of theirs included with the program, not an actual run):

Code: Select all

LogID,LogEntryDate,LogEntryTime,LogEntrySeconds,LogNotes,TPS,RPM,InjPulseWidth,I
njDutyCycle,MAP,AccelEnrich,TimingAdv,FuelTrim_Low,FuelTrim_Mid,FuelTrim_High,O2
FeedbackTrim,O2Sensor,O2Sensor2,Speed,CoolantTemp,AirFlow,AirTemp,Battery,AFRMAP
,LoadCalc,WideBandAF,AirVol,Baro,KnockSum,ISCSteps,Load11bit4,ECULoad,InjectorLa
tency,LoadMUT2Byte,RPMMUT2Byte,TestE1,TestE4,OctaneFlag,TargetIdleRPM,Knock,knoc
k_adc,knock_base,knock_var,knock_change,knock_dynamics,knock_flag,EGRTemp,WGDC,Z
TXEGT,ZTXBoost,ZTXRPM,ZTXTPS,ZTXUser1,ZTXConfig,LC1RPM,LC1Battery,LC1Aux1,LC1Aux
2,LC1Aux3,LC1Aux4,LC1Aux5,Custom
1,2007-10-03,19:37:15.40915,0.36052,,13.7254901960784,1000,1.792,1.4933333333333
3,-6.96467,36.8627450980392,7,100,108.59375,120.3125,110.15625,0.195,0.702,0,193
.7586232,37.74,109.651523824,14.0003,128,27.1395191460937,,248,101,0,,49,32.5,18
,32.5,1000,,,100,990.6,,,,,,,,,,,,,,,,,,,,,,,17: 35
2,2007-10-03,19:37:15.84978,0.80115,,13.7254901960784,1000,1.536,1.28,-6.96467,3
6.8627450980392,7,100,108.59375,120.3125,113.28125,0.624,0.624,0,193.7586232,37.
74,109.651523824,13.927,128,21.8588137734375,14.9058,8,101,0,,48,31.875,19,31.56
25,992.1875,,,100,990.6,,,,,,,,,,,,,,,,,,,,,,
3,2007-10-03,19:37:16.37053,1.3219,,13.7254901960784,1000,1.536,1.28,-6.96467,36
.8627450980392,7,100,108.59375,120.3125,110.15625,0.702,0.507,0,193.7586232,37.7
4,109.651523824,13.927,128,21.8588137734375,14.9646,16,101,0,,48,32.5,18,32.1875
,968.75,,,100,990.6,,,,,,,,,,,,,,,,,,,,,,


I'm hoping that someone (tephra perhaps?) might be able to comment on the bitfields.

[ahagge]

"17: 352"
any idea what this weird field value is at the end of the first line?

No idea. I did a double-take when I first uploaded the lines this morning. The author provided 2 sample files, and both had the same item. I guess it's the "Custom2" field. Here's the second sample file:

Code: Select all

LogID,LogEntryDate,LogEntryTime,LogEntrySeconds,LogNotes,TPS,RPM,InjDutyCycle,TimingAdv,WideBandAF,KnockSum,LoadMUT2Byte,Knock,InjPulseWidth,MAP,AccelEnrich,FuelTrim_Low,FuelTrim_Mid,FuelTrim_High,O2Feedba
ckTrim,O2Sensor,O2Sensor2,Speed,CoolantTemp,AirFlow,AirTemp,Battery,AFRMAP,LoadCalc,AirVol,Baro,ISCSteps,Load11bit4,ECULoad,InjectorLatency,RPMMUT2Byte,TestE1,TestE4,OctaneFlag,TargetIdleRPM,knock_adc,knoc
k_base,knock_var,knock_change,knock_dynamics,knock_flag,EGRTemp,WGDC,ZTXEGT,ZTXBoost,ZTXRPM,ZTXTPS,ZTXUser1,ZTXConfig,LC1RPM,LC1Battery,LC1Aux1,LC1Aux2,LC1Aux3,LC1Aux4,LC1Aux5,Custom
1,2007-10-04,18:46:53.32812,0.89062,,24.7058823529412,2187.5,0,36,,0,104.375,0.507,5.888,,,100,97.65625,135.9375,100,,,26.0975904,,,,,130,,,,,,63.75,,,,,,,,,,,,,,,,,,,,,,,,,,,,17: 255
2,2007-10-04,18:46:53.51562,1,,100,2312.5,0,17,13.7,0,109.0625,0.4875,6.144,,,100,97.65625,135.9375,100,,,26.0975904,,,,,130,,,,,,62.5,,,,,,,,,,,,,,,,,,,,,,,,,,,
3,2007-10-04,18:46:53.60937,1.09375,,100,2343.75,0,17,13.6,0,110.3125,0.5265,6.4,,,100,97.65625,135.9375,100,,,26.0975904,,,,,131,,,,,,62.5,,,,,,,,,,,,,,,,,,,,,,,,,,,
4,2007-10-04,18:46:53.68750,1.17188,,100,2375,0,16,13.5,0,112.5,0.5655,6.4,,,100,97.65625,135.9375,100,,,26.0975904,,,,,131,,,,,,62.5,,,,,,,,,,,,,,,,,,,,,,,,,,,
5,2007-10-04,18:46:53.78125,1.26562,,100,2406.25,0,16,13.5,0,114.375,0.5655,6.656,,,100,97.65625,135.9375,100,,,26.0975904,,,,,132,,,,,,62.5,,,,,,,,,,,,,,,,,,,,,,,,,,,


I CAN tell you that after I inserted the LogEntryDate, LogEntryTime and LogNotes fields into test the OpenPort 2.0 log file, that file was then readable by EvoScan. That bizarre item at the end of the first line was not necessary. I'm not sure that the LogNotes field was necessary either, but the LogEntryDate and LogEntryTime definitely were.

[burnzy]

are we evo owners able to do standlone 2 byte logging, just say if I wanted 2 byte load which is mut00 and mut01, would it be paramid=0x00,0x01 or paramid=0x0001, if both are wrong could anyone tell me how it's done if it can indeed log byte?