koracing

I also use a USB extension as do most of my customers as the MR2 places the ecu in the rear trunk behind the mid-engine and there is no way the supplied USB cable will reach the passenger compartment. The quality of these extensions vary quite a bit (Belkin for me seems to do the best). It might be nice if there was a Link supplied option for a longer cable in the case of applications such as the MR2, or any system where the ecu isn't directly under the dash.

I have several customers still running G4+ ecus and distributor based ignition systems. It would seem like a fairly simple update to the software to give individual cylinder knock signals. I mean the thunder is still only a G4+ after all and still a current product. Is there any chance there will be a software/firmware update for G4+ at some point?

While I love the new G4x ability to log internally up to 512Mb - downloading the data takes quite a bit of time. An ethernet/RJ45 or USB 3.0 connection would make this go a lot faster. Any tips also appreciated to speed this up that I may be missing. What about wireless wifi adaptation for ecu communication/tuning? I found the thread by @Richard Hill using the mango wifi device, but is there a possibly of a more native device?

Why would MGP for fuel be preferred but MAP for timing? Does using MGP automatically correct fueling for altitude via the BAP reading? Wasn't aware of the import/export to and from clip-board - that should save me a lot of time - thanks. The biggest flaw there I see is it copies the whole table contents as well as the axis settings which is fine for cylinder trim tables for example, but for like fuel tables or timing tables, I may not want to copy the tables completely. I still feel an axis only setting copy would be useful.

It would be really nice if when switching a table from a 2D (like idle base position, or start prime for example) to a 3D table that one of the options (currently it asks to zero all values) was to populate the new 3D table with the values that were on the 2D table and possibly vise versa.

Probably my biggest annoyance with the Link software so far is the fact that if I change the load or rpm break points on one table (for the sake of argument fuel table 1) - I typically would like the option to use these same axis settings on the timing table 1, or fuel table 2, etc. If I enable per cylinder fuel trim tables and per cylinder timing trim tables - having to reselect and rescale the axis on each one which is another example of this same hassle and takes extra time. If there were an easy way to copy axis settings from one table to another or when changing axis of certain tables sets to have the option to apply to all tables of that type perhaps would be a big time saver. I can see scenarios where you don't necessarily want to do this, but most of the time I'm using these features I am setting these axes of same type of table to the same parameters and break points. I also have customers that like to view the load starting low at the bottom and going high at the top -- and to be honest a lot of previous ecus were this way. I know there is the invert load axis option on the fuel table and others when you right click, but here again, you have to apply it to each and every table separately instead of a global button to apply it to all tables. I would use this feature potentially if it was a global setting or could be applied globally. Anyone else have these same feelings?

[EDIT] I swear I tried moving those to the 0, 16, 32, and 48 start bits already, but that seems to have done the trick. It must have been at a point when I wasn't getting any data at all coming in due to some other setting misstep. I'm going to leave this information here for anyone else that may run into the same problem down the road. Here's the Stream setup that worked: I also did notice I had the signed/unsigned set to unsigned when the aem dash was set to signed. That seems to have no impact on the readings? What is the purpose significance of this? [/EDIT] Going by the arrows here - it looks like in the dash setup, it starts at bit 8 - goes to 15, then goes up a line to bit 7 then down to 0 - that seems strange. I'm attaching the dash config and pclr. Thanks! EGT forester.linkg4.KO.test4.aemcd7 KO Yap Fozzster 001 10-09-20.pclr

OK, so I'm a CAN noob, but I've been reading these forums and beating my head against trying to make the CAN EGT from AEM read into a Link G4+ Plug in on a 07 subaru STI ecu. The car has a AEM CD7 Dash thatis also reading the CAN EGT just fine (as one might expect). The Settings in the dash are as follows: With the extended ID (non-hex) being 47616, start bits o 8, 24, 40, and 56; 16 wide, signed, (not sure what BE/Motorola means), multiplex off, scalar 0.1, offset 0, reciprocal unchecked. Based on these values I set the Stream in the Link to as follows: With the channel settings: What I get is continuously fluctuation numbers that don't hold stead and will run up to over 10k and then drop to zero and start counting up again. The Dash is holding stead at about 750-950°F depending on which cylinder in particular we are discussing. Here are two screen shots of the readings in the Link a few moments apart at idle: I'm not sure if there is a fundamental issue with how the data is being received or not, or my settings, but I'm at a bit of a loss and could use some help. Thanks in advance for anything you can help me with.

I see the new G4X just released -- is that going to get this update or are we talking like G5 before this would be updated?

What about the next revision/platform?

Would you guys mind fixing this? Knock sensing per cylinder is extremely useful for finding issues with particular injectors, ring seal, valve seal, etc. per cylinder. The ecu appears to be able to trim ignition and fuel per cylinder so why not give us the data per cylinder even with a distributor?