Openport Stand-Alone Logging Beta

[cboles]

I hear you on the OSX library. My dev Mac kicked the bucket a couple of weeks back and I need to fix the power supply to get back to that machine. I should be set up for a pretty quick port of op20pt32.dll though. The only big issue on OSX at the moment is that there is some goofiness with USB composite devices that have communication device class (CDC) devices as one of the devices. This means that you can't have the SD card plugged in and have the OP2 work on a Mac right now. I have someone at Apple that has already made a fix to their CDC driver, but it never seems to make it into any of their releases.

...and yes, you can operate all physical buses on the OP2 simultaneously. You can even tee CAN and ISO15765 data and analyze it via both protocols as well.

It's entirely *possible* to do, it's just a very low priority for me considering all of the other things I need to be doing, including the logging GUI features of EcuFlash. I have already written a sample CAN logger for the PC in the DLL distribution which works well - In fact I use it quite often. I think yours is a pretty execptional case where you are trying to CAN log without someone knowing. In all other cases, it is preferrable to have a laptop in front of you to be sure you are getting the data you want. Make friends with a service dept. and they will let you log while they do the work...

I know the service dept. pretty well, and they are cool with me, but I'd feel like I was imposing if I asked to log their session. Plus, they might be worried about damaging their SSM3/laptop/whatever by connecting it in parallel with an unknown device. I know it would be fine, but it seems like it's asking a lot.

Do you know if your CAN logger in the DLL distribution compiles on mac os x, or does it require the windows library? EDIT: After looking at it, it seems that it is dependent on the windows dll after all. At this point, I'd like to make my request for either the ability to sniff/dump to the microsd card, or mac os x support for the J2534 library.

Also, is it possible to dump both the CAN bus and K Line simultaneously? I don't know which they use for TPMS setup.

Thanks,
Will

[mdedwar]

Hi Colby,

On my setup I find that I have to remove the SD card to allow for programs like ECUflash and RomRaider to talk to the ECU.
Is this supposed to be the case or should I be able to leave the SD card in and still connect with these programs?

Cheers,
Matt.

[Tephra]

^ leaving the SD card in works for me.

[mdedwar]

^ leaving the SD card in works for me.

It occasionally worked for me under a previous version but no luck under the latest release.

[cboles]

^ leaving the SD card in works for me.

It occasionally worked for me under a previous version but no luck under the latest release.

Interesting. It has always worked for me either way long before I ever released the OP2. What OS are you using? If it is XP, what is the version information on usbser.sys and usbccgp.sys? There were many problems with the early versions of both of those MS drivers, but EcuFlash should update them during install.

Colby

[mdedwar]

^ leaving the SD card in works for me.

It occasionally worked for me under a previous version but no luck under the latest release.

Interesting. It has always worked for me either way long before I ever released the OP2. What OS are you using? If it is XP, what is the version information on usbser.sys and usbccgp.sys? There were many problems with the early versions of both of those MS drivers, but EcuFlash should update them during install.

Colby

Hi Colby,

OS is win xp service pack 3 with usb version:
usbser.sys 5.1.2600.5512
usbccgp.sys 5.1.2600.5508

I'm using a usb to serial device for my lc-1 so it may be causing the problems or one of those great xp features.

[bydant]

]I have been using the standalone logging for the last month or so, and its a fantastic tool!

The car I am using it on is a MY01 ADM Forester GT (ECU ID: 2354500405 Internal ID: A4SE700F).

In the last couple of days I have decided to add my LC-1 to the logging but this has yielded some strange results:

Code: Select all

sample   time   RPM   FuelBase   Load   FLKC   FBKC   CLOL   AF1   inno.afr
1948   403.09381   3742.25   10.81767876   1.862548828   0   0   36   11.2546875   4
1949   403.29381   3877.75   10.60803383   2.047180176   0   0   36   11.2546875   4
1955   404.49381   12511.25   0.917909629   1.531494141   -18.6328125   4.921875   16   21.01640625   140
1956   404.69381   1952   0.917909629   1.531494141   -17.578125   32.34375   16   3.10078125   129
1957   404.89381   7520   0.917881643   1.531494141   -17.578125   32.34375   12   9.1875   17
1958   405.09381   13792   0.917881643   1.718994141   -17.2265625   39.0234375   14   0   16


In this snippet of the log you can see that at sample 1949 all is ok, then 5 samples are dropped, and everything comes back all screwed up.

Here is the complete log:

log0001.csv

No conversion is done here. I do all conversions in excel

(327.49 KiB) Downloaded 1008 times

Here is the CSV with conversions:

Log0001.Converted.csv

Converted data

(505.43 KiB) Downloaded 929 times

Here is the output file:

logcfg.out.txt

out file

(3.67 KiB) Downloaded 967 times

Here is the Config file (all parameters are output as x without conversion):

logcfg.txt

Config file

(625 Bytes) Downloaded 994 times

This was never an issue until I hooked up the LC-1. I even had a log where I had the parameter added but didn't have the LC-1 plugged into the tactrix unit and all was fine over a 40 minute drive.

If any more information is required I am happy to provide.

[cboles]

I will take a look at it. I know there is a bug currently where the sample count will increase by more than one per interval due to the additional LC-1 data, but that bug is minor and should not affect the actual data nor the timestamps and sampling. Unfortunately I don't have a LC-1 installed in my 2008 STi at the moment, so I am not getting a lot of real world testing here on this feature.

]I have been using the standalone logging for the last month or so, and its a fantastic tool!

The car I am using it on is a MY01 ADM Forester GT (ECU ID: 2354500405 Internal ID: A4SE700F).

In the last couple of days I have decided to add my LC-1 to the logging but this has yielded some strange results:

Code: Select all

sample   time   RPM   FuelBase   Load   FLKC   FBKC   CLOL   AF1   inno.afr
1948   403.09381   3742.25   10.81767876   1.862548828   0   0   36   11.2546875   4
1949   403.29381   3877.75   10.60803383   2.047180176   0   0   36   11.2546875   4
1955   404.49381   12511.25   0.917909629   1.531494141   -18.6328125   4.921875   16   21.01640625   140
1956   404.69381   1952   0.917909629   1.531494141   -17.578125   32.34375   16   3.10078125   129
1957   404.89381   7520   0.917881643   1.531494141   -17.578125   32.34375   12   9.1875   17
1958   405.09381   13792   0.917881643   1.718994141   -17.2265625   39.0234375   14   0   16


In this snippet of the log you can see that at sample 1949 all is ok, then 5 samples are dropped, and everything comes back all screwed up.

Here is the complete log:

log0001.csv

Here is the CSV with conversions:

Log0001.Converted.csv

Here is the output file:

logcfg.out.txt

Here is the Config file (all parameters are output as x without conversion):

logcfg.txt

This was never an issue until I hooked up the LC-1. I even had a log where I had the parameter added but didn't have the LC-1 plugged into the tactrix unit and all was fine over a 40 minute drive.

If any more information is required I am happy to provide.

[bydant]

I am happy to help out if LC-1s are in demand.

[cboles]

5512 is the correct build for XPSP3. I am not sure why your usbccgp.sys is not 5512. I checked my copy of usbccgp.sys on XPSP3 and it is 5512. When you have the OP2 plugged in, does your system show and additional COM port in device manager? Keep in mind that the OP2 uses a different PID when you plug it in with a SD card, so you have to go through a second driver installation cycle for this configuration. It is possible that you have a good driver install for the cardless OP2 config, but not the carded one.

Hi Colby,

OS is win xp service pack 3 with usb version:
usbser.sys 5.1.2600.5512
usbccgp.sys 5.1.2600.5508

I'm using a usb to serial device for my lc-1 so it may be causing the problems or one of those great xp features.

[mdedwar]

Since using the stand alone logging I have had to recalibrate the LC-1 twice as the LC-1 started showing weird values even through the logworks software. Not sure if this is a problem with pluging it in to the tactrix cable and it randomly reseting the LC-1 or some other problem with the LC-1 (eg lose wire somewhere). However when it is calibrated it has worked fine.

Cheers,
Matt.

[mdedwar]

5512 is the correct build for XPSP3. I am not sure why your usbccgp.sys is not 5512. I checked my copy of usbccgp.sys on XPSP3 and it is 5512. When you have the OP2 plugged in, does your system show and additional COM port in device manager? Keep in mind that the OP2 uses a different PID when you plug it in with a SD card, so you have to go through a second driver installation cycle for this configuration. It is possible that you have a good driver install for the cardless OP2 config, but not the carded one.

Hi Colby,

OS is win xp service pack 3 with usb version:
usbser.sys 5.1.2600.5512
usbccgp.sys 5.1.2600.5508

I'm using a usb to serial device for my lc-1 so it may be causing the problems or one of those great xp features.

I'll try and update usbccgp.sys to 5512 as it may be a driver conflict.

[mdedwar]

5512 is the correct build for XPSP3. I am not sure why your usbccgp.sys is not 5512. I checked my copy of usbccgp.sys on XPSP3 and it is 5512. When you have the OP2 plugged in, does your system show and additional COM port in device manager? Keep in mind that the OP2 uses a different PID when you plug it in with a SD card, so you have to go through a second driver installation cycle for this configuration. It is possible that you have a good driver install for the cardless OP2 config, but not the carded one.

Hi Colby,

OS is win xp service pack 3 with usb version:
usbser.sys 5.1.2600.5512
usbccgp.sys 5.1.2600.5508

I'm using a usb to serial device for my lc-1 so it may be causing the problems or one of those great xp features.

I'll try and update usbccgp.sys to 5512 as it may be a driver conflict.

I updated usbccgp to 5512 and now it works as it should. Thanks for pointing me in the right direction.

Cheers,
Matt.

[dolphin]

Finally I made a progress I'm getting logcfg.out file and many *.cdv files, but what is wrong with them? Why data is so ruined? Check out RPM, TPS, SPEED

log0005.csv

csv files, check out my data

(36.35 KiB) Downloaded 922 times

OUT file log is below:

Code: Select all

01: type=mut2
  : name[type,8] value[mut2,0,0.000000]
02: baud=62500
  : name[baud,10] value[62500,62500,62500.000000]
03: paramname=RPM
  : name[paramname,16] value[RPM,0,0.000000]
04: paramid=0x21
  : name[paramid,17] value[0x21,33,0.000000]
05: scalingrpn=x,31.25,*            
  : name[scalingrpn,18] value[x,31.25,*,0,0.000000]
06: paramname=TPS
  : name[paramname,16] value[TPS,0,0.000000]
07: paramid=0x17
  : name[paramid,17] value[0x17,23,0.000000]
08: scalingrpn=x,0.39215686,*
  : name[scalingrpn,18] value[x,0.39215686,*,0,0.000000]
09: paramname=ECULoad
  : name[paramname,16] value[ECULoad,0,0.000000]
10: paramid=0x1C
  : name[paramid,17] value[0x1C,28,0.000000]
11: scalingrpn=x,0.625,*
  : name[scalingrpn,18] value[x,0.625,*,0,0.000000]
12: paramname=KnockSum
  : name[paramname,16] value[KnockSum,0,0.000000]
13: paramid=0x26
  : name[paramid,17] value[0x26,38,0.000000]
14: priority=2
  : name[priority,19] value[2,2,2.000000]
15: paramname=Speed
  : name[paramname,16] value[Speed,0,0.000000]
16: paramid=0x2F
  : name[paramid,17] value[0x2F,47,0.000000]
17: scalingrpn=x,1.242742384,*
  : name[scalingrpn,18] value[x,1.242742384,*,0,0.000000]
18: paramname=Knock
  : name[paramname,16] value[Knock,0,0.000000]
19: paramid=0x30
  : name[paramid,17] value[0x30,48,0.000000]
20: paramname=AirTemp
  : name[paramname,16] value[AirTemp,0,0.000000]
21: paramid=0x3A
  : name[paramid,17] value[0x3A,58,0.000000]
22: priority=2
  : name[priority,19] value[2,2,2.000000]
23: conditionrpn=RPM,1800,>
  : name[conditionrpn,48] value[RPM,1800,>,0,0.000000]
24: action=start
  : name[action,49] value[start,0,0.000000]
25: conditionrpn=RPM,1800,<
  : name[conditionrpn,48] value[RPM,1800,<,0,0.000000]
26: action=stop
  : name[action,49] value[stop,0,0.000000]

--- log config dump ---


channel type: mut2
protocol id: 3
baud: 62500

param name: RPM
param id: 0x00000021
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,31.250000,*

param name: TPS
param id: 0x00000017
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,0.392157,*

param name: ECULoad
param id: 0x0000001C
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,0.625000,*

param name: KnockSum
param id: 0x00000026
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 1
scaling: x

param name: Speed
param id: 0x0000002F
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,1.242742,*

param name: Knock
param id: 0x00000030
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x

param name: AirTemp
param id: 0x0000003A
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 1
scaling: x

trigger action: start condition: RPM,1800.000000,>
trigger action: stop condition: RPM,1800.000000,<

--- storage info ---
log stringlist: 71 chars
log floatlist: 5 floats
logging interval will be 50000us


[cboles]

I haven't tested 62500 baud here. There may be a problem with the response bytes being considered part of the request because they come back very close in time to the request. What ECU is this Evo 7/8/9? I'll try patching the ROM for 62500 and check it out. Have your tried 15625 baud (standard)? Does that work?

Finally I made a progress I'm getting logcfg.out file and many *.cdv files, but what is wrong with them? Why data is so ruined? Check out RPM, TPS, SPEED

log0005.csv

OUT file log is below:

Code: Select all

01: type=mut2
  : name[type,8] value[mut2,0,0.000000]
02: baud=62500
  : name[baud,10] value[62500,62500,62500.000000]
03: paramname=RPM
  : name[paramname,16] value[RPM,0,0.000000]
04: paramid=0x21
  : name[paramid,17] value[0x21,33,0.000000]
05: scalingrpn=x,31.25,*            
  : name[scalingrpn,18] value[x,31.25,*,0,0.000000]
06: paramname=TPS
  : name[paramname,16] value[TPS,0,0.000000]
07: paramid=0x17
  : name[paramid,17] value[0x17,23,0.000000]
08: scalingrpn=x,0.39215686,*
  : name[scalingrpn,18] value[x,0.39215686,*,0,0.000000]
09: paramname=ECULoad
  : name[paramname,16] value[ECULoad,0,0.000000]
10: paramid=0x1C
  : name[paramid,17] value[0x1C,28,0.000000]
11: scalingrpn=x,0.625,*
  : name[scalingrpn,18] value[x,0.625,*,0,0.000000]
12: paramname=KnockSum
  : name[paramname,16] value[KnockSum,0,0.000000]
13: paramid=0x26
  : name[paramid,17] value[0x26,38,0.000000]
14: priority=2
  : name[priority,19] value[2,2,2.000000]
15: paramname=Speed
  : name[paramname,16] value[Speed,0,0.000000]
16: paramid=0x2F
  : name[paramid,17] value[0x2F,47,0.000000]
17: scalingrpn=x,1.242742384,*
  : name[scalingrpn,18] value[x,1.242742384,*,0,0.000000]
18: paramname=Knock
  : name[paramname,16] value[Knock,0,0.000000]
19: paramid=0x30
  : name[paramid,17] value[0x30,48,0.000000]
20: paramname=AirTemp
  : name[paramname,16] value[AirTemp,0,0.000000]
21: paramid=0x3A
  : name[paramid,17] value[0x3A,58,0.000000]
22: priority=2
  : name[priority,19] value[2,2,2.000000]
23: conditionrpn=RPM,1800,>
  : name[conditionrpn,48] value[RPM,1800,>,0,0.000000]
24: action=start
  : name[action,49] value[start,0,0.000000]
25: conditionrpn=RPM,1800,<
  : name[conditionrpn,48] value[RPM,1800,<,0,0.000000]
26: action=stop
  : name[action,49] value[stop,0,0.000000]

--- log config dump ---


channel type: mut2
protocol id: 3
baud: 62500

param name: RPM
param id: 0x00000021
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,31.250000,*

param name: TPS
param id: 0x00000017
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,0.392157,*

param name: ECULoad
param id: 0x0000001C
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,0.625000,*

param name: KnockSum
param id: 0x00000026
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 1
scaling: x

param name: Speed
param id: 0x0000002F
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,1.242742,*

param name: Knock
param id: 0x00000030
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x

param name: AirTemp
param id: 0x0000003A
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 1
scaling: x

trigger action: start condition: RPM,1800.000000,>
trigger action: stop condition: RPM,1800.000000,<

--- storage info ---
log stringlist: 71 chars
log floatlist: 5 floats
logging interval will be 50000us