Openport Stand-Alone Logging Beta

[freakin]

cboles, can you confirm the max length of a parameter please so i can prevent my app from making long strings

Code: Select all

log parameter name too long at line 2

[paul_p1]

Hi, this seems to work for me when I first initiate the logging, i.e the first log file is complete, any subsequent files created are empty but have a file size greater than 0K, i.e 25K or 50K etc. When you try to open them Excel complains that they're not in a recognisable format. Has anyone else seen this issue?

[mohammadov]

Can anyone plz tell me why inno.afr numbers be like this?????i read before about LM Programmer,but i couldnt found it,what i installed in my laptop is Logwork2.0 and logworks 3.0 and i couldnt found something called LM Programmer.
PS:I have lc-1.

Code: Select all

RPM      Ignition   Throttle   Mass      KC        FLKC            inno.afr
697      10.5      0      1.2      0      0                       5.1548
687.5   11.5      0      1.22      0      0                      5.1695
716      9      0      1.2      0      0                      5.1695
718.75   9      0      1.22      0      0                         5.1891
727.5   8.5      0      1.22      0      0                      5.194
729.5   9      0      1.2      0      0                          5.2283
727.25   9.5      0      1.24      0      0                      5.2185
730.25   9.5      0      1.22      0      0                      5.2283
738.25   9.5      0      1.22      0      0                      5.2087
721.25   11.5      0      1.24      0      0                      5.1646
724.5   11      0      1.2      0      0                      5.1989
725.75   11      0      1.2      0      0                      5.1352
717      12      0      1.2      0      0                       5.1352
706.25   13      0      1.22      0      0                      5.0764
703.25   13      0      1.2      0      0                      5.0666
677.25   15.5      0      1.22      0      0                      5.0666


THANX

[cboles]

The stoichiometric AFR value that inno.lambda is multiplied by that comes from your LC-1 is incorrect. For some reason, the LC-1 seems to lose this value sometimes. Solutions are:

1) Fix the value with the LC-1 tool
2) Create a calulated AFR parameter that is basically inno.lambda * AFRstoich, e.g. inno.lambda,14.7,*
3) I will be adding a new inno.afr147 parameter to the next release which is basically inno.lambda * 14.7

Can anyone plz tell me why inno.afr numbers be like this?????i read before about LM Programmer,but i couldnt found it,what i installed in my laptop is Logwork2.0 and logworks 3.0 and i couldnt found something called LM Programmer.
PS:I have lc-1.

Code: Select all

RPM      Ignition   Throttle   Mass      KC        FLKC            inno.afr
697      10.5      0      1.2      0      0                       5.1548
687.5   11.5      0      1.22      0      0                      5.1695
716      9      0      1.2      0      0                      5.1695
718.75   9      0      1.22      0      0                         5.1891
727.5   8.5      0      1.22      0      0                      5.194
729.5   9      0      1.2      0      0                          5.2283
727.25   9.5      0      1.24      0      0                      5.2185
730.25   9.5      0      1.22      0      0                      5.2283
738.25   9.5      0      1.22      0      0                      5.2087
721.25   11.5      0      1.24      0      0                      5.1646
724.5   11      0      1.2      0      0                      5.1989
725.75   11      0      1.2      0      0                      5.1352
717      12      0      1.2      0      0                       5.1352
706.25   13      0      1.22      0      0                      5.0764
703.25   13      0      1.2      0      0                      5.0666
677.25   15.5      0      1.22      0      0                      5.0666


THANX

[cboles]

Hi, this seems to work for me when I first initiate the logging, i.e the first log file is complete, any subsequent files created are empty but have a file size greater than 0K, i.e 25K or 50K etc. When you try to open them Excel complains that they're not in a recognisable format. Has anyone else seen this issue?

Could you post your logcfg.txt and a couple of the bad files?

[mohammadov]

Thanx a lot cboles,i will try it and feedback.

The stoichiometric AFR value that inno.lambda is multiplied by that comes from your LC-1 is incorrect. For some reason, the LC-1 seems to lose this value sometimes. Solutions are:

1) Fix the value with the LC-1 tool
2) Create a calulated AFR parameter that is basically inno.lambda * AFRstoich, e.g. inno.lambda,14.7,*
3) I will be adding a new inno.afr147 parameter to the next release which is basically inno.lambda * 14.7

Can anyone plz tell me why inno.afr numbers be like this?????i read before about LM Programmer,but i couldnt found it,what i installed in my laptop is Logwork2.0 and logworks 3.0 and i couldnt found something called LM Programmer.
PS:I have lc-1.

Code: Select all

RPM      Ignition   Throttle   Mass      KC        FLKC            inno.afr
697      10.5      0      1.2      0      0                       5.1548
687.5   11.5      0      1.22      0      0                      5.1695
716      9      0      1.2      0      0                      5.1695
718.75   9      0      1.22      0      0                         5.1891
727.5   8.5      0      1.22      0      0                      5.194
729.5   9      0      1.2      0      0                          5.2283
727.25   9.5      0      1.24      0      0                      5.2185
730.25   9.5      0      1.22      0      0                      5.2283
738.25   9.5      0      1.22      0      0                      5.2087
721.25   11.5      0      1.24      0      0                      5.1646
724.5   11      0      1.2      0      0                      5.1989
725.75   11      0      1.2      0      0                      5.1352
717      12      0      1.2      0      0                       5.1352
706.25   13      0      1.22      0      0                      5.0764
703.25   13      0      1.2      0      0                      5.0666
677.25   15.5      0      1.22      0      0                      5.0666


THANX

[freakin]

Colby, any idea why this is happening

[A/F_Sensor_#1_(Direct)*(AFR),0,0.000000]
is too long

yet above on line 54 is longer but seems to pass

[Manifold_Absolute_Pressure_(Direct)*(psi_absolute),0,0.000000]

54: paramname = Manifold_Absolute_Pressure_(Direct)*(psi_absolute)
: name[paramname,16] value[Manifold_Absolute_Pressure_(Direct)*(psi_absolute),0,0.000000]
55: paramid = 0x2186A
: name[paramid,17] value[0x2186A,137322,0.000000]
56: databits = 16
: name[databits,22] value[16,16,16.000000]
57: scalingrpn = x,0.01933677,*
: name[scalingrpn,18] value[x,0.01933677,*,0,0.000000]
58: paramname = A/F_Sensor_#1_(Direct)*(AFR)
: name[paramname,16] value[A/F_Sensor_#1_(Direct)*(AFR),0,0.000000]
log parameter name too long at line 58

[cboles]

because you have really long parameter names

i made a single store for strings so that there is not really a limit on the string size for a single parameter, but you have an overall limit on the total size of all of these strings that you are running up against. better to keep them short...

Colby, any idea why this is happening

[A/F_Sensor_#1_(Direct)*(AFR),0,0.000000]
is too long

yet above on line 54 is longer but seems to pass

[Manifold_Absolute_Pressure_(Direct)*(psi_absolute),0,0.000000]

54: paramname = Manifold_Absolute_Pressure_(Direct)*(psi_absolute)
: name[paramname,16] value[Manifold_Absolute_Pressure_(Direct)*(psi_absolute),0,0.000000]
55: paramid = 0x2186A
: name[paramid,17] value[0x2186A,137322,0.000000]
56: databits = 16
: name[databits,22] value[16,16,16.000000]
57: scalingrpn = x,0.01933677,*
: name[scalingrpn,18] value[x,0.01933677,*,0,0.000000]
58: paramname = A/F_Sensor_#1_(Direct)*(AFR)
: name[paramname,16] value[A/F_Sensor_#1_(Direct)*(AFR),0,0.000000]
log parameter name too long at line 58

[chaeoz]

Still no luck.

Testing with another OP2.0 and the values are still 0, so I'm guessing that the cable is flaky. Tried jiggling, etc... Not much help.

Problem is, the innovate connector is pretty painful. Self fabricated plugs do not fit, as it is a slight rubber protrusion.

I may have to order a proper MTS cable, no?

One thing to watch out for is that I have found that the Innovate 2.5mm connectors can be a bit flaky on the Innovate side - try jiggling them a bit just in case.

LC-1 logging configuration is definitely set up correctly, there is a column inside the log file with the header, inno.afr, but the values are all 0.

I have tested my 2.5mm <-> 2.5mm cable with a multimeter, the connection is fine.

LC-1 logging is definitely okay, I've been logging with a laptop and it is fine. Now, I want to get my hands on another OP2.0 to ensure that it is not a OP2.0 problem.

[mohammadov]

I never found 2.5mm to 2.5 mm cable,so i bought conversion connectors from 3.5 to 2.5 and about 3.5<-->3.5 cable which i found,
Now i faced a problem of the innovate OUT cable,which has rubber and the hole is too small,i cut some of that innvoate cable rubber,and inserted my fabricated cable,and it start reading.

Still no luck.

Testing with another OP2.0 and the values are still 0, so I'm guessing that the cable is flaky. Tried jiggling, etc... Not much help.

Problem is, the innovate connector is pretty painful. Self fabricated plugs do not fit, as it is a slight rubber protrusion.

I may have to order a proper MTS cable, no?

One thing to watch out for is that I have found that the Innovate 2.5mm connectors can be a bit flaky on the Innovate side - try jiggling them a bit just in case.

LC-1 logging configuration is definitely set up correctly, there is a column inside the log file with the header, inno.afr, but the values are all 0.

I have tested my 2.5mm <-> 2.5mm cable with a multimeter, the connection is fine.

LC-1 logging is definitely okay, I've been logging with a laptop and it is fine. Now, I want to get my hands on another OP2.0 to ensure that it is not a OP2.0 problem.

[Paul R]

Just thought I'd update the thread with some findings after using it for a few days, logging works great on an Evo VI with the pin 1 to ground config setting, the speed calc might be out slightly though which shows a max of 55mph but was checked on GPS at 75mph (speedo was showing just under 80mph).

One side-affect is the central locking toggles about 2 seconds after switching the ignition off, could very well be the alarm, no idea.

Thank you

[cboles]

glad to hear it!

Just thought I'd update the thread with some findings after using it for a few days, logging works great on an Evo VI with the pin 1 to ground config setting, the speed calc might be out slightly though which shows a max of 55mph but was checked on GPS at 75mph (speedo was showing just under 80mph).

One side-affect is the central locking toggles about 2 seconds after switching the ignition off, could very well be the alarm, no idea.

Thank you

[mshoemaker]

I just put the suburu-can.txt file out of the logging sample directory on my OP2, renamed to logcfg.txt, and tried it out this morning and I get the same result. I do not get any flashing lights, and all I get on the memory card is an empty logcfg.out file. I have not tried setting it to use k-line logging, but I will try that this evening. Any other suggestions?

Thanks
Matthew

I just applied the patch to my 09 WRX to enable the RAM parameter logging, but now when I connect my OP2 and start the car I get nothing but an empty logcfg.out file. I think the logcfg file worked previously doing k-line logging, and all I did was change the type at the top of the file back. I could be wrong however because it has been about a month since I last tried the stand alone logging. I am at work currently and can not check my file or verify anything, but thought I would ask if anyone has ideas where I should look first.

Thanks
Matthew

[cboles]

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.

I just put the suburu-can.txt file out of the logging sample directory on my OP2, renamed to logcfg.txt, and tried it out this morning and I get the same result. I do not get any flashing lights, and all I get on the memory card is an empty logcfg.out file. I have not tried setting it to use k-line logging, but I will try that this evening. Any other suggestions?

Thanks
Matthew

I just applied the patch to my 09 WRX to enable the RAM parameter logging, but now when I connect my OP2 and start the car I get nothing but an empty logcfg.out file. I think the logcfg file worked previously doing k-line logging, and all I did was change the type at the top of the file back. I could be wrong however because it has been about a month since I last tried the stand alone logging. I am at work currently and can not check my file or verify anything, but thought I would ask if anyone has ideas where I should look first.

Thanks
Matthew

[mshoemaker]

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.