Jump to content

Oprah_152

Members
  • Posts

    14
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Oprah_152's Achievements

  1. Can the gauge show live data or is it an average since last reset? Are the wheel speeds reading correctly in the ecu? Confirmed that the wheel speed coming from the CAN stream is about 15% off. ECU = ~100km/h Vehicle = ~115km/h
  2. You are 100% right, I was confusing the two! Do you have the PID setup to monitor E-throttle 1? I did not! makes perfect sense though. Your multiplier is set to -1%/%. ie. for 25% fuel pump speed you are asking for -25% duty cycle. Derp!, I did this years ago and I believe my thought then was it would invert the DC. Thanks! Can the gauge show live data or is it an average since last reset? Are the wheel speeds reading correctly in the ecu? This is coming from the Live data on the dash, not the AVG. looking through the logs, it does seem wheel speed is about 12% off on the ECU now. I'll take closer note next time I'm out. Ill check that, I do have the cruise set and cruise enabled signal noted on ID864 in our internal documentation but our car doest have cruise so it may not have been tested. I dont think our car has the tach lights so they definitely arent in the stream. What do these tach lights usually do - come on at a certain RPM or something? Sorry, I see how I wrote this can be a bit confusing. The "Tach" I'm referring to is the little dial gauge that comes on when you enable cruise control. I'm happy to aid in further testing if needed.
  3. I just wanted to Report back after upgrading to the latest release. I'm loving the development! but please more table allocations! Feed Forward E-Throttle I followed the recommended steps in the Help menu to setup the feed forward table which unfortunately left me with some delay in throttle operation which I'm 90% sure is calibration issue. When logging the Feed Forward parameter the log output is 0.000. I'm assuming because my throttle response had changed that the feed forward table is working, just not displaying in the log properly?. Fuel Pump Control I think I've always lived with this, but for what ever reason my ECU shows FP Speed to be statically set to 10% which is my minimum clamp %. I don't currently monitor Fuel Pressure but I haven't ran into any fueling issues so I have always ignored this. I've run this from 10% to 70% and not seen any abnormal lean / rich conditions. Virtual Aux I don't see the new virtual aux channels 9-12 available for use when I go to choose these parameters. (not on my critical path, just observed this.) GT86 CAN Fuel economy on the dash is displaying half of what the ECU is displaying. It appears to be statically set to display the fuel consumption of a 4-Cyl. I am personally using a 1UZ in my 86. Example Dash = 4.8L/100km PCLINK = 9.6L/100km Cruise Light on Dash doesn't appear to be included in the CAN package. Below is some basic settings to play with to get the light to work, I haven't put in the time to get the Mult./Divi/Offsets properly setup but I have used the offsets paired with a switch to bring the lights on. Amber Tach | CAN ID = 865 | Start Pos = 32 | Width = 8 | Offset to work = 200 Set Light | CAN ID = 864 | Start Pos = 40 | Width = 8 | Offset to work = 100 Green Tach | CAN ID = 864 | Start Pos = 40 | Width = 8 | Offset to work = 250
  4. Firstly, Sorry for the long winded response and probably for the poor explanation! lol. Air density is just charge temp times a density constant, what would you use the air density values for? Separate sensors for separate banks is something some setups would require but will require some re-writing of the fuel and ignition code as well as considering how this affects anything that uses MAP or inj pw. Would also require doubling up of all the injector pw, afr target etc runtimes. Dual turbo control to account for individual turbos feeding individual banks would also result in some awkwardness around how MAP limits are applied among other things. At this point it is much easier just to run two ECUs for this style of setup with shared sensors and identical tunes. I'd like the Parameter just to make my math channels more efficient. I currently use the Density to calculate back the "Air Per Cylinder Measured" to a VE value to populate "Fuel Table 2". I also use it to work out the Mass Flow Rate through the throttle body, but I'll get into that further down. MAF VE = (G/Cyl / Density) / (Displacement / # of Cyl) MAF VE = (Variable Cylinder Volume) / (Static Cylinder Volume) (Ignore the "/10" at the end, this is to adjust for KPa vs. PA in the math channels) Where are you using the current table allocations, could you be more efficient in your use of them, interpolating gp tables takes up a lot of processing time and storing them takes up a lot of RAM. I do currently have 6 available tables open to me, but I do have plans to eventually turbo charge a 1UZ/3UZ engine and want to add some Torque Request strategies which I kind of foreseeing me start to get limited. Not quite sure what you are trying to do here, are you wanting a generic runtime value that is set based on a table and some conditions? Yeah that's exactly what I was looking for. Right now I'm using "GP PWM 1" & "GP PWM 2" as a CAN AUX output to make these generic runtime tables. One of them could be used as a CAL Table but I've not be able to find a way to make that happen. dThrottle Area (%) is used to define the "Estimate Throttle Open Area". Example here would be; 100% TPS = 6644mm^2 50% TPS = 4985mm^2 25% TPS = 1295mm^2 What variables are you wanting to use on the ratio table axes? The two variables I'm using right now is TPS Delta and dPressure (basically MGP). Fuel Table 1 works as a normal VE table where as Fuel Table 2 aggregates Mass Air Flow & Throttle Mass Flow VE (%). Both MAF & TMF over react a bit to transient throttle conditions and a normal VE Table under reacts. This allows me to sort of capture the best of all three cases. Fuel Ratio If switching between fuel table one and 2 then use the same switching thing for 4d/5d activation, unless you mean blending too? What setup do you have that requires this? As seen below, Fuel Table 1 uses a traditional approach to VE where on a VVT or Variable tuned intake system means everything needs to be dialed on the main fuel table or correction tables created. Since on Fuel Table 2 I am using parameters that measure the current air flow, it would mean the corrections needed for Fuel Table 1 won't be needed for Fuel Table 2. Being able to lock 4D Fuel table to Fuel Table 1 would be an awesome feature. Fuel Table 1 Fuel Table 2 I'd also really enjoy the additional Requested Torque table to allow for driver switchable inputs to control Decel rate, Full power targets and transient power. I know this is easily accomplishable with other more conventional approaches but working inside a Torque Management framework with Throttle control and Boost control makes life a bit more simple once all setup.
  5. I thought I'd toss some of my wishlist items together. Some of which I don't currently need but would like the functions for future and others i've made work arounds for. I'm happy to provide working examples or further justifications to the use cases. Parameters Air Density Bank 1 (Kg/m^3) or (g/m^3) - Currently resolved in Math Channels Air Density Bank 2 (Kg/m^3) or (g/m^3) MAF 2 Air per Cylinder 2 Measured (g/cyl) MAP 2 IAT 2 MAF 1 VE (%) ((“g/cyl”/p)/“Cyl Vol”) - Currently resolved in Math Channels MAF 2 VE (%) ((“g/cyl”/p)/“Cyl Vol”) MAF Avg MAF VE (%) Avg MAP Avg IAT Avg Wastegate %DC 2 Tables 16 more table allocations to better support V8s CAL tables to have 16 more axis points. More granular CAL tables for MAF sensors GP Outputs to be friendlier for “user definable” - Currently resolved in GP output DC (1tbl)or PWM(2tbl) Unit output (g/sec, KPA, ms, g/cyl, %, etc) Allow decibel placement e.g. 0.000, 0.00, 0.0 To allow only 1 table consumed with Larger units than 100. Fuel Table Ratio table to allow for 3D axis - Currently resolved in GP output DC Additional “Torque Request Table” channels. - Currently resolved in GP output DC(Interpolate) Two tables To be able to switch between or interpolate between. Wastegate %DC 2 Allow for second WG Solenoid to control a second turbo. Closed Loop Boost control for second turbo. Single(Parallel) or Twin(Compound) staged control. 4D & 5D Fuel tables assignable. 4D table can be assigned to fuel table 1 and/or fuel table 2 5D table can be assigned to fuel table 1 and/or fuel table 2 Parameter/Channel functions MAF to allow for averaging over time - Currently resolved in Math Channels Math Channel example - av(MAF,0.06) CAN Gen 1 FRS/BRZ/86 ***I do have pretty much all of the surface values worked out(CEL,Fuel,PS,ECT,RPM etc)*** Gen 2 BRZ/86
  6. I would greatly appreciate that! Can be emailed to [email protected]
  7. Hey @Vaughan sorry for the delay in providing this, I had some difficulty uploading last time I tried lol. 1) Before any Changes (Original State) 2) New Axis Setup 3) New Axis Applied 4) After ECU Store. 5) Key Cycled & PCLink Reloaded 6) Axis Setup after Key Cycled
  8. I have a map i can share you, it gets RPM / Fuel / Power Steering / Coolant / Fuel consumption (L/100km) all working properly. It doesn't address everything but it's a great start. I'm hoping the team at Link will start to work on this because I'll be building swap kits for the 86 chassis and I really don't want to use other ECU's as I'm quite proud of the capabilities of the Link G4X series.
  9. Hey @Adamw, Will there be additional table allocation & math channels available in any of the upcoming releases? Also I may have found a bug with "Fuel Table Ratio Table" and scaling MGP. It works successfully with other parameters like MAP / Mass Air Flow etc, but when I use MGP it doesn't hold the "Store" and defaults to a single value on the x-axis. Thanks!
  10. Thanks so much! It's very much winter here so no rush haha.
  11. I always get this Error on any of the Torque management parameters
  12. Sorry to revive an old thread, Will we ever be able to use "Torque Request" parameter as a table axis in the future? I know I have the ability to use the GP Outputs to recreate this table, it just feels silly to have the same table defined twice I do personally would like to use torque modelling for E-Throttle control.
  13. I was wondering if there's plans for future releases where a generic 2d/3d user definable table will be available? Use cases would be a lookup table which could be used against a math channel or alternatively a correction table. Thanks!
×
×
  • Create New...