History of MembersPage/JorgenKarlsson/MiataNb
Older Newer
2015-06-08 10:24:35 . . . . 213-66-224-51-no21.tbcn.telia.com [Intermittent sensor fault found, issue solved.]
2015-04-09 11:00:49 . . . . 213-66-224-51-no21.tbcn.telia.com [Additional testing will be done in the car.]
2015-04-03 10:47:26 . . . . 195-240-176-40.ip.telfort.nl [bench tested in elaborate scenarios, more info needed]
2015-04-02 19:10:45 . . . . 213-66-224-51-no21.tbcn.telia.com [Log and cfg of issue supplied.]
2015-04-02 12:55:59 . . . . 195-240-176-40.ip.telfort.nl [addional info required]
2015-04-02 12:14:36 . . . . host-95-195-158-126.mobileonline.telia.com [Looses sync]
2015-03-22 17:30:11 . . . . host-95-195-215-47.mobileonline.telia.com [Added config for Mazda Miata Nb on 1.1.32]
2015-03-22 17:23:07 . . . . host-95-195-215-47.mobileonline.telia.com [Mazda Miata now runs on 1.2.32.]
2015-03-22 16:54:05 . . . . host-95-195-215-47.mobileonline.telia.com [Mazda Miata no spark after upgrading to 1.2.32]
2015-03-22 16:52:50 . . . . host-95-195-215-47.mobileonline.telia.com [Miata no spark after upgrading to 1.2.32.]
2015-03-22 16:34:54 . . . . host-95-195-215-47.mobileonline.telia.com [No spark on Miata trigger with 1.2.32 longgap]
2015-02-10 16:33:31 . . . . host-95-199-7-172.mobileonline.telia.com [Engine runs on stock Mazda trigger now.]
2015-02-10 14:54:01 . . . . host-95-199-7-172.mobileonline.telia.com [Problem found and fixed.]
2015-02-10 14:49:06 . . . . 195-240-176-40.ip.telfort.nl [scoping might provide insight..]
2015-02-10 14:27:10 . . . . host-95-199-7-172.mobileonline.telia.com [Added triggerlog with a shadow trigger pulse]
2014-11-26 08:46:17 . . . . catv-80-98-222-153.catv.broadband.hu [note: implementation depends on sectrig]
2014-11-26 08:44:55 . . . . catv-80-98-222-153.catv.broadband.hu [implementation depends on sectrig]
2014-11-25 17:48:17 . . . . catv-80-98-222-153.catv.broadband.hu [modified pseudocode]
2014-11-17 15:05:17 . . . . 213-65-30-141-no21.tbcn.telia.com [Completed the trigger documentation.]
2014-10-28 21:11:40 . . . . c-867fe655.07-258-74686e1.cust.bredbandsbolaget.se [Added info]
2014-10-28 21:09:58 . . . . c-867fe655.07-258-74686e1.cust.bredbandsbolaget.se [Added info]
2014-10-22 14:09:30 . . . . ktv54017714.fixip.t-online.hu [question about cam trigger]
2014-10-21 22:36:24 . . . . 213-65-30-141-no21.tbcn.telia.com [Trigger, Work in progress.]


Changes by last author:

Changed:
I think that this trigger does not regains synk after a false trigger. I had the car die several times when hitting the revlimiter on the dyno. The ECU seemed happy while the rpm fell to zero. Cycling the ignition during this time makes the engine catch again.
The "lost sync" issue is solved and the car runs fine, the trigger sensor developed an intermittent fault which became more apparent with time. It was quite consistent at the end, the trigger sensor seemed to lock up and stay high until the next tooth arrived, it then went low and sent out a short pulse again. The total number of teeth per turn stayed the same but everything moved.

The wierd thing is that the stock ECU runs fine when the trigger sensor is acting up, I guess that it's common enough for them to have made a workaround.

It is possible that changing the trigger edge could make the car work better when the trigger occur or that the error detection could be improved by activating the filters, but the car runs now and the error is not something that you can miss.

Changed:
Thanks for testing it, I will try to recreate it enough times to be able to strobe and scope the engine while it happens. As it only happens once in a while when hitting the revlimiter it's not easy. -Jörgen