beninnz

You should be able to PM me now, my inbox was full. 

Its certainly a pretty odd setup he has done there with equation load source set to BAP, then an alpha N fuel map overlayed with a speed density map...  Im not sure if he has out-smarted himself or has ended up with the odd mess when trying to solve a problem.  There are some other issues in there such as the IAT trim is still enabled in modelled mode and the charge temp approximation table has zero coolant bias so you will be getting twice as much air temp correction than you should be.  
Typically for your application just a single fuel table withh TPS as the load axis will do it, equation load source may need to be MAP if any of the bullet points below apply, otherwise load source = BAP will usually work better for NA ITB with high overlap.  
equation load source = MAP if any of the following are true:
The engine has an idle valve The vehicle has vacuum assisted brakes connected to manifold vacuum. The engine is boosted. There is a restrictive airbox/filter arrangement. If you arent in a big hurry, Im in AKL and could take care of it one weekend.  Im pretty much booked solid for about the next 6 weeks though.  

Got it working.  THanks for the help!

I have both the G4X and G4+ working on a M2 MacBook Air (but should work on any apple silicon laptop).
My setup is as follows
UTM - https://mac.getutm.app/ (Parallels etc should work also) Windows 11 Pro ARM Driver Signature Enforcement has to be turned off Although there are ARM version of the FTDI and CP210X drivers available, they do not include the Link ECU PID's so do not work. I have edited the drivers and added the Link ECU PID's which enable them to work with the ARM drivers (maybe link can update their drivers offered to include ARM drivers now?) but driver signature enforcement has to be turned off as the drivers are not signed.
I have attached the custom drivers here, if this is not allowed please let me know and I can post step by step instead for you to do instead.
Link ECU ARM Drivers.zip

I still have a copy of the original modified firmware so have attached it below if you want to give it a try in the meantime.  As far as I know it worked ok for the other rover.  This will be a 6.23 based firmware so you will lose some of the more recent firmware additions. 
G4xApplication-6.0.1958 Rover Triggers.img

It’s alive! 
 
Will be great to get a ‘proper’ fix so I can take advantage of the recent firmware updates & fixes, but for now at least it’s running. What a great early Xmas present:) Thanks team. 
It’s alive! 
 
Will be great to get a ‘proper’ fix so I can take advantage of the recent firmware updates & fixes, but for now at least it’s running. What a great early Xmas present:) Thanks team. 

It lives! (runs terribly of course, but it starts!)

I wired in a 2 channel igniter into my adapter loom and hey presto we have ignition. So embarrassing that I missed that... Thanks for the help team! 

It lives! (runs terribly of course, but it starts!)

I wired in a 2 channel igniter into my adapter loom and hey presto we have ignition. So embarrassing that I missed that... Thanks for the help team! 

I took this out recently to the Pukekohe track, as I wanted to have a go before it closes.
Just a few days prior I setup the e-throttle rev match function. 
AND HOLY HELL THIS IS GOOD! 

In this whole video I didnt do a single rev match, ECU was taking care of it. 
So I could just concentrate on the brakes. 
Not only is it good for reducing lap times, but also reducing mechanical wear from synchros and clutch getting a hard time. 

The motor was getting quite hot (108deg max) so I need to sort the cooling a bit better. 

But on the whole it performed well beyond expectations.