Openport Stand-Alone Logging Beta

[cboles]

I have some fixes for the OP2 logging firmware and a new version of EcuFlash that does easy patching of your ROMs for better logging, but it needs some more testing, and I now have the flu, so I may not have anything until Monday. Hang tight!

Colby

[ladams00]

I named the `logcfg.txt` file as `logcfg.txt.txt`....user error It's functioning properly again.

I'm not sure what is going on there, but it seems like the OP2 is having trouble reading or writing the SD card. If you plug the OP2 into the PC with the card inserted, can you access it OK?

I have this same problem now. Upon plugging in the OP2 into the ODB port with car on or off...I see the blue/green light up momentarily, then switch to red for a couple seconds, then 3 color cycling pattern.

No logcfg.out is generated.

I tried formatting the sd card again (FAT16), same deal. Using the sample k-line subaru with lc-1 (and have commented out the ADC stanza because of the type limit).

--edit--
n00b shit false alarm
/me sighs

logcfg.txt.txt double extension garbage was my fault. I just switched to Windows 7 and haven't change the folder options to display known extension types.

Works better now

Awesome, thanks. I did not realize that.

Now my Tactrix won't respond when plugging it in. The leds just slowly fade in and out of colors rather than the green and red lights flashing. Not sure why. Car is running and its plugged in to the OBD port, and not plugged into USB.

[ladams00]

Don't die on us Colby
Forget the firmware for now

I have some fixes for the OP2 logging firmware and a new version of EcuFlash that does easy patching of your ROMs for better logging, but it needs some more testing, and I now have the flu, so I may not have anything until Monday. Hang tight!

Colby

[ladams00]

The IPW parameter in the sample config file for both subaru k-line and can is referencing the timing parameter's address 0x11 rather than the correct one which is 0x20. The scaling RPN expression however is correct for IPW.

I noticed this as that new calculated IDC was showing 89% at idle

[CasopoliS]

FYI I was able to log a 2 hour trip. I know someone said it died on them after some period of time. It looks like it produced 2 files, so there must but a max file size or mas time stamp. I have not had a chance to look at the files, but anyway... it worked. Full 2.25 hours logged

[cboles]

Feeling better today. I just posted a new version of EcuFlash / firmware at the head of this thread. Read the release notes in that post - it has a couple of new interesting features. I'm going to post a little more detail about the EcuFlash side in the patching thread in this beta subforum.

Don't die on us Colby
Forget the firmware for now

I have some fixes for the OP2 logging firmware and a new version of EcuFlash that does easy patching of your ROMs for better logging, but it needs some more testing, and I now have the flu, so I may not have anything until Monday. Hang tight!

Colby

[altaic]

If you can plug in a OP2 with a SD inserted and the drive shows up, then yes, it has been fixed...

I just tried it on 10.6.1-- it worked!

Is the serial port there as well? If you open it an send "ati\r\n" (where \r and \n are CR LF) do you get anything back?

Ah, I should have checked that... they are not simultaneously available. If the SD card is inserted before the OP2 is connected, it shows up as a drive, but not a communications device; if the SD card is not inserted before connecting, it appears as a communications device, but not a drive. It's odd, however: USB Prober indicates that all the interfaces are present and useable in both situations.

Edit: Apologies; that's not entirely correct. USB Prober shows all interfaces when the OP2 is plugged with an SD card already inserted. If it's connected without the SD card, USB Prober doesn't show the mass storage interface (even if an SD card is inserted after the OP2 has been connected). I did notice one interesting thing, though: the product ID is different between the two situations (w/mass storage it's 0xCC4C; w/o mass storage it's 0xCC4D).

[ladams00]

Here's another piece for possibly spurious or offset values for lc-1 AFR (I currently am having more faith in lambda...but still nothing Excel cant multiply by 14.7 ):

Code: Select all

sample   time   RPM   inno.afr   inno.lambda                                                   

5059.0000   511.8852   3773.5000   4.3071   0.8790
5061.0000   512.0852   3427.2500   4.7873   0.9770
5063.0000   512.2852   3086.5000   6.1740   1.2600
5065.0000   512.4852   2767.7500   8.3300   1.7000
5067.0000   512.6852   2494.7500   10.3684   2.1160
5069.0000   512.8852   2204.7500   13.3721   2.7290
5071.0000   513.0852   1924.7500   19.2423   3.9270
5073.0000   513.2852   1657.5000   24.0835   4.9150
5075.0000   513.4852   1407.2500   25.9798   5.3020
5077.0000   513.6852   1230.2500   25.9798   5.3020
5079.0000   513.8852   1061.2500   21.5159   4.3910
5081.0000   514.0852   1025.7500   12.6959   2.5910
5083.0000   514.2852   1027.2500   7.4627   1.5230
5085.0000   514.4852   1053.7500   5.8408   1.1920
5087.0000   514.6852   1039.5000   5.7820   1.1800
5089.0000   514.8852   1043.0000   4.6060   0.9400
5091.0000   515.0852   1006.7500   4.7285   0.9650



Colby if you need the FM version of my LC-1, I can grab that.

[mdedwar]

Here's another piece for possibly spurious or offset values for lc-1 AFR (I currently am having more faith in lambda...but still nothing Excel cant multiply by 14.7 ):

Code: Select all

sample   time   RPM   inno.afr   inno.lambda                                                   

5059.0000   511.8852   3773.5000   4.3071   0.8790
5061.0000   512.0852   3427.2500   4.7873   0.9770
5063.0000   512.2852   3086.5000   6.1740   1.2600
5065.0000   512.4852   2767.7500   8.3300   1.7000
5067.0000   512.6852   2494.7500   10.3684   2.1160
5069.0000   512.8852   2204.7500   13.3721   2.7290
5071.0000   513.0852   1924.7500   19.2423   3.9270
5073.0000   513.2852   1657.5000   24.0835   4.9150
5075.0000   513.4852   1407.2500   25.9798   5.3020
5077.0000   513.6852   1230.2500   25.9798   5.3020
5079.0000   513.8852   1061.2500   21.5159   4.3910
5081.0000   514.0852   1025.7500   12.6959   2.5910
5083.0000   514.2852   1027.2500   7.4627   1.5230
5085.0000   514.4852   1053.7500   5.8408   1.1920
5087.0000   514.6852   1039.5000   5.7820   1.1800
5089.0000   514.8852   1043.0000   4.6060   0.9400
5091.0000   515.0852   1006.7500   4.7285   0.9650



Colby if you need the FM version of my LC-1, I can grab that.

This looks like the problem I have.

This did work for me under an older version.

[ladams00]

Here's another piece for possibly spurious or offset values for lc-1 AFR (I currently am having more faith in lambda...but still nothing Excel cant multiply by 14.7 ):

Code: Select all

sample   time   RPM   inno.afr   inno.lambda                                                   

5059.0000   511.8852   3773.5000   4.3071   0.8790
5061.0000   512.0852   3427.2500   4.7873   0.9770
5063.0000   512.2852   3086.5000   6.1740   1.2600
5065.0000   512.4852   2767.7500   8.3300   1.7000
5067.0000   512.6852   2494.7500   10.3684   2.1160
5069.0000   512.8852   2204.7500   13.3721   2.7290
5071.0000   513.0852   1924.7500   19.2423   3.9270
5073.0000   513.2852   1657.5000   24.0835   4.9150
5075.0000   513.4852   1407.2500   25.9798   5.3020
5077.0000   513.6852   1230.2500   25.9798   5.3020
5079.0000   513.8852   1061.2500   21.5159   4.3910
5081.0000   514.0852   1025.7500   12.6959   2.5910
5083.0000   514.2852   1027.2500   7.4627   1.5230
5085.0000   514.4852   1053.7500   5.8408   1.1920
5087.0000   514.6852   1039.5000   5.7820   1.1800
5089.0000   514.8852   1043.0000   4.6060   0.9400
5091.0000   515.0852   1006.7500   4.7285   0.9650



Colby if you need the FM version of my LC-1, I can grab that.

This looks like the problem I have.

This did work for me under an older version.

Agreed LC-1 AFR's logged accurately in an earlier version. I however no longer have the logs to confirm.

[legaulois]

the firmware 1.10.2721 no work to adresses type : 0xFF6A10 on a STI EDM

[cboles]

the firmware 1.10.2721 no work to adresses type : 0xFF6A10 on a STI EDM

CAN or K-line? If CAN, have you applied the patch?

[legaulois]

the firmware 1.10.2721 no work to adresses type : 0xFF6A10 on a STI EDM

CAN or K-line? If CAN, have you applied the patch?

Can, where is the patch?

Thank

[cboles]

the firmware 1.10.2721 no work to adresses type : 0xFF6A10 on a STI EDM

CAN or K-line? If CAN, have you applied the patch?

Can, where is the patch?

Thank

Read my other post in this subforum about the ROM patching. Basically you load your ROM into the new beta of ECU flash and there is an option to patch it and then your flash that back to your car.

[cboles]

I'm looking into it, but I've had a couple of sensor failures on the bench... Keep in mind that the OP2 cacluates the AFR based on the AFR multiplier that the LC-1 provides. If you go into the LC-1 configuration tool and find that this is not set to 14.7 (or whatever is right for your fuel) - then this is the reason your AFRs are bad. I have seen the LC-1 loose this information before - I'm not sure why it does it. You could always make a calculated parameter that does the multiply, or I could make a hard-wired inno.afr147 parameter as well.

Here's another piece for possibly spurious or offset values for lc-1 AFR (I currently am having more faith in lambda...but still nothing Excel cant multiply by 14.7 ):

Code: Select all

sample   time   RPM   inno.afr   inno.lambda                                                   

5059.0000   511.8852   3773.5000   4.3071   0.8790
5061.0000   512.0852   3427.2500   4.7873   0.9770
5063.0000   512.2852   3086.5000   6.1740   1.2600
5065.0000   512.4852   2767.7500   8.3300   1.7000
5067.0000   512.6852   2494.7500   10.3684   2.1160
5069.0000   512.8852   2204.7500   13.3721   2.7290
5071.0000   513.0852   1924.7500   19.2423   3.9270
5073.0000   513.2852   1657.5000   24.0835   4.9150
5075.0000   513.4852   1407.2500   25.9798   5.3020
5077.0000   513.6852   1230.2500   25.9798   5.3020
5079.0000   513.8852   1061.2500   21.5159   4.3910
5081.0000   514.0852   1025.7500   12.6959   2.5910
5083.0000   514.2852   1027.2500   7.4627   1.5230
5085.0000   514.4852   1053.7500   5.8408   1.1920
5087.0000   514.6852   1039.5000   5.7820   1.1800
5089.0000   514.8852   1043.0000   4.6060   0.9400
5091.0000   515.0852   1006.7500   4.7285   0.9650



Colby if you need the FM version of my LC-1, I can grab that.

This looks like the problem I have.

This did work for me under an older version.

Agreed LC-1 AFR's logged accurately in an earlier version. I however no longer have the logs to confirm.