Trigger errors from 3000+ rpm on 944 Turbo 132+1 VR

[PeepPaadam]

Could you guys give some hints what could be the problem? Is it noise? It shows tooth length error and in triggerlog lower rpms are clean, from ~3000rpm it starts giving errors.

It is 132+1 tooth "auditrigger", without CAM sync.

Here's triggerlog file: http://www.vems.hu/files/PeepPaadam/v3.3_u009985-2015-06-21-14.22.35.triggerlog

[VEMS]

Hello Peep,

I suspect you need to invest polarity of your single tooth sensor, but your triggerlog does not provide much usefull info; More usefull would be a triggerlog in coiltype + camsync 8-10 seconds without IGN and INJ fuse so i can see the full 132 +1 cycle.

Best regards, Dave

[PeepPaadam]

Alright, I will send you triggerlog with starter motor. But there it doesn't show any errors, clean as a whistle. Used the configlet in VEMStune.

[VEMS]

Hello Peep,

Alright, I will send you triggerlog with starter motor. But there it doesn't show any errors, clean as a whistle. Used the configlet in VEMStune.

Make sure to configure the ecu as normal coiltype + camsync, not auditrigger for this test and reboot ecu after changing from auditrigger to coiltype normal. If you safe your config before changing you can reapply it after the test. Thanks!

Best regards, Dave

[PeepPaadam]

Ok, he made a triggerlog, but I think it is made with 944 Turbo 132+1 configlet: http://www.vems.hu/files/PeepPaadam/v3.3_u009985-2015-06-26-18.52.10.triggerlog

If it is no use, I could ask him to just do another one with the config modified to have just coil type+cam sync.

[PeepPaadam]

Bump, could really need some help with this issue...

[VEMS]

Hello Peep,

The triggerlog you supplied: v3.3_u009985-2015-06-26-18.52.10.triggerlog is not in the instructed format, please ask your customer to follow directions in order to move forward.

Best regards, Dave

[PeepPaadam]

Customer made another triggerlog, this time with coil type+cam sync but cam sync doesn't show up at all? He also power cycled the ECU just as instructed.

http://www.vems.hu/files/PeepPaadam/v3.3_u009985-2015-07-07-17.21.08.triggerlog

[VEMS]

Hello Peep,

Customer made another triggerlog, this time with coil type+cam sync but cam sync doesn't show up at all? He also power cycled the ECU just as instructed.

Without a configuration it is hard to pinpoint what went wrong there, but it is most likely a configuration error as we have seen before the secondary trigger is operational.

Best regards, Dave

[PeepPaadam]

Here's the current config, could you please check it out? http://www.vems.hu/files/PeepPaadam/v3.3_u009985-A-2015.06.24-21.17.31.vemscfg

[VEMS]

Hello Peep,

You posted the config "v3.3_u009985-A-2015.06.24-21.17.31.vemscfg" with auditrigger enabled, we were trying to diagnose (at least i am) why the sectrig does not show up when configured as coiltype+camsync normal; Could you post the config (belonging to triggerlog "v3.3_u009985-2015-07-07-17.21.08.triggerlog" below so i can review ?

Thanks! Best regards,


Dave

[PeepPaadam]

Oh, ok Here's the config he used to make triggerlog: http://www.vems.hu/files/PeepPaadam/for%20recording%20triggerlog.vemscfg

[VEMS]

Hello Peep,

I reviewed "for%20recording%20triggerlog.vemscfg" it should be configured correctly to flag both primary and secondary trigger, the only thing i can think that would cause improper behavior would be forgetting to power cycle in between changes (but you already stated you customer did that), strange ...

Has your customer already tried swapping secondary VR+ and VR- at sensor side to verify VR polarity causing the issue at 3000 rpm (with his normal "v3.3_u009985-A-2015.06.24-21.17.31.vemscfg" config back in place) ?

Best regards, Dave

[PeepPaadam]

Secondary VR polarity should not be changed on 944's. According to Pete, it caused serious issues: http://www.vemssupport.com/forum/index.php/topic,345.msg3826.html#msg3826

I could ask customer to try (though not in permanent way) to swap and see.

[VEMS]

Hello Peep,

Secondary VR polarity should not be changed on 944's. According to Pete, it caused serious issues: http://www.vemssupport.com/forum/index.php/topic,345.msg3826.html#msg3826
I could ask customer to try (though not in permanent way) to swap and see.

Serious issues like 3000rpm trigger errors ? I'm looking forward to your report of swapped secondary VR behavior, please keep in mind that this is the first thing i suggested you to check on: June 25, 2015, 11:44:25 pm; It is very hard for me to provide support when my hints/suggestions are not observed and/or executed.

Best regards, Dave