Jump to content

Adamw

Moderators
  • Posts

    19,853
  • Joined

  • Last visited

  • Days Won

    1,266

Posts posted by Adamw

  1. Im still confused by your explanations.  "I've tried using your method of searching for %AppData% which does bring up the Roaming folder"  Are you using the search bar next to the start button that looks something like this?   QTT7pr1.png

    If you type %AppData% into that search bar and hit enter, in the explorer window that opens up, what does the address bar at the top show (like pic below), is it different to the C:\Users\Administrator\AppData\Roaming location that your PCLink folder is in?

    XMFYgPt.png

     

    Can you attach a copy of the "corrupted" map.  

  2. Ploting your existing calibration gives me a Y-intercept of -35, which is coincidentally close to -32, so I suspect 0V = 0°C or -32°F.  Playing around with round numbers for the span, I reckon 5V = 150°C or 302°F fits the best.  

    Your existing cal numbers in blue with my guess in orange:

    BMdD7jh.png

     

    But be aware, you still have a 1K pull-up on the temp inputs, so the gauge should still read correct, but the analog voltage that the ecu receives is going to be biased. That could be anything from a tiny difference to a massive difference depending on how the analog output is generated in the gauge.    

  3. 1 hour ago, AGalecki said:

    Should I change the metric units to the imperial AFR to get AFR, if that is what I want it to read?

    You can set whatever combo you like.  Some users like temps in deg C but pressures in Psi and lambda in AFR for example, so they would likely choose the imperial set then just change temp units to C in the imperial set.    

  4. Updated PDM and ecu file attached.  I also added CAN aux 2 in case you want to use that so the ecu can control the fan.  In the PDM config I changed the fuel pump output to use the ECU fuel pump request but I didn't change the fans. 

    Sorry I missed the PDM08 config, can you share that with onedrive/google drive/drop box etc. 

    The attached .xc1 is the custom CAN builder file for RS3, you can import this into the CAN builder in RS3 if you want to see how it is done. 

    For the VVT, it is more common to leave the fully advanced/fully retarded positions set to zero, then your target tables are just "degrees from home position" (and yes Ford uses negative for advance, Link uses positive).  If you set the fully advanced/fully retarded positions to the real measured lobe centrelines then your target tables use lobe centre.  Unless you're an engine dev that works in lobe centres every day you may find it less intuitive doing it that way. 

    I would suggest leaving the cam actuators unplugged until you get it running and the basics ironed out.  I suspect this engine will have "mid lock" phasers on the intake like the coyote and bara that use an active high signal and can move both retard and advance from "home" position.  

    Brady_7100TT-3.5L_V1.1.pcl5 LINK_Brady Custom_@20240311_005747_001265.xc1 Doteki 32 703 Brady V1.1.zconfig

     

    Edit - Added later:

    PDM08 config attached.  I have added DI rail pressure to the ECU CAN stream since you had an alarm set up for that.  

    Doteki 703 Brady V1.1.zconfig Brady_7100TT-3.5L_V1.2.pcl5

  5. To explain spill valve On duration a bit more; with a normally open type pump, when you energise the solenoid this pulls the valve closed, this allows pressure to increase inside the pump cylinder, once that pressure is above rail pressure then the valve is held closed just by the pressure pushing against it, the solenoid no longer needs to hold it closed.  The On duration only needs to be long enough to allow that initial pressure to increase enough to hold it closed, once it is held closed you turn off the solenoid to prevent it and the driver/wiring etc from overheating.

    BTW, once that valve is closed it cant be opened again until the pump goes past TDC which is why HPFP control is so tricky.  I think this engine should have a HDP5 based pump so about 40Deg will likely work for initial start up.  

  6. The MAP sensor trend doesnt look right to me, it idles at 100kpa and decreases as you open the throttle.  Is the MAP sensor connected to a port in the plenium?

    If the map sensor is connected to the plenum then the low vacuum and very lean lambda measurement would suggest the cam timing is out or an intake valve isn't fully closing.  

  7. 30-4402 is an oil temp gauge.  Or do you mean just the sensor from that kit is being used?  You cant connect both an ecu and gauge to the same sensor as they will both have pull-ups that will make both read wrong.  

    Sorry just looked again, it says oil/trans/water temp gauge.  I guess it comes with different faces or something.

     

  8. So you are using multi-tooth/missing trigger mode?  

    Since you have 4 cam teeth you cant use "cam pulse 1x" sync mode, Trigger 2 sync mode should be set to Cam Level, if it doesnt start with that set then your offset is wrong and you are sparking on exhaust stroke.  Try the offset at 235 in that case. 

  9. Your cal table for the temp sensor only spans from 40 to 170°F, 170°F is about 77°C.  In fact with only two data points I doubt it shows correct temp at all, a temp sensor wouldnt usually be linear.

    What sensor do you have?  Your temp sensor calibration will need to span the range of normal operating temperature.  

    nw3FGho.png

  10. %AppData% takes you to your personal appdata directory, every user on the PC has one, and this is where the roaming\PC Link directory should be.  If using the %AppData% shortcut doesnt take you to the roaming folder with the PC Link options and parameters cfg then it would suggest you are logged in with a different user account than what was in use when PC Link was installed.  I suspect this will cause issues such as your PC Link options and settings wont be saved.  

  11. I was just replying at the same time as Vaughan, will leave it here as a bit of extra info.

     

    2 hours ago, AGalecki said:

    Unfortunately the tuner I am using doesn't seem super familiar with the Link platform. He's tuned a lot of Link, but the interface to the devices doesn't seem super great. Can you screenshot where it is showing and how to select the lambda in the logging and toggle the type of unit displayed? He wasn't seeing it when we were trying to get the AFR to show.

    First lets confirm it is working.  If it was showing zero that suggests it is in error or the engine was off.  With the engine running, hit F12 or R to open the runtimes screen, use left or right arrow to move to the ecu status tab and here you can see lambda 1 status, errors, temp and measured lambda similar to below. 

    To change units you just hit the "U" key on your keyboard.  If you are not using an english keyboard then there will be an equivalent key, but the other way to get there is to go via the menu bar >options>units>options

    N33WKCx.png 

     

     

     

     

  12. With the ignition test set to "Ignition 1", the ecu is firing the output that is labelled Ign 1 in our pinouts.  Test "Ignition 2" fires "Ign 2" pin.  And those outputs should also be wired to the same cylinder number - So testing "Ignition 1" should give a spark on Cyl 1 coil, test Ignition 2 should spark at cyl 2 coil.  

  13. Something is wrong with your cam wheel or cam sensor wiring.  You are getting 1 pulse every 12crank teeth instead of one every 24T.  And their shape is distorted also, one goes negative first, the other goes positive?  Like it has a big long half moon tooth or something?  Or do you have both cam sensors connected somehow maybe?  

    4fCnnOK.png

  14. 14 hours ago, Adamw said:

    If the missing tooth area is under the sensor with cyl 1 at TDC then the offset should be near 0, +360 or -360.  -180 would suggest the coils are wired wrong or your TDC mark is not TDC. 

    Im not sure how to make it any clearer than that.  If your offset is -180 and the coils are wired correctly then the missing teeth are passing the sensor 180° before TDC #1.  

  15. The lambda was working when you last saved your map.  It will only give a reading when the engine is running.  You can look at the runtime "Lambda 1 status" to see what it is doing.  

    10 hours ago, AGalecki said:

    Also, would like to confirm that the lambda reading will equate to AFR in logging? Not just a lambda value of 0.x or 1.x?

    You can display in AFR or lambda.  U key is the shortcut to change units.  

     

    10 hours ago, AGalecki said:

    I can play with it, but are you able to walk me through selecting the CAN 2 for the gauge? Or is it correct in the map currently? It is not reading as currently set. 

    It is already set up correctly in the map you attached earlier.  If it is not working then there is either a wiring issue or the gauge is not configured correctly. 

  16. 5 hours ago, kaptainballistik said:

    I'm fiddling with maths blocks and is there a particular syntax  to make the equation equal a Virtual AUX or GP output?

    (summation of CAN EGT, Average, this is to equal "EGT" then do correction off this value deemed as teh EGT temp.

    You might have to describe that in a bit more detail, I dont understand what you are wanting to do.  

     

    5 hours ago, kaptainballistik said:

    Secondly, I'm also working on a DCCD output table , Is there a 3d "free' in the 4x That can be used for this?  Or something I can hijack (needs throttle, Accelerator input and  G sensor... Brake pressure would be good but I kinda expect thats a bit much!!)
     

    You can stack as many GP PWM tables as you like - put the output of one on the axis of the next etc.  Note however, I believe you really need closed loop current control rather than just a duty cycle for consistent diff control on a subaru.  Im not sure if the factory controller uses closed loop current, but certainly the Motec, gems and cosworth ones did. 

  17. Yes the haltech GPS speed sensor will work provided you have acceptable GPS reception where you want to use it and enough time to acquire the signal before needing it.

    The only thing to be aware of is your speed will be zero anytime there is no GPS reception so you will be stuck in low boost mode.  

×
×
  • Create New...