Jump to content

mapper

Members
  • Posts

    367
  • Joined

  • Last visited

  • Days Won

    32

Posts posted by mapper

  1. I like to start a thread where everyone can add his Math channels, so a database is built. 

    Please only post Math channels with short explanation in this thread. 

    To keep it simple any discussion must be done in other threads. 

     

    Boost error channel = Target Boost - MAP

    Boost error parameter can then be used to control an electric Blowoff 

    Brake bias = (rear+ front break press)/ rear break press

    Front Wheelspeed Difference = LF wheel speed - RF wheel speed

    Used to tune your LSD differential settings

     

    Slip right = nondriven-wheelspeed - RR wheelspeed

    Setup an Aux and turn on a driver warning light on the right side of the dash. So Driver knows right rear wheel is spinning faster ( eg. attention after a curb). Add the same function another for left. Then it looks like this :-)  from 3.00min

     

    Boost error channel = Target Boost - MAP

    Boost error parameter can then be used to control an electric Blowoff 

    Brake bias = (rear+ front break press)/ rear break press

    Front Wheelspeed Difference = LF wheel speed - RF wheel speed

    Used to tune your LSD differential settings

     

    Slip right = non-wheelspeed - RR wheelspeed

    Setup an Aux and turn on a driver warning light on the right side of the dash. So Driver knows right rear wheel is spinning faster ( eg. Attention after a curb) to another function for left. Then it looks like this :-)  from 3.00min

     

    Boost error channel = Target Boost - MAP

    Boost error parameter can then be used to control an electric Blowoff 

    Brake bias = (rear+ front break press)/ rear break press

    Front Wheelspeed Difference = LF wheel speed - RF wheel speed

    Used to tune your LSD differential settings

     

    Slip right = non-wheelspeed - RR wheelspeed

    Setup an Aux and turn on a driver warning light on the right side of the dash. So Driver knows right rear wheel is spinning faster ( eg. Attention after a curb) to another function for left. Then it looks like this :-)  from 3.00min

     

  2. You can use the generated math channel as:

    - logging channel 

    - input for other function 

    - axis option on tables

    So it's up to your creativity what you can do. Combined with Virtual Aux and timers the possibilies are near endless! 

    A few example:

    Boost error channel = Target Boost - MAP

    Boost error parameter can then be used to control an electric Blowoff 

    Brake bias = (rear+ front break press)/ rear break press

    Front Wheelspeed Difference = LF wheel speed - RF wheel speed

    Used to tune your LSD differential settings

     

    Slip right = non-wheelspeed - RR wheelspeed

    Setup an Aux and turn on a driver warning light on the right side of the dash. So Driver knows right rear wheel is spinning faster ( eg. Attention after a curb) to another function for left. Then it looks like this :-)  from 3.00min

     

     

  3. A easy layout with such button woulf be good for the End-customer.  I would like to setup a layout page for the customer so he can access active test and clear of error code. All other areas of the ECU should be protected or even better there should be access control for every setting. 

  4. On 1/12/2019 at 6:43 PM, Grant Baker said:

    Currently we support a race car that used to run a complete Motec M1 setup with dash, PDM, ECU etc etc.

    He's now got a Fury installed instead of the M130. Engine is running much better... But... Logging is now a massive pain!

    Essentially we log all of the engine data and as much as we can via CAN, but we have run out of channels and can't overlay engine data onto a circuit map, so the result is we use MoTec's i2 for viewing data against track maps. The problem with this is we can't get all of the data into the dash from the Fury! So we have to use 2 different log analysis programs...

    If Link could implement GPS data I think that would be absolutely awesome. In this case, we could probably move the car over to the Link (AIM) Dash as well and not use i2 at all.

    If you have a C-dash you should be aible to program a custome can stream from Furry to Dash with all data you need. 

  5. 23 minutes ago, Shedley said:

    Yes indeed, what brand Rotary switches do you prefer? 

    I'm using AEM 30-2056 and for Highend Application Motec 9 Position. Doesn't matter much which one you use, it just should give you signals between 0 and 5 Volts. 

    Besides, Adamw / Link ECU that would be a nice Accessory in your product lineup! 

  6. If you use a calibration table with Volt input and integer position numbers (1-12) output, the output does only change in steps of 1, so no problem between interpolating. However, if you have a 12 Position Switch for example Launch RPM, the Launch RPM would only change negligible little. 

  7. We use up 4 rotary switches on some cars. 

    12 pos Launch RPM

    12 pos Torque Maps, VA to switch between 3 boost strategies (TP, RPM base, straight) with several Boost Targets. Alter IGN on some maps.  

    12 pos Traction Control Targets

    3 Pos Switch for different E-throttle Targets

    You can do quite complex setups and much more than the Average Joe may think is possible with LINK. Only limiting factor is the overal number of 30 tables. And 4D,5D,6D would be nice for boost. I would also like to have a few more Fuel and IGN overlay tables (7D,8D,9D...). Same for traction control. 

  8. On 12/7/2018 at 10:37 PM, Shedley said:

    Interested in full Rotary switch support as well, so we could alter for example traction control slip %, als setting ect without the need off VA

    You can already do that. Just setup a anloge input for rotary switch. Use eighter direct voltage or use a calibration table to output position. 

    Use rotary voltage or position as an axis for launch rpm, traction aim, boost aim, etc. 

×
×
  • Create New...