Cylinder numbering and firing order are confirmed as correct. I would definitely write this down too. Don't expect anyone to review your setup without the basic information.
Fill in these - let's make this clear: you're most likely on your without this information
publish firmware info
- Firmware 1.0.38
- and config (mcd, mct). Config updated here: MembersPage/PeepPaadam/Config
Firing order : 1-3-7-2-6-5-4-8
UPDATE THIS TABLE !!!
| cyl | ignch | EC36pin.. |
| 1 | 0 | 35 |
| 2 | 1 | 33 |
| 3 | 2 | 34 |
| 4 | 3 | 36 |
| 5 | 4 | 11 |
| 6 | 5 | 12 |
| 7 | 6 | 24 |
| 8 | 7 | 10 |
Without camsync, some trick is needed to drive COP (eg. ign_dualout).
The reasonable wiring is that ignch1 and 0 drive cylinders 360 crankdegree apart. ignch3 and 2 also, etc... That is:
- ignch0,1 cyl 1,6
- ignch2,3 cyl 3,5
- ignch4,5 cyl 7,4
- ignch6,7 cyl 2,8
Update I made the changes in wiring and configured ign-channels
- h[2]=07 03 04 05 01 06 02 00
- You configured it wrong. It's a bad idea to ask on phone, because the chance you miss something important is incredibly high. Plan in wiki, and ask for confirmation (or correction). For cyl 1,3,7,2 (or 6,5,4,8 for that matter) the outputs to be configured are 01,03,05,07 (N-1 will be fired because of ign_dualout, that is 00,02,04,06), so (remember last one is fired first, in MegaTune top to bottom):
- h[2]=07 05 03 01 07 05 03 01
- I configured the channels right (07 05 03 01 07 05 03 01) already when i first rewired the coils
- your table above does NOT reflect the rewired coils
- your config on MembersPage/PeepPaadam/Config doesn't show this h[2]. If we know exact circumstances, we are more likely able to help. If we verify according to old, wrong information, that is wasting our and especially your time: the error will be found later, and we get 0 chance to reproduce your setup. Do the mcd and mct dump and publish to verify ign_out (0x72 means ign_dualout) and h[2] settings. Eg. if they are changed correctly in MegaTune, but not "burnt" into ECU, they change back after powerdown.
- but the engine still worked on 4 cylinders. Changing the wiring and conf back to seq. mode made the engine work ok at higher revs but not all cylinders at idle.
- changing the wiring back ??? why ? You would certainly NOT want to change the wiring back. That just doesn't make sense. Change just the config ( h[2] and ign_out bit1: ign_dualout flag ). But fully sequential cannot work without camsync anyway !
- do all 8 cyls have power on the ignition ?
- power on the injectors ?
- same fuel pressure on both rails ?
- Do I need to update the firmware from 1.0.38 to something newer?
- you can try 1.0.53 if no better idea, but first configure 1.0.38 properly, it should work
- if you apply camsync, or start to lose teeth at 6500 RPM, or dwell-limit near 5000 RPM, it will make sense to upgrade to overlapping dwell firmware (1.0.61 or later), that eases the cam-constraint and shortens the longest-interrupt-path (but still experimental and requires more config-options; table-testing with given config), but definitely make it work smooth (at least idle .. 2500 RPM) with non-overlapping-dwell firmware (1.0.55 or older)
All outputs are logiclevel (0 IGBT inside ECU). Logiclevel outputs pull to GND (0V) when inactive, so when you measure DC voltage with DVM, from 5V as base, you read -5V
- Wiring is separate, i.e. every ign output is to one coil respectavely, also I wired separate +12v supply and grounds for them.
- Switched +12V to coils, they are fused (two banks, 15 amps each) and grounds from the engine. Signal wires come separately from VEMS to each COP.
Car runs ONLY on primary trigger which is stock 100-1 tooth wheel on the flywheel and I don't have cam sync. I fire COPs sequentially and car starts ok every time, but some cylinders don't work on low (below 1500) rpms.
I tried to fire COPs in pairs, as wasted spark, but it did not make any difference.
Note that I fired BMW m50 engine COPs also sequentially by using just stock 60-2 trigger wheel, same low-rpm problem.
The engine runs, but high dwell (3 .. 3.5 msec ?) was needed.
- Im worried about the little voltage (almost none) from VEMS.
- what outputs ?
- what conditions ?
- what's connected ?
- measured how ?
A: I measured all logic level ign outputs and nothing was connected at that time. Used DVM in usual DC mode and it read 1 volt on ign. event. As Marcell said, it's ok.