1.1.43 alpha2 test result

[Sambas]

Post problems and result when testing 1.1.43.

!Save your old tables and configs.!

READ! changelog and disconnect injector and ignition fuses before updating. Lot of new output channels avaible so check them from  output pages.

Export your tables from old msq, VE and sparktables had some changes.

If you need to revert back to older firmware, note that new firmware is running at comspeed 19200. You need to add "-b 19200" to your upload firmware command.

If needed I can convert your running msq file for this new firmware, just add link where to download.

[gunni]

60-2 VR sensor

No trigger errors whatsoever , but I have one ignition coil and thus all cyl´s output on the one pin.
but I only get 2 ignition events at the plugs. Timing gun had right rpm´s for both of those cylenders ( 2 and 5 )
but nothing from the other ones. coil lead had twice the engine rpm

here is the msq.
http://www.gstuning.net/files/files/vems/test%20run%201.zip

Config and tables at the bottom of this page.
http://www.vems.hu/wiki/index.php?page=MembersPage%2FGunnarReynisson

[Sambas]

Your reference tooth table was wrong and also h2 had bad values. Fixed in here http://kotisivu.dnainternet.net/sakrkorh/vems/fw1143/testrun1gunnifixed.msq
Disabled AIM stream so if it is used enable it from lcd config page. Mat curve is enabled when in mat table lowest tpsbin is 100%, if something else then mat table is used.

[gunni]

I couldn´t change the reference table, only the first value, the other ones where greyed out.

any info on those settings?
Also explain the MAT table , why 100% in the bottom row?

[Sambas]

I couldn´t change the reference table, only the first value, the other ones where greyed out.

any info on those settings?

Ignition outputs in use in h[2] defines it. That's the way it should be with 1.1.x firmware, number of ignition channels equals number of cylinders even if only one channel is used. Toothref table is there for counting position. You should just burn in that fixed msq.

Also explain the MAT table , why 100% in the bottom row?

MAT table is advanced version of MAT curve that also uses TPS as one variable. If you want to use it just put 0% to lowest bin.

[gunni]

More testing.

Runs now.
Tip in is amazing difference. and so is throttle accel while driving, almost like the engine flywheel has been taken off
compared to before.

I have some running problems at above 4k.
Dwell goes upto 4,4ms and Vbatt falls as the rpm´s go up and it missfires/stumples. Looked into log from 1.0.78, vbatt does the same but the dwell doesn´t go as high (3,52ms) and no problems driving actually.

So I guess there is an issues with my alternator or wiring.

EDIT

After looking at logs from 1.0.73 1.0.87
It seems it´s this
coil chargetime map scale that must be extending the dwell?
it´s now at 37 , nothing about it on the Wiki or this forum.

[[email protected]]

Is this because the dwell voltage compensation is now automatic?

[Sambas]

since 1.1.32

Code: [Select]

#  config.ign_dwellmap configurable MAP-based dwell scaleup (VBATT based is automatic)

    * 00 no dwell extension at all (neither VBATT nor MAP based): ign_dwell14 is used
    * 01 only VBATT based dwell extension (max *2, when VBATT <= 7V)
    * values 02..FF : VBATT based extension is automatic. Slope of MAP-based dwell-extension is configured with this variable. MAP-based extension is max *1.4 (+40%), while total scaleup (vbattmultiplier * mapmultiplier) is max *2
          o dwell is extended by (map - 70kPa) * ign_dwellmap/4096 but no more than +0.4 (40% extension that is *1.4). Examples:
          o ign_dwellmap=0A (decimal 10) max dwell-extension +40% reached at 234 kPa because (234 kPa - 70 kPa) * 10 /4096 = 0.4
          o ign_dwellmap=14 (decimal 20) max dwell-extension +40% reached at 152 kPa because (152 kPa - 70 kPa) * 20 /4096 = 0.4
          o higher value means higher slope (so max dwell extension reached earlier). Take care not to overload the ignition output or the coil (use lower ign_dwell14 so you only get extended dwell when really necessary).



[Denmark]

I do now regret to have to many cars to work so, i havend got time to doing some test on my own car


/Skassa

[gunni]

Latest update.

Everything is sorted.

cut the dwell down to 2,18ms and the map scale down to 2(max possible dwell from map added is 3,08ms, max at 7V is 4,3ms, the 10,xx v I was getting before would not let it past about 3,4ms.
 
Now there is no pull down of the voltage as rpm´s go higher and dwell doesn´t go further then 2,25ms.
I will later add to the map scale if I get blow out at boost(my max would be about 3,2ms or so for this coil I think).

It must have been the excessive dwell causing the voltage to go down and that further adding to the dwell , so a chain reaction basically until it missfired. I´d assume it was the coil pulling the voltage down (this problem I had is probably the reason I blew two IGBT´s before doing long runs under load )

Adjusted accel enrichment a little more. Now it´s like I have ITB´s
car before was great to drive on throttle , low load , high load partial throttle accel, now all that is just better from the accel enrichment settings and tip in issues are all gone.

Great upgrade.

[Sambas]

Nice to hear it works and behaves, hope someone with different trigger setup can also test this. Do you find the new accel enrich easy to tune?

[[email protected]]

I might be able to test on 24+1 this weekend - If I send you my config and tables can you check what needs to be changed?
Then I'll write up on here some instructions - highlighting what values are needed to be calculated and adjusted and we'll have a bit of a how-to upgrade guide.

Rob

[Sambas]

Sure I can Rob. Some of the test cases I did are avaible here http://kotisivu.dnainternet.net/sakrkorh/vems/fw1143/. Tables and outputs might be messy, but trigger related setting should be correct for all cases.

[gunni]

Nice to hear it works and behaves, hope someone with different trigger setup can also test this. Do you find the new accel enrich easy to tune?

yea very easy.

[[email protected]]

Can you give us some sort of description of the method that you used?