Scott

If you had the ECU on firmware version 5.6.4 and then loaded in a base-map from your hard drive that was from firmware 5.1.1, the ECU would try and correct the base-map to suit the new firmware. Because that is quite a jump in firmware versions and the newer firmware (5.6.4) has settings that didn't exist in 5.1.1 the ECU may not correctly allocate these settings. So if you load a base-map from older firmware into an ECU on newer firmware make sure you check all the settings.
Scott

Thanks for the screenshots, I see what you mean. I'm happy to ask the engineers to consider something like this.
Scott

The Audi/VW 1.8T engines we worked with had two narrow teeth and two wide teeth on the cam trigger wheel.  On our default Audi TT base-map we use the 'Multi-tooth/Missing' trigger mode. However this likely not work with a VVT engine, but the 'Holden V6 Alloytec II VVTi' trigger mode should work instead.
Scott.

Work correctly with DH61
ALS adjustment
 

MERRY CHRISTMAS FOR ALL AND FAMILIES.
THAT THAT YEAR OF 2017 WE CAN RIDE MANY STRONG ENGINES.
I'M SORRY FOR MY ENGLISH.
AUGUSTO

Currently the 2 traction tables can not be overlaid. I will ask the engineers to consider adding this functionality. I will also ask about the possibility of using a virtual aux as a disable switch with user costomisable conditions.
Scott

I found the problem :-) it was something wrong in the trigger setup, sync pulse was set to Cam. but it should be set to None :-) 
Now maybe its time to celebrate Christmas :-) :-) have been working on this car none stop all week an last weekend :-)
Thanks for help everyone :-D and merry merry Christmas :-D

You are on the right diagnostic track with finding the problem. The ECU will not do spark until it is reading engine speed.
What is the tooth pattern that trigger 1 and trigger 2 see?
Please attach your base-map.
Scott

Dave, Dave, Dave......never a truer word spoken in jest...
Just completed my Spool RB34 and fired her up yesterday.
Sounding awesome !
Will post updates as "we" go along..:-)
 

Why not use a windows table and link software
https://www.youtube.com/watch?v=cXmmUjhMPGc
 

Thanks Scott!! Ill be getting more videos come spring of me putting the TC to work. As ill be turning it up to 43psi a little over 700whp. 

Hey guys.

Posting up my 643whp Mini build. Not sure if you guys want a long post or just the jist of it. So Ill be short and sweet.
 
It is currently the record holding MINI in the world for HP. Would have made more with traction.

2005 MINI Cooper S
 
1.,7L RMW stroker--Carrllio Rods//High Compression coated Arias pistons//RMW billet crank//RMW head//RMW cam//RMW intake Manifold
JCFab turbo kit using EFR8374 Twin scroll housing dual wastegate and exhaust dump out the hood
Insane Shaft 1000hp axles
Quaife diff
Fic 2150's with a Walbro 450 in tank at 18V and a external DW 350 at 18V Running E85-E100///Static pressure set at 50psi
Tuned by me on a Vipec I series PnP (Link G4+ now) 
Car made 640whp at 31psi in 3rd gear at 4600ft of elevation uncorrected. Couldn't keep it from spinning on the dyno. No where on the front of the car to rachet down tight enough. Going to a hub dyno. Shooting for 710-730whp before upgrading to the EFR9174 and shooting for 850whp
 
 









Couple videos
Testing out the traction control and Rolling Anti-Lag with the Link
https://www.youtube.com/watch?v=WBP1oXMV0N0
 

Quick second to third gear pull on MT 225/15 Drag radials
 
 
 

John,
The link does have the capability to set "custom TDC's".  I have never used this function so I dont know for sure if it will like us commanding 2 cylinders to fire at the same time, but screenshot below is how I think it should be set up.  Scott might be nice enough to run that setup on his sim to confirm it behaves as expected, otherwise you can just try it and see.  Set engine as 2 stroke, 2cyl, injection mode to sequential, ignition mode to direct spark, rest of config as below;

 
If the above method doesnt work there are a couple of other ways you could do it.  One is setting it up as a single cylinder as you have suggested above and driving both coils and both injectors from the Cyl #1 drivers.  Another way you could do it is set it up as a 4cyl, 2 strokke, coil & injector for cyl #1 goes to ECU #1 drivers,  coil & injector for cylinder #2 goes to ECU #4 drivers.  Drivers 2&3 dont get connected.

Thanks for uploading the base-map. The engineers will work on fixing the FP Speed problem on channels that can't do PWM.
I've had a quick look over your base-map and didn't spot anything strange. Most engines running on modelled fuel mode seem to need a value of 60 to 70 in the idle area of Fuel table 1, so you could try setting cells in this area to this value.
You will want to use a timing light to check/set the base timing.
The higher numbered aux channel labelleling will be included on our next main firmware release.
Scott

The G4+ atom doesnt have a builtin MAP sensor.  It seems you might be looking at a manual for the old G4 model which did.

I'll see what I can get happening on this.
Scott.

Hey Scott
Yes, we did disconnect while working through some problems on the dyno.
I will give the resetting a go. 
 
CHeers 
sorted and clears the errors

windows 10 tablet .
B4 and after .thanks for the awesome Link software.

Iecku, I just thought I would mention a little bit of info that many people miss.  These kits appear to use the Honeywell 1GT101 sensor, these sensors are much slower on the rising edge than the falling edge.  The datasheet quotes a 15µs rise time Vs 1µs for fall time.  So for at least trigger 1 (that controls the timing) it would be more correct to set the trigger edge to falling. Even though 15µs is only like 0.9 deg at 10000RPM, if you can get extra accuracy just by a simple setting change - then you might as well use it...

I can ask the engineers to consider this.
Scott

I think if you keep things how Adam suggested but add a 3rd condition to Aux 8 then the  scavenge pump will not start running when you turn the key on and rpm is zero. Something like this:

Scott

Hope this helps

You are on a very old firmware version, 4.7.*  According to the help file, the Wideband1 parameter was not logged prior to version 4.9.9.
Update to the latest version and you will be good.