Jump to content

Rozsko

Members
  • Posts

    232
  • Joined

  • Last visited

Posts posted by Rozsko

  1. 1 hour ago, Adamw said:

    Please explain what you are trying to do.  You can send or receive the same stream on both buses but Im not sure why you would want to do that. 

    20 CAN slots with 10 custom multi-frame streams is already very generous and more than most ECU's of this level allow.

    You might be right about the generous part, but as I was reviewing my inputs, it seems I am running out of options.

    I want to fit quite a few extra sensors, air temp, and emap, and because I did not use all the CAN streams yet, I thought I will be able to fit an AEM 22 channel CAN module and hook all those sensor up like that. I have 6 AEM gauges and an EGT modul already that are sending data to the ECU on custom CAN. So I would need more then 10 streams.

  2. 55 minutes ago, Adamw said:

    So you have to program one CAN Lambda module to be Lambda 2 before hand using the CAN devices tab.

    Yep, I figured that, but I would have thought that all lambda modules will need to be assigned individually to a stream with its own ID starting from 950 and up.

  3. 16 minutes ago, Adamw said:

    You can have up to 8 CAN lambdas all on that one channel.

    WOW, I would have never tried that. (but only two more modules to go to have 4 :) ) Not sure if I want to go there though as I am not sure for how long the LSU sensors will last pre turbo.

    So that means, the 950 ID is not relevant either in the setup screen?

  4. 10 minutes ago, Adamw said:

    You have a max of 10 custom streams (ID's) shared across all CAN devices.

    Oh, that's very sad.

    Is there any reason why? and is there any plan to add more?

    And in this case I can have a custom stream assigned only to one bus, correct? I mean if I assign a device to Stream 1 on bus 1, then I can't assign an other device to stream 1 on bus 2.

  5. Hey guys,

    As I had to change the bit rate of the CAN-Lambda I have, I decided to attach it to the other CAN bus connector.

    Doing that I was expecting that the streams tab will be empty of frames (if that's an actual expression :) ), but it wasn't.

    No matter which bus I selected on the main tab of the CAN setup screen, it was streams1-10 displayed with the list of frames I have setup currently for the rest of the gauges.

    This is becoming a problem for me as a 22channel AEM modul is on the way so I'll need to use both buses.

    Thanks

  6. Hey guys,

    In the process of configuring my new CAN-Lambda modul and while reading trough the setup instructions, there seems to be no mention of the stream setup. Is that because it is not needed for real or is that just so obvious that it is not mentioned?

    Thanks

  7. 4 minutes ago, Adamw said:

    Its not an easy one to answer and not usually something I would suggest, it can become quite a challange to make everything work happily.  If you only do fuel and ignition it wont be so bad but there will still be a couple of issues to overcome such as a CE light since CLL wont be doing what the OEM ecu expects.  sometimes there are reflashing options to disable so of these faults.

    The more control you take, the more difficult it becomes.  You really want the Link controlling E-throttle since idle control etc wont work well when the factory ecu doesnt have control of ignition.  But then taking control of E-throttle can be a big head ache with all the safety systems often not able to be disabled. 

      

    Thanks Adam.

    So then the only thing I can do is wait and see how you guys are progressing and hope that you will be ready on time (for me) with the Subaru CAN support. Otherwise I will need to look elsewhere, which I would really hate for multiple reasons.

  8. Tried to ask this question in the G4+ section in an older thread, but no answer for a couple of days, so thought to give it its own topic.

    Do you guys have any suggestion how wire up a G4X to piggy back the OE ECU?

    Any suggestions, link to documents, etc.. is appreciated.

    Thanks

  9. Sorry for bringing back and sort of hijacking an old thread, but do you guys have any documentation or some suggestions how to start a piggy back project like this? Might need to do something similar for a 2013 STi if there will be no CAN support for these Subarus in a few months.

    Thanks

  10. This is great news @Adamw. Thanks very much.

    Are there any major differences with beyond 2011? The car I am trying to find the solution for is a 2013 sedan, which shares many many things with the hatch.

    This project is a few months out, so I wish the plugin will be ready by that time as you say.

  11. I am sure I read it somewhere that you guys are already working on adding the native support of Subaru CAN, so that 2008+ STis can use these really standalone and no piggy pack, but can't find that thread.

    Do you have any estimate on when this is going to come?

    Thanks,

    Béla

  12. Hello there again,

    I was playing with AEM's CAN gauge (30-0312) as at the end I want that to display the lambda values from the Link CAN Lambda (which is on the way home) and potentially an other one to display EGT.

    Unfortunately the gauge itself is not customizable by means of specifying what ID or frame structure to use, but it has a big bunch of AEM specific message types preset.

    I was able to configure the G4X to send the IAT and ECT and those were displayed correctly, however the Infinity user guide states a scaling like this for the lambda vale: 0.00390625 Lambda/bit. There are other parameters with similar scaling, so I guess this is more of a generic scaling question.

    Do you have any idea how to translate this to G4X "language"? The multiplier and divider fields don't seem to accept fractions and they are limited to 5 digits only.

    Thanks

  13. 7 hours ago, Vaughan said:

    This was spotted fairly quickly and a new version was put up with a fix (6.18.32), another version with language support (6.18.44) has also been put up since that so grab the latest PCLink and firmware please and let me know if it's still a problem.

    Thanks

    Got you. Sorry, did not spot any announcements about that. Will try and revert back in case of any further issue.

    Thanks

  14. It seems to me that in this release we've got a bug in the fan control.

    As per the help (and so far that's how it worked) if you enter 0 into the speed lockout, then there is no speedlockout. I mean it is disabled.

    Right now, with the new firmware, 0 means actual 0, so if I start driving, the fans will stop. This was quite uncomfortable as I almost boiled the coolant in town cruising.

    log: https://1drv.ms/u/s!Ale4oyMCOgLThM4edFre7Av_S3wKIw?e=kbQLtp

    Thanks,

    Béla

  15. On 8/19/2020 at 2:02 PM, M1tch said:

    Will there be any extra feature upgrades for the G4+ at all? Or is my £1,300+ ECU now obsolete? I was waiting for long term fuel trims to be added to my ECU as part of the closed loop lambda (as it usually is on OEM ECUs), probably should have gone with an ECUMaster rather than Link it seems.

    When I bought my original G4+, I was very happy with that (although there was not much updates coming for that recently). Then 6 month later the new generation was announced. Right then I started advertising my G4+ for sale, because I knew I will want the new bells and whistles that come with it. I ended up paying an extra 300EUR for the G4X which I think is a reasonable price for the upgrade. Maybe you can do the same as the G4+ is still a strong ECU and I am pretty sure there are people who will happily pay a few hundreds less and get a little smaller feature set then the current line-up.

  16. So, my turbo is done and I am reviewing the latest logfiles to figure out what mistakes I made if any.

    One thing I figured, that my knock trim tables had inconsistent axes setup. #1 TPS and RPM, the other 3 had MAP and RPM.

    If you check the screenshot on the below link, you can see there was some misfire due to over retarding of ignition due to 5 degrees of trim. Initially I thought it was due to the knock trim tables, but I think it is more due to the Limit Ignition Trim parameter which should be set when a limit is active. On the other hand, there is no active limit during that time period (MAP, Speed, GP, etc.). Do you have any suggestion where that is coming from?

    screenshot: https://1drv.ms/u/s!Ale4oyMCOgLThMtYP357jH81Zrl5qg

    log: https://1drv.ms/u/s!Ale4oyMCOgLThMsJ_3rw80Z6DRXUTw?e=5WToXO

    Thanks a lot

  17. Just thought to give you guys a quick update.

    Just came back from the third dyno session. It started out nice, but ended up bad as it seems the turbo is gone.

    if you are interested, on the link you can see some dyno chart screenshots, the log of the pull and a video as well.

    So now I'll need to get the turbo out and see what is exactly the fault. More to come...

    https://1drv.ms/u/s!Ale4oyMCOgLThMsJ_3rw80Z6DRXUTw?e=5WToXO

  18. On 7/14/2020 at 7:45 AM, Adamw said:

    I suspect it is the fuel table needs flattening in that area, the logged fuel table value in that area is bouncing between 47-70%.  Since the exhaust gas is moving through the system so slowly at low engine speeds you cant see the rich/lean cycling on the lambda.

    k7QODWE.png

    Thanks Adam.

    I gave it a try, and I can tell you it is better then before, but it needs a little more work. Hopefully I can make it smooth soon.

  19. On 7/12/2020 at 11:36 PM, Vaughan said:

    Not all pins on the ECU are exposed, most vehicles only need a small subset to perform all the factory operations and more. On the WRX107+  An Volt 12 and Aux14-16 are not exposed but if you need more pins than you have exposed we can add a connection to these pins (read soldering on some flying leads). Typically this is a send back to have the servicing guy do this kind of thing.

    Thanks Vaughan. Right now I am good, who know what the future brings.

    Yesterday night I spent couple of hours on the highway doing WOT pulls to dial in the EBCS, and towards the end I realized I have the following fault code:

    ECU Fault Code 84: Aux9/10 E-Throttle 1 IC Over Temperature / Under Voltage

    Since then I did not start the car, but I am wondering if this is something I should worry about.

    Thanks

    Béla

×
×
  • Create New...