Jump to content

TnF

Members
  • Content Count

    58
  • Joined

  • Last visited

  • Days Won

    3

Reputation Activity

  1. Like
    TnF got a reaction from SimonSTI in Assuming there is already an ADC for knock detection on board why can't you stream the filtered and/or prefiltered audio to the PC?   
    This will make checking and setting up the knock settings without needing to plug an external knock sensor and/or extra equipment. Knock audio function is already there.
    Of course this requires some bandwidth (not really much see below) but USB 3.0 or disabling logging channels to the rescue.
    For 32khz mono 16bit = 32000 * 16 * 1 = 512 kbps or 64 KB/s which is not much
    If the electronics required don't exist on current ECU's (i don't know about G4X, i only have G4+) you may consider implementing it in the future.
    Kind regards
  2. Like
    TnF reacted to Confused in PCLink 6.18.20 and Firmware 6.18.8 Released!   
    I get that Link are a relatively small company, with limited resources.
    I'm not expecting large features to be back-ported, but there are a number of longstanding known bugs and issues with the G4+ range (cruise active light, as one simple example that directly affects me), and we feel abandoned, because there's something new and shiny, and existing features on our product aren't working properly.
     
    I'm intrigued to see the new advances coming in the G4x range, and I might be tempted to upgrade in the future, but I'm currently wary about upgrading and having another issue that's left unresolved, as I've found has happened to me with the G4+.
  3. Like
    TnF reacted to Steve in Differential fuel pressure - Nominal fluctuation range?   
    I actually went from aeromotive fpr to stock when i started pwm'ing my pump.
  4. Like
    TnF reacted to Iguanapeluda in Windows tablet power from USB?   
    Try searching Voyo A1 mini.
    Has another port to charge 5v, is 8" and can connect with your link ecu
  5. Like
    TnF reacted to TechDave in [UPDATE] PCLink 5.6.5.3338b Released   
    That and a few other handy features are already on my list of "Things that would make PCLink much nicer to use as a tablet dash".

    Thanks!
  6. Like
    TnF got a reaction from v7sti_nz in [UPDATE] PCLink 5.6.5.3338b Released   
    It's been a long time since the last firmware update.. Are we getting something soon with maybe some of the requested features?
  7. Like
    TnF got a reaction from b3tuning in [UPDATE] PCLink 5.6.5.3338b Released   
    It's been a long time since the last firmware update.. Are we getting something soon with maybe some of the requested features?
  8. Like
    TnF reacted to Adamw in Launch problems   
    With aggressive ignition cut limiting on a engine with hydraulic lifters the large bangs in the exhaust port/manifold can lift the valves slightly and cause the lifters to "pump up".  This can play out in different ways depending on the valve train design.  SR20's for instance are almost guaranteed to through a rocker off.  Some other engines pump up enough for the valves to hit the pistons.  I dont think the 4G63 usually has much drama in this respect but I personally still wouldnt use prolonged ignition cut limiter if I had hydraulic lifters.   
  9. Like
    TnF reacted to Brad Burnett in Electronic throttle body   
    I find that 04-06 Subaru pedals are all over ebay for around $40-50 US.
    A while back I modified a Greddy manifold for SR20 with a Subaru flange to suit DBW sti throttle body.
  10. Like
    TnF reacted to TechDave in [UPDATE] PCLink 5.6.5.3338 Released   
    New release:
    http://www.linkecu.com/software-support/pc-link-downloads/
  11. Like
    TnF reacted to Adamw in Electronic throttle body   
    Further to Simon's comment, you can also use E-throttle for idle control and dont need a separate idle valve.
    You can presently have up to 3 E-throttle target tables, so to give an example you could have one for normal driving, one for when antilag is activated (which doesnt allow throttle to close beyond 15%) and another for say highway cruising that has a nicer response curve at small throttle openings.
  12. Like
    TnF reacted to Simon in Electronic throttle body   
    Any of the above would be good options. Yes antilag works really well with E throttle as you can run a second target table to activate based on the antilag switch.
  13. Like
    TnF reacted to Adamw in [UPDATE] PCLink 5.6.5.3338 Released   
    Post removed to avoid confusion.
  14. Like
    TnF got a reaction from TechDave in [UPDATE] PCLink 5.6.5.3338 Released   
    Thanks a lot guys, remember i was the one contacting you on facebook XD Will finally take a look now
  15. Like
    TnF reacted to Crispin in Strategy switch by different map groups   
    For racing ECU's it's common to use a strat switch that changes multiple settings at once.
    The Link ECUs are now becoming so good with so many different settings and maps available that being able to group different settings seems like the natural next step.
    I'm thinking a list of different settings and a dropdown to select which of the available maps to use for this specific Strategy setup.
    You could e.g. have 3 different settings for Dry race, Qualification and Wet race.
    Each strat option could then affect:
    Fuel map, igniton map, rpm limit, boost map, traction map, throttle map (in case of DBW) etc.
  16. Like
    TnF reacted to Crispin in REQUEST/IDEA - Control multiple features via a single Analog input (or DI, CAN, Serial etc.)   
    This is the same type of functionality I requested here: 

  17. Like
    TnF reacted to Scott in Fuel system type Map to FP sensor   
    This is a bug. Currently if you use ANV12 or higher for fuel pressure it does not work. We have an update coming shortly that will fix this issue and some others.
    Scott. 
  18. Like
    TnF got a reaction from Adturb in REQUEST/IDEA - Control multiple features via a single Analog input (or DI, CAN, Serial etc.)   
    Hello. This is something i've been thinking long ago, even before i bought my Link G4+ xtreme black ecu. I am not sure if you will flip me off because it will probably be much work for you guys but on the other hand i believe no-one has such a feature and it goes more into OEM one-off applications we see in newer cars. 
    So to get going, my idea is a feature where in the simplest form is to use a single Analog Input to control multiple parameters (in the activate-deactivate sense) like launch control, anti-lag, traction control, map switching etc so to spare DI for other stuff. Normally if you want to have control over these features/parameter you require to add switches wired to DI's for every one of these things you want to control. However assuming your analog inputs have 10bit ADC's it gives 2^10=1024 individual voltage steps from a range of 0-5V (5/1024=0.0048V per step) which gives 10 possible combinations of parameters you can control (ideally, in reality the ADC might be too sensitive so we go down to less parameters (5 parameters for a 0.02V voltage step). So from Link's side you essentially need to construct a "table" where you can set 10 different parameters to control on and off. To simplify this let's go down to 3 parameters to make this easy to visualize:
    where x means the function is activated and blank means it is deactivated .
    Of course it doesn't have to to be a table with voltages like that since if using 10 parameters will require 1024 columns for the voltage steps. The proper way to do this is via binary counting since you can easily index all combinations and calculate the state of each parameter (on or off) without an array which would take lots of space. As a follow up to the example above where we set n=3 as the total number of the parameters to control we need a binary value of n (3 in this case) digits. If we set 1st digit as parameter A, 2nd as B, and 3rd as C we have the following combinations that will always hold true (index the same) for any n number of parameters we want to control:
     Thus we can easily calculate and control any parameter directly through the ADC value of the analog input. This works great for both sides (Link ecu and client side of which i will go into detail later in the post). To simplify again how this should work lets break it down. In this case let's say we use all 10bits of the ADC.
    PcLink should have a table that you can set 10 parameters to control. It is important that these parameters are entered with the same order for both PcLink and client side. Let say we set:
     Let's say i want to activate B and H. This means i need to convert the binary 0100000100 (note where i put 1's, B is 2nd, H is 8th). If i do the conversion i end up with the decimal value of 260. Then the client side DAC sends a signal of about 5V * 260 /1024 = 1.27V. The link ecu receives this voltage on the analog input (ADC) and measures it as decimal 260. Converting back this decimal to binary we get 0100000100. The ecu sees the 2nd and 8th digits of the binary value are 1 so it activates functions B and H. I hope this makes it clear. We can go into more detail why this not work perfectly and the ADC might read 259 or 261, thus why i said we might need to use less than 10 parameters depending on the sensitivity of the ADC. Also you are not limited to using a single ADC. If you have 2 analog inputs connected you can potentially control 10x10 = 100 parameters.
    Of course we are not limited to using analog inputs for this feature, we can do this via a DIGITAL INPUT, SERIAL, CAN etc. Client wise this is very easy to do. What i personally plan to do is use a microcontroller (an arduino for example), an oled screen and some push switches to make a nice, user friendly interface where you can select what to control at any moment without having to add lots of switches and knobs. I am also planning to control more things, like boost target since a $5 arduino microcontroller gives you lots of I/O. Plus it only costs $10-$20 in materials total. I will freely provide code, schematics and diagrams if this thing is implemented. It's not that i can't at the moment, it's just i will run out of AN's and DI's which should be reserved for sensors, not for controlling FEATURES. 
    SO PLEASE PLEASE PLEASE MAKE THIS HAPPEN! NO OTHER AFTERMARKET EMU (i know of) has such a feature and would add greatly to your products. And while you could release such a module yourself's please do not make it proprietary, we want to have the flexibility as end users (afterall that's why we bought an aftermarket ecu in the first place!)
    AFTERTHOUGHT: I bought an aftermarket ecu not to make more power - you only require air, fuel and right timing for that - but to get and control more features. This is so that i can modernize the car and make it more relevant as a daily and even give more flexibility for a motorsport application. All the above and more can be done really easily nowadays - you can get a cheap windows tablet connect it via usb and run PcLink on it if you want. And this is another way we should think my idea. Maybe you want to use it as to monitor stuff without a laptop, control things, think of R35 dash for example. Why bother to use OBD when you can do so much more via direct USB? It is not like hardware changes are needed, you can do this via software alone. So please consider this   
     
      
  19. Like
    TnF reacted to Scott in REQUEST/IDEA - Control multiple features via a single Analog input (or DI, CAN, Serial etc.)   
    They have seen it  I'll move it to the request area now.
    Scott.
  20. Like
    TnF reacted to Scott in Start position parameter issue in DI2 - still not fixed in latest build   
    Thanks for letting us know (again!). I'll pass this on to the engineering team.
    Scott.
  21. Like
    TnF got a reaction from Rich RDE in Knock control - Clear I-trim tables question   
    Yes exactly what you said David  But Rich yes that's a nice feature to implement actually since at the moment when you are trying to identify the correct threshold values for the knock tables even with a narrowband knock sensor it is very much a trial and error process (although on my setup i have already set them up pretty close to ideal). However when having a tuning session it is pretty much impossible to replicated all the conditions, so like David explained if the i-trim tables are persistent you may catch some knock where otherwise you would never see (and it is in my case like 3-5 cells on 2 cylinders i caught once). So if the tables are persistent then the engine will be more safe since some knock may happen in one drive, then next time you start the engine it won't have to run the advanced values and it will try to put more timing slowly saving you from potential damage  
  22. Like
    TnF got a reaction from Rich RDE in REQUEST/IDEA - Control multiple features via a single Analog input (or DI, CAN, Serial etc.)   
    Hello. This is something i've been thinking long ago, even before i bought my Link G4+ xtreme black ecu. I am not sure if you will flip me off because it will probably be much work for you guys but on the other hand i believe no-one has such a feature and it goes more into OEM one-off applications we see in newer cars. 
    So to get going, my idea is a feature where in the simplest form is to use a single Analog Input to control multiple parameters (in the activate-deactivate sense) like launch control, anti-lag, traction control, map switching etc so to spare DI for other stuff. Normally if you want to have control over these features/parameter you require to add switches wired to DI's for every one of these things you want to control. However assuming your analog inputs have 10bit ADC's it gives 2^10=1024 individual voltage steps from a range of 0-5V (5/1024=0.0048V per step) which gives 10 possible combinations of parameters you can control (ideally, in reality the ADC might be too sensitive so we go down to less parameters (5 parameters for a 0.02V voltage step). So from Link's side you essentially need to construct a "table" where you can set 10 different parameters to control on and off. To simplify this let's go down to 3 parameters to make this easy to visualize:
    where x means the function is activated and blank means it is deactivated .
    Of course it doesn't have to to be a table with voltages like that since if using 10 parameters will require 1024 columns for the voltage steps. The proper way to do this is via binary counting since you can easily index all combinations and calculate the state of each parameter (on or off) without an array which would take lots of space. As a follow up to the example above where we set n=3 as the total number of the parameters to control we need a binary value of n (3 in this case) digits. If we set 1st digit as parameter A, 2nd as B, and 3rd as C we have the following combinations that will always hold true (index the same) for any n number of parameters we want to control:
     Thus we can easily calculate and control any parameter directly through the ADC value of the analog input. This works great for both sides (Link ecu and client side of which i will go into detail later in the post). To simplify again how this should work lets break it down. In this case let's say we use all 10bits of the ADC.
    PcLink should have a table that you can set 10 parameters to control. It is important that these parameters are entered with the same order for both PcLink and client side. Let say we set:
     Let's say i want to activate B and H. This means i need to convert the binary 0100000100 (note where i put 1's, B is 2nd, H is 8th). If i do the conversion i end up with the decimal value of 260. Then the client side DAC sends a signal of about 5V * 260 /1024 = 1.27V. The link ecu receives this voltage on the analog input (ADC) and measures it as decimal 260. Converting back this decimal to binary we get 0100000100. The ecu sees the 2nd and 8th digits of the binary value are 1 so it activates functions B and H. I hope this makes it clear. We can go into more detail why this not work perfectly and the ADC might read 259 or 261, thus why i said we might need to use less than 10 parameters depending on the sensitivity of the ADC. Also you are not limited to using a single ADC. If you have 2 analog inputs connected you can potentially control 10x10 = 100 parameters.
    Of course we are not limited to using analog inputs for this feature, we can do this via a DIGITAL INPUT, SERIAL, CAN etc. Client wise this is very easy to do. What i personally plan to do is use a microcontroller (an arduino for example), an oled screen and some push switches to make a nice, user friendly interface where you can select what to control at any moment without having to add lots of switches and knobs. I am also planning to control more things, like boost target since a $5 arduino microcontroller gives you lots of I/O. Plus it only costs $10-$20 in materials total. I will freely provide code, schematics and diagrams if this thing is implemented. It's not that i can't at the moment, it's just i will run out of AN's and DI's which should be reserved for sensors, not for controlling FEATURES. 
    SO PLEASE PLEASE PLEASE MAKE THIS HAPPEN! NO OTHER AFTERMARKET EMU (i know of) has such a feature and would add greatly to your products. And while you could release such a module yourself's please do not make it proprietary, we want to have the flexibility as end users (afterall that's why we bought an aftermarket ecu in the first place!)
    AFTERTHOUGHT: I bought an aftermarket ecu not to make more power - you only require air, fuel and right timing for that - but to get and control more features. This is so that i can modernize the car and make it more relevant as a daily and even give more flexibility for a motorsport application. All the above and more can be done really easily nowadays - you can get a cheap windows tablet connect it via usb and run PcLink on it if you want. And this is another way we should think my idea. Maybe you want to use it as to monitor stuff without a laptop, control things, think of R35 dash for example. Why bother to use OBD when you can do so much more via direct USB? It is not like hardware changes are needed, you can do this via software alone. So please consider this   
     
      
  23. Like
    TnF got a reaction from Rich RDE in Start position parameter issue in DI2 - still not fixed in latest build   
    Hello. I had notified you of this through facebook a couple months ago but it seems it has been lost somewhere.
    So when you set DI2 as start position you get an Active edge option instead of On level option as it should be. On other DI it shows ok (but i haven't tested all). 
     
    Kind regards
  24. Like
    TnF got a reaction from Scott in Connect oil pressure and oil temp sensors to analog inputs   
    Not possible in my case, not to count all the negative factors going that route. Either way i was correct after all and i did it
    Went with number (2) aka the micro-controller route. While it can't be done in analog is much easier this way, cheaper and more efficient. What i did is to connect an Arduino micro-controller that takes measurements when the mtx-d pulls up the line and then feeds them as 0-5V to the analog inputs of the Link ecu. Then you do a table calibration there and you are done. Since the microcontroler has 10bit ADC resolution is good enough. Output is done via pulsewidth modulation at 980hz. I should add a small capacitor to smooth out the voltage but i didn't bother yet. Here the code says it all:
    And see my screen attachment i lost last time - mtx-d does do alternative measurements indicating they are using a single ADC

×
×
  • Create New...