Openport Stand-Alone Logging Beta

[mfb]

Yes. I may eventually make it log a bit faster too. The timing is somewhat conservative because I found that the ECU would occasionally not respond if you tried to go faster, so I picked a timing formula where I never saw any dropouts. If the ECU doesn't respond, the OP2 just uses the previous value, so it's not a big deal.

As is , its already very fast to what we have been accustomed to (RR) Its possible to make RR log via CAN right?

[cboles]

Yes. You can do the same via the PC with J2534. I am adding logging to EcuFlash. With the new driver, the latency is limited by the full speed USB frame timing to 1ms, which allows you to issue 1000 separate writes and reads per second. If the opportunity presented itself, the stand-alone logging could go faster, since it doesn't have the USB latency, but you might be limited by floating point calcs or sd write speed if you start talking about reading more than a couple thousand params/sec.

Yes. I may eventually make it log a bit faster too. The timing is somewhat conservative because I found that the ECU would occasionally not respond if you tried to go faster, so I picked a timing formula where I never saw any dropouts. If the ECU doesn't respond, the OP2 just uses the previous value, so it's not a big deal.

As is , its already very fast to what we have been accustomed to (RR) Its possible to make RR log via CAN right?

[Digitalfiend]

Hey Colby,

How far off do you think datalogging support in ECUFlash is? I only ask because I was considering writing my own CAN logger for those times when I need to actually see the data versus just using Tactrix in standalone mode. If your datalogger is only a couple weeks away, I might just wait. Do you have any beta versions to try?

[cboles]

I'm reluctant to put a number on it, but the graphing will definitely be more than a couple weeks out.

Hey Colby,

How far off do you think datalogging support in ECUFlash is? I only ask because I was considering writing my own CAN logger for those times when I need to actually see the data versus just using Tactrix in standalone mode. If your datalogger is only a couple weeks away, I might just wait. Do you have any beta versions to try?

[mfb]

I'm reluctant to put a number on it, but the graphing will definitely be more than a couple weeks out.

Hey Colby,

How far off do you think datalogging support in ECUFlash is? I only ask because I was considering writing my own CAN logger for those times when I need to actually see the data versus just using Tactrix in standalone mode. If your datalogger is only a couple weeks away, I might just wait. Do you have any beta versions to try?

Im assuming the graphing will just read off what is being logged by the microsd card right? Kinda like live graphing? If the pc will log instead of the microsd, it will be limited by what the usb can handle right?

[LM_logger]

if you see the cable in device manager under "vehicle interfaces" without any trouble icons, it should be OK. where is this copy of the J2534 DLL you are trying to get rid of? I am referring to ones in places other than the windows system directories, such as the evoscan exe directory.

Hi Colby,

Yes thats the dll i removed. That one was my fault lol, I was executing an old shortcut for the 2.6, doh, it was late and i was tired, note to self to not mess with computers or cars when like that

Evoscan is working again as before, everything fine there.

Got a new cable. When I run innomts.exe this output comes :

Code: Select all

J2534 error [no devices available].

Ecuflash is able to read ecu ok, evoscan works, but still no logs on SD card, no matter what I put in config (default mitsubishican.txt (renamed) or my own lightened version). I even tried with and without a condition on rpm but nothing logged.

Some details from Ecuflash:

Code: Select all

[13:09:14.151] EcuFlash Version 1.43.3000
[13:09:14.151] OS Version Windows Vista
[13:09:14.151] Qt Version 4.6.2

....

[13:09:28.869] J2534 API Version: 04.04
[13:09:28.869] J2534 DLL Version: 1.00.2997 (DEBUG) Mar 31 2010 18:34:34
[13:09:28.869] Device Firmware Version: 1.10.2996

Attached is a pic of what device manager shows

Cheers.

[cboles]

Are you running something else like EcuFlash or EvoScan while trying to run innomts.exe?
What does your logcfg.out say (delete the current one first to be sure that a new one is even being generated each time you plug it into the car).

if you see the cable in device manager under "vehicle interfaces" without any trouble icons, it should be OK. where is this copy of the J2534 DLL you are trying to get rid of? I am referring to ones in places other than the windows system directories, such as the evoscan exe directory.

Hi Colby,

Yes thats the dll i removed. That one was my fault lol, I was executing an old shortcut for the 2.6, doh, it was late and i was tired, note to self to not mess with computers or cars when like that

Evoscan is working again as before, everything fine there.

Got a new cable. When I run innomts.exe this output comes :

Code: Select all

J2534 error [no devices available].

Ecuflash is able to read ecu ok, evoscan works, but still no logs on SD card, no matter what I put in config (default mitsubishican.txt (renamed) or my own lightened version). I even tried with and without a condition on rpm but nothing logged.

Some details from Ecuflash:

Code: Select all

[13:09:14.151] EcuFlash Version 1.43.3000
[13:09:14.151] OS Version Windows Vista
[13:09:14.151] Qt Version 4.6.2

....

[13:09:28.869] J2534 API Version: 04.04
[13:09:28.869] J2534 DLL Version: 1.00.2997 (DEBUG) Mar 31 2010 18:34:34
[13:09:28.869] Device Firmware Version: 1.10.2996

Attached is a pic of what device manager shows

Cheers.

[LM_logger]

Are you running something else like EcuFlash or EvoScan while trying to run innomts.exe?
What does your logcfg.out say (delete the current one first to be sure that a new one is even being generated each time you plug it into the car).

Thats a definitive no You even had me doubting myself for a minute

Here's the last logcfg.txt and logcfg.out (all previous .cfg and .out were removed) with the standard mitsubishican.txt (renamed to logcfg.txt) with inno stuff added from subaru lc-1 example though using afr as the LM-1 doesn't seem to loose its multiplier, well it hasn't for me...yet. BTW i'm sure you realise i've added the .txt onto the .out so I can attach.

logcfg.out.txt

(4.94 KiB) Downloaded 617 times

logcfg.txt

(1009 Bytes) Downloaded 605 times

Edited to note: Forgot to add, still getting the "J2534 error [no devices available]." when running innomts.exe

[adamw2]

Hi all

I am about to apply the CAN logging memory read patch that colby developed to an ADM 09 WRX.
I'm pretty confident it's fine considering ECUFlash is finding the right binary strings and hence giving me the checkbox to perform the CAN patch to the ROM image.

Would just like to confirm that these changes look sane (done using FC /b "stock.hex" "stock with can patch.hex" in MS-DOS) before I flash it in. No other changes to the ROM other than the CAN patch.

Thanks
Adam

Code: Select all

Location Old Value New Value
000770EA: 6A 65
000770EB: E3 4D
000770EC: 65 E2
000770ED: 4D 03
000770EE: E2 35
000770EF: 03 27
000770F0: 35 8F
000770F1: 27 0F
000770F2: 8F 6B
000770F3: 0F E3
000770F4: 6B E2
000770F5: E3 FD
000770F6: E2 62
000770F7: FD 2C
000770F8: 62 35
000770F9: 2C 27
000770FA: 35 89
000770FB: 27 0A
000770FC: 89 A0
000770FD: 0A 02
000770FE: A0 66
000770FF: 02 43
00077100: 66 7E
00077101: 43 01
00077102: 7E 76
00077103: 01 FD
00077104: 76 60
00077105: FD 6D
00077106: 60 E1
00077107: 6D 03
00077108: E1 30
00077109: 03 17
0007710A: 30 89
0007710B: 17 F9
0007710C: 89 88
0007710D: F9 01
0007710E: 88 8B
0007710F: 01 00
00077110: 8B ED
00077112: ED E2
00077113: 00 FD
00077114: E2 62
00077115: FD 2C
00077116: 62 35
00077117: 2C 27
00077118: 35 8F
00077119: 27 02
0007711A: 8F 66
0007711B: 02 43
0007711C: 66 E6
0007711D: 43 FD
0007711E: E6 66
0007711F: FD 6C
00077120: 66 DC
00077121: 6C 38
00077122: DC 65
00077123: 38 C3
00077124: 65 75
00077125: C3 02
00077126: 75 D2
00077127: 02 38
00077128: D2 E4
00077129: 37 A8
0007712A: E4 42
0007712B: A8 0B
0007712C: 42 64
0007712D: 0B 4C
0007712E: 64 60
0007712F: 4C D3
00077130: 84 88
00077131: C2 01
00077132: 20 8B
00077133: 08 01
00077134: 8B A0
00077135: 32 33
00077136: 60 EB
00077137: D3 13
00077138: 88 ED
00077139: 01 00
0007713A: 8B 69
0007713B: 01 ED
0007713C: A0 98
0007713D: 2F 61
0007713E: EB 7C
0007713F: 13 03
00077140: ED DA
00077141: 00 33
00077142: 69 3D
00077143: ED 93
00077144: 98 89
00077145: 5D 2B
00077146: 66 61
00077147: DD C4
00077148: 36 60
00077149: 93 1E
0007714A: 89 41
0007714B: 25 18
0007714C: 60 62
0007714D: 63 C4
0007714E: 40 62
0007714F: 00 2C
00077150: 30 31
00077151: 6C 2C
00077152: 62 41
00077153: C3 18
00077154: 72 62
00077155: 02 C4
00077156: 72 62
00077157: 01 2C
00077158: 02 31
0007715A: 64 88
0007715B: 2C FF
0007715C: 44 E4
0007715D: 28 00
0007715E: 62 89
0007715F: C3 05
00077160: 72 88
00077161: 02 F4
00077162: 72 E4
00077163: 02 03
00077164: 02 89
00077165: 2C 02
00077166: 65 88
00077167: 2C F2
00077168: 45 E4
00077169: 18 01
0007716A: 35 8B
0007716B: 4C 0A
0007716C: 62 3E
0007716D: C3 4C
0007716E: 72 E0
0007716F: 02 0F
00077170: 72 40
00077171: 03 28
00077172: 02 21
00077173: 2C 0B
00077174: 61 60
00077175: 2C 14
00077176: 31 2A
00077177: 5C 00
00077178: 31 7A
00077179: 82 01
0007717A: 89 44
0007717B: 0C 15
0007717C: D5 74
0007717D: 23 FF
0007717E: 60 89
0007717F: 13 F9
00077180: 40 A0
00077181: 08 0A
00077182: 06 31
00077183: 5E 82
00077184: 46 89
00077185: 0B 0A
00077186: 64 D5
00077187: 1D 21
00077188: 62 60
00077189: 03 13
0007718A: D6 40
0007718B: 21 08
0007718C: 60 06
0007718D: DD 5E
0007718E: 06 46
0007718F: 24 0B
00077190: 70 64
00077191: 01 1D
00077192: AF 62
00077193: D8 03
00077194: 6D 2A
00077195: 03 20
00077196: EA 7A
00077198: 2A AF
00077199: A8 D3
0007719A: 89 7D
0007719B: 00 01
000FFB88: 05 7F
000FFB89: 0F 4A
000FFB8A: 1B 27
000FFB8B: A5 AE


[cboles]

This patch replaces an entire function, so if EcuFlash finds a match (which means the original function matched exactly), you can be pretty sure it is going to work.

Hi all

I am about to apply the CAN logging memory read patch that colby developed to an ADM 09 WRX.
I'm pretty confident it's fine considering ECUFlash is finding the right binary strings and hence giving me the checkbox to perform the CAN patch to the ROM image.

Would just like to confirm that these changes look sane (done using FC /b "stock.hex" "stock with can patch.hex" in MS-DOS) before I flash it in. No other changes to the ROM other than the CAN patch.

Thanks
Adam

Code: Select all

Location Old Value New Value
000770EA: 6A 65
000770EB: E3 4D
000770EC: 65 E2
000770ED: 4D 03
000770EE: E2 35
000770EF: 03 27
000770F0: 35 8F
000770F1: 27 0F
000770F2: 8F 6B
000770F3: 0F E3
000770F4: 6B E2
000770F5: E3 FD
000770F6: E2 62
000770F7: FD 2C
000770F8: 62 35
000770F9: 2C 27
000770FA: 35 89
000770FB: 27 0A
000770FC: 89 A0
000770FD: 0A 02
000770FE: A0 66
000770FF: 02 43
00077100: 66 7E
00077101: 43 01
00077102: 7E 76
00077103: 01 FD
00077104: 76 60
00077105: FD 6D
00077106: 60 E1
00077107: 6D 03
00077108: E1 30
00077109: 03 17
0007710A: 30 89
0007710B: 17 F9
0007710C: 89 88
0007710D: F9 01
0007710E: 88 8B
0007710F: 01 00
00077110: 8B ED
00077112: ED E2
00077113: 00 FD
00077114: E2 62
00077115: FD 2C
00077116: 62 35
00077117: 2C 27
00077118: 35 8F
00077119: 27 02
0007711A: 8F 66
0007711B: 02 43
0007711C: 66 E6
0007711D: 43 FD
0007711E: E6 66
0007711F: FD 6C
00077120: 66 DC
00077121: 6C 38
00077122: DC 65
00077123: 38 C3
00077124: 65 75
00077125: C3 02
00077126: 75 D2
00077127: 02 38
00077128: D2 E4
00077129: 37 A8
0007712A: E4 42
0007712B: A8 0B
0007712C: 42 64
0007712D: 0B 4C
0007712E: 64 60
0007712F: 4C D3
00077130: 84 88
00077131: C2 01
00077132: 20 8B
00077133: 08 01
00077134: 8B A0
00077135: 32 33
00077136: 60 EB
00077137: D3 13
00077138: 88 ED
00077139: 01 00
0007713A: 8B 69
0007713B: 01 ED
0007713C: A0 98
0007713D: 2F 61
0007713E: EB 7C
0007713F: 13 03
00077140: ED DA
00077141: 00 33
00077142: 69 3D
00077143: ED 93
00077144: 98 89
00077145: 5D 2B
00077146: 66 61
00077147: DD C4
00077148: 36 60
00077149: 93 1E
0007714A: 89 41
0007714B: 25 18
0007714C: 60 62
0007714D: 63 C4
0007714E: 40 62
0007714F: 00 2C
00077150: 30 31
00077151: 6C 2C
00077152: 62 41
00077153: C3 18
00077154: 72 62
00077155: 02 C4
00077156: 72 62
00077157: 01 2C
00077158: 02 31
0007715A: 64 88
0007715B: 2C FF
0007715C: 44 E4
0007715D: 28 00
0007715E: 62 89
0007715F: C3 05
00077160: 72 88
00077161: 02 F4
00077162: 72 E4
00077163: 02 03
00077164: 02 89
00077165: 2C 02
00077166: 65 88
00077167: 2C F2
00077168: 45 E4
00077169: 18 01
0007716A: 35 8B
0007716B: 4C 0A
0007716C: 62 3E
0007716D: C3 4C
0007716E: 72 E0
0007716F: 02 0F
00077170: 72 40
00077171: 03 28
00077172: 02 21
00077173: 2C 0B
00077174: 61 60
00077175: 2C 14
00077176: 31 2A
00077177: 5C 00
00077178: 31 7A
00077179: 82 01
0007717A: 89 44
0007717B: 0C 15
0007717C: D5 74
0007717D: 23 FF
0007717E: 60 89
0007717F: 13 F9
00077180: 40 A0
00077181: 08 0A
00077182: 06 31
00077183: 5E 82
00077184: 46 89
00077185: 0B 0A
00077186: 64 D5
00077187: 1D 21
00077188: 62 60
00077189: 03 13
0007718A: D6 40
0007718B: 21 08
0007718C: 60 06
0007718D: DD 5E
0007718E: 06 46
0007718F: 24 0B
00077190: 70 64
00077191: 01 1D
00077192: AF 62
00077193: D8 03
00077194: 6D 2A
00077195: 03 20
00077196: EA 7A
00077198: 2A AF
00077199: A8 D3
0007719A: 89 7D
0007719B: 00 01
000FFB88: 05 7F
000FFB89: 0F 4A
000FFB8A: 1B 27
000FFB8B: A5 AE


[mfb]

We have exclusively used OP2 CAN logging for my tune. After so many maps, we're at the final stages. Thanks to your work Colby! We wouldnt have seen the flck, fkc and various oscillations without the speed this is giving. We only got up to 25 samples per second due to the number of parameters we wanted to cover. Thats more than enough to get things dialed in. I hope your Ecuflash logger with live graphing will be out in beta soon. That would be useful for those tuning in the dyno.

[mfb]

Hi Colby,

Can you check on possibility that the external jack intermittently sending out a signal back to the lc-1? This is my third time to experience getting an error on my afr reading that makes me do another recalibration. When this happens, I see the blue light go on longer a bit before it starts blinking for can. At this time, I know that AFR already needs recalibration. Im thinking that I need to enable the logger first (one then off) prior to inserting and logging with the lc1.

Also, there was an instance before that I wasnt able to log even after I pressed the defogger to on. Observing it, there's a long blue led light when I press the defogger switch for the first time before it starts to blink. When I turn it off and later turn it on again, this no longer occurs. Not sure if its connected to what Im experiencing.

[LM_logger]

Hi Colby,

Sent that file (innomts.exe) to a few others for testing
See if they are getting the same results as me.

Any more deliberations on having the LM-1 supported to date?

[cboles]

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

Hi Colby,

Can you check on possibility that the external jack intermittently sending out a signal back to the lc-1? This is my third time to experience getting an error on my afr reading that makes me do another recalibration. When this happens, I see the blue light go on longer a bit before it starts blinking for can. At this time, I know that AFR already needs recalibration. Im thinking that I need to enable the logger first (one then off) prior to inserting and logging with the lc1.

Also, there was an instance before that I wasnt able to log even after I pressed the defogger to on. Observing it, there's a long blue led light when I press the defogger switch for the first time before it starts to blink. When I turn it off and later turn it on again, this no longer occurs. Not sure if its connected to what Im experiencing.

[cboles]

If someone can loan me a LM-1, I can get it working.

Hi Colby,

Sent that file (innomts.exe) to a few others for testing
See if they are getting the same results as me.

Any more deliberations on having the LM-1 supported to date?