Ben C

I think its a great feature being able to compare two tune files and having the differences highlighted to easily scan over everything.
But one area I find it lacking is in the tables such as fuel and ignition. Currently you're just presented with black/yellow numbers within red cells (or whatever colour you change your "highlight" theme to) and it's very difficult to quickly (and comfortably) read the values that have changed, and by how much.
It would be nice to have a "heat map" style similar to the mixture map sceen where the colours change based on how different the new value is from the old value and relative to other changes.

It is an issue with Windows scaling... Change it to 100%, it will look ok. Nothing can be done within PCLink to correct that.

It's like im trying to extract teeth or something...  Im trying to help you in the middle of my weekend, please attach your map so I can take a look and offer the next steps in diagnosing.

I misunderstood the units.
Thank you very much for your guidance.
 

With the sensors removed from the engine, but still plugged into the loom and with ignition on so they are all powered up, back probe the signal pin at the sensor connector and connect a voltmeter (use a paper clip poked through the wire seal).  The signal wire should be 4V or higher with no metal in front of it and 0V when you hold something steel in front of it (like a screw driver or spanner).  If you dont see that voltage change then there is some problem with the wiring/pinout/sensor.
If you see a voltage change at the sensor when you do the above test, then the next step would be to do a similar test using the triggerscope, with metal and no metal in from of both sensors.  If the signal is getting through the loom and back to the ecu correctly then you will have two flat lines on the scope showing 4+V when there is no metal in front of the sensors and flat lines at 0V with metal in front of the sensors.  

Not that I know of, the 350Z one works with our ECU but wouldn't be easy to setup in another vehicle, I personally use the DI feature in one of my vehicles but I have been tempted on more than one occasion to do something with an arduino, a serial to CAN converter and a NFC reader. 

You can chop off the plastic from the end and just have the Thermistor poking in.
 

add crank enrichment. a fair bit. you want it to fire first to know it is the crank enrich at play, if it takes ages to fire it is normally crank enrich. E85 ends up with large numbers for cold crank enrichment, so don't be scared of big numbers in the lower temps.

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?

You will need to change your relay's coil feed to be ignition switched, rather than permanently powered. This way, the ECU will still pull to ground to activate, but when ignition is off, the coil cannot be energised, even with the ECU defaulting to grounding the outputs.

Update... Everything seem to be working correctly as far as the fueling is concerned.
 
I did change the Hz to 1000 like was recommended.
I also am now running the FP in Open Loop... for now.
Lastly, I did update the firmware.
The "FP Speed (%DC)(%)" does still show the "reverse" for me.  As the actual FP speeds up, the "FP Speed (%DC)(%)" goes down. Min DC clamp at 30% so "FP Speed (%DC)(%)" shows 70% and ramps up to 100% by 30% Inj DC.

I couldn't even tell you. Smh. Prob me seeing "80hz" on the 33/66/100 setting. I'll let you know though. 
Thanks again. 

Hi, I have a IS300 myself, although not running the xcessive/panicwire pnp kit, I repinned my loom to the right headers to suit. I don't have any issues.. It sounds like to me that the MPX isn't wired correctly on your loom and/or not going to where it suppose to go.
Since you are using the IS300 2JZ loom, and using the panicwire patch loom, Check out pins E-5 (MPX1) and E-12 (MPX2) on the Link/Altezza header side loom, , make sure they are connected to the body loom and goto the body computer. On the IS300 loom side they "should" be connected to E4-21 (MPX1) E4-20 (MPX2). I'd unplug the patch loom and check continuity with a multi-meter to make sure the patch loom is ok. Then if so, make sure your MPX network on your body loom is ok. Also make sure that the Altezza CAN configuration on the Link has been done correctly.
 

Update: 
For what it's worth there is an o-ring in the VTC gear valve cover plate and sure enough the oring was damaged.  I can only assume that I messed it up during install.  I installed a new flat rubber oring, fired the car up and VTC is functioning on both sides.  
Issue:
Fixed:
 
 

I had asked a while back when the G4x wasn't released yet if Link could add a way of comparing two analog values to control an output (in my case I am controlling IC fans with the differential temperature of two temp sensors) and I never heard anything back on whether this could be implemented. I realize a majority of the requests on the wish list cannot be added, but this seems like a pretty basic and highly useful function to add to the software. So recently I was poking around in the G4x software and noticed you added the "Math" functions in the "ECU Settings" tab which is exactly what I was looking for to be added to the G4+ software. I upgraded to a G4+ Thunder during the time that the G4x platform was rolling out, but it was only on the "smaller" ecus and I was assured by Link that it would be a long time until the G4x Thunder was released. So since I needed an ecu with the amount of functionality that the Thunder had and I couldn't wait for the G4x version to be released...I made the decision to just buy the G4+ version. Now that I am stuck with this platform, could Link seriously consider incorporating these "Math" functions into the G4+ software before they discontinue firmware updates in a years time? I realize there could be a hardware limitation with the slower processor and possibly less memory, but if there is not...this would be a really valuable addition to the software and something I believe should have been there all along.  

Well that worked pretty much perfectly. Thank you very much.
 

If you need and injector signal and a MAP signal why wouldnt you just splice into those signals?  

Cant you just swap the pins in the ECU plug?