Jump to content
LegacyGT.com

merchgod

Members
  • Posts

    171
  • Joined

merchgod's Achievements

Collaborator

Collaborator (7/14)

  • First Post
  • Collaborator
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. There's a delay in the hard parts estimated at about 2-3 months. Everything else looks good. I would expect this to release before the end of the year, unless the parts situation takes a turn for the worse.
  2. The OBXT shares the same ECU as the LGT so any LGT support automatically means OBXT support. The supported models/years for the FF release are as I listed them before.
  3. This will be V3 AP only. The V2 has been discontinued for some time now and has not received any new features/updates for quite a while. All of our features are hard-coded to the ECU - once you've reflashed the map with the features, you never need to connect the AP unless you want to change to different map, uninstall the AP, or data log / view live data (such as monitoring your ethanol percentage).
  4. The process of adding the CCF features to an AT ROM would not be difficult in this case but there are a lot of other steps involved in a release of software (ATP and AT®) and hardware (AP) support including a lot of testing that goes into it especially when "new" ECUs are added. We want to make sure everything works seamlessly and avoid using our customers as effectively beta-testers. There's also a lot of different Subaru projects we have in mind that are much more highly demanded so that plays a big role in it as well (there's only so much time/resources). I think there's a decent chance for AT LGT/OBXT support in the future if a lot of customers are reaching out to us and asking for it (especially after MT support is released). And I don't mean the same 3 dudes calling in once a week
  5. Nothing's changed as far as vehicle support I mentioned previously: 05-09 LGT/OBXT manual transmission only 10-12 LGT Development is complete and it is well into the testing phase. However, a few things have to come first before LGT/OBXT CCF can be released: 1. There's a big internal update to the Accesstuner software (called HL) that's already in the pipeline and has to be finished and released first. 2. Our existing FF hardware has to be modified for certain model years. Time on this one could be variable as you wait for parts from suppliers/etc. We don't plan to release without FF hardware support. As far as auto tranny support, there's no plans for it at this time. Not ruled out in the future, however. Not my domain, but I would guess that how well the kits sell for the manual tranny vehicles and how many requests we receive from individual customers and protuners for auto tranny support will play a big role into whether or not that becomes a reality in the future.
  6. The current plan is 05-12 Legacy GT (05-09 Outback XT), manual tranny only. No plans for auto tranny support, but could happen in the future if there's enough demand. EDIT: that is as far as tuning support only. Still investigating flex fuel hardware fitment/etc so it's unclear on that end.
  7. One thing that is commonly missed is that changes to FBKC, changes to FLKC, and changes to the IAM are all three separate knock responses and only one is active at any given time. So, if you look at only FBKC, you are not getting the whole picture. FBKC is not the response to ALL knock events, it is the response to knock events when it happens to be active. This is all based on a number of conditions that are outlined in the knock control sticky. That is, the ECU, at any given time, is "poised" to respond to knock events using only one of the three knock control elements OR it is "poised" to do nothing at all in response to a knock event (say at low RPM). Another common misconception is that the ECU will make a change to FLKC or the IAM based on FBKC. This is false. The ECU could care less what FBKC is at any given moment - it could be -2, -12, doesn't matter, it is not going to change FLKC or IAM at all. That is because FBKC, based on those conditions in which it is active, is the proper response given those conditions. Only changes to the FLKC and the IAM are linked. IAM can be thought of as a means of get timing roughly where you need to be and then FLKC does the finer adjustments. This is why the entire FLKC table is cleared when the IAM changes. It is more difficult to determine when the FLKC changes because when you log it, you are logging the applied (learned) correction for the currently accessed cell. You can log 'fine learning table offset' and if the offset stays the same and FLKC changes, then a change was made to that cell. Easier, as already mentioned, would be to check a learning view before and after the run. With the latest RomRaider logger definitions, I added the 'knock sum' parameter. All USDM Legacy GTs support this parameter. It is easily your best bet to track knock events because it deals with the knock signal which is exactly what determines a knock "event". Changes to FBKC, FLKC and the IAM are all based on this same knock signal. If your ECU support the knock sum, this is the only thing that I would log (while doing a learning view snapshot before and after the run). It will also improve your sampling rate because it is a 1-byte parameter. The only downside is that it will not increment with consecutive knock events, but this is not generally an issue.
×
×
  • Create New...

Important Information

Terms of Use