Openport Stand-Alone Logging Beta

Re: Openport Stand-Alone Logging Beta

Postby richardh » Mon Dec 27, 2010 8:12 am

Hi all.

My first post here. G'day!

I'm trying to get LC-1 standalone OP2.0 logging working. Like some others I've seen, I'm just getting zero values from it.

- This is for a Mitsu. All mode23 logging is working beautifully, standalone.
- My OP2.0 firmware version is 1.11.3137.
- All connectors seem to be plugged in securely.
- The LC-1 data link works correctly to the Innovate LogWorks3 application, connected to serial port on a PC. Valid, dynamic AFRs are displayed.
- The "terminator" thingy is plugged into the LC-1 "IN" socket, and stereo 3/32" male-to-male patch lead is used from LC-1 "OUT" to the OpenPort 2.0.
- My "logcfg.txt" file doesn't have any triggers - nothing fancy. Just the standard Mitsu mode23 entries, and the sample "inno" text from the relevant example file under "OpenEcu/.../logging" (the Subaru example).

I've seen LC-1 standalone logging reported as working in posts 6-9 months ago, but lately I've read more than one report of "all zeroes" for people trying LC-1 standalone. Makes me wonder if perhaps the addition of LM-1 support somehow caused an incompatibility with the old LC-1 protocol. Yes, that's pure, uninformed conjecture, sorry!!! ;)

I've tried "baud=19200" under the "type=inno" (as noted in previous posts), but I still get zero values.

So a bit at a loss now - not sure where to go next with it. Has anyone actually got this working on a recent OP2.0 firmware?

I'd hate to give standalone logging the flick - it's a brilliant system...

Cheers,


Rich
richardh
 
Posts: 3
Joined: Mon Dec 27, 2010 7:17 am

Re: Openport Stand-Alone Logging Beta

Postby earlyapex » Sun Jan 02, 2011 8:27 pm

earlyapex wrote:Colby,

Any chance to get Evo 10 CAN channel logging support with this?

Example:

SST Transmission Temp
CAN28-0

- Bryan


Bringing this back up from two months ago....

Any progress on this?
earlyapex
 
Posts: 158
Joined: Tue Apr 25, 2006 2:47 pm

Re: Openport Stand-Alone Logging Beta

Postby richardh » Wed Jan 05, 2011 12:03 am

richardh wrote:Hi all.

My first post here. G'day!

I'm trying to get LC-1 standalone OP2.0 logging working. Like some others I've seen, I'm just getting zero values from it.

- This is for a Mitsu. All mode23 logging is working beautifully, standalone.
- My OP2.0 firmware version is 1.11.3137.
- All connectors seem to be plugged in securely.
- The LC-1 data link works correctly to the Innovate LogWorks3 application, connected to serial port on a PC. Valid, dynamic AFRs are displayed.
- The "terminator" thingy is plugged into the LC-1 "IN" socket, and stereo 3/32" male-to-male patch lead is used from LC-1 "OUT" to the OpenPort 2.0.
- My "logcfg.txt" file doesn't have any triggers - nothing fancy. Just the standard Mitsu mode23 entries, and the sample "inno" text from the relevant example file under "OpenEcu/.../logging" (the Subaru example).

I've seen LC-1 standalone logging reported as working in posts 6-9 months ago, but lately I've read more than one report of "all zeroes" for people trying LC-1 standalone. Makes me wonder if perhaps the addition of LM-1 support somehow caused an incompatibility with the old LC-1 protocol. Yes, that's pure, uninformed conjecture, sorry!!! ;)

I've tried "baud=19200" under the "type=inno" (as noted in previous posts), but I still get zero values.

So a bit at a loss now - not sure where to go next with it. Has anyone actually got this working on a recent OP2.0 firmware?

I'd hate to give standalone logging the flick - it's a brilliant system...

Cheers,


Rich



I can also confirm that logging of the LC-1 data through EvoScan works fine (serial connection to laptop).

Something doesn't seem to be right with the "inno" serial comms link on the OP2.0 standalone. Just zeroes and more zeroes logged to microSD...

Rich
richardh
 
Posts: 3
Joined: Mon Dec 27, 2010 7:17 am

Re: Openport Stand-Alone Logging Beta

Postby AlexNorinh » Tue May 31, 2011 1:26 am

i've come across some strange phenomena when logging. values seem to 'stall' and repeat giving fairly bad resolution, whilst the lc-1 gives a more uninterrupted stream of data. this is making tuning difficult. can anyone shed any light on this?

previously, i've had trouble with the logger dropping out & producing 'gappy' logs (ie 4000rpm to 6000rpm in one sample) on wot runs when plugged straight into the obd2 port. this occurred with the op2.0 standalone or 1.3u. the following log is from the op2.0 plugged into the obd2 extension cable (so i had to reomove the socket from the factory mount - gd wrx)

also, mrp was pegged at 1.27053 upon full boost (my target is 1.4 - which is reached). going to try mrp direct (0x2192E) in the next iteration of the config file. the rom id is a4te100g (edm 03 wrx, but flashed on an adm 01 wrx ecu)

config:
type=inno
paramname = LC1
paramid = 0x0101

type=ssmk

;paramname = Intake_Air_Temperature(C)
;paramid = 0x000012
;databits = 8
;scalingrpn = x,40,-

;paramname = Mass_Airflow(g/s)
;paramid = 0x000013
;databits = 16
;scalingrpn = x,100,/

paramname = Engine_Speed(rpm)
paramid = 0x00000E
databits = 16
scalingrpn = x,4,/

paramname = Engine_Load*(g/rev)
paramid = 0x200EE
databits = 16
scalingrpn = x,.00006103515625,*

paramname = Manifold_Relative_Pressure(bar)
paramid = 0x000024
databits = 8
scalingrpn = x,128,-,37,*,255,/,14.50377,/

paramname = Mass_Airflow_Sensor_Voltage(V)
paramid = 0x00001D
databits = 8
scalingrpn = x,50,/

paramname = Primary_Wastegate_Duty_Cycle(%)
paramid = 0x000030
databits = 8
scalingrpn = x,100,*,255,/

paramname = Primary_Wastegate_Duty_Maximum*(%)
paramid = 0x20E0E
databits = 16
scalingrpn = x,.00390625,*

paramname = Ignition_Total_Timing(degrees)
paramid = 0x000011
databits = 8
scalingrpn = x,128,-,2,/

paramname = Feedback_Knock_Correction*(degrees)
paramid = 0x20C60
databits = 8
scalingrpn = x,.3515625,*,45,-

paramname = Fine_Learning_Knock_Correction*(degrees)
paramid = 0x20C65
databits = 8
scalingrpn = x,.3515625,*,45,-

paramname = Throttle_Opening_Angle(%)
paramid = 0x000015
databits = 8
scalingrpn = x,100,*,255,/

;paramname = IAM*(raw_ecu_value)
;paramid = 0x20120
;databits = 8
;scalingrpn = x

conditionrpn = Throttle_Opening_Angle(%),80,>
action = start

conditionrpn = Throttle_Opening_Angle(%),80,<
action = stop
Attachments
log0015.csv
(5.16 KiB) Downloaded 221 times
AlexNorinh
 
Posts: 2
Joined: Fri Apr 11, 2008 4:46 pm

Re: Openport Stand-Alone Logging Beta

Postby Jochen_145 » Sat Jun 18, 2011 7:04 am

I started playing around with a stand-alone Logger on a subaru Diesel.

Working even fine on K-line, as expacted, now got on with CAN-logging, because EURO5 Diesels can be only logged via CAN...

This gives a big advances because sample rates are very high, even when you log a lot value.
For a short "pull-up" perfect, but logging a complete regeneration need about 12 minutes and provides a mass of logging data, witch noone can realy handle.

So in short:

Is it possive to de-crease the logging rate (not sample rate !) to a value up to 5 or less Hz ?

Witch way can it be done or is it anohter item on the "wish list" for stand-alone logger ?

Best regards
Jochen
Jochen_145
 
Posts: 70
Joined: Thu Nov 12, 2009 8:45 am

Re: Openport Stand-Alone Logging Beta

Postby mfb » Tue Aug 02, 2011 2:19 pm

Hi Colby,

I currently have this set up
--- storage info ---
log channels: 2
log parameters: 45
log stringlist: 498 chars
log floatlist: 27 floats
worst case ssm request is 113 bytes long, response 90 bytes long and will be sent every 50000us (40557us is fastest possible)
logging interval will be 50000us

How can I improve on sampling rate? As per CSV its 20 samples per second. I number of logged parameters are many. :-) I currently have 4 parameters as 1 sampgroup. Will adding more sampgroups increase the sample rate?

Kind Regards,

Mark
mfb
 
Posts: 59
Joined: Fri Mar 26, 2010 1:49 am

Re: Openport Stand-Alone Logging Beta

Postby richardh » Sun Aug 21, 2011 1:16 am

Does anyone have a way to extract, say, a single byte from a 16- or 32-bit logged item?

eg. Log this...

Code: Select all
paramname=word
paramid=0x808080
databits=16
scalingrpn=x


...and then get separate high and low bytes from it?

Code: Select all
type=calc

paramname=highbyte
scalingrpn=word,<whatever>

paramname=lowbyte
scalingrpn=word,<whatever>


I've tried all sorts of arithmetic jiggery-pokery, like trying to push calculated vars beyond their precision limits to "drop" unwanted lesser-significant bits, but haven't found an approach sensible or reliable.

A bitwise AND operator supported by "scalingrpn" would make light work of this.

As far as I can see, the offsetbits thing doesn't work on "calc" type variables - only at the raw data-read stage.

Rich
richardh
 
Posts: 3
Joined: Mon Dec 27, 2010 7:17 am

Re: Openport Stand-Alone Logging Beta

Postby gwigga » Wed Oct 05, 2011 4:31 am

Have the op2, sd card, copid the logcfg.txt to the sd card, plugged the op2 inot the car, driven and all i get is logcfg.out no csv file??

nly the green light flashes no red light

I have updated all the firmware etc

any ideas
gwigga
 
Posts: 2
Joined: Wed Oct 05, 2011 4:24 am

Re: Openport Stand-Alone Logging Beta

Postby Merp » Mon Oct 31, 2011 7:58 pm

Any blue/red lights when you first plug it in?

Open logcfg.out and look for warnings/errors.
Merp
 
Posts: 22
Joined: Mon Mar 02, 2009 4:23 pm

Re: Openport Stand-Alone Logging Beta

Postby Zman15 » Sat Nov 05, 2011 10:37 am

I'm having a hard time logging data from my LC-1 directly into my Openport 2.0 device. I've reviewed the material in this thread and even submitted a ticket to support@tactrix.com - ultimately, he referred me back to this thread.

Here's what I'm working with:
Mitsubishi Evo 9 running Tephra Rom 88590715
Tactrix OP2.0 Firmware: 1.11.3137, Serial Number: TAT3q$YH
Innovate LC-1 Wideband O2 Sensor

I've had no problem logging data from the ECU, but continue to get 0 values for the wideband.
Here's what I have in the logcfg.txt file for the wideband:
type=inno
paramname = inno.afr
paramid = 0x0101
scalingrpn = x,14.7,*

I purchased the OP2.0 for the standalone logging capability and the LC-1 to be compatible with the OP2.0 for standalone logging. I really do not want to remove the rear O2 sensor and hardwire the LC-1 to the ECU.

Does anyone have any suggestions on what else I can try?

Thanks for the help!
Zman15
 
Posts: 1
Joined: Sat Nov 05, 2011 10:14 am

Re: Openport Stand-Alone Logging Beta

Postby mdedwar » Wed Nov 09, 2011 3:22 am

Zman15 wrote:I'm having a hard time logging data from my LC-1 directly into my Openport 2.0 device. I've reviewed the material in this thread and even submitted a ticket to support@tactrix.com - ultimately, he referred me back to this thread.

Here's what I'm working with:
Mitsubishi Evo 9 running Tephra Rom 88590715
Tactrix OP2.0 Firmware: 1.11.3137, Serial Number: TAT3q$YH
Innovate LC-1 Wideband O2 Sensor

I've had no problem logging data from the ECU, but continue to get 0 values for the wideband.
Here's what I have in the logcfg.txt file for the wideband:
type=inno
paramname = inno.afr
paramid = 0x0101
scalingrpn = x,14.7,*

I purchased the OP2.0 for the standalone logging capability and the LC-1 to be compatible with the OP2.0 for standalone logging. I really do not want to remove the rear O2 sensor and hardwire the LC-1 to the ECU.

Does anyone have any suggestions on what else I can try?

Thanks for the help!


x2 It use to work but it broke in the last firmware update.

I gave up and went back to romraider as Colby was unresponsive.
mdedwar
 
Posts: 24
Joined: Sun Oct 04, 2009 3:23 pm

Re: Openport Stand-Alone Logging Beta

Postby gvfs » Tue Dec 20, 2011 11:01 am

I apologize in advance for the n00b post, but can anyone explain why the OP2.0 fw 1.11.3137 will not log (create any .CSVs) via CAN when using the following logcfg.txt for standalone logging on a 2008 USDM STI? K-line works fine.
Code: Select all
;
; 2008 USDM STI
;
; AZ1G202I 6912783007
;
; ================ CAN or K-Line =============================
type = ssmcan
;type = ssmk
; ================ Parameters ===============================
;paramname = Cool_Tmp(F)
;paramid = 0x000008
;databits = 8
;scalingrpn = 32,9,x,40,-,*,5,/,+

;paramname = Cool_Tmp(C)
;paramid = 0x000008
;databits = 8
;scalingrpn = x,40,-

paramname = RPM
paramid = 0x00000E
databits = 16
;scalingrpn = x,4,/
scalingrpn = x,0.25,*

paramname = MPH
paramid = 0x000010
databits = 8
scalingrpn = x,0.621371192,*

paramname = ITT(deg)
paramid = 0x000011
databits = 8
;scalingrpn = x,128,-,2,/
scalingrpn = x,128,-,0.5,*

paramname = MAF(g/s)
paramid = 0x000013
databits = 16
;scalingrpn = x,100,/
scalingrpn = x,0.01,*

paramname = Accel_Ped_Ang(%)
paramid = 0x000029
databits = 8
;scalingrpn = x,100,*,255,/
scalingrpn = x,100,*,0.003921569,*

paramname = Fuel_Pump_DC(%)
paramid = 0x00003B
databits = 8
;scalingrpn = x,100,*,255,/
scalingrpn = x,100,*,0.003921569,*

;paramname = Gear
;paramid = 0x00004A
;databits = 8
;scalingrpn = x,1,+

paramname = ELoad_(4-Byte)*(g/rev)
paramid = 0xFF6578
isfloat = 1
scalingrpn = x

paramname = Tgt_Bst_(4-byte)*(psi_absolute)
paramid = 0xFF5E84
isfloat = 1
scalingrpn = x,0.01933677,*

paramname = FBKC_(4-byte)*(deg)
paramid = 0xFF7F14
isfloat = 1
scalingrpn = x

paramname = FLKC_(4-byte)*(deg)
paramid = 0xFF7FB0
isfloat = 1
scalingrpn = x

paramname = MAP_(4-byte)*(psi_absolute)
paramid = 0xFF6394
isfloat = 1
scalingrpn = x,0.01933677,*

paramname = Req_Tq*(raw_ecu_value)
paramid = 0xFF8278
isfloat = 1
scalingrpn = x

paramname = Pri_WGDC_Max*_(4-byte)*(%)
paramid = 0xFF5EA0
isfloat = 1
scalingrpn = x

; ======================= Triggers ==================================
; Start logging when the rear defroster is turned on -----------------------
paramname = defogger_sw
paramid = 0x64
databits = 1
offsetbits = 5
isvisible = 0

conditionrpn = defogger_sw,1,==
action = start

conditionrpn = defogger_sw,0,==
action = stop

; Start logging on RPM>0 -----------------------------------------------------------------
;conditionrpn = RPM,0,>
;action = start

;conditionrpn = RPM,0,==
;action = stop

; Start logging when coolant exceeds 168.8F ---------------------------------------
;conditionrpn = Cool_Tmp(F),168.8,>
;action = start

;conditionrpn = RPM,0,==
;action = stop

; Start logging when coolant exceeds 76C ---------------------------------------
;conditionrpn = Cool_Tmp(C),76,>
;action = start

;conditionrpn = RPM,0,==
;action = stop
gvfs
 
Posts: 3
Joined: Fri Nov 25, 2011 2:02 pm

Re: Openport Stand-Alone Logging Beta

Postby gvfs » Wed Dec 28, 2011 3:17 pm

Tried reducing the number of params to log to one. Made no difference.
gvfs
 
Posts: 3
Joined: Fri Nov 25, 2011 2:02 pm

Re: Openport Stand-Alone Logging Beta

Postby PollieXmas » Mon Jan 02, 2012 11:54 pm

Hi All,

I think I'm missing something... My config file and output file that I'm using are attached. These and other combinations I have used does not create any csv files. I have tried different ECU types relating to Tribecas, tried CAN and K-line options as well as different triggers. The Tactrix device just cycles through the blue, green and red, similar to when it is connected to the PC only.

The only thing I can think of is that my ROM is not one of the supported ROMs. (I have a 2007 Tribeca B9 and am in South Africa.) I recall reading a post about a file that you have to add to the SD card in order for the Tactrix device to communicate with the ECU.

I have already placed the xml file that I need to load tuned ROMs using ECUFlash on the SD card, but am not sure if the filename needs to be altered or not.

Any ideas/help?

Edit: I hate when this happens... Just tried it again after doing a log with RR and now it works!? The only thing I can think of is that I had the usb cable connected and/or not allowing it enough time to "start up". Anyway, at least I got a log out now, but I must still test to see if it is accurate.

Thank you

Paul
Attachments
Archive.zip
(2.26 KiB) Downloaded 183 times
PollieXmas
 
Posts: 1
Joined: Mon Jan 02, 2012 11:36 pm

Re: Openport Stand-Alone Logging Beta

Postby fostytou » Wed Mar 07, 2012 10:45 am

Zman15 wrote:I'm having a hard time logging data from my LC-1 directly into my Openport 2.0 device. I've reviewed the material in this thread and even submitted a ticket to support@tactrix.com - ultimately, he referred me back to this thread.

Here's what I'm working with:
Mitsubishi Evo 9 running Tephra Rom 88590715
Tactrix OP2.0 Firmware: 1.11.3137, Serial Number: TAT3q$YH
Innovate LC-1 Wideband O2 Sensor

I've had no problem logging data from the ECU, but continue to get 0 values for the wideband.
Here's what I have in the logcfg.txt file for the wideband:
type=inno
paramname = inno.afr
paramid = 0x0101
scalingrpn = x,14.7,*

I purchased the OP2.0 for the standalone logging capability and the LC-1 to be compatible with the OP2.0 for standalone logging. I really do not want to remove the rear O2 sensor and hardwire the LC-1 to the ECU.

Does anyone have any suggestions on what else I can try?

Thanks for the help!


Check out my earlier posts about the AEM UEGO and make sure you put your information in the correct spot.
fostytou
 
Posts: 15
Joined: Wed Jun 09, 2010 7:51 am

PreviousNext

Return to Openport Stand-Alone Logging Beta

Who is online

Users browsing this forum: No registered users and 1 guest