spark issues, faulty coils or cas?

[tc-rolla]

Car - ae71

motor - 4age (bigport)

use - street

problem - lack of go!

occurs/started when - constant

Hey guys,

after ages of fucking around everything was looking good finally got the motor to kick over but there it struggle's to idle and you cant really rev it as it splutters and chokes and cracks the shit then will eventualy die.
i have checked the cam timing and got a mate to as well and its spot on.
ignition timing were still fine tuning but cant get it right as the motor will not stay running (but the timing is pritty close to perfect).

Plugs were replaced, fuel filters, fuel, ouil, coolant, the works and still no good. leads are new(ish).
my 4age runs on wolf 3d using a waste spark system with denso coils (that no one has any idea what there off) and it seemed like the spark coming from 2 & 3 (which are on the same coil) was a "duller" compared to 1 & 4.
also, my dizzy has been converted to a CAS. but the wiring inside the dizzy looks a but "iffy".
im not sure what the compents are called, but here's picture (note, this is not my dizzy showing this as a referance to what im talikng about)



im not sure what the unit does, but the both arn't looking the best, could this be causing problems?
also, what would cause a set of coils to fuck out? apart from wear.

thanks heaps, ben.

here's a pic of my coils:

[biggo]

wolf3d = theres your problem

but seroisly, check primary+secondary resistance of the coils (dont worry about specs just see if theyre the same)

I had a reluctor CAS setup in my 3sge that had a bees dick too much air gap on one of the pickups. this cause the whole show to stop.

[H8CHIR6KU]

why dont you swap leads around and see if that changes spark? if is the same cylinders then you know its not the coils. if its different cylinders then its the coils or leads

[tc-rolla]

got it going and was all good, drove it to work. on way home from work stoped at shops and turned the car off. was gone no longer than 5 minutes and will not start. no spark!
but everything is reading as it should. could a faulty reluctor interface cause this?