Td_d

Ecutek is about as closed a platform as you get - not knocking it, many advantages to using it (in particular for tuners who would like to protect their IP by locking their tunes, also the tuning workflow is generally quicker) - but you pay for it. Both in financial terms, and in being bound to an Ecutek tuner (unless you've gone the self-tuning route, only recently available, which I know is now available for the BRZs which I've been helping disassemble).

Ok, well switch back to either the 1bit extended parameter IAM or 4 bit, not convinced it's reading it properly now (or log a little more but not straight after flashing, when IAM is set to 0). Also - why are you logging wastegate duty? It's NA, not forced induction, there is no wastegate duty...

Ok, so you are using exactly that one, no edits. I'll have a look. Sent from my iPad using Tapatalk HD

Post up your logcfg.txt - I think some parameters are not properly defined in the file. Sent from my iPad using Tapatalk HD

Were these logs taken straight after flashing? I'm wondering why IAM is zero. What did you use to log - Romraider logger?

No, not as far as I know. Sent from my iPad using Tapatalk HD

You can log using k-line if you don't patch, but CAN is much faster (and requires the patch). Sent from my iPad using Tapatalk HD

When you are in advanced mode in Ecuflash (which you need to be in to see all the Alpha maps) you will see all the underlying maps in the 32bitbase, whether defined or not for your rom. Trust me, as much as you'd like, there's no direct injection on the legacy Sent from my iPhone using Tapatalk

Those should definitely get you going, will give you a good idea of how the car is doing. The patch is available as a tick box in Ecuflash when you open the rom (right at the bottom) you need to flash the rom to enable it (even you don't change any maps). Fast poll is just a tick box in Romraider logger (which requires a laptop). Sent from my iPad using Tapatalk HD

Depends on what you're trying to do I would read IAM as a p parameter, less bandwidth, and the AF correction and learning as the 2byte or 4byte parameters (more resolution). No need to duplicate the manifold relative sea level parameter - just log the 4byte one. Incidentally, if you are logging fast poll or with the CAN patch, the bandwidth is a lot higher (i.e. you can log more higher resolution parameters).

There's a patch required to enable fast CAN logging - just a tick box in Ecuflash. Sent from my iPad using Tapatalk HD

If you're seeing your rom ID, then you've set it up right - those addresses are already being used in logcfg. Check off the parameters you need, basically - there's a good tutorial on how / what to log on the Romraider forum. Also - make sure you check the can logging patch in Ecuflash, otherwise you won't be able to log CAN. Sent from my iPad using Tapatalk HD

Ah, ok - it had not yet synced from Dropbox. Try now. There are two type of parameters - standard parameters (p numbered - i.e. paramid = 0x07) and extended parameters, which are higher resolution (2byte or 4byte) - i.e. E parameters (E_Engine_Load_1byteExtExt_E86).

for romraider, check out the settings.xml file in the C:\Program Files (X86)\RomRaider directory, and just make sure that all your directories (i.e. for the ecu definitions, and for the logger.xml file) are correct. Then logcfg.exe will work.

Have you set up the Alpha Romraider logger files yet? It won't work without those. The online generator won't have this Alpha definition, but you could use it to create a logcfg using any other 32bit rom, and then plug in the addresses that I've posted up in the thread. The 'p' parameters will work in any rom.