Jump to content

Cozcorners

Members
  • Posts

    61
  • Joined

  • Last visited

Everything posted by Cozcorners

  1. @Adamw Just a thought... Is there a way to send a datastream from the link thunder ecu to my AEM cd7 dash logger, so i get a image/sign/light of some kind that will tell me if the ecu is in logging mode?( say a image comes up that says "logging" as soon as the thunder ecu starts logging. That way i'll know if the thunder is logging, and if it doesnt, ill be able to keep a record and report it etc?
  2. Excellent. ive just added it and tried it, works like a charm :) Again, thanks for the excellent support as always :
  3. Ok, i found the MGP in the Links software, so i added it for logging wich will make it much easier for me when viewing logs...awesome. However, i cant find MGP when im searching it in the AEM dash softwhere! to add it as a stream. Theres intake manifold pressure (MAP)( wich ive been using ) And there Boost pressure, could this be the one thats MGP?
  4. haha sorry, i realised PSI is not metric, but i hate KPA so i use the USA Imperial for pressure haha, the rest is metric like speedo etc :) Yes, using MAP...Ok, ill try to see if i can find this MGP in there, thanks alot, i knew there must be something im doing wrong :)
  5. I am after a hopefully simple answer. I have a thunder ecu and AEM cd7 dash. The ecu is setup to read metric(PSI) and so is the dash, but my boost/intake manifold pressure is reading in positive reading while at idle( my case 9psi on idle). Am i to understand its reading this number 9psi because atmospheric pressure = 14.7psi , so take away my vacum at idle ( in this case 5.7psi), and i end up with a 9psi reading at idle? I mean the ecu does the same thing, to figure out my boost pressure, i have to always minus the 14.7psi of total. Is there a simple way to delete the way the ecu see's this 14.7psi atmo? can it be setup to read in negative for vacum, and positive when under pressure? basically the same way a normal gauge would work if you hooked it up?
  6. Aem have a setup file for link ecu on theyre forum. You need to select that in the can setup software and select a layout. Once done you upload to ecu. Link ecu also has a few setups needing adjusting in the can stream tab. Which part are you struggling with?
  7. Can you guys that have traction control somewhat working, post the setup screen/values screenshot please so i can use as a starting point? I have the 2 settings setup/button (traction off/traction on) for now but will go for multi setup once its figured out. Cheers
  8. Did you check your injector settings in the software?
  9. Nice. How would i setup to start logging above a certain speed like 25km until engine off? Thats a good idea. Yes i want to try for it to log only once and stop when engine off, that may be the fix for my intermitant logging on and off.
  10. Thanks Andy for another suggestion on how i can set it to start logging. Is there a reason why this method would work better then say set the activation trigger rpm at >500(or any other low number like 200rpm) in the normal logging setup? Or did you try both ways and found your method fixed the "sometimes not logging issue"? When setup via normal activation trigger in the logging setup... Cheers.
  11. Thanks for letting link know, good to see im not the only one with the issue. Maybe more people will come in after reading this post. Problem is, i like to download the log after every race , i dont let it get full. But still dont understand how after many cycles and 2 race sessions i only ended up with 2 and a bit minutes of log! When did it start to log? When did it stop? And now currently logging again! Just weird...
  12. Ive been thinking... Since i have it to start logging from 800rpm, what happens is when my car is cold, it will idle at say 700rpm(no idle motor), gradually as it starts warming up the idle will raise and get to the point where the logging will start, but whats happening(i was watching) the logging would flicker on/off/on/off etc constantly for a good say 30sec until the engine warms up more and passing the 800rpm threshold and settles to a 920/950rpm idle once fully warmed up. During this constant on/off, maybe at some point the logging freezes and stops recording because its going haywire in those 30seconds or so. But in saying that, that would also happen if you were to set it to turn on at anything say over 5% tps, or anything over 1psi boost etc... during a race it would also be going on/off hindred times... What i might try anyway, is for it to start logging at anything above 500rpm, that way it starts logging at first startup and doesnt stop logging until switched off( that way i eliminate the flickering on/off of the logging when my idle reaches the 800rpm point ) does that make any sense what im trying to explain? If you can try mimicking the on/off constantly and see if it freezes(stops logging ) at some point that may show up? But you cant be resetting the power to it as you may miss it freezing up, just like how it started working again on mine after i power cycled again...
  13. hi Adam. I sent you the file via your email. I tried inserting it here but there is a very low limit of 143kb size so wasn't able to, unless I'm doing something wrong? Let me know if you find out anything please. cheers
  14. This is what i got out of it today I then started it today to see if it was logging without any changes, and it was as you can see the highlighted. Then checked the log again and you can see it logged another 30/40seconds or so...so its working!
  15. It actually had 2min or so (but i say that was nothing because it should have over 20min of logged data, the 2min or so is just from idling, must of been when unloading it off trailer or such), i know this as i checked it and water temp is cold and no reving past about 3000rpm ,but the log should of been a lot more as i had 2x sessions which were about 15min ea
  16. Its the 2nd time now that my link thunder hasnt logged... first time was at world time attack 2017 and i had i believe Rob from the link stand look at it. When he went to check it it was setup to log at anything above idle and when he looked over it and had me start it, it was showing to log, but had no log of previous run/session. I then had a practice day 3 days ago and went to download the logs... nothing, no logs of my 6 laps or so! I would of cycled the car a few times by getting it off trailer, doing 2 sessions and then putting it on trailer, unload back home etc... I have the setup to start logging above 800rpm. Anyone else had this issue? Ecu firmware 5.6.5.3389. Pc link firmware 5.6.5.338 build date 15 feb 2017
  17. Yes ok, so your covered for the oil and fuel pressure protection ( which is what i was saying i found out ).. but say you want AFR protection as well? Wheres the 3rd gp limit???
  18. Hey guys. Looking through the software last night to see how the engine protection is done for fuel and oil pressures, read the help file and seen that you use gp limit for oil and fuel pressure. Noticed on mine(thunder), there are 2x gp limits... gp limit1 and gp limit2 (under engine protection )... my question is, what if you need a 3rd gp limit? Say i have oil and fuel pressure setup for those two limits, how would i setup a 3rd limit for say lambda/afr? Is there a seperate limit for AFR? Just trying to figure this out before i decide which parts i would want for protection etc. Cheers.
  19. All good, i have been in tuch with AEM before posting that and had a reply in the meantime. It was just in the settings and CAN ports used. The manual was a bit hard to follow for me so all the cans and ports got me confused, but all sorted now and works awesome. Thanks again
  20. Hi Scott. Any chance you can do the same thing but with a AEM cd-7 and link thunder ecu? In the link software i have everything exactly as per your pdf file and have the can wires from cd7 running to the thunders wiring harness D plug can1 hi and can1 low. I however get lost when dealing with aem dashdesign to configure theyre end! Cheers. Danny
  21. Ok cool. I'll try putting series2 sensors see if they are better at it then the series1 im running at the moment, they may have made them better perhaps
  22. Ok, ive had some success. Went for a drive and im getting all 4x wheel speed sensors to work and show on my logging. Some issues tho and not sure whats at fault, so maybe someone can give me an idea what to try? Rear wheel speed sensors come on fairly early on, around 12kmh, so pretty good. Front wheel speed sensors however start coming on at about 28kmh! So a bit later then what id like, is there anything i can do or try to bring that sensativity earlier on like the rears? Once im 28kmh and over, all 4x are nice and smooth and speeds match fairly well to my dash speedo from what i could see at lower speeds. In the calibration file, i have 2450, i havent tuched this myself so i assume my tuner did, does that sound right? (295/30/18 wheel), and pullup resistor is OFF. I read the help file and it states usual calibration numbers are 170 to 280...so thats way off. I did a quick calculations of my diameter which is 0.634meters (295/30/18), and my abs sensor rings have 48 tooth, so.... 48/0.634×31.83 = 2409.8, so the inputed calibration number is not so far off! Not sure how the extra 50 in the calibration could affect my front sensors picking up speed earlier? Should i try this number?
  23. Ok, another simple question There are two sets of wheel speeds i can take to log from! One is the wheel speeds from the "digital input" folder and the other wheel speeds are from the "body and chassis" folder. Is there a difference between the two, and if so which one to use for logging?
  24. Thanks Adam. Ok thats good to know it still works even tho theres a bug(i assumed its not on due to what it stated). I only spun it by hand, so maybe i cant spin it fast enough like you say. I'll try over the weekend one day to go for a spin and see what happends. Thanks again, much appreciated
×
×
  • Create New...