TephraXMOD V2

Reply Subscribe

Thread Tools

Search this Thread

Apr 21, 2014 | 02:08 AM

#166

mclaren

Evolving Member

iTrader: (6)

Joined: Nov 2010

Posts: 153

Likes: 0

From: Tacoma, WA

Quote:

Originally Posted by tephra

Sorry for the lack if updates guy, work has been killa and I've been sick...

I've found a (the) issue with 56890013 and I'll have updated 2012 gsr ready tonite..

It's all good man, we are all thankful for the work you do for the community. Get well soon David!

Apr 22, 2014 | 08:59 AM

#167

99EclipseGSX

Evolving Member

Joined: May 2005

Posts: 100

Likes: 0

From: Santa Monica, CA

Quote:

Originally Posted by BlueX702

Nice! The baro and iat bits were my main concern. The fast logging would be nice too, but seems redundant with v2?

My findings have been that RAX fast logging is still much faster than the new V2 logging, as well as allowing many more logged channels while still getting more than acceptable sample rates. I might try the RAX patch on V2 myself soon!

Apr 22, 2014 | 09:06 AM

#168

murlo26

Evolved Member

iTrader: (9)

Joined: Aug 2008

Posts: 4,119

Likes: 1

From: Minnesota

I was under the impression that Colby at Tactrix still had to alter ECUflash to actually give full v2 style logging?

Apr 22, 2014 | 11:23 AM

#169

itzwolf

Evolved Member

iTrader: (9)

Joined: Mar 2005

Posts: 1,193

Likes: 2

From: Florida

I hadn't heard about ECUFlash changes for logging only the protected area for flashing.

According to tephra's LT program I typically see 101-103 samples/sec.

Apr 22, 2014 | 12:05 PM

#170

SpeedCircuit

Former Sponsor

Joined: Jul 2008

Posts: 71

Likes: 0

From: New Jersey

Woot woot!

Apr 22, 2014 | 03:42 PM

#171

tephra

Thread Starter

EvoM Guru

iTrader: (6)

Joined: Feb 2007

Posts: 9,486

Likes: 67

From: Melbourne, Australia

ok so i will explain the logging bit.

both V2 and RAX utilise byte packing - what this means is you stuff multiple interesting log items into a memory area and you grab that memory area, less requests means your able todo more of them.. as far as i know evoscan only grabs 4 bytes at a time, so to get 20 bytes of memory you still need to do 5 requests... LT grabs 20 bytes at a time, but the CANBUS protocol will split that up into 4 packets...

byte packing requires that the logging program understands what is going on.. thats why RAX in EvoScan exists..

in ADDITION to this, V2 also implements FastOBD, which removes (or reduces) the rate limit for OBD requests from 100 every second to about 350 every second... evoscan doesn't need to be made aware of this to take advantage of it... Standalone logger needs 2 lines of config to take advantage of this because Colby rate limits requests in the OP20 to ensure a time consistent response..

so to recap:
stock evox logging = 100ish discrete samples second
rax evox logging (with a rax aware logger) = around 600 discrete samples a second??
V2 + evoscan = 350 discrete samples a second
V2 + LiveTuner logging = about 2500 discrete samples a second.

FYI - When my logger says 104 samples a second, it means ROWS, and a ROW contains about 25 requests...

So, if you want super fast logging, use V2 + LiveTuner.. There are 2 custom slots in LiveTuner to let you log whatever memory byte you wish if the current list of 25 common variables isn't enough for you!

Apr 22, 2014 | 05:40 PM

#172

Hellfire0986

Newbie

Joined: Jul 2007

Posts: 16

Likes: 0

From: Los Angeles

Quote:

Originally Posted by tephra

Thanks for the explanation. What 2 lines are needed to take advantage of FastOBD. I'm guessing due to the limitations of OP2.0 it won't be able to fetch multiple bytes of memory like what can be done on EvoScan and LiveTuner, well at least not without a firmware update.

Apr 22, 2014 | 05:51 PM

#173

tephra

Thread Starter

EvoM Guru

iTrader: (6)

Joined: Feb 2007

Posts: 9,486

Likes: 67

From: Melbourne, Australia

put

calcsampinterval=2850
calcconstdelay=0

into your logcfg.txt

unfortunately the numbers need to be tuned depending on how many things you are logging, but for me the above works well with 10 or so things being logged..

and yes - without a firmware update the op20 cant utilise the byte packing :S

Apr 22, 2014 | 10:55 PM

#174

BlueX702

Evolving Member

Joined: Nov 2009

Posts: 177

Likes: 19

From: Las Vegas

Thank you!

Now I just need my motor finished up so I can get this fancy mod!

Apr 23, 2014 | 04:52 PM

#175

redlinegvr4

Newbie

Joined: May 2004

Posts: 8

Likes: 0

Im getting an error with Live Tuner when I try to open the rom tehpra sent me. I did email him but just figured id ask if anyone had a fix. Here is the error

"Process XML: Error: No scaling attrubute setup for map "MAF Scaling" "

Any ideas?

Apr 23, 2014 | 05:54 PM

#176

tephra

Thread Starter

EvoM Guru

iTrader: (6)

Joined: Feb 2007

Posts: 9,486

Likes: 67

From: Melbourne, Australia

check the V2 xml.

it probably has a table called "MAF Scaling" at the end?

check the includes for that xml, and see what MAF Scaling you are using.. It might be "MAF Scaling Horizontal"...?

if so change V2 XML to use "MAF Scaling Horizontal"..

Problem is with all the different definitions floating about its impossible for the V2 XML to be able to reference them all.. it should be setup correctly for stock ECUFlash XML's...

Apr 24, 2014 | 07:49 AM

#177

mclaren

Evolving Member

iTrader: (6)

Joined: Nov 2010

Posts: 153

Likes: 0

From: Tacoma, WA

Quote:

Originally Posted by tephra

My 56890013 says:
<table name="MAF Scaling" lt-group="0" lt-memory-ptr="805054" lt-memory-blk="80d150"/>

After changing the "MAF Scaling" to "MAF Scaling Horizontal" in live tuner is still pops up with the same error but with horizontal at the end of it.

So what else needs to be changed to find an attributed value/reference for live tuner to work? Thanks

Apr 24, 2014 | 08:23 AM

#178

itzwolf

Evolved Member

iTrader: (9)

Joined: Mar 2005

Posts: 1,193

Likes: 2

From: Florida

Quote:

Originally Posted by mclaren

Check the 56890013 XML you are using, I am guessing the tables have to be named exactly the same. In my XML I have horizontal scaling AND vertical which is broken into 3 tables. Is your XML from Golden I presume?

56890013 XML MAF Tables:

Code:

  <table name="MAF Scaling Horizontal" address="575ae" category="Fuel" type="2D" scaling="GramsPerSecond">
    <table name="Volts" address="62014" type="X Axis" elements="130" scaling="VoltsADC1023"/>
  </table>

  <table name="MAF Scaling Part 1" address="575ae" category="Fuel" type="2D" level="2" scaling="uint16">
    <table name="Volts" address="62014" type="Y Axis" elements="44" scaling="VoltsADC1023"/>
  </table>

  <table name="MAF Scaling Part 2" address="57606" category="Fuel" type="2D" level="2" scaling="uint16">
    <table name="Volts" address="6206c" type="Y Axis" elements="44" scaling="VoltsADC1023"/>
  </table>

  <table name="MAF Scaling Part 3" address="5765e" category="Fuel" type="2D" level="2" scaling="uint16">
    <table name="Volts" address="620c4" type="Y Axis" elements="42" scaling="VoltsADC1023"/>
  </table>

I am on 59580004 so addresses will be different but this is what mine looks like and works.

59580004 XML:

Code:

  <table name="MAF Scaling Horizontal" address="5757a" category="Fuel" type="2D" scaling="GramsPerSecond">
    <table name="Volts" address="61fd0" type="X Axis" elements="130" scaling="VoltsADC1023"/>
  </table>

tephra XML:

Code:

<table name="MAF Scaling Horizontal" lt-group="0" lt-memory-ptr="805054" lt-memory-blk="80d150"/>

Apr 24, 2014 | 09:20 AM

#179

JinxsEvoXMR

Newbie

iTrader: (1)

Joined: May 2012

Posts: 87

Likes: 0

From: SoCal

+1 for wanting V2 for 2008 USDM MRs! =D

Apr 24, 2014 | 01:46 PM

#180

mclaren

Evolving Member

iTrader: (6)

Joined: Nov 2010

Posts: 153

Likes: 0

From: Tacoma, WA

Quote:

Originally Posted by itzwolf

Code:

  <table name="MAF Scaling Horizontal" address="575ae" category="Fuel" type="2D" scaling="GramsPerSecond">
    <table name="Volts" address="62014" type="X Axis" elements="130" scaling="VoltsADC1023"/>
  </table>

  <table name="MAF Scaling Part 1" address="575ae" category="Fuel" type="2D" level="2" scaling="uint16">
    <table name="Volts" address="62014" type="Y Axis" elements="44" scaling="VoltsADC1023"/>
  </table>

  <table name="MAF Scaling Part 2" address="57606" category="Fuel" type="2D" level="2" scaling="uint16">
    <table name="Volts" address="6206c" type="Y Axis" elements="44" scaling="VoltsADC1023"/>
  </table>

  <table name="MAF Scaling Part 3" address="5765e" category="Fuel" type="2D" level="2" scaling="uint16">
    <table name="Volts" address="620c4" type="Y Axis" elements="42" scaling="VoltsADC1023"/>
  </table>

I am on 59580004 so addresses will be different but this is what mine looks like and works.

59580004 XML:

Code:

  <table name="MAF Scaling Horizontal" address="5757a" category="Fuel" type="2D" scaling="GramsPerSecond">
    <table name="Volts" address="61fd0" type="X Axis" elements="130" scaling="VoltsADC1023"/>
  </table>

tephra XML:

Code:

<table name="MAF Scaling Horizontal" lt-group="0" lt-memory-ptr="805054" lt-memory-blk="80d150"/>

I'm using the XML that tephra sent for the tmod v2 56890013. I dropped it into the Evo folder in rommetadata. Does it have to access the regular XML of 56890013 that is there when you install ECUFLASH. Do I need to erase the original 56890013 and replace it with the one that tephra sent me?