Jump to content

coupe-r

Members
  • Posts

    26
  • Joined

  • Last visited

Posts posted by coupe-r

  1. Regarding the TPS output sensor that Haltec offers, did you notice it Specifically says for R34? I assume its a 1:1 TPS output scale.
     https://www.haltech.com/product/ht-038001-nissan-attesa-4wd-tps-adaptor/

    R32/33 seem to input to the 4WD ECU at a scale of 2/3 or so the Link manual states this?
    I assume when using a scale of 1:1 then the 4WD ECU of the R32 will see MORE TPS voltage than it usually would for a given throttle angle. Unsure the effects of this, but maybe MORE is sent to the front wheels than normally would be?

    What say you Link Gurus?
     

    TPS out.png

  2. Ok cool so all our settings are correct then. No dice...

    its getting power and ground, plus its wired correctly. I asked him about the gap which is says is correct.

    Starting to look like failed sensor

    He could use the AEM EPM but thats giving rubbish readings also; its been sent back to AEM but they state nothing wrong with it....
    Its a 24-1 optical sensor I believe.

    I guess he REALLY needs to scope the output from it (can't on G4 plugin correct?)

    This is with engine idling stable but RPM all over the place. (at higher RPM it jumps 1000rpm!)

     

    RPM stability.jpg

  3. " (Honda use the signal inverted to what we do)"

    hah, i think honda use it inverted to how EVERYONE else does it. Hmmmm thats a curve ball then if you changed the pinout to reverse the signal.

    Ok he has put it back to B16 and B12, still nothing.

    However he hooked up his old AEM EPM which is a bit faulty (causes RPM spikes and issues) But he sees RPM now.

    starting to look like its the T1 trigger..

  4. Hi there, helping a friend with a B18C Integra link G4 plug in.

    He has fitted a T1 Race developments Cam trigger setup (used to have an AEM EPM but it failed and gave issues)
    http://help.t1racedevelopment.com/support/solutions/folders/4000002167 

    His Trigger 1 setup is
    Hall/Optical:
    Filtering =LOW
    Pullup=ON
    Trig1 edge=falling
    Multi-Tooth position=cam
    Tooth Count=12

    Trigger 2 is the same but cam pulse 1x

    While logging (with injectors disabled) he gets ZERO RPM and no trig errors.

    I have got him to post me pictures of the wiring and the trigger 1 (crank) goes to Pin B15 on the honda OBD1 B plug (CKPP)
    trigger 2 (cam) goes to pin B11 (CYLP)

    The wiring seems correct, ecu sees nothing. Power and ground are getting to the sensor, with the gap adjusted to 40 thou. Can't figure this one out.

    tried changing pull up on and off and changing rising and falling but no change.

    Also tried changing it to Crank driven and 6 teeth (but no change either)

     

  5. Ok the reason is because on a LC1 the YELLOW WIRE IS THE 0-1V narrow band by default.

    Get a USB to serial (RS232) converter (a decent one) and download the logworks software and LM-programmer and re-program the analog 1 (YELLOW) to be

    0v =7.35, 5v=22.39

    http://www.innovatemotorsports.com/support.php

    OR just plug the BROWN WIRE into the ecu lambda 1.

    http://www.innovatemotorsports.com/support/manual/LC-1_Manual.pdf 

     

    Make sure you have wired the SENSOR ground to the SENSOR ground of the link.

    DO NOT just join the power ground and sensor ground wires together from the LC-1.
     

    P.S Do a free air calibration with the sensor pulled out of the exhaust

  6. Cheers for the relay advice b3tuning. I didn't wire the car, I am just helping a friend with initial start up.

    Andre Simon also confirmed they are a 2 AMP limit for Aux high drive.

    I did get the owner to measure current draw when firing the solenoid which was 0.6AMPS *2 is well under the current limit but i'll leave that up to the owner.

    Will post when we figure why link won't scope (the fact it logs RPM and cycles SURELY means we are seeing both triggers with no errors)

     

  7. Yep as per the first map and log posted ;)

    Thanks Scott, we will ocntinue scoping with an actual scope to set trigger arming. Then try ecu reset and reload map.

    Regarding AUX 5 current limits...

    Although I can't find anywhere in the PC Link guide that specifies current limit for aux it does say that you can wire a vtec solenoid directly to Aux5,6,7 or 8 without a relay.

     

    aux5.PNG

    This taken from the G4 PDF manual

     

    aux 5 current.PNG

  8. Thanks for the quick replies.
    Hmmm so effectively the firmware is actually tied to the map file which stored in the ecu at the time of Firmware update.

    I can update the firmware on a map stored in the ecu from 5.1.1 to 5.6.4
    I can then upload an old saved map to the ecu which is on older firmware 5.1.1. The result is the ecu and map now reports old 5.1.1 firmware again.

    Sounds like Firmware is tied to maps NOT ECU.

    If it was tied to the ECU and remained in the ecu then when you attempted to open an old map the PCLink software could say something like "You have opened a map on older firmware then your ECU is running, would you like to upgrade this map to match ECU firmware"

  9. Sure has. (I think you can see that info in the attached log? Maybe not...)

    I'll go around to the owners house and copy my map over. Update firmware again then save the map, STORE etc. Start a log and crank then i'll upload here again if I have trouble.

    QUESTION: Updating firmware while you have a map open: Does this FIRMWARE update also update the map file you have open?

    I.E. If I update the Link FIRMWARE then I open an old map file it will be on older firmware right? So FIRMWARE is tied to a map file NOT the ECU?

  10. I'd like to add my vote for the addition of optional 2D graphs as well...  I like switching between 3D and 2D in other platforms to quickly find areas that need a little more attention or being able to identify trends to speed up mapping certain areas, as well as just another data point for finding bottle necks in setups.

    Exactly! I thought surely i'm not the only one! It's sooooo much quicker this way to get a nice fuel curve at all load zones. I can tell tuners who don't do this when i look at their maps in 2D. A complete MESS

     

    I have a done a few ITB set ups recently and I would highly recommend the setting the load equation as MAP and then set the load axis in the fuel/ignition map as TPS.  Most of these setups were using the Modelled fuel equations.

    But then do you go on to use open loop Target lambda also? Modelling fuel I am not sure I can use as I just don't have all the exact variables it calls for.

     

    I see you are on firmware 5.1.1, I would consider upgrading PCLink and firmware to our latest as there have been changes and fixes to TriggerScope.

    Got the owner to follow the firmware update video. Firmware updated still no scope (max voltage on both triggers 0.17V (just trigger noise)
    I'll have to have a play with this. Possibly create a new basemap from scratch and try

  11. These are VERY old screen shots from Hondata but you get the idea.

    First pic shows a badly tuned map (you would struggle to see this quickly in 3D mode)
    (purple line at the bottom is low map kPa, top green line is high map kPa load full throttle)

    fuel-old.jpg

    Second pic shows fuel curves tidied up. 

    fuel-new.jpg

    I use the software below where you can see your Raw values AND the graph at the same time (as you can in PCLINK just not quite with the graph I am after)

    NepTune.jpg 

     

     

  12. You guys are EXCELLENT with your response time! Cheers Scott

    Regarding the Scope I also recommended updating firmware but the owner got a error 1019 when attempting this. Then he got a success afterwards but it still reports older firmware...
    I'll try to carry this out myself (the car isn't with me right now it's at the owners house)

    I will try the target lambda method provided the logged AFR is accurate and stable enough (noisy analogue input), it sounds like a fancy method but I'm a little wary of allowing a wideband and unstable map to make further adjustments to my tuned TP fuel map. (I can try in future and see) It all depends on how you scale the target lambda map vs load axis I guess...

    I have dead times but not short pulse width adder data. They are Honda RDX injectors (Factory injectors from a US Spec RDX) So my fuel model won't be super accurate (maybe i'll stick with traditional in that case)

    Regarding the current draw when driving TWO soleniods I assume there will be a spike of more than 0.5 AMPS as you say when opening both at once. Holding both open after that possibly not... Thanks for the recommendation though.

     

    I'm surprised with the CRAZY amount of features and years of development that no other tuner has requested 2D fuel and timing maps? Maybe it's just me? Then again you use different fuel models (VE and modelled fuel)

    When tuning fuel maps with injector time and you tune for a FLAT AFR under full load, it's great to see 2D fuel maps. You can see where the motor demands more or less fuel. It also matches the torque curve of the motor on the dyno vs your engines fuel demands.
    I'm sure you would see this in VE also (where motor demands more fuel)

     

  13. Hi there, well it's my first time ever using link software but I have tuned MANY engines before using flash tune, chip socket, Haltec etc.

    Engine: C30A NSX engine running large cams and 6 ITB's.

    Trigger 1=Stock 24 tooth VR NSX (cam driven) crank rotation trigger

    Trigger 2=Stock 1 tooth VR NSX (cam driven) cylinder sync trigger

    QUESTION 1: When cranking the engine we get a YES for trigger 1, then very quickly a YES for trigger 2 and RPM of around 180RPM while cranking.
    ZERO trigger errors and we log engine cycles as we keep cranking.
    **BUT SCOPE TRIGGERS RETURNS NO DATA** Even when we chose capture for the trigger while connected and logging the ecu and cranking.

    I don't think we have any issues with the triggers but it would be nice to confirm the arming voltage at cranking using the link Scope software.

    QUESTION 2: I got this NSX map from someone else and it's not really to my liking for ITB and big cams. The link help talks about tuning an NA motor with unstable MAP (that will be us) says to use load equation=BAP and fuel and ignition y axis=TP Main. (Makes sense to me)

    THEN the Lambda target table help section talks about how G4+ is very good with ITB's and to use load equation=MAP, open loop lambda on so that the MAP axis of target lambda can make adjustments.

    So which is the best recommendation for a NA motor with ITB? (We are running a map sensor to a vac box off the runners)

    QUESTION 3: Should I scrap this map, update the firmware and just use modelled fuel (this map using traditional and the Xtreme Red is on old firmware so I can't choose modelled yet.)

    QUESTION 4: NSX motor has dual vtec solenoids. Can I use AUX5 to drive BOTH of these high side vtec solenoids with no relay. OR should I use individual AUX5 and AUX6 for each wired separately? (ON at same time of course)
    Stock NSX ECU drives both solenoids at 12+ from ONE ECU pin I believe.

    QUESTION 5: How can I view the fuel and timing maps as a 2D graph (showing lines for EACH load/TP scale) I find this MUCH more useful than a pretty 3D map. 2D more easily shows if lines are crossing over or any ugly basemaps.

    I have attached the map and also a log while cranking (Fuel and Spark disabled in this log hence no injector duration or spark dwell etc)
    I have NOT finished with my fuel and ignition RPM scales or ignition timing map. So it's a bit of a mess. I have made the maps dual fuel and ignition (like a Honda ecu) for more RPM resolution. 

     

     

     

    fuel 1 changed.pclr

    cody 2.llg

  14. Thanks for the reply Simon. Ah well I guess we are stuck with this.

    Looking over the manual it looks to be pretty terrible, no IAT readings, no alpha-n tuning for the ITB's (just a VEFIX hack work around)

    all in all a very old primitive product. I'll suggest he go Link G4 ;)

×
×
  • Create New...