So there is a "MAF Scaling" table in your 58010005 XML file?

 

yea, though it's split up to 3 tables and naming convention is a bit different due to that. looks the same as the supplied "evo10base.xml" file.

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

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

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

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


and just to verify, the scaling is defined:

<scaling name="VoltsADC1023" units="Volts" toexpr="x*5/1023" frexpr="x*1023/5" format="%.2f" min="0" max="5" inc="0.05" storagetype="uint16" endian="big"/>

 

Tephra, thanks for V2!, I am having a couple problems though. When using NLTS, it seems to be ignoring the rpm drop setting. I have tried 1000, 2000, and 3000 rpm drop, and it seems to drop to 6K rpm and then bounce there, no matter what RPM I clutch in at. I have min rpm to engage at 6k, if that matters.

My other issue is with live tuner. It doesn't want to connect. It will say openport 2.0 connected when i first open the program, but then will go to not connected, and flip between connected and not connected. I haven't been able to get it to work. I don't have any problems logging with evoscan.

I have a 2010 USDM GSR

Any idea what might be my issue?

 

maybe you have to change the min rpm to engage setting. change it to 5000 and see what happens.

 

yeh.. a "bit different" is what the problem is.

58010205 xml is referring to "MAF Scaling", it expects that that table will be defined in the parent XML's, which isn't the case.

If your using "MAF Scaling Horizontal", then just update the V2 XML to refer to that one instead

 

Thats a bit strange, if you dont "connect", but just start logging does it work ok?

 

Momo, I just tested it and you got it. It makes sense it was falling in and out of nlts mode and not actually using the nlts limiter. Working now.

Thanks!

 

both the connect and start logging buttons are greyed out. They flash available when it says "connected", but then immediately goes to "not connected"

 

ok, The LT app (like ECUflash) detects when the OP20 cable is plugged into the computer.

the connect and start logging buttons will "enable" when the OP20 is plugged in.

if its going connected/not connected then either something is interrupting it, or the cable is dodgey... i think it checks every 1/4 (or maybe 1/2) second, which i think is a bit more often that ecuflash...

can you try another USB cable?

 

I tried another cable, and had the same issue. To test, I tried my old laptop, and it connected with no problem. The old machine is running Vista, and my new machine is running on 8.1, maybe that has something to do with it?

 

good call, i should have tried that but a part of me figured most people had the same name for MAF tables.

it works now. loaded rom and connected to live tuner for a second before i went to work.


THANKS!

 

I think people have been running on W8.1, so that shouldn't be a problem.

what version of ecuflash do you have?

 

1.44.4341

 

I think Beeble is on W8 too (not sure if 8.1 thou)

 

Btw , sorry for asking again, any advancing news about the SST issue?
I'm patiently awaiting for it (and a couple of friends ready to donate as soon as available)