VEMS Community Forum
VEMS => Software => Topic started by: Sambas on November 24, 2008, 08:03:28 pm
-
Available here:
http://kotisivu.dnainternet.net/sakrkorh/vems/firmware_1.1.44alpha2.zip (http://kotisivu.dnainternet.net/sakrkorh/vems/firmware_1.1.44alpha2.zip)
since 1.1.44:
- Customlcd is on page 4
- Customlcd cleaner design
- SIPR protocol bugfix (always return with ign_table )
- Config switch also swaps configs, megatune shows used slot flag. Both configs need to be prepared for correct slot and correct slot has to be manually selected when uploading. For example slot0 confswitch=199 and slot1 confswitch=215
- requested tenpoint cranking pulsewidth curve, used if config.cwl=config.cwh=0
-
:)
Just load it onto my test board!
Are "geek" LCD is dropped? I suggest leave it. Page 4 and 8 is unusable. May be it is possible replace one with old mode?
In new LCD i miss EgoC. It looks more valuable info than advance.
EgoC can tell much if some problem is rising. But advance is only a result. similar to PW on "geek" style.
My strategy is sell LCD for every customer. Main reason - with LCD is easy to solve simple problems by phone. No need for laptop and me.
Gints
-
- requested tenpoint cranking pulsewidth curve, used if config.cwl=config.cwh=0
Sorry. What it means?
-
- requested tenpoint cranking pulsewidth curve, used if config.cwl=config.cwh=0
Sorry. What it means?
In mortal language: if both - CrankWarmPW and CrankColdPW is 0ms, cranking table being used. Right? :)[/list]
-
Megatune now is much clearer! Graphical editing rules! Now i see how lumpy was my IAC curve ;D
What is Boostswitch?
I have switching configs on my test board. :D
-
Are "geek" LCD is dropped? I suggest leave it. Page 4 and 8 is unusable. May be it is possible replace one with old mode?
In new LCD i miss EgoC. It looks more valuable info than advance.
EgoC can tell much if some problem is rising. But advance is only a result. similar to PW on "geek" style.
geekmode is not dropped, it just got replased this customlcd. I think I'll put this customlcd to page 4.
In mortal language: if both - CrankWarmPW and CrankColdPW is 0ms, cranking table being used. Right? :)[/list]
Yes.
What is Boostswitch?
It can scale your BoostDCtable on fly, either by potentiometer or switch and voltagedivider.
-
Release version is now alpha2
-
Hi!
Can I use the 1.1.44 with simple trigger? 2 teeth hall trigger, plus hall trigger camsynk? ::)
-
Hi!
Can I use the 1.1.44 with simple trigger? 2 teeth hall trigger, plus hall trigger camsynk? ::)
Did quick test and it should be ok. c004 signal-> coiltype, No. teeth=4, triggertooth=0, another triggertooth=1, toothwheel width=180, secondary trigger=25 and reftooth table=[0,3,2,1]
-
I've done some work on the .ini file, really mainly polishing work, cleaning up titles and so on.
The cold cranking is only adjustable if the two cranking values are set to zero.
Save a copy of: http://www.vems.co.uk/VEMSDev/vemsv3_1.1.44.ini
And rename it to vemsv3.ini then put it in any of the profiles you want.
-
I've done some work on the .ini file, really mainly polishing work, cleaning up titles and so on.
The cold cranking is only adjustable if the two cranking values are set to zero.
Save a copy of: http://www.vems.co.uk/VEMSDev/vemsv3_1.1.44.ini
And rename it to vemsv3.ini then put it in any of the profiles you want.
Updated the packet with your file including some additions. If someone wants to contribute, we could use some helppages (the ones that appear when F1 is pressed) for the megatune menus. Just simple guide what does the variables mean in current menu with examples, default values etc.
-
Today tried config/tables switch and works perfekt. Now i can use pwm for lpg(0.9ohm injectors) and no pwm for gasolin(15ohm injectors).
Tnx for this update.
-
In the .ini file ,
fuel pressure gauge is analog channel 7 input, would it not just be simple to call it that?
-
Hi!
Can I use the 1.1.44 with simple trigger? 2 teeth hall trigger, plus hall trigger camsynk? ::)
Did quick test and it should be ok. c004 signal-> coiltype, No. teeth=4, triggertooth=0, another triggertooth=1, toothwheel width=180, secondary trigger=25 and reftooth table=[0,3,2,1]
Hello, Thank you for your help! Tested Firmvare 1.1.44 today. The car started without any problems. :-)
-
Any more info on setting up the dual config?
-
Any more info on setting up the dual config?
If you connect config switch to analog ch 7 than you use confswitch=199 for slot 0 and confswitch=215 for slot 1.
If you use analog ch 6 than confswitch=198/214
-
where are those information changed?
is the switch a 0v (off) / 5v ( on )
I think a little more outlined explanations are required.
-
where are those information changed?
is the switch a 0v (off) / 5v ( on )
I think a little more outlined explanations are required.
When is confswitch=199 and 5V is on analog input(on vems board is pull up resistor) then is slot 0 activeted.
When you connect ch7 to ground(0v) then is slot 1 activeted.
-
Where is that changed?
I changed it in MT and after that next time I went into MT
the firmware was all of a sudden 16x14 STD instead of the 16x14 I was using.
Is this done in the config before uploading using the .bat files initially?
A little walk through would be appreciated ;)
-
Save your config(msq) with megatune. Make two copies. Open it(first copie) with wordpad or something like that and find confswith
change to this if you use ch7
<constant name="confswitch">195</constant>
<constant name="confswitch_bits">"7"</constant>
if you use ch6 to this
<constant name="confswitch">194</constant>
<constant name="confswitch_bits">"6"</constant>
Then open second copie(msq) and again find confswiht and change to this(for ch7)
<constant name="confswitch">215</constant>
<constant name="confswitch_bits">"7"</constant>
Now you have two config(first is for slot0 and second for slot1).
Upload first config to vems, exit megatune, change switch to short analog channel to ground(slot1), turn on megatune and upload second config. Now you can tune individual each config(slot0, slot1). But if you change slot you must close and start again megatune.
-
Excellent,
Thanks, now I just need to change my MCP chip and we´ll have double config.
-
Hi! I am testing the 1.1.44 alpha in my car. My car is fine up to 1600rpm. From 1600 - 2000rpm missfires/stumples it, than 2200rpm, it seems that it is ok?
Tried to lower dvell from 2ms to (1ms) and the engine is fine up to 1800rpm. Are now Running with 1.1.79 with the same fuel and IGN map with no problem.
c004 signal-> coiltype, No. teeth=4, triggertooth=0, another triggertooth=1, toothwheel width=180, secondary trigger=25 and reftooth table=[0,3,2,1]
My mat table is at Tps 0-100% (120% -38c) (115% -18c) (100% 0c) (100% 20c) (99% 40c) (97%50c) (95% 60c) (93% 70c)
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
-
I have same maps for ignition,ve.. for 1.0.73 and 1.1.44. But now you have mat enrichment talbe(loock that table).
-
And note other setting for angular width of tooth.
-
(http://www.gstuning.net/files/images/vems/standard%20temp%20biased.jpg)
This would be the startup temp map biased from 20°C
It´s based on the standard temp/pressure to density ratio.
TPS can further from this adjusted for heatsoak situations.
Agreed?
-
I can't reproduce this lcd 1.xx lambda problem. Tested many setups, including MWfire's msq. Could it be some mystery interference problem? How long is your lcd cable? Is it shielded and shield connected to case from Ecu end of connector?
Slow lcd is explained by new task handling. Lcd is low priority task which is over ruled by higher priority tasks ( engine management ).
I tested .44alpha2 on real car. 4cyl 60-2 no camsync, Alpha-N. Wasted spark.
I note mentioned problem. It is present most of the time. 0 and 1 did not changing when needed.
Car previous ran on 1.0.73 with no any LCD related issue.
No other bugs noted.
Gints
-
Hi! I am testing the 1.1.44 alpha in my car. My car is fine up to 1600rpm. From 1600 - 2000rpm missfires/stumples it, than 2200rpm, it seems that it is ok?
Tried to lower dvell from 2ms to (1ms) and the engine is fine up to 1800rpm. Are now Running with 1.1.79 with the same fuel and IGN map with no problem.
c004 signal-> coiltype, No. teeth=4, triggertooth=0, another triggertooth=1, toothwheel width=180, secondary trigger=25 and reftooth table=[0,3,2,1]
My mat table is at Tps 0-100% (120% -38c) (115% -18c) (100% 0c) (100% 20c) (99% 40c) (97%50c) (95% 60c) (93% 70c)
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
I've tested 1.1.44 more today. lowered the spark to 20 degrees in 1500-2500rpm area . The missfires/stumples are gone. ? ?
Does anybody have any idea why this happens?
-
Were you testing the advance with a timing light?
-
Were you testing the advance with a timing light?
yes. I have tested with timingligth at 1000-1500 rpm, seems ok. I will test 1500 - 3000 rpm later.
-
There is always possibility that your trigger type doesn't work properly in all conditions with this firmware. I can only do very limited testings.
-
So far i made 500km on 1.1.44(opel(gm) 60-2 trigger wheel)) whitout problems.
-
First off, Merry Christmas. TV is crap and im visiting the family tomorrow :D
Im looking at upgrading to this, this week and I have been looking through.
I was a teeny weeny little bit disapointed when looking at the misc outputs that there is still no min and max temperature settings. I thought I had seen this at some point somewhere, and was pleased. Now, again, I have no proper strategy for the emissions purge control :-\
edit
OK I found what I was looking for in 1.1.43. how stable is this compared to 1.1.44, i like the speed sensor and n20 settings
-
Today I have decided to upgrade to this version of firmware, as there still appears to be issues I am not happy with, with other versions. So my thinking was this was a better place to start. It has not been without issues!
After struggling through this with the limited information I could find or follow, I still had to 'wing it' with certain settings, namely, I was unable to get the config switching to work. I did everything that was described in setting up the two MSQ files, but it still only uploaded one MSQ. The LED at the bottom of Magatune indicated the slot for the active config, but the switch just didnt work. I changed the config_enable setting from disable to enable and it worked, but for what ever reason the MSQ files were screwed except for the tables. Not a problem and easy to fix, just anoying after sitting in the car for over an hour in the cold!
Other things I am not sure about, which may be simple, I am just after confirmation. The primary trigger settings are different to those in 1.0.73. The angular width of teeth setting is now a little confusing, not that it wasnt before. I read the F1 help, which says that for 36-1 the angular width should be 10. Is this correct? The line at the very bottom of the help window confuses everything. The setting Megatune threw in there was 193.5, deffo does not sound right at all. Perhaps the reason the engine wouldnt start
Other than that I think i got through everything reasonably well. I was not looking forward to the AIM stream/ Megatune crash thing, which had been said to be fixed, it appears that it was ;D
Oh, the only other thing. I have an LED in red at the bottom right corner of Megatune with three dashes in it, Why?
Edit, and something else I just remembered. In ignition settings, the coil charge time MAP scale. How do I set this up? This may be something else that stopped the engine firing, perhapse I have blown the fuse for the coils?
Edit again, I found this :D http://195.159.109.134/vemsuk/forum/index.php/topic,653.msg6767.html#msg6767
Edit yet again :D I have been playing around with Megatune. I set the config switch to 195, but when Megatune loads the MSQ it changes it to 199?
-
Angular width of tooth setting was confusing in all previous versions. Now it is very straightforward - it means crank angle between two teeth. (yes 10.00 deg for 36-1) Real angle in most cases except Audi concept where dividing by 3 virtually makes 3 time bigger gap than on real wheel.
Also take a look to reference tooth table. Fill it with 0-18 or 0-18-36-54 with camsync. Backwards - start from bottom! Then check injector staging settings.
Oh, the only other thing. I have an LED in red at the bottom right corner of Megatune with three dashes in it, Why?
It is misfire indicator. Forget it!
Config switch. Check changelog. For first it was possible to change only tables. What input and according values in MT you try to use?
Gints
-
Ok thanks for that.
The two slots configs were not corrupt as i had thought. For whatever reason they all look as they should.
I am still having problems getting the engine to start!! I changed the angular width of the tooth to 10, and every now and then the engine does trie and start but it kicks back. I am now wondering If I have to change any of the other settings. At the moment I have 35 for the number of teeth, 1 as the trigger tooth and 18 as the next trigger tooth, this obviously being a 36 -1 trigger
This is the 1.0.73 config txt
primep=00
primep_temp_scaling=00
cwl=DC
cwh=37
cranking_thres=04
awev=28
awev_temp_scaling=1A
awec=7D
warmup_clt_range[0]=00
warmup_clt_range[1]=00
warmup_clt_range[2]=11
warmup_clt_range[3]=25
warmup_clt_range[4]=50
warmup_clt_range[5]=64
warmup_clt_range[6]=78
warmup_clt_range[7]=8C
warmup_clt_range[8]=AA
warmup_clt_range[9]=C8
warmup_clt[0]=BE
warmup_clt[1]=B9
warmup_clt[2]=C3
warmup_clt[3]=AF
warmup_clt[4]=A5
warmup_clt[5]=91
warmup_clt[6]=87
warmup_clt[7]=7D
warmup_clt[8]=73
warmup_clt[9]=64
warmup_rpm_scale=BF
req_fuel=2E
divider=01
alternate=13
injopen=16
battfac=26
kpafac=8A
kpaoffs=80
injocfuel=32
injrampup_battfac=FF
injpwm=FF
injpwmt=FF
als_launch_input=CC
rpmk[0]=0B
rpmk[1]=B8
tpsdot_kpadot_conf=00
tpsdotrate[0]=03
tpsdotrate[1]=05
tpsdotrate[2]=14
tpsdotrate[3]=28
tpsaq[0]=05
tpsaq[1]=06
tpsaq[2]=11
tpsaq[3]=3C
als_cut_mintps=FF
tpsasync=04
acmult=DC
tpsacold=00
launch_enrich=00
launch_retard=00
overrun_fuelcut=FF
overrun_fuelresume=FF
rev_limit=5A
airden_ignore=55
config11=31
config12=40
config13=16
batt_cal=BF
fastidle=C8
als_max_cut=00
dbaro=0C
tps_low=0B
tps_high=B2
fan_temp=F3
fan_hyst=04
fan_channel=67
iac_step_seq=D8
iac_conf=04
iac_max_steps=B4
iac_tps_thres=03
iac_cold_idle_temp=A2
iac_warm_idle_temp=C6
iac_cold_rpm=78
iac_warm_rpm=5A
iac_cold_start_pos=B4
iac_warm_start_pos=B4
iac_afterstart_rpm=14
iac_afterstart_duration=96
iac_speed=07
iac_kp=28
iac_ki=14
iac_kd=0A
launch_rpm=28
iac_integral_limit_dec=FF
iac_integral_limit_inc=FF
iac_integral_deadband=0A
iac_deadband=0A
als_cut_maxtps=00
iac_overclose_interval=02
iac_ref_pos[0]=B0
iac_ref_pos[1]=AB
iac_ref_pos[2]=9C
iac_ref_pos[3]=8F
iac_ref_pos[4]=7A
iac_ref_pos[5]=6B
iac_ref_pos[6]=5E
iac_ref_pos[7]=52
iac_ref_pos[8]=3D
iac_ref_pos[9]=29
iac_sol_channel=7F
iac_ign_slope=04
softrpm_range=32
iac_ign_advance_limit=28
iac_ign_retard_limit=14
iac_ign_threshold=00
ego_conf=06
ego_lag=01
ego_coolant=CF
ego_maxtps=FF
ego_maxmap=FF
ego_minrpm=07
ego_maxrpm=56
ego_warmup=3C
ego_lean_limit=66
ego_rich_limit=33
ego_pid_kp=28
als_enrich=00
ego_delta=03
ego_target=19
ego_pid_window=FF
wbo2_warmup_ramp=A0
als_react_tps=00
wbo2_abs_limit=E4
wbo2_limit_maxt=A0
wbo2_fallback=B0
wbo2_retry_t=06
wbo2_edgetime_corr=BA
wbo2_edgetime_min=50
wbo2_ri_target=96
wbo2_nernstdc_target=89
wbo2_pump_pw_zero=66
wbo2_calibration=C1
wbo2_heater_pid_kp=46
wbo2_heater_pid_ki=10
wbo2_heater_pid_kd=1A
wbo2_heater_pid_ilimit=80
wbo2_pump_pid_kp=15
wbo2_pump_pid_ki=4E
wbo2_pump_pid_kd=00
wbo2_pump_pid_ilimit=84
wbo2_ri_confidence_scale=80
knock_conf=00
knock_sampling_window=F3
knock1_frequency=2C
knock1_gain=00
knock1_integrator=0F
knock2_frequency=2D
knock2_gain=00
knock2_integrator=0F
knock_threshold=FF
knock_noise_scale=FF
knock_max_retard=00
knock_default_retard=00
knock_retard_step=00
knock_retard_delay=00
knock_advance_step=00
knock_advance_delay=00
knock_minrpm=00
knock_maxrpm=00
ve_learn_coolant=D8
ve_learn_max_power=FF
ve_learn_rpm_scale=1E
ve_learn_kpa_scale=1E
ve_learn_ego_scale=43
ve_learn_min_weight=4D
ve_learn_speed=FF
ve_learn_limit=33
ve_learn_conf=00
lcd_c0=FE
lcd_delay=FF
lcd_backlight=FF
kpa_conf=21
ign_balance=00
als_retard_mintps=FF
als_retard_maxtps=00
lcd_default_view=00
primary_trigger=11
secondary_trigger=02
tooth_wheel=23
trigger_tooth=01
another_trigger_tooth=12
crank_minper=30
tooth_wheel_twidth1=03
tooth_wheel_twidth2=06
cam_sync_r_edge_phase=01
cam_sync_f_edge_phase=02
reset_engphase_after=F0
ign_tdcdelay=86
ign_dwell14=17
ign_dwell6=1C
ign_crank_advance=28
ign_out=72
ignchmax=01
engine_off_delay=0F
pump_on_mintime=0B
fuelpump_channel=57
inj_stage2_rate=FF
inj_stage2_start_tps=FF
inj_stage2_start_map=FF
als_deact_rpm=FF
als_deact_time=01
als_deact_egt=00
als_retard=00
als_rev_limit=40
misc1out_minrpm=01
misc1out_maxrpm=5A
misc1out_mintps=00
misc1out_maxtps=FF
misc1out_minmap=00
misc1out_maxmap=FF
misc1out_channel=47
misc2out_minrpm=19
misc2out_maxrpm=23
misc2out_mintps=00
misc2out_maxtps=03
misc2out_minmap=00
misc2out_maxmap=0A
misc2out_channel=6F
act_wot_rpm=55
act_wot_channel=6F
act_rpm_rpm=49
act_rpm_channel=61
egt1_cal=47
als_tks_channel=FF
boost_conf=00
boost_targetoffs=00
boost_minpressure=FF
boost_pid_kp=20
boost_pid_ki=80
boost_pid_kd=11
boost_pid_ilimit=FF
boost_channel=FF
water_pump_temp=B4
hybrid_rpm_a=FF
hybrid_rpm_m=FF
water_pump_hyst=00
water_pump_channel=F0
toothrel_normal=66
toothrel_missing=7F
fuelcut_min_kpa=00
fuelcut_max_kpa=FF
tach_channel=0F
tach_div=10
shiftcut_conf=01
shiftcut_channel=FF
shiftcut_time=00
softrpm_rpm=58
-
And this is the 1.1.44 config txt
# Dump generated from version 1.1.44
primep=00
primep_temp_scaling=00
cwl=D2
cwh=37
cranking_thres=04
awev=28
awev_temp_scaling=1A
awec=7D
shiftcut_potlow=00
shiftcut_pothi=00
shiftcut_retcut=11
boost_matdec=25
boost_egtdec=50
iacref_matslope=F4
shiftcut_minrpm=78
blabla[0]=FF
blabla[1]=FF
blabla[2]=FF
warmup_clt[0]=BE
warmup_clt[1]=B9
warmup_clt[2]=C3
warmup_clt[3]=AF
warmup_clt[4]=A5
warmup_clt[5]=91
warmup_clt[6]=87
warmup_clt[7]=7D
warmup_clt[8]=73
warmup_clt[9]=64
warmup_rpm_scale=BF
req_fuel=2E
divider=01
alternate=13
injopen=16
battfac=26
kpafac=8A
kpaoffs=80
injocfuel=32
injrampup_battfac=FF
injpwm=FF
injpwmt=FF
als_launch_input=CC
rpmk[0]=0B
rpmk[1]=B8
tpsdot_kpadot_conf=FE
tpsdotrate[0]=03
tpsdotrate[1]=05
tpsdotrate[2]=14
tpsdotrate[3]=28
tpsaq[0]=05
tpsaq[1]=06
tpsaq[2]=11
tpsaq[3]=3C
als_cut_mintps=FF
tpsasync=04
acmult=8C
tpsacold=00
launch_enrich=00
launch_retard=00
overrun_fuelcut=FF
overrun_fuelresume=FF
rev_limit=5A
airden_ignore=55
config11=31
config12=40
config13=16
batt_cal=BF
iac2load=C8
als_max_cut=E0
dbaro=0C
tps_low=0B
tps_high=B2
fan_temp=F3
fan_hyst=04
fan_channel=67
iac_step_seq=D8
iac_conf=04
iac_max_steps=B4
iac_tps_thres=03
iac_cold_idle_temp=A2
iac_warm_idle_temp=C6
iac_cold_rpm=78
iac_warm_rpm=5A
iac_cold_start_pos=B4
iac_warm_start_pos=B4
iac_afterstart_rpm=14
iac_afterstart_duration=96
iac_speed=07
iac_kp=28
iac_ki=14
iac_kd=0A
launch_rpm=28
iac_integral_limit_dec=FF
iac_integral_limit_inc=FF
iac_integral_deadband=0A
iac_deadband=0A
als_cut_maxtps=00
confswitch=D7
iac_ref_pos[0]=B0
iac_ref_pos[1]=AB
iac_ref_pos[2]=9C
iac_ref_pos[3]=8F
iac_ref_pos[4]=7A
iac_ref_pos[5]=6B
iac_ref_pos[6]=5E
iac_ref_pos[7]=52
iac_ref_pos[8]=3D
iac_ref_pos[9]=29
iac_sol_channel=7F
iac_ign_slope=04
softrpm_range=4B
iac_ign_advance_limit=28
iac_ign_retard_limit=14
iac_ign_threshold=00
ego_conf=06
ego_lag=01
ego_coolant=CF
ego_maxtps=FF
ego_maxmap=FF
ego_minrpm=07
ego_maxrpm=56
ego_warmup=3C
ego_lean_limit=66
ego_rich_limit=33
ego_pid_kp=28
als_enrich=00
ego_delta=03
ego_target=19
ego_pid_window=FF
wbo2_warmup_ramp=A0
als_react_tps=00
wbo2_abs_limit=E4
wbo2_limit_maxt=A0
wbo2_fallback=B0
wbo2_retry_t=06
als_retard_rpm1=BA
als_retard_rpm2=50
wbo2_ri_target=96
wbo2_nernstdc_target=89
wbo2_pump_pw_zero=66
wbo2_calibration=C1
wbo2_heater_pid_kp=46
wbo2_heater_pid_ki=10
wbo2_heater_pid_kd=1A
wbo2_heater_pid_ilimit=80
wbo2_pump_pid_kp=15
wbo2_pump_pid_ki=4E
wbo2_pump_pid_kd=00
wbo2_pump_pid_ilimit=84
wbo2_ri_confidence_scale=80
knock_chan=F0
knock_sampling_window=F3
knock1_frequency=EC
knock1_gain=C0
knock1_integrator=EF
knock2_frequency=ED
knock2_gain=C0
knock2_integrator=EF
knock_threshold=00
knock_noise_scale=00
knock_max_retard=00
knock_default_retard=00
knock_retard_step=00
knock_retard_delay=00
knock_advance_step=00
knock_advance_delay=00
knock_minrpm=00
knock_maxrpm=00
ve_learn_coolant=D8
ve_learn_max_power=FF
ve_learn_rpm_scale=1E
ve_learn_kpa_scale=1E
ve_learn_ego_scale=43
ve_learn_min_weight=4D
ve_learn_speed=FF
ve_learn_limit=33
ve_learn_conf=00
lcd_c0=FA
lcd_delay=FF
lcd_backlight=FF
kpa_conf=21
als_igncut_rpm2=00
als_retard_mintps=FF
als_retard_maxtps=00
lcd_default_view=04
primary_trigger=11
secondary_trigger=02
tooth_wheel=23
trigger_tooth=01
another_trigger_tooth=12
crank_minper=30
tooth_wheel_twidth[0]=00
tooth_wheel_twidth[1]=28
cam_sync_r_edge_phase=01
cam_sync_f_edge_phase=02
reset_engphase_after=F0
ign_tdcdelay=86
ign_dwell14=17
ign_dwellmap=01
ign_crank_advance=28
ign_out=72
ignchmax=01
engine_off_delay=0F
pump_on_mintime=0B
fuelpump_channel=57
inj_stage2_rate=FF
inj_stage2_start_tps=FF
inj_stage2_start_map=FF
als_igncut_rpm1=FF
als_deact_time=01
als_deact_egt=00
als_retard=00
als_rev_limit=40
misc1out_minrpm=01
misc1out_maxrpm=5A
misc1out_mintps=00
misc1out_maxtps=FF
misc1out_minmap=00
misc1out_maxmap=FF
misc1out_channel=47
misc2out_minrpm=19
misc2out_maxrpm=23
misc2out_mintps=00
misc2out_maxtps=03
misc2out_minmap=00
misc2out_maxmap=0A
misc2out_channel=6F
act_wot_rpm=55
act_wot_channel=6F
act_rpm_rpm=49
act_rpm_channel=61
egt1_cal=47
als_tks_channel=FF
boost_conf=00
boost_targetoffs=00
boost_minpressure=FF
boost_pid_kp=20
boost_pid_ki=80
boost_pid_kd=1F
boost_pid_ilimit=FF
boost_channel=FF
water_pump_temp=B4
hybrid_rpm_a=FF
hybrid_rpm_m=FF
water_pump_hyst=00
water_pump_channel=F0
toothrel_normal=66
toothrel_missing=7F
fuelcut_min_kpa=00
fuelcut_max_kpa=FF
tach_channel=0F
tach_div=10
shiftcut_conf_input=08
shiftcut_tpsthresh=FF
shiftcut_time=00
softrpm_rpm=58
n2o_mintps=73
n2o_minrpm=74
n2o_maxrpm=76
n2o_retard=78
n2o_minkpa=7A
n2o_maxkpa=7C
n2o_input=7E
n2o_output_channel=81
n2o_settings=3C
launch_out_channel=3C
launch_out_delay=3C
launch_out_pwmlow=47
launch_out_pwmhigh=73
launch_out_pwmramp=75
launch_out_ontime=77
launch_out_conf=78
boostsw_conf=7A
boostgauge_channel=7F
boostgauge_offset=7E
boostgauge_mul=80
map_filter=04
speed_sensor=02
gears[0]=08
gears[1]=10
gears[2]=01
gears[3]=20
gears[4]=40
gears[5]=80
boost_mult[0]=FF
boost_mult[1]=FF
boost_mult[2]=FF
boost_mult[3]=FF
boost_mult[4]=FF
inj_mult_trim[0]=FF
inj_mult_trim[1]=FF
inj_mult_trim[2]=FF
inj_mult_trim[3]=30
inj_mult_trim[4]=10
inj_mult_trim[5]=00
inj_mult_trim[6]=00
inj_mult_trim[7]=00
iac_conf2=00
warning_rpm=00
warning_kpa=00
warning_conf=FF
warning_adc_value=FF
warning_egt=FF
warning_afr=FF
warning_clt=00
warning_channel=FF
injection_angle=FF
boost_tps_dc_scale=FF
n2o_mingear=FF
misc1out_conditions=00
misc1out_condition1=FF
misc1out_condition2=FF
misc2out_conditions=00
misc2out_condition1=FF
misc2out_condition2=FF
knock_gain[0]=FF
knock_gain[1]=FF
knock_gain[2]=FF
knock_gain[3]=FF
knock_gain[4]=FF
knock_gain[5]=3D
knock_gain[6]=3D
knock_gain[7]=3D
knock_reference[0]=3D
knock_reference[1]=3D
knock_reference[2]=3D
knock_reference[3]=3D
knock_reference[4]=3D
knock_reference[5]=3D
knock_reference[6]=3D
knock_reference[7]=3D
knock_calibration_min=3D
knock_calibration_max=3D
inj_add_trim[0]=3D
inj_add_trim[1]=3D
inj_add_trim[2]=3D
inj_add_trim[3]=3D
inj_add_trim[4]=3D
inj_add_trim[5]=3D
inj_add_trim[6]=3D
inj_add_trim[7]=3D
inj_deadtime[0]=3D
inj_deadtime[1]=3D
inj_deadtime[2]=3D
inj_deadtime[3]=3D
inj_deadtime[4]=3D
inj_deadtime[5]=3D
inj_deadtime[6]=3D
inj_deadtime[7]=3D
inj_deadtime[8]=3D
inj_deadtime[9]=3D
acc_coeff_cold=3D
acc_coeff_warm=3D
acc_fadeout_rate1=3D
acc_fadeout_rate2=3D
acc_tps_deadband=3D
dec_coeff_cold=3D
dec_coeff_warm=3D
dec_fadeout_rate1=3D
dec_fadeout_rate2=3D
dec_tps_deadband=3D
film_coeff_cold=3D
film_coeff_warm=3D
film_rate=3D
film_scale=3D
film_rpm_scale=3D
vvti_cold=3C
vvti_idle=3C
vvti_pid_kp=3D
vvti_pid_ki=3D
vvti_pid_kd=3D
vvti_pid_ilimit=3D
vvti_channel=3D
accel_rpm[0]=3D
accel_rpm[1]=3D
accel_rpm[2]=3D
accel_rpm[3]=3D
accel_scale[0]=3D
accel_scale[1]=3D
accel_scale[2]=3D
accel_scale[3]=3D
inj_stage2_conf=3C
crankpw[0]=3D
crankpw[1]=3D
crankpw[2]=3D
crankpw[3]=3D
crankpw[4]=3D
crankpw[5]=3D
crankpw[6]=3D
crankpw[7]=3D
crankpw[8]=3D
crankpw[9]=3D
-
May sound obvious but did you fill in the reference tooth table?
-
Refference tooth?
???
-
mega tune, advanced, reference tooth table
-
Now then :-[
What value do I put in there then. I had a look through the change log but i cant see anything that relates to this :-\
-
change ignchmax to =03 and put in table 0 16 0 16
And check ignition output.
-
Now this is getting confusing :-\
I have dual out configured, what do I do with the other two h[2] entries and why 0 16 0 16 in h[1]
I have trigger tooth as 1 and next trigger tooth as 18, would these not be the values to enter into h[1] 1 18, then my TDC after trigger will remain the same.
I did eventualy find something on this ( not very explanative)but the Change log supplied with the firmware mentions nothing of this.
Please remember I have moved from 1.0.73 firmware where the 1.1.x firmwares were for special trigger applications, I know nothing of all these new (apparently old) features :-\
-
Ok then so the first h[1] entry acording to this will indeed be 0, so the second entry will be 17 on a 36-1 wheel?
I think I understand now that even with dual out mode, if I set ignchmax to 03, then set h[2] to 0+1 2+3 0+1 2+3 then h[1] to 0 17 0 17. But why do that when the same thing is ignchmax = 01. h[2] = 0+1 2+3. h[1] 0 17???????
???
Please help me with this as I have a week to get this back up and running, for a return visit to the dyno to finish off where we failed as a result of 4 degrees ignition advance dissapearing from the map to what went into the engine! Then its the dyno shoot out on the saturday and I HAVE to be there, after all it was I that organised it :D
Thanks chaps
---------------------------------------------------------------
h[1] is the reference tooth array (trigger_tooth and ign_tdcdelay is added to this to get TDC), for each output specified in respective h[2] entry. Examples:
* h[1]=1E 00 1E 00 .. .. .. .. # 60-2 4 cyl (tooth 00 and 30)
o another_trigger_tooth=1E
* h[1]=8A 3C 1E 00 .. .. .. .. # 60-2 4 cyl with camsync (tooth 00,30,60 and 90)
o another_trigger_tooth=1E
* h[1]=60 48 30 18 00 .. .. .. # 60-2 5 cyl with camsync (tooth 00, 24,48,72 and 96)
-
Sorry, refrence tooth table is 18 0 18 0 and in ignt output put same value for 0. row to 2. row and also value form 1. row to 3.row
This is my output table(wasted spakr, 2. and 3. cylinder are connected to 0 ign channel, 1. and 4. cylinder to 1 ign channel)
(http://img216.imageshack.us/img216/8049/34277017pm3.th.jpg) (http://img216.imageshack.us/my.php?image=34277017pm3.jpg)
primary setting leave like it was, except set angular widht of tooth=10 degrees
and check VE,spark and lambda map if map and rpm values are good
-
Im running COP with dual out :-\
This config is looking very similar to the injector config, its just fragmanted in comparison.
Why though, set ignchmax = 03? when 01, h[2] 0+1 2+3, h[1] 0 18 is the same
I am learning alot with this but think there is some un nescisary config going on here. I think I will have to have a play tomorrow ;D
Keep the info coming, I need all the info I can digest over the next 16 hours so when I come home from work, I can start playing with the car :D
-
If you had on 1.0.73 h[2] 0+1 2+3, than put this
ignchmax = 03 h[1] 18 0 18 0 and h[2] 0+1 2+3 0+1 2+3
You can put h[1] 0 18 0 18 but than you need change h[2] to 2+3 0+1 2+3 0+1
-
Ok cool, just one other thing. should the 18 not infact be 17?
-
Ok cool, just one other thing. should the 18 not infact be 17?
18. If you have 4 cylinders and 36-1 you just divide 36/2=18 (this value is same like next trigger tooth)
For 60-2, 60/2=30 (my h1 table is 30 0 30 0)
-
It runs, but there is deffo something different how the engine runs and idles, I'll need to get to that at the week end, main thing is that it runs. I had to add about 10 degrees to the idle advance to get it to run anywhere near right at idle, which makes me think that I lost 10 degrees or one tooth with all this trigger set up. I'll check it with timing light at the week end.
Something I did find odd however, is with slot 1 enabled, TPS at 0%, KPA reads 17. This is the exact same config as slot 0 which does not suffer this problem. TPS is calibrated properly
-
Put msq file of 1.1.42 on net. Did you put new mat/tps table?
-
MAT TPS table all filled in. 100% in every field so it has no effect. For now.
Thinking more about this, I have indeed lost 10 degrees some where wich equates to one tooth, so ogoing from my original set up to this set up, there has been one tooth unacounted for in the settings
Still doesnt tell me why two identical MSQ (except the configswitch settings) there is an error on slot 1 where kpa reads 17 at 0% throttle
Set up is Alpha N by the way
-
As I had thought!!!!! There was a 10 degree difference on the refference tooth of the trigger!!!! I had to remove 10 degrees from the 'TDC after the trigger (deg)' setting, originaly 67 degrees now 57 degrees.
Where has this error come from An I think people should be made aware of this, As I changed none of the original trigger settings in 1.0.73, but had to change the tooth width becuase of the new firmware 1.1.44 and then set up the refference tooth table.
Perhapse there is a config error by setting first trigger tooth to 1 and next trigger tooth to 18 in the primary trigger settings? those are my original settings. I am still confused as to what part they play in the over allscheme of things now we have the trigger refference table ???
This is the 36-1 trigger with COP dual out and sequential injection.
Test drive tomorrow ;D
-
Today I found out why the kpa read 17 with 0% throttle. If IAC type is configured for PWM/ Stepper with everything disabled and values in the stepper refference table, on key on, the kpa would drop to 0 then rise to 17, once running it dropped to 5. Is this meant to do this? I cannot use ignition idle control when the IAC type is set to on/off.
Again this is using alpha N
-
Is IAC to load value 0 either?
-
I am getting some kick back while cranking, some times, not all the time, other times all the time :-\ Its fine once its running
-
I am getting some kick back while cranking, some times, not all the time, other times all the time :-\ Its fine once its running
I noticed same. I think that is bug when starter can't rotate engine above 200rpms.
Can you make log when you cranking and when you have kick back?
-
Trigger log or just a data log?
I can do this this week but the engine is coming out at the week end for two or three weeks there after.
My starter only turns the engine over at 160- 180rpm and its a custom high torque gear reduction unit and the battery is a relatively huge 500 crank amp, 70 ah battery so that is as good as it will ever get.
-
What cranking advance are you running?
-
Hi,
10 degrees I think Bob :)
Cheers,
Gavin :)
-
Trigger log or just a data log?
I can do this this week but the engine is coming out at the week end for two or three weeks there after.
My starter only turns the engine over at 160- 180rpm and its a custom high torque gear reduction unit and the battery is a relatively huge 500 crank amp, 70 ah battery so that is as good as it will ever get.
data log
-
yep 10 degrees
-
you can go less than that without a problem, I've seen cranking as low as 4deg.
-
Hi,
Mine doesn't like more than 5...
Cheers,
Gavin :)
-
I'll drop it to five, but it may be a few weeks before I can report. I may well be back ;D
-
Maybe I'm behind the times now 1.1.50 is floating around, but I noticed TPSdot is not reading correctly in MT. Is this because TPSdot has changed it's meaning (or scaling) now or just something bad in the v3.ini file?
Thanks.
-
Managed to the engine back up and running today.
I knocked the crank advance back to 5 degrees. It now takes longer to fire and still kicks back every now and then. I cannot be removing any more advance as starting will get more difficult.
Trigger before TDC has been set correctly with the timing light ;)
What is causing the kickback?
-
I had similar problems with 24-1 wheel. Rearrange tooth table from 0-12 (0-12-24-36) to 12-0 (24-36-0-12) and changing spark output table accordingly seems helps.
-
While i have an idea what you are talking about, i dont quite follow it :-\
-
Bump!
:-[
-
bump Bump! :-\
-
I'd love to help but I'm stuck too - do you think its possible to re-phrase your question as that might provoke some discussion.
-
Ok Rob :)
During the cranking phase, the engine sometimes stalls the starter motor as if the spark has occurred far too early. Some times does it the once before the engine starts, other times maybe twice, and sometimes it just does this and the engine does not start.
It is almost like a backfire.
I never had this problem with 1.0.73 or 1.0.78, only with 1.1.44.
I also found I had lost 10 degrees on the 'trigger before tdc' value, even though nothing had physicaly changed on the engine. Perhaps this may have something to do with it.
The trigger set up is 36-1, 'trigger before TDC' is set to 54, tooth refference table set as 18-0-18-0 from top to bottom.
Infact I have just looked at a log that this problem happened on twice in a row before starting. The log clearly shows the rpm jump to almost 2800rpm and the spark jump from 10 to 33. The rpm and spark peaks are the exact same shape.
-
I just tuned a 60-2 setup and the rpm did shoot up and the crank to start was delayed.
one time it started so smoothly and fast it was quite strange.
Overall it always starts though
-
While i have an idea what you are talking about, i dont quite follow it :-\
Sorry, what exactly is not understandable?
Idea is: first time when spark occurs is delayed by half of cycle than in usual method.
-
While i have an idea what you are talking about, i dont quite follow it :-\
Sorry, what exactly is not understandable?
Idea is: first time when spark occurs is delayed by half of cycle than in usual method.
Im not sure where the 0-12-24-36 relate to a four cylinder 36-1 trigger when i originaly have 0-18-0-18
F**k it, im going back to 1.0.73 and putting up with the Acceleration enrichments :-\
-
My story was about 24-1!
For 36-1 then use 18-0-18-0 or 36-54-0-18 if camsynced
Gints
-
Well I have just reverted to 1.0.73 and I regained those lost 10 degrees 'trigger before TDC' and it fires first time everytime without any kickback. There is something fundamentaly amiss with this firmware with the 36-1 trigger.
-
Mine works fine with 36-1 and 1.1.44. I have no idea why mine should work and yours doesn't.
-
I have just upgraded from 1.0.36 to 1.1.44a, now I don't have any rpm signal any more ??? 0 rpm all the time.
I run a simple coil type trigger with two screws on a crankshaft pulley, no cam shaft sensor. 1GT101 sensor from webshop. Trigger was working fine with old 1.0.36.
Do I need to manually change any settings in the config file to make it work?
Here are my current config, tables and msq files:
http://www.vems.hu/files/MembersPage/MagnusKarlstrom/1144/config.txt
http://www.vems.hu/files/MembersPage/MagnusKarlstrom/1144/tables.txt
http://www.vems.hu/files/MembersPage/MagnusKarlstrom/1144/megasquirt200905011527_ej_ok.msq
I guess I miss a lot of info in the config file, can somebody share a working config file? Just the basic stuff needs to be okay so I can get it running again. (It is just a stock Porsche 944 engine without turbo so I don't need anything turbo related working)
//Magnus
-
fill up reference toth table.
-
I have just upgraded from 1.0.36 to 1.1.44a, now I don't have any rpm signal any more ??? 0 rpm all the time.
I run a simple coil type trigger with two screws on a crankshaft pulley, no cam shaft sensor. 1GT101 sensor from webshop. Trigger was working fine with old 1.0.36.
You need to go 1.1.52 or newer to get simpletrigger to work on 1.1.x branch. Or go with 1.0.79a.
-
I got the 1.1.43 to work with 2+1 simple trigger alright...
-
I got the 1.1.43 to work with 2+1 simple trigger alright...
Yeah, it works with camsync, but even simpler simpletrigger doesn't.
-
You need to go 1.1.52 or newer to get simpletrigger to work on 1.1.x branch. Or go with 1.0.79a.
Okay, thanks! I'll give 1.0.79a a try until I have finished my camsync trigger installation.
//Magnus
-
Okay, thanks! I'll give 1.0.79a a try until I have finished my camsync trigger installation.
//Magnus
Tried 1.0.79a and engine started up right away. After maybe 30s it died and refused to start again... I looked at display and noticed that injector pulses was at 0ms while cranking no matter what I did. Downloaded config again and it started again and run for a couple of seconds before it died again with 0ms.
Put back version 1.0.36 again and it works again. ??? ??? ??? Anyway, it runs again so I can use it while I think.
//Magnus
-
Hi,
Just got round to trying this on my 36 -1 -1 -1 -1 setup. I also had a similar issue to Sprocket, but it was 14 degrees out rather than 10 on the "Trigger before TDC." :o
Double check the timing when upgrading ;)
Cheers,
Gavin :)
-
I am hearing great things about VEMS Tune and the 1.1.5x firmware that it can download off t'internet...
-
I am hearing great things about VEMS Tune and the 1.1.5x firmware that it can download off t'internet...
Well don't just leave us hanging in suspense, details man, details! ;) :D
-
I am hearing great things about VEMS Tune and the 1.1.5x firmware that it can download off t'internet...
Well don't just leave us hanging in suspense, details man, details! ;) :D
No more than that really, if adventurous souls want to track it down and run it on their cars then that's all good, but don't expect me to hand you each a loaded gun :P
-
Hi
I've still got to figure out how to use VemsTune before I can shoot myself in the foot! ::)
Cheers
Gavin :)
-
Does anyone have problems on 1.1.44 with tacho, fuel pump and other things driven from P259 chip?
Looks I have :-\
Gints
-
Does anyone have problems on 1.1.44 with tacho, fuel pump and other things driven from P259 chip?
Looks I have :-\
Gints
No, so far tested on 6cars.
BTW i'm driving on 1.1.5x for more than 2 months and using vemstune without problems.
-
Like tach cyclic jumps from zero point during non running engine?
Or misc outputs do not work as wanted?
-
VEMStune doesn't like my laptop, so I had to manufacture a Megatune version of the said loaded gun to shoot myself in the foot...
Needless to say it didn't work properly - I couldn't get the laptop to talk to the car reliably, so I reverted to 1.1.44
-
Hi,
I've noticed PW in MT jumps from 13 to zero repeatedly for a few seconds and then stops.
This is with engine not running. ???
Couldn't see any changes in the log that I did other than the PW changing...
Cheers,
Gavin :)
-
hi just going through this ready for the weekend,
why is there so many download and upload comands?
confussing or what.
download-config-9600 or download-config-19200
generate-config-12x12 and generate-config-12x12 with defaults
upload-config-9600 or upload-config-19200
upload-firmware-12x12 or upload-firmware-boot-12x12
firmware-uploader
what ones do i need to use please :-(
-
You need "upload-firmware-12x12" to put the firmware on. (You may need "upload-firmware-boot-12x12" if things go wrong, but don't worry about that until it happens)
There's no real point in backing up your config because you should have that on the laptop and it's going to be like a new car anyway. :)
-
ok mate ta
-
Are you clear on your wideband calibration (nernst dc and pump pw) values?
-
nope lol,
i was going to look at the values in my current msq,
i did this last time we upgraded,
as double checked the ijector settings etc,
is there something i need to know then regarding the wideband etc Rob?
-
I've been dealing with some issue ever since I got my car running and driving. Whenever it is cold out, I cannot for the life of me get the injector pulse width at idle to be reasonable for the first 20 seconds until EGO kicks on.
I think the PW should be about 2.2 at 17 degree IAT and CLT (Celcius) but it jumps to and stays at 3.5-4ms until EGO kicks in, causing rich miss-fires. I have gone through every menu on MT many times trying to get this to stop, or at least adjust it. Today, I fiddled with multiple settings and now the car is too rich to start. Any advice?
This is 1.1.44alpha on a 4age 20V using Alpha-N.
-
Warmup enrichment, afterstart?
Use the logs and megalogviewer to find the XXXe values .
Then you can which part is causing the effects.
-
what are injectors settings(open time...)?
-
Sorry, I was away from my car and laptop this weekend. I'll post up the settings. They don't seem right though, as injector opening time is 0 at 13.2V or w/e the setting is, and the ramp up rate is a large (4 digit) number.
Gunni, I got a map from Jap-Kadett that you supposedly did for his 20V. I can't see all of the data as I never found out what firmware he was reading. 1.44alpha doesn't show all of the information.
Can I assume the injector sequencing is correct? I'm not sure what phasing I should have the injectors right now. I think I will update my thread in the projects section later tonight with a few pictures and issues I'm having (mainly fuel economy around town).
BTW guys, the inability to actually start was from the car going from pig rich right after cranking (but still would run, just with rich miss-fires) to dieing right after cold start b/c of TOO LEAN! I didn't realize I went from pig rich to too lean. So today I messed with the warm up enrichment and I at least got the engine to maintain idle after a luke-warm start. I'll see how it goes tomorrow morning.
-
I posted a few of my screen shots on my project page:
http://195.159.109.134/vemsuk/forum/index.php/topic,974.15.html
I'm unsure of the injector sequencing or the injector opening times. Also, accel enrichment seems to be on full time, no matter how slow I open the throttle.
-
just to add my probs to the list using this firmware version,
when cold while cranking if the car fires then stalls and you re-crank the engine to start again i get lots of kick backs until it fires and runs,
if it fires straight away from cold have no probs and when cranking from hot no probs,
-
Hey just curious,
1.44alpha has been pretty reliable for me. I still have issues when cold starting, but I'm not positive it's not something that I'm doing wrong.
I do have a general question though:
Do any versions support acceleration enleanment? I know AE works well, but whenever I close the throttle while driving around town, the mixture goes way rich, then stabilizes.
I think this is why Megasquirt people have also created acceleration enleanment. Some people report 10-20% fuel savings from this feature while driving around town. Does this firmware support it?
-
Can you send me config(msq) to [email protected] so i can try to adjust cranking and AE?
-
I sent you my MSQ.
For me, I don't know if there is something wrong with cranking or not. It might just be my lack of experience. Hot starts are great, cold starts are fine when outside temp is above 11 celcius or so.
-
just a curious question:
after tring to load v 1.1.64 on the ecu and having no luck with getting the car running we reverted back to 1.1.44,
today was the first time we had chance to road test the car again after the firmware swap arounds,
car fire as normal while cold today went for a 20mile drive and parked up,
came back to the car about 5hrs later, tried to start it and it tried to fire but didnt,
tried again there was a backfire in the exhaust and it fired,
BUT we noticed that everything seemed to be richer now,
let the car run up to temp, and lambda is usually 0.92-0.94 at idle,
im now seeing 0.86-0.88,
and same while driving,
where cruising we were seeing 1.00-1.01 its now reading 0.97
any ideas?
map sensor going????
-
I don't think there is anything to worry about. The way lambda is reported to Megatune was changed in 1.1.44 so that it could be made more precice. There's nothing actually any different with the car other than it is now telling little lies to MT. ;)
-
phew thank god,
can't wait for you to get 1.1.64 sorted on the v8 mate :-)
-
Might be 1.1.65 now. How's the oil issue progressing? I doubt I'll be too long before I'm on the mainland.
-
hope to have an answer on the oil issue next weekend,
have made the tools for removing the valve caps while heads still on engine,
hoping changing the stems seals on them two suspect cylinders work, if so we are good to go,
failing that its engine out, but will wait till you have done your bit if it has to come out mate,
-
I don't think there is anything to worry about. The way lambda is reported to Megatune was changed in 1.1.44 so that it could be made more precice. There's nothing actually any different with the car other than it is now telling little lies to MT. ;)
ah just read this bit again,
and realised i never said that im also running a standalone vemstune gauge,
which is also showing different readings from before,
And i know that aint got anything to do with 1.1.44 :-)
-
Is the stand alone gauge getting its data from a separate sensor?
-
yes mate in the other bank,
and both are reading the around the same give or take a bit but both showing around 0.88 at idle now instead of 0.94
-
right i think,
and i say THINK>>>> i may of found the problem regarding rich idle,
one of the plug leads was not seated fully home onto the plug, and must of got dislodged the weekend when we were giving the car a once over in the garage before returning home, and thus only firing now and then when it made contact.
lambda is still not 100% but its at least in the 0.9ish region now at idle and not 0.88
will check the rest of the leads this weekend,
-
right took car for a drive tonight,
seems to be a bit better while driving.
but after 5 mins at idle it started creeping from 0.94 back to 0.88 for some reason.
and when vieving the 3D VE table the kpa was jumping around all over the place,
blip the throttle and it would level out around 55kpa again,
then after 5-10 mins every so often it would start jumping up and down again as if reving the car rapidly,
whats going on?
been fine till now :-(
-
Logs?
-
will get one tomorrow,
-
I'd say the VE map is too lean at high(ish) kPa and low RPM or the TPS vs MAT compensation is not big enough when the car starts to heatsoak at idle.
I've had both of the above in the past...
-
Might be 1.1.65 now. How's the oil issue progressing? I doubt I'll be too long before I'm on the mainland.
Well we wont be looking at mine for a while mate,
the engine has to come back out, we are hoping to do the work and back in over a long weekend,
when you on the main land?
as may wait till you have been or will do it before your over here.
-
got a big problem guys,
drove the car for the last time last weekend before the engine comes out (today). drove fine except for the odd rich idle as posted previous,
went to start today no go, it coughed a few times but stinks of fuel,
uploaded the msq again just in case still the same, changed the plugs still the same,
i have noticed though that while cranking somes times the PW goes to 0 and stays there until you turn ignition off then back on and crank again,
any ideas,
have a dlog here which will upload shortly,
I have a workshop booked for today (taken 2 months to get this slot for this weekend) and now the car wont start.
-
datalog of trying to start:
http://www.capriracing.co.uk/dlog06-03-10.zip
-
datalog of trying to start:
http://www.capriracing.co.uk/dlog06-03-10.zip
Something wrong with your MAP value?
-
not sure mate,
nothing has changed on the car from driving it last weekend and parking it up in the garage and trying to start it today,
I even uploaded the msq file from the laptop thats on the ecu incase something had spooked it, but still no go,
Im getting a crank signal as the rpm gauge on Mt is reading 150-200rpm while cranking.
-
MAP signal is very wrong - this would cause a complete lack of fuel for starting.
Maybe the signal hose is blocked with oil?
-
nope checked that tonight after sambas post hose is clear,
I did post a while back that the kpa at idle was doing strange things if you can remember, was pulsing up and down,
could the map sensor be playing up?
-
just rigged the ecu up in doors to the pc,
should the kpa be reading 100kpa with no engine running?
if so im only getting 14-15kpa :-(
-
at least you found problem. ;D
-
i gather its a dead map sensor then???
-
Or config corruption - there are scale parameters for the MAP sensor.
-
Hi Dave,
why would it be ok last weekend but not this weekend?
and still the same after uploading the msq and config?
im willing to try anything, but its getting to be a pain now,
moved this map sensor topic to here now as its nowt to do with this topic:
http://195.159.109.134/vemsuk/forum/index.php/topic,1148.0.html