1.1.47 with experimental features

[tcode]

Hi,
went from 1.0.43 to 1.1.47 fw version. Lambda readings are gone now

Ri:009F Nernst:095A
Heat:A4 Pump:FF     
AFR=?     ??.?     
AFR=14.77  P      ON
Ri:00F5 Nernst:0B0C
Heat:D9 Pump:FF     
AFR=?     ??.?     
AFR=14.77  P      ON
Ri:00F4 Nernst:018E
Heat:9A Pump:FF     
AFR=?     ??.?     
AFR=14.77  P      ON
Ri:00F0 Nernst:0276
Heat:B9 Pump:FF     
AFR=?     ??.?     
AFR=14.77  P      ON
Ri:00C3 Nernst:0880
Heat:7F Pump:FF     
AFR=?     ??.?     
AFR=14.77  P      ON
Ri:00C3 Nernst:0880
Heat:7F Pump:FF     
AFR=?     ??.?     

and so on..

Does anyone have similar problem?

[GintsK]

Only an observation, I would have thought to set knock_alternative, you need to remove the # infront of set??

No # sits everywhere. No matter function is set or unset.

Gints

[MWfire]

Code: [Select]

#set KNOCK_ALTERNATIVE    "Experimental"
#set EXPERIMENTALS "Experimental"
Message is almost similar on 16x14 and 12x12.

 

You don't need to set(in megatune) knockalternative for speed sensor. If you want use knock alternative you must small page 9 from 12x12(16x16) to 8x8. I can upload that vems.ini if you want.

[Sprocket]

Only an observation, I would have thought to set knock_alternative, you need to remove the # infront of set??

No # sits everywhere. No matter function is set or unset.

Gints

My bad

This is one reason I wont use any of these new fangled firmwares. They are just not dumb user friendly, and I dont class my self as dumb but I do find all this just a little to much programmer speak!!

[z0tya]

Is there knock alternative in 1.1.47?
How can I switch on it?
I think it is a good solution on hardware side in the VEMS, the knock chip and the electronic. But the old method is hard to setup correcly. This knock alternative would be a better solution.
Has any exprerience somebody?

Thx

Code: [Select]

#set KNOCK_ALTERNATIVE    "Experimental"
#set EXPERIMENTALS "Experimental"
Message is almost similar on 16x14 and 12x12.

 

You don't need to set(in megatune) knockalternative for speed sensor. If you want use knock alternative you must small page 9 from 12x12(16x16) to 8x8. I can upload that vems.ini if you want.

[Sambas]

Ext package replaced with v2, speedsensor and megatune problems hopefully fixed. Look the first post.

I wasn't able to make megatune happy with knock_alt enabled

[PeepPaadam]

Ext package replaced with v2, speedsensor and megatune problems hopefully fixed. Look the first post.

I wasn't able to make megatune happy with knock_alt enabled

Thank you!!!

[ecutec]

i did the v2 upload via command prompt and it failed. all gauges in megatune were jumping up-down andfinally no connection at all.
should i use vemstune for upload only?

also right after upload in cmd window it gave me successful upload but all weird chars started appearing in the window.
after downgrade to 1.0.73 it was ok again

any ideas?

[MWfire]

http://netload.in/dateiUj7KyLjq5M/firmware_1.1.47_ext_v2fixed.rar.htm
here is fixed megatune(settings.ini for standard boost).
I put v2 on two cars without problems.

[z0tya]

Is the megaloader bug, what makes wrong config.txt like this:
accel_rpm[0]=09
accel_rpm[1]=pm[2]=1E
accel_[0]=0C
accel_sc2]=64
accel_scaonf=FE
crankpw[crankpw[2]=FF
c]=FF
crankpw[5]ankpw[7]=FF
craFF

and makes 14 rows in VE,Spark,Lambda tables?

j[C]=58 58 58 58 58 58 58 58 58 58 58 58
j[D]=58 58 44 3D 3D 3D 3D 3D 48 48 48 48

known bugs:
* megaloader has problems with downloading config, terminal works ok (Manmcdbye)
* Megatune 3d map view sometimes buggers, 2d ok

Thx

[T40]

I have a problem with boostgauge output.
It worked fine, if boost pressure was no more than 1.1 bar (210kPa absolute).
But if boost pressure is increased, pressure indicator drops to 0 when boost reaches over 1.3 bar (roughly).
Seems like boostgauge output signal is lost above that pressure. I tested it with constant manifold pressure at 275kPa and indicator shows 0, no matter what is written into offset and multiplier fields.

Ideas?

Edit:
Looks like the boostgauge output doesn't work with MAP values above 240kPa.
Solution: adjusting map sensor range so that vems can see smaller numbers than real map values.
For example, atmospheric pressure = 50kPa. Maybe not the smartest idea, but works fine for me.

[MWfire]

Link is dead, so i reuploaded.
http://www.sendspace.com/file/k2n7hc