Openport Stand-Alone Logging Beta

[mdedwar]

For me the sample config file was wrong. I used
paramname = mylc1.afr
paramid = 0x0101
scalingrpn = x,14.7,*

[kewlboxer2]

NTFS wont work. Only FAT16 and FAT32. I'll need to look into what is going on. Unfortunately, I haven't seen any problems here.

Im having this issue as well. Its a 1gb transcend card. I have it setup for coolant temp on and rpm 0 off. Sometimes it will work sometimes it wont. green light flashes when i have the car off. when i start it up the blue flashes once, then its just red and green flashing(normal), but the blue never comes on to start the writing.

I think i have the card formatted for fat32. maybe i should try ntfs? or a whole new card

I know the previous firmware for the sd logging worked like a champ. any way i try to downgrade the firmware incase its not my card?

Also what size card can the OP2.0 take?

[zcivic]

Ok I am confused on how to make the log file to put on the SD card. I will admit I'm not very good with some of this stuff. Do I just need to create the log.txt file using the peram creater and place it on my card. I was wanting to use the rear def as a trigger. If someone can get me to a starting point I would greatly appreciate it. I have done everything just unsure about the txt file.
I'm using and 02 WRX A4SGE01C ECU.
Have a working ECUflash and OP2. Its ECUflash 1.43 beta and the OP2 have been licensced

Thanks,
Randy

[cboles]

The OP2 can use any SD or SDHC card. I don't have a good way to downgrade the firmware - what previous version worked for you? Was it before I added the background file system? That was a major, but necessary overhaul to allow faster logging speeds and prevent SD card delays from affecting the logging interval.

For all of the users out there having a problem: I still haven't seen any of your logcfg.txt files - please send them so I can see if I can reproduce the problem here.

I know the previous firmware for the sd logging worked like a champ. any way i try to downgrade the firmware incase its not my card?

Also what size card can the OP2.0 take?

[kewlboxer2]

It cant take just any SD or SDHC card. I have an 8gb card. all I get is a the color cycle.

I have fiarly good luck today with the logging. only had to unplug once out of 6 starts.

here is my logcfg and logcfg.out

i haven't been logging for a while know, but the firmware the worked perfect for me was the one about 4-5 months after sd logging was available, i think. i dont have my old version anymore because i have the newest on it right now.

The OP2 can use any SD or SDHC card. I don't have a good way to downgrade the firmware - what previous version worked for you? Was it before I added the background file system? That was a major, but necessary overhaul to allow faster logging speeds and prevent SD card delays from affecting the logging interval.

For all of the users out there having a problem: I still haven't seen any of your logcfg.txt files - please send them so I can see if I can reproduce the problem here.

I know the previous firmware for the sd logging worked like a champ. any way i try to downgrade the firmware incase its not my card?

Also what size card can the OP2.0 take?

[mfb]

The OP2 can use any SD or SDHC card. I don't have a good way to downgrade the firmware - what previous version worked for you? Was it before I added the background file system? That was a major, but necessary overhaul to allow faster logging speeds and prevent SD card delays from affecting the logging interval.

For all of the users out there having a problem: I still haven't seen any of your logcfg.txt files - please send them so I can see if I can reproduce the problem here.

I know the previous firmware for the sd logging worked like a champ. any way i try to downgrade the firmware incase its not my card?

Also what size card can the OP2.0 take?

Hi Colby,

I already posted my LogCfg, please see here http://forums.openecu.org/viewtopic.php?f=57&t=4319&start=435#p23345

[mfb]

Ok I am confused on how to make the log file to put on the SD card. I will admit I'm not very good with some of this stuff. Do I just need to create the log.txt file using the peram creater and place it on my card. I was wanting to use the rear def as a trigger. If someone can get me to a starting point I would greatly appreciate it. I have done everything just unsure about the txt file.
I'm using and 02 WRX A4SGE01C ECU.
Have a working ECUflash and OP2. Its ECUflash 1.43 beta and the OP2 have been licensced

Thanks,
Randy

What parameters do you need logged?

[cboles]

Does your 8GB card work as USB as a storage device using the OP2? Is it formatted FAT32? I'll try running your config and seeing if I run into trouble.

It cant take just any SD or SDHC card. I have an 8gb card. all I get is a the color cycle.

I have fiarly good luck today with the logging. only had to unplug once out of 6 starts.

here is my logcfg and logcfg.out

i haven't been logging for a while know, but the firmware the worked perfect for me was the one about 4-5 months after sd logging was available, i think. i dont have my old version anymore because i have the newest on it right now.

The OP2 can use any SD or SDHC card. I don't have a good way to downgrade the firmware - what previous version worked for you? Was it before I added the background file system? That was a major, but necessary overhaul to allow faster logging speeds and prevent SD card delays from affecting the logging interval.

For all of the users out there having a problem: I still haven't seen any of your logcfg.txt files - please send them so I can see if I can reproduce the problem here.

I know the previous firmware for the sd logging worked like a champ. any way i try to downgrade the firmware incase its not my card?

Also what size card can the OP2.0 take?

[cboles]

I ran your exact logcfg.txt on my 08 STI (some of the RAM address are incorrect, but I didn't care). I hit the defroster over 20 times. Each time it started logging normally. I checked with my PC and all of the log files are OK. I think it has something to do with the card (and perhaps the OP2 not dealing with the resulting problem well). I am interested in getting this card from you. We can send you a different one to use meanwhile... Also, can you verify what version of firmware you have (less than version 2996, and there is a limitation of 512 bytes for the column header - and i can see yours is over 512...)?

The OP2 can use any SD or SDHC card. I don't have a good way to downgrade the firmware - what previous version worked for you? Was it before I added the background file system? That was a major, but necessary overhaul to allow faster logging speeds and prevent SD card delays from affecting the logging interval.

For all of the users out there having a problem: I still haven't seen any of your logcfg.txt files - please send them so I can see if I can reproduce the problem here.

I know the previous firmware for the sd logging worked like a champ. any way i try to downgrade the firmware incase its not my card?

Also what size card can the OP2.0 take?

Hi Colby,

I already posted my LogCfg, please see here http://forums.openecu.org/viewtopic.php?f=57&t=4319&start=435#p23345

[adamw2]

For me the sample config file was wrong. I used
paramname = mylc1.afr
paramid = 0x0101
scalingrpn = x,14.7,*

Problem solved.. it turned out to be the fact that I didn't have a terminator plug in the Serial In port of the LC-1! I had no idea this was necessary!

All working now, I just had to change 0x0102 to 0x0101 as well so that the scalingrpn does 14.7 * lambda rather than 14.7 * AFR.

Thanks
Adam

[kewlboxer2]

Yes it works as a USB storage, because i can stick the logcfg and stuff on it.

Does your 8GB card work as USB as a storage device using the OP2? Is it formatted FAT32? I'll try running your config and seeing if I run into trouble.

[mfb]

I ran your exact logcfg.txt on my 08 STI (some of the RAM address are incorrect, but I didn't care). I hit the defroster over 20 times. Each time it started logging normally. I checked with my PC and all of the log files are OK. I think it has something to do with the card (and perhaps the OP2 not dealing with the resulting problem well). I am interested in getting this card from you. We can send you a different one to use meanwhile... Also, can you verify what version of firmware you have (less than version 2996, and there is a limitation of 512 bytes for the column header - and i can see yours is over 512...)?

Yes Im using the latest beta, one which addressed long header names. I was the one who got that problem before. I also experience that, logging over 20 times without issues. Its just that there are times that I just find the OP2 CAN in a hang state (blue light). There will be instances that upon first time insertion, pressing the defroster would make the blue light come on for a second plus before it starts to blink. Once this happens, pressing defogger again to deactivate will not get me a logged file. Again, I've lost a couple of logs due to this. So in the meantime, I always ensure that I see it blinking fast without the hesitation at the start before I confidently start logging.

My card is just a sandisk micro sdhc class 6. Getting this physically from me might be difficult as Im here in Manila. Let me know how else I can help, Salamat Colby! (That's thanks in Filipino)

[MechEE]

For me the sample config file was wrong. I used
paramname = mylc1.afr
paramid = 0x0101
scalingrpn = x,14.7,*

Problem solved.. it turned out to be the fact that I didn't have a terminator plug in the Serial In port of the LC-1! I had no idea this was necessary!

All working now, I just had to change 0x0102 to 0x0101 as well so that the scalingrpn does 14.7 * lambda rather than 14.7 * AFR.

Thanks
Adam

Confirmed for me as well: 0x0101 is the correct paramid for logging lambda on the LC-1. I was pulling my hair out trying to figure out why I was getting such a strange calculated AFR (~72:1) after flashing to the latest OpenPort firmware. It turns out it was a combination of an error in the sample LC-1 logcfg.txt suggesting the paramid should be 0x0102 and the infamous LC-1 reset bug that had a stoich of ~4.7:1 set. Oops!

[LM_logger]

Hi Colby,

Could you PM me your email address. Not sure if you're using the standard admin<at> one. Have an offer of a loan of LM-1 for you and want to pass on personal details as person has a few queries.

Cheers

[mfb]

For me the sample config file was wrong. I used

Confirmed for me as well: 0x0101 is the correct paramid for logging lambda on the LC-1. I was pulling my hair out trying to figure out why I was getting such a strange calculated AFR (~72:1) after flashing to the latest OpenPort firmware. It turns out it was a combination of an error in the sample LC-1 logcfg.txt suggesting the paramid should be 0x0102 and the infamous LC-1 reset bug that had a stoich of ~4.7:1 set. Oops!

Yep, I got this one too. Only problem is we all followed the address in the sample file. No biggie... Its one or the other, haha There's only 2 channels to choose from. If you look at LM programmer, you'll see it there.

Just be careful to make sure that you only pull the lc1 plug or attach it to OP2 if LC1 is off meaning ignition is off. Not doing so and operating this while on may cause LC1 to be sent a "recalibration" command and you will just get a 7 or 22 afr reading. This happened to me thrice already and in Colby's post here, it confirms and solved my issue. You can see it here http://forums.openecu.org/viewtopic.php?f=57&t=4319&start=420#p23313

I think I covered this somewhere before - it is basically a minor hw/sw design flaw in the LC-1 that can cause it to lose its settings when you you plug it into another device. What happens is that the tip terminal of the 2.5 plugs can get grounded as you plug them in, which is not a big deal in itself since it is an input, but some unfortunate protocol choices can make that glitch look like some sort of "clear calibrations" command. This isn't speculation - I heard this from the engineers at Innovate. So the solutions are to:

1) Plug the LC-1 in to the OP2 only when the LC-1 is off
2) Let the OP2 take care of the AFR scaling so that you don't notice the problem

Best to make OP2 do the scaling as per the sample file. Btw, once you got it calibrated and working, dont be surprised to see a custom settting when you go back to LM Programmer. I just chose gasoline again. I dont know why it went to custom, maybe it because Im using ethanol 10 based gas? But non issue as we scale using OP2.