Jump to content

bradsm87

Members
  • Posts

    60
  • Joined

  • Last visited

Everything posted by bradsm87

  1. DBW outputs are also for electronic wastegates and DBW throttles as blow off valves these days so the uses are a lot more than just primary throttles. People can always add one CAN lambda if they want dual wideband.
  2. It'd be great to see an ECU between the Fury and Thunder that's smaller and cheaper than the Thunder. 2x 34-bin and 1x 26-pin 8 ignition 8 injector 2x e-throttle (one more than Fury). High amperage support for futureproofing for electronic wastegates etc. Single wideband like Fury More I/O than Fury but less than Thunder
  3. bradsm87

    Fury or thunder X

    Yeah that's fine. Can do. It was just hard to know if this 2 or 3 weeks is different to every other 2 or 3 weeks I've heard so if there is progress and it's not just the same no ETA from the manufacturer, then that's great news. Cheers!
  4. bradsm87

    Fury or thunder X

    I'm bowing out of the Link wait now sadly. You really should consider switching to a manufacturer who can at least give you an ETA and regular updates if the ETA changes. The COVID excuse can only be pulled so many times. Every time I've called Link in the past 4 months, I've been told either 2 weeks or 3 weeks. After last time 2 weeks ago being told 2 weeks and today now it's 3 weeks from now, what will it be when I call in 3 weeks? 2 weeks again or maybe 3 weeks that time? The time after that etc etc.
  5. I agree for many situations . Why not have two separate options then? But often on 3d tables you will want to interpolate some but not all rows or columns and still have the resolution to make changes in other areas. One example where I would have liked it for a starting point was is the E-Throttle target table to be able to make a non-linear curve with finer resolution in the bottom 15%, not a lot of resolution around the middle where it's quite straight and linear, and finer adjustment again near the top end but if I want to use the interpolate function, I'm kinda forced to have a linear Y axis.
  6. Yeah I definitely won't be changing the wheel if it's already got the good one. I'll only change it if it's like in the picture but I suspect the picture is wrong..
  7. Thanks guys. That pic is from the Nissan factory service manual for the TB48. Hopefully it's wrong.
  8. So my TB48 Nissan optical CAS is as per the attached pic. I know that the factory ECU never shuts down. All fuel trims, idle learning etc is stored in RAM. I've noticed that people with aftermarket ECUs never have it crank and start as quick as the factory ECU. My theory is that the factory ECU stores which cylinder it is up to in RAM all the time. It does often take longer to turn over if the battery has been disconnected which supports this theory. Aftermarket ECUs power off when you turn ign off or shortly after so it would be impossible for an aftermarket ECU to know which cylinder it is up to when starting the vehicle. Is that fair to say? If I swap to a CAS wheel where each of the 6 slots all have a different length, will a G4X be able to start the car without needing to go all the way around to the home slot?
  9. I mean new firmware features for existing G4X ECUs. From what I hear, the Thunder is still quite a long way away.
  10. OK thanks. The FuryX may not be for me after all as I'd run out of outputs. I'll have a think about XtremeX + CAN Lambda but that kinda kills the budget.
  11. I understand it's hard to disclose what you're working on just in case they take longer than expected or get canned but any chance of letting us know what's in the pipeline for the G4X?
  12. I'm not too keen on using a precious output on an e-throttle relay trigger. If e-throttle control is ever lost, couldn't the ECU just cut fuel, ignition or both instead?
  13. Does moving the APS % runtime out to another table to feed values into the final e-throttle target table like this have any impact on any safety features? I'm definitely wanting more control than just one 3d table.
  14. I noticed today that with non-linear Y axis values, using the interpolate vertically function, it interpolates presuming axis row spacing is equal even if they aren't. It's be great if the feature could factor axis values.
  15. Is CLL in "Auto Mode (Wideband)" suitable for full load operation? There are lockout settings that are set up to lock it out at full load but do I have to lock it out? Many factory and aftermarket ECUs work well with closed loop wideband under all load conditions including WOT.
  16. Can this be done now with the new firmware by doing a GP PWM out and assigning it to one of the "CAN Aux" channels and simply not using any actual CAN aux devices?
  17. Nice! This feature sounds great.
  18. How would non-interpolated work when you have for example?: 1000 2000 40 0 1 80 1 1 Would the "cutoff line" follow straight between those diagonal cells? Would 60kpa at 1500rpm be 1 because that's what I would need?
  19. I know with a perfect tune, short term fuel trims alone are fine, BUT, we don't always pick up issues immediately like a failing fuel pump or blocked fuel filter without a fuel pressure sensor present. I'm sure there are many other cases where the tune gets thrown out. a LTFT table would not only be great for better fuel control in such cases, but also a great table to regularly check up on and either 1) integrate any small changes into the main fuel table or 2) quickly identify an issue. What are the chances of adding this to the G4X to-do list?
  20. After a bit more playing with this, can I request that you consider implementing a dedicated "cam switch" feature? This could apply to Nissan VTC on SR20s and TB48s as well as Honda VTEC, Toyota VVTL-i etc etc. It would be nice to have setpoint setup with the same (or more) control as the arrangement screenshotted in the first post as well as user definable lockouts (eg. don't engage below X speed, X MAP)?
  21. Thanks. I'm waiting for the G4X Fury so can't test but it looks like I have options for VTC.
  22. That'd be great. Even just allowing a Y axis config so we can assign a switch status to it would be great.
  23. It would be great to see low range transfer case switch recognition and 2 separate sets of RPM/Speed gear detection gears. Without the gear detection knowing transfer case status, it could never be able to tell the difference between L3's 4.078:1 ratio compared to H1's 4.084:1 for example. I think a good way would be a new input/runtime for transfer case status as "low range" and "high range" that can be used anywhere on the ECU as needed plus the ability to have two sets of stored RPM/Speed gear detection ratios that are switched by the transfer case status switch. An easy way to start with might be to simply allow the addition of a Y axis on the gear ratio table so someone can add a switch status as a Y axis and set up the ratios for each.
  24. I'd still need to enable a GP PWM output which occupies a real output pin to get the PWM value from. I need a GP output to apply the on/off to a real output anyway so what advantage would bringing a Virtual Aux in have?
×
×
  • Create New...