ECUFlash - Getting close!

[AdrianG]

Nice! I hadn't seen it if you had. Are these 8 bit too?

- AdrianG

[Td-d]

Nope - float values, x-50

[AdrianG]

Would you mind helping me out with putting this to use? Please?

[Td-d]

Sure

paramname = Intake_VVT_Advance_Angle_Right(degrees)
paramid = 0xFF8C0E8
isfloat = 1
scalingrpn = x,50,-

paramname = Intake_VVT_Advance_Angle_Left(degrees)
paramid = 0xFF8C0EC
isfloat = 1
scalingrpn = x,50,-

paramname = Exhaust_VVT_Advance_Angle_Right(degrees)
paramid = 0xFF8C130
isfloat = 1
scalingrpn = x,50,-

paramname = Exhaust_VVT_Advance_Angle_Left(degrees)
paramid = 0xFF8C134
isfloat = 1
scalingrpn = x,50,-

Try that out, otherwise, it might just be the float value without the conversion.

[AdrianG]

If shipping to South Africa didn't cost as much as a turbo kit, I'd buy you a case of beer. Let me know if you're ever in continent

In case anyone cares, my logcfg.txt on dropbox has been updated with the AVCS parameters, but I haven't been able to test them personally yet.

[steve99]

Originally Posted by Td-d

Nope - float values, x-50

Hey Td-d Thanks for fixing the 32BITBASE base timing scaling problem works fine.

Thanks

[steve99]

Originally Posted by AdrianG

If shipping to South Africa didn't cost as much as a turbo kit, I'd buy you a case of beer. Let me know if you're ever in continent

In case anyone cares, my logcfg.txt on dropbox has been updated with the AVCS parameters, but I haven't been able to test them personally yet.

Does anyone know if these RAM addresses for Tactrix/ecuflash logging various ROM's are posted anywhere, so we don't have to annoy guys like Td-d.

I got a few off @ztan for G rom which was great. Have you managed to find gefogger for "G" ROM ?? thanks

Maybe a branch on Github would be useful ??

[AdrianG]

There's a list or two from Td-d in this thread actually. I started a separate thread just for logging parameters thinking it would help but it didn't get much traction, the conversation stayed in this thread.

[Td-d]

Originally Posted by steve99

Does anyone know if these RAM addresses for Tactrix/ecuflash logging various ROM's are posted anywhere, so we don't have to annoy guys like Td-d.

I got a few off @ztan for G rom which was great. Have you managed to find gefogger for "G" ROM ?? thanks

Maybe a branch on Github would be useful ??

Doesn't bother me, really. The Github branch is a good idea - just thinking how to do it.

Bit of a chicken and egg situation - the easiest way of generating the logcfg files is using logcfg.exe with the Romraider logger.xml file - which currently has no BRZ parameters, since logging for the BRZ in Romraider (using OBD) is still being developed by DSchultz. That being said, doesn't prevent me from creating an Alpha branch of the logger xml that can be substituted - I'll just need to create a whole set of new parameter definitions, since you don't have P parameters anymore (e.g. before, AVCS would be logged using a P parameter, not direct logging - will now need to create a new AVCS set of direct parameters).

Once I have that set up, it's very quick to generate the logger xml files for all the roms - I define the ram locations as I go along in any case.

[Td-d]

Originally Posted by steve99

Have you managed to find gefogger for "G" ROM ??

RAM:FFF89393 Ram_Defogger_Switch

ZA1JA01G

[steve99]

Originally Posted by Td-d

RAM:FFF89393 Ram_Defogger_Switch

ZA1JA01G

Just tried it works fine can see defogger toggle 0 to 1 in log.


Only drama is trigger does not seem to work runs as soon as ignition on and toggling defogger does not start stop log.
@AdrianG did your trigger work ??

; Defogger switch for logging start/stop
paramname = Defogger
paramid = 0xFFF89393
databits = 8

conditionrpn = Defogger,1,==
action = start
conditionrpn = Defogger,0,==
action = stop

[AdrianG]

I haven't been able to test yet, but I will update when I do.

- AdrianG

[Td-d]

Maybe put the defogger parameter up higher in the list, not sure why it's not being used as the trigger...

[steve99]

Originally Posted by Td-d

Maybe put the defogger parameter up higher in the list, not sure why it's not being used as the trigger...

Just tried that same problem unfortunately, might see how @AdrianG goes

I'll go back to my RPM trigger for now, might try commenting out some parameters in case theirs a limit or something.

Thanks