Jump to content


  • Content Count

  • Joined

  • Last visited

About M1tch

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Thanks for that, I will see if it's the tablet going to sleep etc, I can see it's recorded 7 minutes of data so thought it should be ok. Guess I will go out again for another drive with the logging on. Luckily this should only be a slight tweak to the map, fuelling seems to be about right.
  2. Hi all,200419.llg I have just updated to the latest PCl200419 v2.pclrink software, just been out for 2 runs to log the data, just got back and dropped the log data into the file to look at the mixture map, only 1 cell is showing with data? Previously the whole mixture map was showing so I could see where I needed to correct fuel. I have a fair amount of data showing on the log file but it looks like I now have to check manually through every cell to be able to see what my fueling was like - this is a rather backwards step! Not sure whats wrong with the setup - have attached the log and map file - can anyone see what I am doing wrong? I am using a tablet to log the data, does it matter at all that the screen is off when logging? Seems to have a full log of data but can't see to get it to correctly show all of it in the mixture map?
  3. The current version I just downloaded from the windows store doesn't seem to work on my windows 10 tablet, it starts up but then just crashes out, shame as it would be great to have a dash.
  4. Are we ok to run the in the downloads folder? I held off updating mine when I saw this post a few months back.
  5. Thanks for confirmation, yeah these are stock cam at the moment, but as you mentioned, maximum advance isn't going to give optimal performance, when I was running the antiquated PFC I did try back to back with the VVTi tables optimised vs all 0s, made quite a difference in low end torque. I was using the 1UZ basemap as a starting point as I didn't have any other VVTi figures to go from, not ideal but going from a table with all 0s to the 1UZ map has yielded a fair improvement in drivability low down although not optimal. I did fire up FCEdit again last light and loaded one of my old PFC maps, I had been using them to check the maximum ignition timing the engine was running on previously (was using Copilot to log and adjust ignition depending on knock), I have matched up the PFC map with the Link map, it would seem that full load on the PFC was at around 11,500 - as the engine is NA that would equate to full vacuum, I had previously logged which cells were being read from as well and can match this up using the mixture map view. I believe the maximum value in the PFC for VVTI was at 28 or 30, 55 would be the highest value in the PFC so that would equate to between 25-27 in the Link so might nudge back the VVTi figures using the 1UZ or perhaps one of the basemaps to get the curve. I think I also saw a setting within the Link help file that stated that I can set it to degrees advanced rather than degrees from fully retarded which might mean I can use the figures from the PFC. I will be going a few drag runs in the next month or so, will be logging data for each run and might do a few adjustments where needed, I did find however that the VVTi optimisation is only really useful at the lower RPMs meaning that for a 1/4 mile drag run it will only be of use in 1st as after that the RPM will probably only drop to 4k or so between shifts so it will probably only run through the VVTi cells once in each run. @Adamw thanks for confirming that if the VVTi goes fully advance it shouldn't cause issues from a mechanical standpoint - that is mainly what I was concerned with.
  6. Apologies, I didn't necessarily mean 'aggressive', and I know that road tuning the car won't get my the perfect tune as there is no way of measuring wheel torque etc. Was about checking if it was ok to use the basemap VVTi figures as the +55 setting for VVTi would be at its most advanced - just need to check that this won't cause issues with piston and valve clearance considering it is a generic starting basemap which I would be guessing would be a safe starting map. I have some VVTi settings from some previous tuning on the Apexi PFC which I think were optimised closer to the 1UZ from memory (in terms of maximum advance) - unless of course the PFC and Link ECU are opposite in terms of what is the maximum advance number.
  7. Hi there, I have currently got a VVTi inlet target using the 1UZ basemap which uses the TP vs RPM to work out the VVTi, I have also had a look at a few of the basemaps for the black, Xtreme as well as the Altezza VVTi values (3S-GE I believe), I think the Altezza one uses a MAP figure vs rpm for the inlet target. Just wondering what values I should use on my 1zz engine, should I look to run the base values from the Xtreme basemap? I can't really tune VVTi on a road tune so would just be looking for the most aggressive but still safe set of values - the 1UZ map has a max value of 35 (35 degrees from fully retarded), the Xtreme basemap pushes this to 55 which is fully advanced (tailing off at higher RPMs) - just checking that this should be ok to run considering its a basemap so should't cause any issues. Thanks in advance!
  8. I have DI#1 set as the speedo in from the OEM loom from the ABS and the calibration number I have works, I have grabbed a DI output and its set to be 'speedo out', there is a folder further down which has the speedo correction figure (percentage or offset etc) - am I correct to say that it will automatically use the DI Speedo out as the output or is there somewhere I need to configure the ECU to tell it what output to use?
  9. I have gone into the map and pulled timing in that cruise cell - think it was up at something like 35, have dropped it to 28 as per the cell next to it, will also see if I can log the knock next time I am out and driving - its only got a narrowband OEM sensor but will see what the knock is like. Its a 79mm bore so going with the 7KHz option. Will be swapping to a better Bosch 'wideband' knock sensor at some point, but its impossible to get to the stock sensor with the engine in the car. Might look to change the ignition table further by using one of the basemap files - the car is running on V power so knock should be under control slightly better than say 95.
  10. Hi there, Its a Toyota MR2 roadster (mk3), it does use a Canbus, reading further here is the current setup: ABS sensors > ABS ECU > ECU (1hz = 1mph) > Instrument cluster The speed signal is being intercepted by the Link, I think I came to the same conclusion as yourself with where the speed needs to be intercepted, I was initially thinking: ABS sensors > ABS ECU > ECU (1hz = 1mph) > Link ECU > Instrument cluster However to your point it would make sense to intercept it before it gets to the ECU so: ABS sensors > ABS ECU > Link > ECU (1hz = 1mph) > Instrument cluster I think to make it work I just need to feed an output from the Link to the input on the ECU for the speed signal - should be as easy as simply cutting the original feed into the ECU and repinning the connector to take the output from the Link - basically feeding the stock ECU an adjusted signal. I had a look at the link yesterday, I selected a spare digital output and set it to 'speed out', how do I configure the Link to take the input and send the adjusted output to the output? I can see the configuration for the speedo adjustment in the settings - does it automatically use this figure as I have set the digital out as a speedo out in the function list drop down? I will at some point need to tap directly into the ABS ECU for signals to enable traction control, but that's a bit further down the road!
  11. Hi all, Currently my stock ECU is running the instrument cluster (as well as a few other functions), I am looking to swap out my wheels and tyres so might need to adjust my speedo to correct for the different size, there is only 1 speed signal that comes into the ecu (Link is reading this as DI#1) and is at 1hz per 1mph. The Link itself isn't connected to the instrument cluster at all it seems meaning that any correction on the Link won't affect the instrument cluster so I am looking at how I could get the Link to run the cluster. My guess is that I could just use the stock wiring loom and use a digital output to the speedo on the instrument cluster instead of the stock ECU running it? I am thinking that if the rest of the cluster is powered and everything else is run on the stock ECU the cluster would just need the speed signal fed through. I have the pin outs for the stock ECU somewhere, guessing I can just configure one of the digital outs to send the signal adjusted on the Link? I can see the tach input and output but can only see a speed signal coming in and there seems to be a data line going to the instrument. I guess I would need to check the signals at the back of the instrument to work out which one is the speed in at that end? I know that the stock ECU is running the instrument cluster as I have set the Link ECU to sweep the rev counter on start up (which it doesn't). I am guessing that instead of trying to find a speedo out signal I could feed the speed in signal into the link into DI#1 as it is at the moment and then output it via another DI and feed that output into the input on the stock ECU meaning that the Link can adjust the speed signal before it gets to the ECU to then be sent to the cluster. Thanks in advance!
  12. Just wanted to thank you for your help on this, that calibration figure seems to be about right! Also looks like the ECU has worked out the gear number as well which is great
  13. Thanks for that, yeah I grabbed the 350z table combined with one of the Toyota VVTi inlet target tables as well based on TP, just taken the car out for a drive and just checking the logs now. I noticed/could hear what I think is a bit of pinging on cruise at low load, fueling seems to be about right so might need to retard the ignition slightly.
  14. Hi all, Just doing a bit more tuning on my NA 1zz, idle MAP is at around 30-35 so I am aiming for an Lambda of 1, full vacuum is obviously 100 - car is currently not boosted so won't be using any MAP value above 100 at the moment. I have it current set to aim for around 13.5:1 top end, might look to richen it up slightly 12.5:1 - perhaps using a basemap for the 350z as an option. What does everyone think? Current Basemap for 350Z:
  15. Thank you, will check to see how close that figure is, hopefully then I can work out launch control!
  • Create New...