formula for "Boost Error psi based" data item

Reply Subscribe

Thread Tools

Search this Thread

Aug 12, 2012 | 09:38 PM

crimson red

Thread Starter

Evolving Member

Joined: Aug 2009

Posts: 284

Likes: 21

From: Hokkaido, Japan

formula for "Boost Error psi based" data item

Hello,

Sorry for newbie question,

Is there anyone who can tell me the formula and unit ( probably "psi") for the "Boost Error psi based" for evoscan data logger?

#I use GrimmSpeed 3-ports.

Thanks,

Aug 12, 2012 | 11:54 PM

richardjh

Evolved Member

Joined: Oct 2010

Posts: 2,447

Likes: 14

From: Australia

Hi Crimson.

This is what I've got in my logcfg.txt -

Code:

paramname=BoostError
paramid=0x808597
scalingrpn=x,128,-,0.0483675,*

So for Evoscan it would be: (x-128)*0.0483675

Its range is +/- 6.1 psi

See if that works for you.

Rich

Aug 13, 2012 | 07:31 AM

crimson red

Thread Starter

Evolving Member

Joined: Aug 2009

Posts: 284

Likes: 21

From: Hokkaido, Japan

Thanks Rich! I'll try your formula.

Quote:

Originally Posted by richardjh

Hi Crimson.

This is what I've got in my logcfg.txt -

Code:

paramname=BoostError
paramid=0x808597
scalingrpn=x,128,-,0.0483675,*

So for Evoscan it would be: (x-128)*0.0483675

Its range is +/- 6.1 psi

See if that works for you.

Rich

Aug 13, 2012 | 12:03 PM

Golden

Evolved Member

iTrader: (1)

Joined: Nov 2009

Posts: 1,456

Likes: 0

From: Omaha, NE

I simply do the subtraction myself and don't log the psi error.

Aug 16, 2012 | 03:57 AM

crimson red

Thread Starter

Evolving Member

Joined: Aug 2009

Posts: 284

Likes: 21

From: Hokkaido, Japan

Hi, Golden.

It's a smart way to keep versatility to a logged item. Excellent strategy.

Quote:

Originally Posted by Golden

I simply do the subtraction myself and don't log the psi error.

Aug 16, 2012 | 09:37 AM

fostytou

EvoM Community Team

iTrader: (15)

Joined: Sep 2006

Posts: 3,143

Likes: 7

From: Aurora, IL

Quote:

Originally Posted by crimson red

Hi, Golden.

It's a smart way to keep versatility to a logged item. Excellent strategy.

Quicker logging (more items at least) and semi-versatile, but if you have a variable target the subtraction is pretty difficult and it doesn't let you know when the ECU is doing something wacky / out of the ordinary.

Both are good tools.