rassie Posted October 25, 2023 Report Share Posted October 25, 2023 Hi I'm trying to run a Fit (Jazz) L15B with Force GDI. I entered the base data, but the number of trigger errors has increased and the trigger cannot be started. ECCSSync also remains NO during cranking. I would like some advice on where to look again. Attached is the trigger data while cranking. Trigger Scope Log 2023-10-25 8;37;20 pm.llg Quote Link to comment Share on other sites More sharing options...
Adamw Posted October 25, 2023 Report Share Posted October 25, 2023 The trigger scope looks like it should work ok. ECCS sync status is only used for the Nissan 360 trigger so this is normal to remain as NO for other trigger modes. Can you do a short PC log with the engine cranking, and attach a copy of your tune also. Quote Link to comment Share on other sites More sharing options...
rassie Posted October 26, 2023 Author Report Share Posted October 26, 2023 Attached are cranking logs and data. The symptoms are the same with JAzz base data. ログ 2023-10-26 5;50;午後55時.llg test1.llg test2.llg fit1.pclr Quote Link to comment Share on other sites More sharing options...
Adamw Posted October 26, 2023 Report Share Posted October 26, 2023 Your logs certainly show a trigger issue, but I dont yet see an obvious cause from the trigger scope. You are using quite old firmware and I remember there was a version around 5.6.6 that had some issues with some trigger modes, so I think the first thing to do is update the ecu to the latest firmware which is 5.6.8. After the firmware update, temporarily set the trigger mode to "Subaru V1-6", do a store, then change the trigger mode back to the original Holden Alloytec II settings, do a store again, then cycle ignition switch off and back on and give it a try. This procedure will re-initialise the trigger code if there is possibly something messed up from the unknown firmware. Quote Link to comment Share on other sites More sharing options...
rassie Posted October 26, 2023 Author Report Share Posted October 26, 2023 Thanks I'll try it. Quote Link to comment Share on other sites More sharing options...
rassie Posted October 26, 2023 Author Report Share Posted October 26, 2023 I updated and changed the trigger settings from V1 to V6 and returned them to their original state, but there was no change. When cranking with the K20A trigger pattern, there was an action that seemed to stop the cranking with a hammer. Log 2023-10-26 9;41;26 pm.llg Log 2023-10-26 9;41;48 pm K20.llg Quote Link to comment Share on other sites More sharing options...
Adamw Posted October 26, 2023 Report Share Posted October 26, 2023 Can you do 2 further trigger scope captures while cranking, and attach a freshly saved copy of your map. Quote Link to comment Share on other sites More sharing options...
rassie Posted October 27, 2023 Author Report Share Posted October 27, 2023 I can't test today, so I'll attach the test data tomorrow. This is the map 1 is alloytec, 2 is K20 If it is 1, the trigger error count will increase. fit1.pclr fit2.pclr Quote Link to comment Share on other sites More sharing options...
rassie Posted October 30, 2023 Author Report Share Posted October 30, 2023 Work has temporarily stopped because it will not be completed in time for the next run. sorry. Trigger pattern is attached. I found a document that says the alloytec cam trigger is 4x, but is it okay to leave it as it is at 3x? Trigger Scope Log 2023-10-25 8;37;20 pm.llg Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.