Td_d
-
Posts
30 -
Joined
Content Type
Profiles
Forums
Gallery
Posts posted by Td_d
-
-
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
-
They were logged direct to SD card right after flashing the patch to the ecu.
Post up your logcfg.txt - I think some parameters are not properly defined in the file.
Sent from my iPad using Tapatalk HD
-
I finally got around to patching my ECU and pulling a couple of logs.
https://www.dropbox.com/sh/kcsig0hhq0bc6oe/JLpH3TVH1E/log0001.csv
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
-
Another question; why does it say "Alpha - BRZ" in the ROM Metadata section when I open up my ROM in EcuFlash?
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
-
Does this look like a good stand alone logcfg file for logging?
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
-
Okay, so I got the logcfg.exe downloaded and working, I was able to select my ROM in the EcuType drop box, I checked the "Can" check box, I chose "Use Rpm" for logging start stop. Now, do I check off all the check boxes for the "RR ID" or just some of them? And those logger addresses you posted for my ROM on the romraider forum, do I do anything with those?
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.
-
None of that worked for me.
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.
-
The xml file is the link from the word Ecuflash in the post (you'll see it's a URL).
Use this 32bitbase: https://raw.github.com/TD-D/SubaruDefs/Alpha/ECUFlash/subaru%20standard/Bases/32BITBASE.xml
There's an online logcfg generator here, uses your Romraider Logger profile to create a logcfg: http://verticaltier.net/configtool/logger.php
My personal preference is this piece of software:
-
Another question, the def file for the 2011 has "MT" for transmission type, is that a typo?
Yup, typo - if you download the latest version from Github (see the link in the thread) it is corrected, and has more tables than the first one I posted in 2012.
-
Awesome.
Question, what are the Logger addresses for in the second post?
You'll see there's a link to an Alpha set of logger definition in the post - you can used those to replace the existing Romraider logger.xml so you can log the Ecu using Romraider Logger.
I post the addresses so that they can be incorporated in the formal logger releases - you can also use the addresses for the logcfg.txt if you are using onboard SD card logging on the OP2.
-
-
Usually the CAL ids are territory specific - i.e. USDM, EDM, AUDM, SADM etc. not state specific. The only time I've seen a difference is if it's a PZEV vehicle - and then the logic also tends to differ (since there are 5 O2 sensors).
-
Did I get it right this time?
https://dl.dropboxusercontent.com/u/27879197/2012_Legacy_36R.bin
Yup, that's what I needed. This rom's calibration id (CAL) is DE5K800B, not yet defined. I'll pull one together for you.
Incidentally, this is the last definition I put up (for Paul at ECS) - 2013 USDM 3.6 Legacy:
-
Yeah - that's a CSV log file, can't define that
-
I need some clarification. Is it the Tactrix Openport 2.0 that you guys are using for the 5th gen? And, is there a need for the OBD2 extension cable?!
OP2 is the one, correct - all CAN vehicles (post 2007) require the OP2. You don't necessarily need the OBD extension cable, the OP2 can be plugged straight into the OBD port - but it makes life a lot easier in terms of not inadvertently kicking it out of place, and reaching the OP2.
Logging can be done either onboard (SD card) or using a laptop (Romraider).
-
Td_d are you familiar and/or affiliated with Dastek in any way?
I have yet to pull my stock rom for you, but will do so for sure.
No, not at all - I know the Unichip well, but I'm not a big fan of piggyback systems at all.
-
Pull the rom, and I can check if it's the same or a different CAL id.
Official 3.6R Mod List
in Fifth Generation Legacy (2010 - 2014 )
Posted