Changelog:
1.0.79
* Config switch for tableswap, if not in use makesure confswitch=00
/**
* Configuration switch.
* confswitch=C3 does load_variables(1) if mcp3208 ch3 goes low
* confswitch=D3 does load_variables(0) if mcp3208 ch3 goes high
* confswitch=83 does load_variables(1) if mcp3208 ch3 goes low AND misc1 condition is true
* confswitch=93 does load_variables(0) if mcp3208 ch3 goes high AND misc1 condition is false
* any mcp3208 analog input channel can be chosen with confswitch bit 0:3 (ch 0..7)
*/
* New implemention for acceleration enrichment, RPM vs Amount and Dotrate vs Scale
http://www.vems.hu/wiki/index.php?page=GenBoard%2FUnderDevelopment%2FAccelerationEnrichment
* Velearn dropped
* Injector staging enabling now in config variables !!CHECK YOUR SETTING!!
http://www.vems.hu/wiki/index.php?page=MegaTune
I realise this is still in testing, but as im starting from scratch with this engine, i'll give it a go ;)
Any one able to help me understand the dual config switch settings :-\ I put 195 in as it says in the F1 help menue but it didnt like that :-\
There was a number in there to start with, but cant remember what it was :D and it was not one shown in the F1 help, now my uploaded tables have dissapeared and been replaced with something obscure :D not a problem if i have to re flash, i should have saved msq before i started ::)
And, im not sure on how to configure the input channel, nothing new there then :D
I have configured to 00 to dissable for now, and not really looking at using this feature at the moment, but could be usefull in the future for E85 or dry nitrous perhaps
Don't try from scratch Sir, start from a known good well tested firmware version. What trigger pattern are you using?
I think I will do Rob. I cant get the KPA bins in the tables as I want them, it apears that only even numbers are acceptable, therefore 5kpa jumps are out, makes the contour a little odd, with 4, 6, 4, 6, 4, 6 kpa jumps :-\ Maybe this is something new on later firmwares, but im sure i have set up the tables with some 5kpa jumps around the idle area.
Going back to the 1.0.73 or maybe the 1.0.78 untill its mapped, seeing as VE learn has been dropped, I manage to rough out the map with VE learn set agressive, and i have had good results in the past. I need something to get me started and driving to put some run in miles on it before the dyno.
I have a couple of good configs from Matty and Andre that will get me in the ball park for these engines anyway.
Still, the switchable maps is an atractive prospect :)
Im running the plain 36 -1 trigger ;)
Yep, gone back to 1.0.73 and i can fit odd numbers into the kpa axis on the tables.
Both 1.0.78 and 1.0.79 exhibit the same issue, the kpa axis only accepts even numbers :-\
I've never noticed the even number thing before. Mine seems happy on 1.0.78 with odd numbers, although they all end in 5.
This is because Highboost is set in settings.ini
Quote from: Sambas on October 08, 2008, 06:37:16 AM
This is because Highboost is set in settings.ini
:D
Yes, indeed.
I did have an error on starting Megatune, and was going to get round to working out what the hell that meant. ^^^^ :D
All is better now ;)
Thanks
Is it possible to get. Mat enrichment table, Map filter, and full Config swap? In a new 1.0.80? As it is in the 1.1.44? :)
I thought the point in 1.1.42 onwards is to integrate the code so that you won't need to use 1.0.xx code any more ???
Quote from: [email protected] on December 02, 2008, 03:15:26 PM
I thought the point in 1.1.42 onwards is to integrate the code so that you won't need to use 1.0.xx code any more ???
I tried the 1.1.44. startet completely fine, From 1600 - 2000rpm missfires/stumples it. It got worse with 2.5ms dvell, and slightly better with 1ms dvell. 1.0.79 works without problem with the same fuel and IGN map. Maybe a little bug?
My 1.1.44 trigger settings:
c004 signal-> coiltype, No. teeth=4, triggertooth=0, another triggertooth=1, toothwheel width=180, secondary trigger=25 and reftooth table=[0,3,2,1]
Can you datalog this? If you are not getting trigger errors then your settings shouldnt be a problem, the fact that you're changing the dwell time and getting a positive change suggests that the dwell/boost scaling might be the issue.
Rob
Quote from: [email protected] on December 02, 2008, 04:00:16 PM
Can you datalog this? If you are not getting trigger errors then your settings shouldnt be a problem, the fact that you're changing the dwell time and getting a positive change suggests that the dwell/boost scaling might be the issue.
Rob
I've tried map scale 0.1 and 2. Did not notice any difference.
My msq file 1.1.44: http://www.vems.hu/files/ArvidOlausen/Volvo%20740.test%2098%20SLOT%200%20config199.ny%20test.01.msq
Datalog 1.1.44: http://www.vems.hu/files/ArvidOlausen/datalog200812021815.xls
Righto
this is just for posterity, as I am probably the only person running 1.0.79 perhaps.
I spent three hours sat in the car, just trying to get the dual table switching working, which was no easy task with the code speak instructions relating to it. Just to note while I am here, the configuration for this in 1.0.79 is different to that in 1.1.XX
Hopefully this should be a 'dual table config for dummies' I was that dummy, and it took me three hours. I hope this will at least help others to reduce the time sat in the car during a thunder storm :D
-------------------------------------------------------------------------------------------------------------------------------------
Dual table switching
Dual table switching only, does not change config, tables only (VE, Lambda, Spark, Boost)
Save MSQ in Megatune and back up MSQ file in a safe place.
Run 'download-config.bat' and back up config.txt and tables.txt, in a safe place
Edit config.txt at line 'confswitch=xx' where 'xx' is the config setting as bellow
confswitch=C3 (does - load_variables(slot1) if input ch3 grounded)
confswitch=D3 (does - load_variables(slot0) if input ch3 at 5volts (pull up))
confswitch=83 (does - load_variables(slot1) if input ch3 grounded AND misc1 condition is true)
confswitch=93 (does- load_variables(slot0) if input ch3 at 5volts (pull up) AND misc1 condition is false)
to change input channel number to one you are using, replace the '3' in any of the above with the channel number (0..7) IE using input channel 7, the four configuration variables above would be C7, D7, 87, 97
It would be normal to just use the first configuration value IE C0,C1,C2,C3,C4,C5,C6,C7 dependant on the input channel used. The config switch is then grounding the input to activate 'slot1'
Save changes to config.txt
Run 'generate-config-16x14WithDefaults.bat' (or, 'generate-config-12x12WithDefaults.bat')
Run 'upload-config.bat'
Create two folders in the profile folder ('VEMSv3-16x14' or 'VEMSv3-12x12') one called 'slot0' and the other called 'slot1'
Copy and paste the previously saved MSQ file into each of the new folders
Run Megatune with the config switch in the 'off' position (slot0) open MSQ file in 'slot0' folder, send and burn to the ECU.
Correct the ALS input miss configuration by setting to 'DISABLE' send and burn to the ECU.
Save MSQ in 'slot0' folder
Close Megatune
Power off the ECU
Change the config switch to the 'on' position (slot1), Power up the ECU, run Megatune, open MSQ in 'slot1' folder, send and burn to the ECU.
Correct the ALS input miss configuration by setting to 'DISABLE' send and burn to the ECU.
You will now be able to change the config tables at the flick of a switch. Note that the ECU needs to be powered down before changing the config switch from one to the other, Megatune does not nescisaraly have to be closed. It is a good idea to save the MSQ files for the two different 'slots' in the folders you created.
It would appear that with Megatune running and the ECU powered up, changing the position of the switch does still change the tables without the need to power down the ECU or close and restast Megatune. I am however scared to try it with the engine running :D remembering that it is the tables only in 1.0.79 and not the whole config as in 1.1.XX.
While Wiki dredging, I found this relating to questions I previously asked regarding Barometric Correction
barometric correction roughly: adds 4% fuel if pressure at startup is -10% (eg. on a high hill) compared to normal. In fact it's a linear function, and insane values (too low baro) are eliminated. Inactive is OK, especially with WBO2
and also
# Pure Alpha-N
* VE table: TPS based
* Spark table: TPS based
* Lambda table: TPS based
# Alpha-N with baro correction
* VE table: TPS based with MAP multiplication
o important: with map sensor connected in free air or before throttle bodies
* Spark table: TPS based
* Lambda table: TPS based
# Alpha-N with boost compensation, map based spark+lambda all the time
* VE table: TPS based with MAP multiplication
* Spark table: MAP based
* Lambda table: MAP based
# Alpha-N with boost compensation, tps based spark+lambda before boost arrives
* VE table: TPS based with MAP multiplication
* Spark table: TPS based when MAP<=barometric pressure, MAP based above
* Lambda table: TPS based when MAP<=barometric pressure, MAP based above
So by the sounds of this, The question I originaly asked is answered in there. Basicaly with Alpha N, Baro Correction enabled on a normaly aspirated engine, and the MAP sensor measuring free air, fuel is added or subtracted based on the difference of MAP to 100kpa?
Wiki seems to be fragmented with two different firmware hiaraci, with some missing in one, and others missing in the other and still little expalanation of any of the real meanings of the settings
http://www.vems.hu/wiki/index.php?page=GenBoard%2FUnderDevelopment%2FFirmwareChanges
http://www.vems.hu/wiki/index.php?page=MegaTune
The pressure compensation with Alpha-N is only in 1.1.x firmware, and only above atmospheric.
Hope to stabilise that with 1.1.54 or is it 1.1.56 soon to be released. VemsTune even seems more solid now, Emil has been visiting the developers and made some progress.
Quote from: mattias on June 24, 2009, 08:24:36 PM
The pressure compensation with Alpha-N is only in 1.1.x firmware, and only above atmospheric.
Hope to stabilise that with 1.1.54 or is it 1.1.56 soon to be released. VemsTune even seems more solid now, Emil has been visiting the developers and made some progress.
Changelog and 'FirmwareChanges' on the wiki state Baro correction since 1.0.19???? :-\
I am very surprised that there is no propper barometric compensation with Alpha N. Simple MAP sensor in free air measuring the barometric pressure air temp and air pressure gives density and therefore a correction can be worked out. The world is not flat and it rains a lot. :-\
Speed desnity it doesnt matter anyway as the map sensor is being used and compensates for barometric changes.
Quote
since 1.0.19:
* added full power shift cut, with configurable spark and/or fuel cut
* baro correction updated to work in the new non-lookup scheme; baro value to megatune is in real kpa now
* baro/kpafactor table lookup is no longer supported
* if MAP multiplying is configured, only used for RPM >= config.hybrid_rpm_m
* added tach output supporting funcionality
* new per page read and write serial commands were added to fix the megatune trashing config bug
* old non-compat megatune commands were removed
As far as I knew the Baro correction works fine on AlphaN ??? I've been told that Air temp is factored in to the fuel calcs on AlphaN too.
Covered over 1200 miles this last week and only a few niggles. Well only one actualy.
Dual switching tables seems to be a problem. I canged the VE table to correct a spurious value right in the middle of cruse. It was a blatently obvious error in the table. Table was burned to ECU and MSQ saved. car was left over night, started in the morning and this spurious value was back!!. This was again corrected, and everything was fine. The following morning this spurious value was back !!!
It was at this point I configured the conf switch to 00 to dissable it and the problem dissapeared and I have had no trouble since.
Now then. I have a good idea why this happened. Prior to this last week, I changed the ignition coils to the ones I originaly was having problems with, but dramaticaly reduced the dwell times. This worked at first but then the ignition fuse blew again,after a good few hours driving. With a dwell of 0.5ms and crank added of 0.25ms, it still blew the fuse, eventualy. I wont be going back to those coils! anyway, during all this, I loaded a previous MSQ to switch back to the reliable coils, but I think I may have loaded the wrong one whith the wrong conf switch setting, which matched the other config on the opposing conf switch setting. This I think confused Vems, not knowing where to put any new changes, so it does not actualy burn them to memory, they are however in volatile memory.
I had it working, and now it doesnt, and the point at which I can trace back to was when the fuse blew on the coils and the MSQ was loaded.
Some research time in the next few days to prove that theory ;D