Vaughan

Ah yes, sorry for the bad info.  Im so used to not having that reallocation functionality in our older software and have never needed it so forget it is even there.

With G4X ECUs on the latest firmware (comes with the G5 PCLink install) you can reallocate which ignition and injection drive is used for what so if you can use any of the Ign 5-8 pins on the expansion header as your additional ignition outputs as long as you reallocate them correctly in the Ignition Reallocation table.
Example below uses Ignition 1 output for cyl 1 coil, Ignition 2 output for cylinder 2 coil, ignition 5 output for cyl 3 coil and ignition 6 output for cyl 4 coil.

To clarify that is in there to say that the ECU doesn't support the E-Throttle AP2 models as they have different pinouts to suit the E-Throttle and different requirements around CAN etc. The ECU does support having E-Throttle added but it doesn't support vehicles that have the Loom from an E-Throttle model.

Have added more info to the help, a note to the CAN Devices tab of the CAN Setup window and improved how specific it is when pointing you at help from each CAN Setup tab. Will be in next release.

Have added more info to the help, a note to the CAN Devices tab of the CAN Setup window and improved how specific it is when pointing you at help from each CAN Setup tab. Will be in next release.

Have added more info to the help, a note to the CAN Devices tab of the CAN Setup window and improved how specific it is when pointing you at help from each CAN Setup tab. Will be in next release.

I have used a Link CAN Lambda with the JST 4 pin plug on newer plugins and it has worked fine.

Newer ones have the 7Bar, I feel like there might be sticker on the box but easiest way is to just set it to one of the two calibrations and see if the MAP value is close to the BAP value.

It's pretty easy to copy most of it across, anything PID will need to be retuned and definitely double check your trigger calibration value.

There is some trigger and firing order info in the PCLink help file (as pictured below), if using factory injectors you could use a traditional based fuel tune with a master fuel of maybe 10-15ms to start with, other than that generic fuel and ignition tables from one of the EVO sample maps should be enough to get it started and running once you have tested your wiring and found the correct trigger offset with a timing light.

Which engine do you have? Quick google shows the RS3 uses the Bosch HDEV5.2 which we have the current and voltage data for. The RS3 high pressure fuel pump we don't explicitly have data for yet but a quick scope with a current trace will show it's peak and hold current values.
You will also need to measure your high pressure pump cam lobe shape and find the angle of the top of one of the lobes relative to tdc of cyl 1 when cam is in it's rest position.
Hardware wise we have 4cylinder box on the way with built in fuel pump peak and hold driver but I don't have any specific timing as to when this will be available to purchase.
I would also assume that the XBow has a CAN bus system which will need reverse engineering so that we can replicate what the factory ECU transmits and receives.

You're trying to trigger the AC Clutch and Condenser Fan relays with a high side signal from inj5&6 which can only do low side control. Same issue with Thermofan on Aux 3. Aux 7 controlling the starte solenoid can do high side but you generally would try and use low side triggering for this.
I would also recommend moving the coil power for the fuel pump relay and isc solenoid relay from the ignition switch signal to the ECU power side of the relay switch so that if the main relay fuse blows it doesn't power up those devices while the ECU is not powered causing all manner of weird back feeding issues.
If it were me I would run Coils, Injectors, ISC Solenoid and ECU all off of one 30A capable relay and fuse, I only see separate relays for those things as added complications and added room for issues to occur with no real benefit. I would also have the power side of the coil for all other relays (fuel pump, starter, fans etc) coming from the ECU power on the ECU side of that relay.
Your pinout also seems to be setup for an Xtreme not a Fury as you are trying to use B plug pin 30 as a digital input when it is one of the dedicated wideband pins on a Fury and you have a CAN based wideband instead of wiring the sensor directly to the ECU.

The issue is to do with graphics drivers, the reason you see it on this particular build and not on previous builds will be because the issue is related to the graphics libraries as they were when that version of PCLink is compiled. If these libraries are updated between PCLink builds regardless of any change in our PCLink code then these issues can occur, we don't write the graphics drivers, just code that uses them.
We are planning on doing a new PCLink and firmware release soon so hopefully the graphics issues will be fixed by that.
The change was made so that people with the new G5 Voodoo Pro ECUs with Wifi could find and connect to them. It also means that instead of PCLink sitting there trying to connect to everything it can find, which is what it did previously, you can now direct it to connect to a particular device.
There is a slight change coming for the next release where if Connection Port is set to USB and only one device is found during a regular connect attempt then it will try to connect directly to that. Shift + F3 will still do the full search.

Graphical issues are compiler related and so not something we can change in the code, more of a look to see if they have been fixed since by various updates to the build computer. It's also not something I've seen on my own computer so isn't necessarily going to be the easiest to test if it has been fixed.
No current plans to remove the ECU selection box, it does work better in Manual mode as auto mode will try and fail when you power cycle ECU or disconnect and so lose the selected ECU.
There are some setting around directories in the options menu with tick boxes and editable directory paths. Do you have the boxes ticked or not (ticked means always use that folder, unticked means go to last place you opened that type of file from).
I don't think that setup changed at all on the G5 update stuff.

The issue is to do with graphics drivers, the reason you see it on this particular build and not on previous builds will be because the issue is related to the graphics libraries as they were when that version of PCLink is compiled. If these libraries are updated between PCLink builds regardless of any change in our PCLink code then these issues can occur, we don't write the graphics drivers, just code that uses them.
We are planning on doing a new PCLink and firmware release soon so hopefully the graphics issues will be fixed by that.
The change was made so that people with the new G5 Voodoo Pro ECUs with Wifi could find and connect to them. It also means that instead of PCLink sitting there trying to connect to everything it can find, which is what it did previously, you can now direct it to connect to a particular device.
There is a slight change coming for the next release where if Connection Port is set to USB and only one device is found during a regular connect attempt then it will try to connect directly to that. Shift + F3 will still do the full search.

Will also crank over faster and get better spark with the spark plugs out making it easier to get it timed before the battery runs out of juice

Will disable tomorrow when attempting 

I know that it was a sample map and is just to get it started, the reason I got the an mx5 and put a link on it in the first place was to teach myself how to tune. I have spent a decent amount HPA courses and read hours and hours of info from this forum. I get that the easy way out is to just get someone to do it for me, but I like trying to have a go myself.
I have made the changes in the ecu myself apart from the ignition table which a local tuner sent me to try. It is the first time I have attempted to even drive the car today. If it's a case of there is nothing seriously wrong and it just needs more work on the tune, then I will just keep having a go until I figure it out.

The issue is to do with graphics drivers, the reason you see it on this particular build and not on previous builds will be because the issue is related to the graphics libraries as they were when that version of PCLink is compiled. If these libraries are updated between PCLink builds regardless of any change in our PCLink code then these issues can occur, we don't write the graphics drivers, just code that uses them.
We are planning on doing a new PCLink and firmware release soon so hopefully the graphics issues will be fixed by that.
The change was made so that people with the new G5 Voodoo Pro ECUs with Wifi could find and connect to them. It also means that instead of PCLink sitting there trying to connect to everything it can find, which is what it did previously, you can now direct it to connect to a particular device.
There is a slight change coming for the next release where if Connection Port is set to USB and only one device is found during a regular connect attempt then it will try to connect directly to that. Shift + F3 will still do the full search.

We don't have any spare units left at this point but production should be starting soon, might be best to get in touch with the sales team to see if they can let you know when they'll have them available.

That's looking a lot happier and I can see you have the sensor wired the correct way around, it should spark correctly while cranking now.

The ECU output isn't PWM, it is synchronous to the engine speed where it turns on and off at very specific angles relative to the specific cam the pump is on, if your PDM can do peak and hold control and you can guarantee a consistent and small deadtime between the ECU output and the PDM output then yes you could do it with the PDM. If you want to try running a constant but higher current through it then maybe a FET or a solid state relay with a smaller or no ballast resistor would work.
Just to reiterate from memory the Life setup had ~6A of peak current and 2.68A of hold current. To make it move you most likely require close to that 6A of peak and so if you ran a FET or solid state relay with appropriate ballast resistance to get 5-6A you could just run it at that full current the whole time and then keep an eye on whether or not you overheat the pump solenoid.
Alternatively we are in the testing phases of our DI drivers which include a pump driver but I'm not sure when they are going to be available for purchase.

Hello Gents,
Truck took 1st place at the San Felipe 250 race in Mexico!! Running very well on port for now. Just need to get the DI working properly. The pump is not working at all with the resistor inline. I suspect it needs a proper H-bridge and will need to clamp the amperage. Factory they allow the amperage to go to 6 amps at peak.
Can I use the output for the G5 to go to the AIM PDM and control it through the AIM unit with a PWM control?
 
Thank you

Thank you, this worked perfect. Someone on another forum whipped up the attached calculator, and I was able to get a perfect calibration for AIM's 2k pullup resistor. 
https://willwaldron.com/voltage_divider_calculator/sensorvoltage.html
 

Got the MX5 out last weekend.  Addition of the diode solved this issue.