If the ECU does not have knowledge of 360 vs 720 degrees, you can still run the engine. However it will not be sequential, as it would squirt when intake is both open, and closed.
ok, i fully understanding now.
let's say mitsubishi 4/2 tiggers. it is still enough if using only one slot cam signal?
i found 4g92/4g93 cas is 4/1 slot.
last firmware i use is 28/3/2017 and got update it to 22/6/2017. engine start quite fast and running smoothly.
so, Rusefi will be at my daily drive car..
You were asking about when launch control feature would be available - to be honest I have no idea For that to happen someone would have to work on that and I doubt that would be me in 2017
done some testing just now. i use standard nissan ignition coil with distributor. first start couple month ago with individual honda k20 coil. i wonder why trigger offset is 365 (nissan coil) instead of 630(k20 coil)?
tomorrow will do some wideband tuning, hopefully all running good. if all ok, this ecu will be installed at nissan GA16DE by next week.
pin 1: gnd
pin 2: 12v
pin 3: 360 slot
pin 4: 4 slot
pin 5: 1st switch on signal ( i dont know what it is)
pin 6: 12v (ignition coil)
pin 7: gnd
pin 8: ignition signal
i start my engine today, it runs few minutes and suddenly stop. key of and on again no rpm sync at all. only pin 3 and pin 5 not connected to rusefi. any suggestion?
I read throughout and not 100% understand. Let says If I would like to control my neo vvl, intake is open at 5500rpm and exhaust is at 6000rpm. Got two solenoids that I believe same as Honda VTEC, on/off type. What should I figure in tuner studio?
from my understanding, i just figure it out at console and nothing todo with TS?
i trying to figure it with shift light function, looks like it suitable with my neo vvl solenoid.
yes, i use new firmware. now my engine running nissan primera trigger with standart coil with distributer. before this it running ms2 with 4g63 trigger, 2 of my k20 cop got burn.
got test drive this car for 2-3 days, and like i said before.. next week will race with that rusty nissan march
It appears it failed on the first byte it attempted to write. I see it notes " is not erased, verify the memory protection"
Is it possible that you have selected a memory protection feature and have locked up the memory on that board. I have not looked into memory protection, so I do not know for sure, but you message does seem to indicate that is what you have done.
I'm ignorant about how to correct it if you activated the security features. It's even harder for me as I did not preform the sequence which got it like this. It's probably a $12 mistake.
For that to happen someone would have to work on that and I doubt that would be me in 2017 
