Jump to content

Tim Hardisty

Members
  • Posts

    29
  • Joined

  • Last visited

Reputation Activity

  1. Thanks
    Tim Hardisty reacted to Adamw in V88, CAN data for EGT, Ethanol and WG Duty   
    This is what I was using: 
    So in your CAN template you just broadcast "AN V6"  The ECU sees that it is configured to temp units by a cal table and scales the CAN data appropriately.  I tried both a linear calibration and a non linear table and got the same result over CAN.
    One catch to look out for is that last 0x0E frame gets shortened to 6 bytes, some devices might not interpret that correctly?
     
  2. Thanks
    Tim Hardisty reacted to Grant Baker in CAN DI for Antilag activation   
    I've set this up on 2 cars now and it works fine Tim.
    Done it exactly as Adam says, but I used Can DI8
  3. Thanks
    Tim Hardisty reacted to Adamw in CAN DI for Antilag activation   
    The setup below should work as expected.  You can invert the behaviour by changing the highlighted field to a 0 instead of 1, but I would expect 1 to be correct.
      
  4. Thanks
    Tim Hardisty reacted to AbbeyMS in Link CAN lambda and methanol   
    My 2 pence worth , 0.65 on Meths is super rich but the difference between 0.8 and 0.65 lambda is safety the power difference will be very small from what I have found.
    We we was running a methanol drag car we was running NTK sensors but was only using the lambda's as a reference we looked upon the EGT's to get an better idea on how the car was running.
    Running CLL on full throttle on the Link is something that I would like to do but we dont have the ability to change the closed loop control from low load to high load like Syvecs. I.e have a much smaller adjustment parameter when on high load parameters and it would be good to have the ability to change the CLL % to a different figure from +(add) to -(minus) again like Syvecs.
     
     
     
  5. Like
    Tim Hardisty got a reaction from Adamw in PWM Output based on DI Input and Timer   
    If it helps with creative solutions, the expander can be configured as a full bridge or pair of half bridges. I'm wondering if it would be easier to use a pair of virtual on/off functions to drive the half bridges - to open the flap one output, and hence bridge, could be driven on and the other off; vice versa to close it; and both off to stop movement.
    If the on/off was scaled in the CAN transmit setup so that "on" sent the value needed for 100% duty, and "off" sent as 0, then this might work?
    I know I said to send 50% duty when no movement is required, as for a full bridge that gets us a net 0% drive, but with half bridges that's not necessary (and, as an aside, a 0% duty request to the full bridge will actually cause it to shut down, for DBW safety reasons, but no in half bridge mode).
×
×
  • Create New...