History of MembersPage/MichaelRichards/TriggerTutorial/SimpleTrigger
Older Newer
2007-04-12 20:17:18 . . . . modemcable009.32-200-24.mc.videotron.ca [updates]
2007-03-25 19:30:49 . . . . modemcable009.32-200-24.mc.videotron.ca [fixed]
2007-03-25 19:29:00 . . . . modemcable009.32-200-24.mc.videotron.ca [oops]
2007-03-25 19:28:21 . . . . modemcable009.32-200-24.mc.videotron.ca [debug info]
2007-03-21 09:34:34 . . . . MembersPage/MarcellGal [reset_engphase_after haunting; + minor cleanup]
2007-03-21 05:06:53 . . . . MembersPage/JorgenKarlsson [Fixed a few errors, but there is still some questions.]
2007-03-21 03:05:38 . . . . modemcable009.32-200-24.mc.videotron.ca [finished with the info I have.]
2007-03-20 23:38:31 . . . . modemcable009.32-200-24.mc.videotron.ca [primary]
2007-03-20 14:54:07 . . . . modemcable009.32-200-24.mc.videotron.ca [more edits]
2007-03-20 14:32:47 . . . . modemcable009.32-200-24.mc.videotron.ca [Creation]


Changes by last author:

Changed:
0x40 as in MembersPage/Fero/SUPRA, absolutely consistent with GenBoard/UnderDevelopment/FirmwareChanges (!!!) and confirmed by Marcell in MembersPage/MichaelRichards/Projects/NicksGTX/Trigger for this specific setup. Is there a reason to deviate (to something that will most likely NOT work!) and push 04 again and again ? Or was that by accident ?

<code>

reset_engphase_after=40 # since camsync is used

</code>

Reading the source code shows that this parameter is not used therefore its value has no effect on the operation.
Changed:
For 1.1.x series firmwares running in 'non-missing' mode this tell the firmware which tooth to trigg from in relation to the H[1]table. trigger_tooth must be < another_trigger_tooth. For this application this only leaves trigger_tooth=0
For 1.1.x series firmwares running in 'non-missing' mode this tells the firmware which tooth to trigg from in relation to the H[1]table. trigger_tooth must be < another_trigger_tooth. For this application this only leaves trigger_tooth=0
Changed:
For 1.1.x series firmwares running in 'non-missing' mode this tell the ECU how many steps to take at a time in the H[1]table. For this application we want to use every entry in the H[1]table and which give us another_trigger_tooth=1
For 1.1.x series firmwares running in 'non-missing' mode this tells the ECU how many steps to take at a time in the H[1]table. For this application we want to use every entry in the H[1]table and which give us another_trigger_tooth=1
Changed:
reset_engphase_after=04
reset_engphase_after=ff
Added:

---

Debug Info

These settings do not appear to work correctly as the spark timing is way off. I've created an excel spreadsheet to calculate the datalogged results. I am logging the primary, secondary and 2 coil signals. For the coil signals I used a voltage divider so it will float at vbatt/2 volts and be pulled to ground during dwell as my DAQ card will only read -10-+10vdc. Sample rate is set at 10khz to catch the 1.6ms dwell.

|| TDCDelay || Prim Down || Prim Up || Trigger || sec/degree || RPM || TDC || Actual Timing || desired timng ||

|| 0x60 || 2.976 || 3.092 || 3.016 || 0.002188679 || 152.2988506 || 3.070113208 || 24.72413793 || 10 ||

|| 0x60 || 3.553 || 3.67 || 3.594 || 0.002207547 || 150.997151 || 3.647924528 || 24.42735043 || 10 ||