Jump to content

AbbeyMS

Members
  • Posts

    210
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by AbbeyMS

  1. 57 minutes ago, Japtastic141 said:

    Sure, here it is:

    https://drive.google.com/file/d/1mQtrxLFBgl6IUbwO945mr6Lz9PK1QaWj/view?usp=sharing

    I'll double-check this but pretty sure it does. Report back later.

    Yes, it's been mentioned a few times in this and other groups how bad it is. Not sure why. After speaking to Mark he kindly offered to lend me an NZ one to test but I think it's just better to upgrade to the NZ trigger kit either way. This CAS is 32 years old (with AEM disc) so has probably seen better days.

    After thinking about it overnight I was also under the impression that it probably won't fix my FP issue as this is mechanical rather than ECU-controlled but maybe I'm wrong..?

    Adam , also the fuel pressure output isn't good either , MAP output is good thou. 

  2. Looking at the logs again, are the log files direct from a laptop log or via the logging memory in the ECU just to know the logging frequencies?

    The reason I ask and i am sure I have asked this before the RPM and fuel pressure sensor out are terribly unstable, the map sensor signal (output) isnt thou.

     

    image.png.e8ef837a239de7cc773c2ab3b1785855.png

     

    I find it very hard to understand why the fuel pressure is dropping off even at base boost?

     

    can you clarify what base fuel pressure is please , 1- with the pump being run via the test output (so no possible issues with interference etc) 2- with the car running with the boost ID removed from the fuel pressure reg,

     

    can these be logged at the highest frequencies (500hz +) please to see whats happening with the outputs please.

  3. 5 minutes ago, wastegate said:

    So at QR raceway here in Brisbane, Australia, we have had a couple of fatalities from throttle issues being stuck or not closing. Not to say this was ethrottle but more the fact there was a couple of deaths because a throttle failed. 

    Disabling safety features because you want to come first is the first way to the morgue. As a father of two, I hope for your son's sake you don't risk it.

    To put it in Australian, "Don't be a bloody idiot"

    so what happens with cars with a throttle cable, been around for years and they do have issues with bad installs or heat from a turbo/fire. What happens when a throttle cable sticks only thing is to turn the car off. 

  4. On 4/4/2024 at 10:58 AM, RobPhoboS said:

    Very small update on this.

    I checked the wiring, and it ended up being the bank 1 sensor dead. I've replaced it, thankfully I found the exact same Bosch sensor as it turns out they have changed the connectors.

    So he must have told me there was a problem with it and that it was only tuned with data from bank 2. Quite a long time ago now so I cannot recall what was said at the time.

    I've kept the sensor but I presume each sensor is calibrated, so you wouldn't just be able to cut the old connector off and switch out the new one?

    I did email them 2 months ago but still no response, so I'm going to my local place to get the map sorted out when I can. I did a short test log only at idle to make sure it worked and yeah both banks are correcting differently (bank 1 seems to correct half the amount).

     

     

    to save me reading up are you running can lambda or analogue input lambda's system?

    this will help us understand what your trying to sort? 

     

  5. So back out with the car last week , Datalogging set up to trigger just on RPM , making sure the log pop up is turned off before pulling the USB, 10 sessions all with data. So next time I think I need to add the old datalog trigger set up and see what happens

  6. After testing I've noticed if you dont close the log download window before disconnecting the ecu USB. The ecu logging status will say hold logging for download. Upon reconnecting to the ecu the logging status displays the "hold for download" message and when trying to download a log there is nothing in the memory. 

    To get the ecu to start logging again I have to reopen the logging download window and close it while connected to the ecu to get the logging status to say OFF then the ecu will log again.

  7. 12 hours ago, koracing said:

    Running a richer AFR target will also aid in reducing cylinder and exhaust temps. Typically on pump gas, I target around 12.7 AFR (gasoline scale) or .86 Lambda at 0psi (101kpa MAP) and by 10psi (170kpa MAP) I normally target around between 11.5 AFR or about .78 lambda.  EGT I don't like to see over 850-860°C.  I may be a bit more conservative on my targets than most, but I would rather give up some power in exchange for longevity.

    You can pull and inspect your spark plugs also to see if it has evidence of running extra hot.  Just FYI aluminum melts at 1300°F, and it's the intake air and fuel that cools the pistons during the combustion cycle (as well as oil splashed on the back/bottom side).

     

    Everyone tunes a little differently , I feel 0.86 at 100kap is far to rich , these cars feel woolly when running those numbers dont spool very quickly.

    Totally agree the EGT's are a little worrying pretty easy to add some fuel via the open loop lambda map now the fuelling is pretty close. Just drops the numbers of the lambda/AFR to richen the car up a little and see if it does change the EGTS at all.

    As we all know controlling EGT is all about a combination of things. 

  8. AFR/LAMBDA looks a lot closer now.

    Regards EGT , yes a little hot , I would say the car needs some more ignition timing in the map this will lower the EGTS as the energy for the combustion will be used more than wasted down the exhaust port.

    Are we happy that the timing commanded in the map is what the car is actually running, something that could be verified on a dyno under a constant rpm load with a timing light, while I think about ignition timing how did you check the trigger offset , did you add a HT lead in between the coila nd plug on cylinder 1 to attached the timing light too or did you use the loops at the back of the cylinder head?

     

    Wonder how many cars have been tuned without EGT measurement?

     

     

     

  9. 10 hours ago, Knox said:

    Hello, I tuned a nissan 350z with g4x plugin ecu. DBW throttle gives error sometimes when "ON" mode. Error code is "ecu fault code 69" which is E-throttle Max DC error. But on setup mode there is no error. How can I solve this issue?

    Thanks.

    are you using the PID that Link supplied or have you tweaked the PID  numbers? Looks like the throttle body been driven to hard open

  10. 15 hours ago, koracing said:

    I will admit I don't have a lot of RB26 experience, but this table looks a LOT leaner than I would typically tune anything on boost on pump fuel.  Can you elaborate your reasons for this target table (i.e. 14.7 AFR gasoline at 7.5psi of boost)?  Is there something special with the ITBs and boost that would make one decide to use leaner values for some reason?

    This seems very hot to me as well...

    The multi throttle bodies on the RB , change a few things, if you map in Speed Density (RPM versus MAP) your have to have a throttle compensation map to adjust the fuelling at smaller throttle openings 1 bar boost @ 100% throttle  at 4500rpm needs different fuelling than 1 bar boost @ 60% throttle at 4500rpm. Moving over to Alpha n with overlay lambda removes the need to have a throttle compensation map.

    0.5bar boost will not normally be seen at full throttle , it will be seen on part throttle or transistion to a higher boost level. 50% throttle at 0.5 bar @ lambda 1.0 wont cause any issues in my opinion now seen in all the years we have been tuning RB's also makes the car have super snappy throttle response .

    looking at the screenshot of the log file above the map was 0.68 so was bleeding into the higher map level on the  AFR layout table, log shows 13.2/13.5 not 14.7.

    image.png.632b1ebe5fcf05a1d68a213ca5a81a99.png

     

    Maybe we can see the ECU log file?

    This is how I work with an RB with a Link ECU on multi throttle bodies, an RB on a single throttle body doesnt need tuning on Alpha N, it is easier to tune the car on Alpha N on a dyno thou and faster as you can pick up all the map points easily

    Thanks

     

     

    16 hours ago, Japtastic141 said:

    Thanks, will do.

    Does ECU logging look any better? Looks about the same to me.

    image.thumb.png.5a3ec91e9fad75afcbec4f5927b72a9a.png

    BTW Went out and logged some more and looking pretty good across the board imo. Well happy with the way the car feels. Turned the boost back on to 1 bar and did some hard pulls. Worked a treat and still tracked AFR target well!

    EGT's max out at around 1050c

    The EGT's are they from running 1.0 bar boost? you can try very easily to run a richer/fatter fuelling by just adjusting the AFR layout map number , try lowing the AFR number by 0.2 , the fuelling will instant track a richer mixture by 0.2AFR without any work on the main fuel map.

    The RPM log looks better now it is being logged at 200HZ, so the irregularity on the RPM logs before must of been the low log frequency it was being logged at. 

     

  11. Fat means too rich;

    You really need a faster responding IAT sensor, this will help with tuning;

    Laptop logs are a little slow for trimming the fuel map I find your only logging @ 40 hz.

    I have modified you CAL for internal ecu logging at faster HZ, your need to download the data from the LOGGING drop down.

    CLL fueling is set up , I have just raised the ECT start temp to 125 deg C to stop CLL working until you want it to work

    I cant attached the CAL here,  I also cant find our emails between each other , email me @abbeymotorsport I will fire you the new CAL back

     

     

  12. you are a little rich(fat) at 100% throttle, looking at your log file, this maybe the kick in the top of the map your mentioning. The map shape is good , far better than the initial fuel maps you posted.

    What IAT sensor do you have fitted , the IAT temp changes are pretty slow on the logs, your also pulling too much fuel @ a low IAT value in my opinion, I wouldnt start to pull fuel until 38/40 deg IAT with a fast responding  IAT sensor fitted.

    The logs you are hosting for us to view are they coming from the computer or via the ECU log?  the RPM signal looks pretty unstable , maybe due to log frequency or maybe due to something else.

    image.png.96ad36770f707617aa241b93c7693299.png

    Ignition timing looks a little low , this could cause issues with fuelling due to incomplete combustion

     

    Can we see the current cal (map) file as well please

     

×
×
  • Create New...