Update
Found that this only happens when a non existing trigger setup is in use, we were both testing with a plain 60-2 wheel trigger without camsync, and tried to use more outputs than possible with this setup.
examples:
- Working properly
- 4 cylinder setup (next trigger tooth = 30), using 2 coil outputs
- 6 cylinder setup (next trigger tooth = 20), using 3 coil outputs
- 8 cylinder setup (next trigger tooth = 15), using 4 coil outputs
- NOT working properly
- 4 cylinder setup (next trigger tooth = 30), using anything more than 2 coils
- 6 cylinder setup (next trigger tooth = 20), using anything more than 3 coils
- 8 cylinder setup (next trigger tooth = 15), using anything more than 4 coils
This changing behaviour based on tdcdelay or dwell is still strange, but not a huge issue any more!
//Emil
Issue
IGN output behavior changes with RPM and # of cylinders.
- Firmware 1.0.23, Megatune r27 and r30 all show same results
- Firmware is precomiled from website version 1.0.23
I found this issue when attempting to functional check a unit prior to configuration. Initial reports suggested that it was a bad trigger signal (benchtop generation). Resolved this problem and now can generate a proper 60-2 wheel VAG style without any wheel count errors.
mcel.. if you change your IGN outputs to 00 01 02 03 04 05 06 07 instead of 00 01 00 01 00 01 00 01 you can recreate the error with your config
Description of issues
- Given: [MembersPage/GrmRacer/TurboSetup/TurboConfig Config] firmware, and tables
- there is an output channel conflict: misc1out_channel=06 and misc2out_channel=06. Also, you might want to change the disabled channels for FF (although xF shouldn't cause problem)
- divider=02 why ? (should be 01 right ?)
- try to configure tooth_wheel_twidth1, tooth_wheel_twidth2 and reset_engphase_after properly (although shouldn't matter with secondary_trigger=02 thus disabled)
- Issue is a function of # of cylinders, RPM, and default Megatune IGN output behavior.
- Under Idle conditions, ie. < 1500 RPM for a wasted spark ( 2 outputs alternating) works fine for any setting. If the RPM goes above a threshold (41Hz for 4 clyn, 29Hz for a 8 clyn). the output changes to include other non-configured output.
Current experiment
Reflash VEMS v3.3 with new firmware 1.0.23 first then use the latest release.
Firmware version 1.0.23 as downloaded from filethingie
- no recompilation done
- configs & Table changed using MegaTune (r30) only
- pretending to be end user trying to get board setup
- I also don't want to go thru the toolchain setup to do it.
Problem is that the number of outputs driven changes when a factor of RPM and # of clyns and #of IGN outputs selected
Original configuration to find problem
Basic description is the Ingnition outputs were set in
Ignition Settings
Outputs to use in h[2] set to [7..0]
- Ingnition ouputs set to
- 0 Drive00
- 1 Drive01
- 2 Drive02
- 3 Drive03
- 4 Drive04
- 5 Drive05
- 6 Drive06
- 7 Drive07
- above 41Hz(~2500rpm) with an 8 clyn setup. Note that another_trigger_tooth=1E doesn't seem good for 8cyl. Please provide all the configs you used.
- above 29Hz(~1650RPM) with a 4 clyn setup
if Ignition Settings
- outputs to use in h[2] is set to [1..0] symptom goes away.
if Ignition Settings
- outputs to use in h[2] is set to [2..0] three outputs trigger above 41Hz(4clyn)
if Ignition Settings
- outputs to use in h[2] is set to [3..0] four outputs trigger above 41Hz(4clyn)
- outputs to use in h[2] is set to [7..0] 8 outputs trigger above 41Hz(4clyn)
Emils report
triggering the board at 2000 rpm, trying to reproduce GRMracers report of strange ignition outputs
2000 rpm, 60-2, tried with ignchmax = 03 or 07, same result
based on marcell's example config
- at 2000 rpm, it works properly with dwell >= 2.82, but with 2.75mS or less, only 2 outputs is driven
- if i then lower TDCdelay from 56 to 55 degrees, all outputs turn back on
- with TDCdelay = 55, only 2 outputs are active with dwell anything lower than 2.75 mS
- with TDCdelay = 50, dwell below 2.30 mS will give the same result