Shared report: 2014-07-24 08:59:46
Status: Sharing

Report generated: VemsTune (Help menu/Vems Sharing Center by one-click)
I have difficulties setting secondary trigger. Using rising edge, the signal comes after the 14th primary teeth, so "secignore" value of ~15-20 seemed to be a good idea (with or without using sectrig minimum/maximum angle between 80-100 degrees). Still I cannot get this sorted, all I get is various trigger position errors in triggerlog, even for primary, which is working fine alone.

Note: You can share the link with your friends or keep it secret.
Show/Hide report details
Comments 
admin 2014-07-31 09:08:14
Hello Gergely,

Answered these symptoms in your other report:
http://vems.hu/vemstune/bugreports/reports.php?cmd=view&key=2InRHX

Best regards, Dave
GergelyLezsak 2014-07-31 07:52:24
Hi,
I've resolved serious missfire problems caused by ignition cable issues here, the car is running clear now.

Annoying things happened however, during desperate cranking tries:
- flash corruption happened two times, stuck in bootmode: had to reflash firmware
- sudden jump into safe mode happened one time (not even PC connected)

I suggest some serious protection against these to happen accidentally (by electric noise), can cause the car left on roadside.

Thanks
admin 2014-07-28 13:46:38
Hello Gergely,

Thanks for the update! If you want me to review something to help you diagnose the non-running problem, feel free to ask.

Best regards, Dave
GergelyLezsak 2014-07-28 07:23:30
Thanks Dave,
I confirm the triggering is OK using fw 1.2.27.
Apart from the triggering, the car is not running yet for unknown reason. I hope it's not firmware-related, and I can keep this fw version for stable street use.
admin 2014-07-25 03:44:42
Hello Gergely,

To put you mind at ease i did an additional benchtest using a trigger wav created from your triggerlog, with trigger setting sectrig_ignore = 22, syncs and runs perfect on 1.2.27 (attached in m44_camsync_1_2_27.png).

Make sure to update your reftooth table to "0, 30, 60, 90" from current "0, 30, 0, 30".

Best regards, Dave
admin 2014-07-25 02:37:27
Hello Gergely,

I have tested and verified many setups with secignore=20 or around that, and found they worked well with 1.2.27, including fast syncup (even if unfortunate reftooth rotation is applied).

We advise to review FirmwareChanges to get the latest updates about firmware status (even after release), unfortunate that you missed it.

Best regards, Dave
GergelyLezsak 2014-07-24 10:08:09
I have found recently at
http://www.vems.hu/wiki/index.php?page=GenBoard%2FUnderDevelopment%2FFirmwareChanges
for version 1.2.18 : "1.2.16 and 1.2.17 was restricted to secignore = 255"
It clarifies my problem I think, still it's very annoying that this information was not published at the time it was actual (for 1.2.16). And ini files, help files have no updated info on different usages of same config variable.


Attachments