Openport Stand-Alone Logging Beta

Re: Openport Stand-Alone Logging Beta

Postby cboles » Tue Mar 23, 2010 3:49 pm

RacnJsn95 wrote:I'm having the same problem as above. Only getting like 5 or 6 samples before it stops logging, but the lights continue flashing, as if it were... Good to see I'm not the only one having this problem. I have an 07 Sti, btw. I'll be watching to see this get resolved. :)


It took me almost 2 days, but i have it figured out now. :roll:

I'm hoping to get something out today, or tomorrow morning. Just need to do some more testing.
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Re: Openport Stand-Alone Logging Beta

Postby cboles » Wed Mar 24, 2010 5:06 pm

OK. I have a new version on the beta downloads page of www.tactrix.com now that should fix these problems. Be aware that the filename ecuflash_1432951b_win_beta.exe is very similar to the previous one. The EcuFlash version has not changed - that's why. The J2534 DLL and firmware have. So as always, be sure to go through all of the driver installations so that you are sure to get the new DLL. Once it is installed, run EcuFlash and go to the Help | Licensing menu item so that it will update your firmware. From there, let me know how it goes!

Colby


cboles wrote:
RacnJsn95 wrote:I'm having the same problem as above. Only getting like 5 or 6 samples before it stops logging, but the lights continue flashing, as if it were... Good to see I'm not the only one having this problem. I have an 07 Sti, btw. I'll be watching to see this get resolved. :)


It took me almost 2 days, but i have it figured out now. :roll:

I'm hoping to get something out today, or tomorrow morning. Just need to do some more testing.
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Re: Openport Stand-Alone Logging Beta

Postby Tephra » Wed Mar 24, 2010 5:07 pm

lol..

i was JUST logging in to see if there was a new version too :)

awesomeness!
Tephra
 
Posts: 59
Joined: Mon Aug 27, 2007 2:16 am

Re: Openport Stand-Alone Logging Beta

Postby poohbear » Wed Mar 24, 2010 6:04 pm

How can you tell what version you have?

I can get an out file but no logging... whats up with that?
poohbear
 
Posts: 24
Joined: Tue Mar 23, 2010 4:55 am

Re: Openport Stand-Alone Logging Beta

Postby cboles » Wed Mar 24, 2010 6:14 pm

ironically, if you have the new version, it will report the version number in the logcfg.out file...

otherwise EcuFlash can show you the firmware version.

poohbear wrote:How can you tell what version you have?

I can get an out file but no logging... whats up with that?
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Re: Openport Stand-Alone Logging Beta

Postby poohbear » Thu Mar 25, 2010 5:38 am

^ Well when I go to Help>liscensing or Ctrl+ Shift + L I get a prompt thats ask for a key... Is that correct? I dont have a key so I dont know what to do at that point :cry:

And why would I get ant out file but no logging ?
poohbear
 
Posts: 24
Joined: Tue Mar 23, 2010 4:55 am

Re: Openport Stand-Alone Logging Beta

Postby cboles » Thu Mar 25, 2010 7:09 am

you don't need to do anything in that window - it's just a simple way to connect to your OP2 which will cause a firmware upgrade if one is needed.

what does your logcfg.out file say? you forgot to attach it previously.

poohbear wrote:^ Well when I go to Help>liscensing or Ctrl+ Shift + L I get a prompt thats ask for a key... Is that correct? I dont have a key so I dont know what to do at that point :cry:

And why would I get ant out file but no logging ?
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Re: Openport Stand-Alone Logging Beta

Postby poohbear » Thu Mar 25, 2010 8:11 am

Yeah I did try to attach the file but got a file extension not allowed error from the forum... Here is a copy and paste of the out file

01: type = ssmcan
: name[type,8] value[ssmcan,0,0.000000]
02: paramname = RPM
: name[paramname,16] value[RPM,0,0.000000]
03: paramid = 0x00000E
: name[paramid,17] value[0x00000E,14,0.000000]
04: databits = 16
: name[databits,22] value[16,16,16.000000]
05: scalingrpn = x,4,/
: name[scalingrpn,18] value[x,4,/,0,0.000000]
06: paramname = mph
: name[paramname,16] value[mph,0,0.000000]
07: paramid = 0x000010
: name[paramid,17] value[0x000010,16,0.000000]
08: databits = 8
: name[databits,22] value[8,8,8.000000]
09: scalingrpn = x,0.621371192,*
: name[scalingrpn,18] value[x,0.621371192,*,0,0.000000]
10: paramname = Total_T
: name[paramname,16] value[Total_T,0,0.000000]
11: paramid = 0x000011
: name[paramid,17] value[0x000011,17,0.000000]
12: databits = 8
: name[databits,22] value[8,8,8.000000]
13: scalingrpn = x,128,-,2,/
: name[scalingrpn,18] value[x,128,-,2,/,0,0.000000]
14: paramname = g/s
: name[paramname,16] value[g/s,0,0.000000]
15: paramid = 0x000013
: name[paramid,17] value[0x000013,19,0.000000]
16: databits = 16
: name[databits,22] value[16,16,16.000000]
17: scalingrpn = x,100,/
: name[scalingrpn,18] value[x,100,/,0,0.000000]
18: paramname = MAF_V
: name[paramname,16] value[MAF_V,0,0.000000]
19: paramid = 0x00001D
: name[paramid,17] value[0x00001D,29,0.000000]
20: databits = 8
: name[databits,22] value[8,8,8.000000]
21: scalingrpn = x,50,/
: name[scalingrpn,18] value[x,50,/,0,0.000000]
22: paramname = CL/OL
: name[paramname,16] value[CL/OL,0,0.000000]
23: paramid = 0xFFA2C5
: name[paramid,17] value[0xFFA2C5,16753349,0.000000]
24: databits = 8
: name[databits,22] value[8,8,8.000000]
25: scalingrpn = x,6,+
: name[scalingrpn,18] value[x,6,+,0,0.000000]
26: paramname = MRP_PSI
: name[paramname,16] value[MRP_PSI,0,0.000000]
27: paramid = 0x000024
: name[paramid,17] value[0x000024,36,0.000000]
28: databits = 8
: name[databits,22] value[8,8,8.000000]
29: scalingrpn = x,128,-,37,*,255,/
: name[scalingrpn,18] value[x,128,-,37,*,255,/,0,0.000000]
30: paramname = PWGDC
: name[paramname,16] value[PWGDC,0,0.000000]
31: paramid = 0x000030
: name[paramid,17] value[0x000030,48,0.000000]
32: databits = 8
: name[databits,22] value[8,8,8.000000]
33: scalingrpn = x,100,*,255,/
: name[scalingrpn,18] value[x,100,*,255,/,0,0.000000]
34: paramname = FLKC
: name[paramname,16] value[FLKC,0,0.000000]
35: paramid = 0x000199
: name[paramid,17] value[0x000199,409,0.000000]
36: databits = 8
: name[databits,22] value[8,8,8.000000]
37: scalingrpn = x,0.25,*,32,-
: name[scalingrpn,18] value[x,0.25,*,32,-,0,0.000000]
38: paramname = FBKC
: name[paramname,16] value[FBKC,0,0.000000]
39: paramid = 0xFF7F2C
: name[paramid,17] value[0xFF7F2C,16744236,0.000000]
40: isfloat = 1
: name[isfloat,24] value[1,1,1.000000]
41: scalingrpn = x
: name[scalingrpn,18] value[x,0,0.000000]
42: paramname = LOAD
: name[paramname,16] value[LOAD,0,0.000000]
43: paramid = 0xFF6A06
: name[paramid,17] value[0xFF6A06,16738822,0.000000]
44: databits = 8
: name[databits,22] value[8,8,8.000000]
45: scalingrpn = x,.015625,*
: name[scalingrpn,18] value[x,.015625,*,0,0.000000]
46: paramname = defogger_sw
: name[paramname,16] value[defogger_sw,0,0.000000]
47: paramid = 0x64
: name[paramid,17] value[0x64,100,0.000000]
48: databits = 1
: name[databits,22] value[1,1,1.000000]
49: offsetbits = 5
: name[offsetbits,23] value[5,5,5.000000]
50: isvisible = 0
: name[isvisible,25] value[0,0,0.000000]
51: conditionrpn = defogger_sw,1,==
: name[conditionrpn,48] value[defogger_sw,1,==,0,0.000000]
52: action = start
: name[action,49] value[start,0,0.000000]
53: conditionrpn = defogger_sw,0,==
: name[conditionrpn,48] value[defogger_sw,0,==,0,0.000000]
54: action = stop
: name[action,49] value[stop,0,0.000000]

--- log config dump ---


channel type: ssmcan
protocol id: 6
baud: 500000

param name: RPM
param id: 0x0000000E
read width: 2 bytes
data width: 16 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,4.000000,/

param name: mph
param id: 0x00000010
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,0.621371,*

param name: Total_T
param id: 0x00000011
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,128.000000,-,2.000000,/

param name: g/s
param id: 0x00000013
read width: 2 bytes
data width: 16 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,100.000000,/

param name: MAF_V
param id: 0x0000001D
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,50.000000,/

param name: CL/OL
param id: 0x00FFA2C5
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,6.000000,+

param name: MRP_PSI
param id: 0x00000024
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,128.000000,-,37.000000,*,255.000000,/

param name: PWGDC
param id: 0x00000030
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,100.000000,*,255.000000,/

param name: FLKC
param id: 0x00000199
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,0.250000,*,32.000000,-

param name: FBKC
param id: 0x00FF7F2C
read width: 4 bytes
data width: 32 bits
data offset: 0 bits
float: 1
low priority: 0
scaling: x

param name: LOAD
param id: 0x00FF6A06
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x,0.015625,*

param name: defogger_sw
param id: 0x00000064
read width: 1 bytes
data width: 1 bits
data offset: 5 bits
float: 0
low priority: 0
scaling: x

trigger action: start condition: defogger_sw,1.000000,==
trigger action: stop condition: defogger_sw,0.000000,==

--- storage info ---
log stringlist: 133 chars
log floatlist: 14 floats
worst case ssm request is 57 bytes long, response 22 bytes long and will be sent every 50000us (30000us is fastest possible)
logging interval will be 50000us
poohbear
 
Posts: 24
Joined: Tue Mar 23, 2010 4:55 am

Re: Openport Stand-Alone Logging Beta

Postby cboles » Thu Mar 25, 2010 8:27 am

1) Have you installed the CAN RAM parameter patch to your ROM? If not, you can't use RAM parameters (which you are doing).
2) Are you triggering the logging with the defrost switch? I would get rid of these triggers first and see if that works.

poohbear wrote:Yeah I did try to attach the file but got a file extension not allowed error from the forum... Here is a copy and paste of the out file
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Re: Openport Stand-Alone Logging Beta

Postby poohbear » Thu Mar 25, 2010 8:33 am

1)No I have not applied any patches to my rom.. To be honest I did not know a patch had to be applied. But wouldnt that stop me from logging with romraider also? should I switch over to K-line then? Whats the big difference between the two?

2) yes I was using the defroster to trigger the logging... HOwever originally I was using RPM with out luck. I thought the defogger would make things more simple...

ANd thanks a lot for your Help Cboles..
poohbear
 
Posts: 24
Joined: Tue Mar 23, 2010 4:55 am

Re: Openport Stand-Alone Logging Beta

Postby cboles » Thu Mar 25, 2010 8:44 am

patch the rom - all you need to do is load it in ecuflash and check a box at the bottom of the table list and flash the rom. you can't log CAN *RAM* parameters otherwise. you are either using RomRaider to log K-line, or non-RAM CAN parameters. you want to use CAN - the logging is 10x faster.

poohbear wrote:1)No I have not applied any patches to my rom.. To be honest I did not know a patch had to be applied. But wouldnt that stop me from logging with romraider also? should I switch over to K-line then? Whats the big difference between the two?

2) yes I was using the defroster to trigger the logging... HOwever originally I was using RPM with out luck. I thought the defogger would make things more simple...

ANd thanks a lot for your Help Cboles..
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Re: Openport Stand-Alone Logging Beta

Postby poohbear » Thu Mar 25, 2010 8:56 am

What box at the end of the list? past the CEL error codes?
poohbear
 
Posts: 24
Joined: Tue Mar 23, 2010 4:55 am

Re: Openport Stand-Alone Logging Beta

Postby cboles » Thu Mar 25, 2010 11:02 am

poohbear wrote:What box at the end of the list? past the CEL error codes?

Subaru CAN RAM logging.png
Subaru CAN RAM logging.png (106.31 KiB) Viewed 11478 times
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

Re: Openport Stand-Alone Logging Beta

Postby poohbear » Thu Mar 25, 2010 11:29 am

Umm yeah I dont see that... Do I have to patch the rom separately or is it ECUflash that does the patch?
poohbear
 
Posts: 24
Joined: Tue Mar 23, 2010 4:55 am

Re: Openport Stand-Alone Logging Beta

Postby cboles » Thu Mar 25, 2010 11:31 am

poohbear wrote:Umm yeah I dont see that... Do I have to patch the rom separately or is it ECUflash that does the patch?


EcuFlash does it, if it thinks it can. If it can't the option does not appear. Can you send me your ROM to support@tactrix.com so I can take a look at it?

Colby
cboles
Site Admin
 
Posts: 1233
Joined: Wed Dec 29, 2004 5:45 pm
Location: Seattle, WA

PreviousNext

Return to Openport Stand-Alone Logging Beta

Who is online

Users browsing this forum: No registered users and 1 guest