So who wants their ECU's "Chromed"?

[Greg E]

No Greg, I use MUT witch Tactrix SD log input

MUT00 and 01 values remain at 1,2, or 3 but not more !?

I wonder if the SD card can't read both MUTs as one request. If so then ill have to write custom code to do this math in the ECU and save it as one byte value. I can probably do this in the next version of chrome.

[dyter]

I wonder if the SD card can't read both MUTs as one request. If so then ill have to write custom code to do this math in the ECU and save it as one byte value. I can probably do this in the next version of chrome.

I log LoadRAW00 to LoadRAW03 and other 20 MUT commands, and my Load Calc work perfect with this:


paramname=LoadRAW00
paramid=0x02
scalingrpn=x,255,*

paramname=LoadRAW01
paramid=0x02

paramname=LoadRAW02
paramid=0x02
scalingrpn=x,255,*

paramname=LoadRAW03
paramid=0x03

type=calc

paramname=LOAD
scalingrpn=LoadRAW02,LoadRAW03,+,0.3125,*


but

paramname=Airflow(Chrome)
scalingrpn=LoadRAW00,LoadRAW01,+,0.09828125,*

is wrong in result because of invalid LoadRAW00 and LoadRAW01 (values is very low: 0 or 3 maximum)

[Greg E]

I log LoadRAW00 to LoadRAW03 and other 20 MUT commands, and my Load Calc work perfect with this:


paramname=LoadRAW00
paramid=0x02
scalingrpn=x,255,*

paramname=LoadRAW01
paramid=0x02

paramname=LoadRAW02
paramid=0x02
scalingrpn=x,255,*

paramname=LoadRAW03
paramid=0x03

type=calc

paramname=LOAD
scalingrpn=LoadRAW02,LoadRAW03,+,0.3125,*


but

paramname=Airflow(Chrome)
scalingrpn=LoadRAW00,LoadRAW01,+,0.09828125,*

is wrong in result because of invalid LoadRAW00 and LoadRAW01 (values is very low: 0 or 3 maximum)

It's hard to explain. I don't think we can get the SD card to log the 2 byte stuff.

See doing it that way LoadRAW00 = 1 and LoadRaw01 = 255 (unscaled). Your equation would return 1 and 256 not 257 like it should be. This is because it doesn't read both requests as one value.

The only way I can think of to get around it is to have the ECU do the equation and save it into 1 byte value. This I can do in a future chrome release.

Looks like for the time being, you will have to use EVOScan to tune.

[Greg E]

Guys I've updated the first post of the thread with links to the V2 threads. I've also asked the mods to lock this thread. Let's move all flash ECU discussions into the Tuning, Engine electronics and ECU discussions forum.

Please start your own threads in there or add to the topic discussion thread I've started.

http://www.3sgto.org/f104/how-tune-y...ecu-10775.html
http://www.3sgto.org/f104/chrome-v2-...ual-10777.html

[J. Fast]

Guys I've updated the first post of the thread with links to the V2 threads. I've also asked the mods to lock this thread. Let's move all flash ECU discussions into the Tuning, Engine electronics and ECU discussions forum.

Please start your own threads in there or add to the topic discussion thread I've started.

http://www.3sgto.org/f104/how-tune-y...ecu-10775.html
http://www.3sgto.org/f104/chrome-v2-...ual-10777.html

It's an excellent read. Very well put together! Good job man!

Read that thread, read it again, read it again, again, and again... It makess absolute sense.

[Greg E]

It's an excellent read. Very well put together! Good job man!

Read that thread, read it again, read it again, again, and again... It makess absolute sense.

Thanks man! Only took me a month and a half to put it all together.

Hopefully it'll help answer a lot of the commonly asked questions and also help ease some of the intimidation factor when first getting into this.

[CoopKill]

Will be at this point very soon. A big thanks Greg! You will be seeing another thank you soon via PPal...

[dyter]

Very good manual Greg ! It's very complete and indispensable, thanks

[Jeff V.]

It's hard to explain. I don't think we can get the SD card to log the 2 byte stuff.

It logs 2-byte responses just fine. Set it up like this:

paramname=RPM
paramid=0x00
databits=16
scalingrpn=x,3.90625,*

This will force it to read requests 0x00 and 0x01 as a proper 2 byte value and scale it appropriately.

[Greg E]

It logs 2-byte responses just fine. Set it up like this:

paramname=RPM
paramid=0x00
databits=16
scalingrpn=x,3.90625,*

This will force it to read requests 0x00 and 0x01 as a proper 2 byte value and scale it appropriately.

Jeff FTW!!!