Available here http://kotisivu.dnainternet.net/sakrkorh/vems/firmware_1.1.47_ext_v2.zip (http://kotisivu.dnainternet.net/sakrkorh/vems/firmware_1.1.47_ext_v2.zip)
All precautions apply same also here as does with previous releases.
Start from changelog
included features:
* Speedsensor (!PS2KEYBOARD)
* N2O retard (N2O_RETARD)
* Warning feature (WARNING_BEEP)
* Advanced misc_outputs (EXPENSIVE_MISC1OUT & EXPENSIVE_MISC2OUT)
known bugs:
* megaloader has problems with downloading config, terminal works ok (Manmcdbye)
* Megatune 3d map view sometimes buggers, 2d ok
!note even with some previous releases in megatune menus show advanced features, firmware might not actually support it. my_make tells you which features are enabled.
edit: ext package replaced with v2, speedsensor and megatune problems hopefully fixed
Sambas, great work as usual - what is the problem with Megaloader? I can take a look at it if we need to - the problem is that the download is too passive, we could really do with sending a payload size in the first instance so that MegaLoader knows when to close, rather than relying on a timeout.
Thank you!
Is the non-geek LCD mode also enabled (LCD page 4)?
And is SDcard logging enabled in firmware (so could be used with VEMS Tune)?
Yes both are available by default. Non-geek lcd is my_make CUSTOMLCD variable.
Brilliant. I just need a car to use this on now!
i know that feeling dnb :(
I have same same trooble :)
Or i have the car, i just dont have the time to try it ;)
/Skassa
Is LCD still slowish with this firmware?
If you want use speed sensor, than KNOCK_ALTERNATIVE must be enabled. Whiout KNOCK_ALTERNATIVE
speedsnesor works, but you can't see speed or gear in megatune.
Any of you know were it can be seen how to make the hardware connection for the speed input, meaning, were do i mount the wire internally at the genboard?
Thanks,
Skassa
You have to use PS2 keyboard DATA input pin. Be careful though, this input is unprotected and connect directly to Atmega128. Beware of voltages over 5volts, it could (and most likely will) kill CPU.
I wonder if we could use some diodes or something to protect the input better?
Definately use a zener diode to protect the DATA line.
(http://img512.imageshack.us/img512/4171/speedzn1.th.jpg) (http://img512.imageshack.us/my.php?image=speedzn1.jpg)
http://www.vems.hu/files/Marteleur%20Tim/PS2header.JPG (up pin is 1., down 4.)
or if you use ps cable, black is GND(1. pin on vems), yellow is clock(4.pin on vems)
d27 is 5.1V zener diode.
Quote from: MWfire on January 02, 2009, 09:48:05 PM
If you want use speed sensor, than KNOCK_ALTERNATIVE must be enabled. Whiout KNOCK_ALTERNATIVE
speedsnesor works, but you can't see speed or gear in megatune.
Updated pack with hopefully fixed vemsv3.ini, if this case was speed and gear missing from logs?
Quote from: Sambas on January 03, 2009, 12:28:34 AM
Quote from: MWfire on January 02, 2009, 09:48:05 PM
If you want use speed sensor, than KNOCK_ALTERNATIVE must be enabled. Whiout KNOCK_ALTERNATIVE
speedsnesor works, but you can't see speed or gear in megatune.
Updated pack with hopefully fixed vemsv3.ini, if this case was speed and gear missing from logs?
I think that firmware must be complied whit knock_alternative fuction. Like this mymake(12x12)
http://www.vems.hu/files/DamirMuha/1.1.47/my_make1147.txt
I tried change settings.ini(set knock_alternative), but than i can't start megatune
Can you compile this my_make?
Ok, found the problem, need to do re-release.
Could you make(compile) this my_make so i can test boost controler on car thise weekend?
Quote from: MWfire on January 03, 2009, 01:04:35 AM
Could you make(compile) this my_make so i can test boost controler on car thise weekend?
Here you are http://kotisivu.dnainternet.net/sakrkorh/vems/MWfirefirmware.zip (http://kotisivu.dnainternet.net/sakrkorh/vems/MWfirefirmware.zip), firmware only
Quote from: Sambas on January 03, 2009, 01:18:19 AM
Here you are http://kotisivu.dnainternet.net/sakrkorh/vems/MWfirefirmware.zip (http://kotisivu.dnainternet.net/sakrkorh/vems/MWfirefirmware.zip), firmware only
Tnx alot.
Quote from: MWfire on January 02, 2009, 11:40:50 PM
(http://img512.imageshack.us/img512/4171/speedzn1.th.jpg) (http://img512.imageshack.us/my.php?image=speedzn1.jpg)
http://www.vems.hu/files/Marteleur%20Tim/PS2header.JPG (up pin is 1., down 4.)
or if you use ps cable, black is GND(1. pin on vems), yellow is clock(4.pin on vems)
d27 is 5.1V zener diode.
Schematics crop is confusing. I vote for 1nF cap ;)
Thanks Sambas fore all the hard work.
Nobody is really using the knock I think so it would be cool if we could get this to work so have any one tested alternative knock?
Happy New Year
Peter
Quote from: GintsK on January 03, 2009, 03:30:22 AM
Schematics crop is confusing. I vote for 1nF cap ;)
Yes, 1nF is correct value.
I have some cars where knock control really needed. If this feature can work and can be tuned in reasonable time, it is great weapon to get all juice from engine. Protected engine!
Here is some info about:
http://www.vems.hu/wiki/index.php?page=MembersPage%2FAndrey%2FKnock
Keyword selfcalibration.
I do really need the knock control as well and right now I'm looking other solutions then the onboard chip.
And the best solution so far is to use a box from Phormula called KS4 and log the 0-5v output from this box and connect it to one of the analog inputs at the Vems box. There is an example from an log on their web page.
http://www.phormula.co.uk/KnockMonitor-KS-4.aspx
The main reason for this is that when using E85 as fuel, you really can't hear the knocking and with the Phormula box I will be able to "see" how the engine sounds via the log.
So I would like to see that we could log the output from the knock chip in the same way the I can do it with the Phormula box.
Is this possible in some way?
You can get some of the knock noise info out of the Datalog with some modification of the .ini file.
dnb did a modification of the ini file for his knock experiments, try PMing him to see if he can tell us the method behind the mod.
Rob
I have previous KS-3 Knock sense model. It use same chip as VEMS. KS works only from frequency. It do not knew nothing about rpms, load etc. My ears, when Peltor headphones used, is more reliable.
Also I have sound amplifier from Phormula. I must say my self-made amplifier with filter is much more handy. Amplifier from Phormula has very primitive construction - it is wide band: schoolboy electronics. So my hearing is loaded with every kind of engine noise.
Also Phormula knock listener has clear sound until you attach KS to them. KS is powered from cigarette lighter and then alternator and other noises comes in.
Yes the KS-3 is pretty much a simple solution it stores a max value and anything higher is knock but maybe we could have this fore third solution.
Could it be possible to have a look op table that stores data automatically if you advanced the ignition manual (Vt button) and did some test runs?
There are people in her that knows haw Subaru due the knocksens could be nice to hear from them.
Tnx
Peter
I haven't tried to use knock-sensing on VEMS yet but I could really make use of this feature on my E85 fueled race-car. Obviously not when tuning but more like safety feature during race.
(http://pic2.fotki.lv/photos2/7/W0002527/000252627/000025262694_%23_2_%23_GintsK.jpg)
#set KNOCK_ALTERNATIVE "Experimental"
#set EXPERIMENTALS "Experimental"
Message is almost similar on 16x14 and 12x12.
??? ???
Only an observation, I would have thought to set knock_alternative, you need to remove the # infront of set??
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?
Quote from: Sprocket on January 04, 2009, 05:32:46 PM
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
Quote from: GintsK on January 04, 2009, 04:19:05 PM
(http://pic2.fotki.lv/photos2/7/W0002527/000252627/000025262694_%23_2_%23_GintsK.jpg)
#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.
Quote from: GintsK on January 04, 2009, 08:41:09 PM
Quote from: Sprocket on January 04, 2009, 05:32:46 PM
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!!
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
Quote from: MWfire on January 04, 2009, 10:41:00 PM
Quote from: GintsK on January 04, 2009, 04:19:05 PM
(http://pic2.fotki.lv/photos2/7/W0002527/000252627/000025262694_%23_2_%23_GintsK.jpg)
#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.
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
Quote from: Sambas on January 06, 2009, 09:58:39 PM
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!!!
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?
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.
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
Quote
known bugs:
* megaloader has problems with downloading config, terminal works ok (Manmcdbye)
* Megatune 3d map view sometimes buggers, 2d ok
Thx
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.
Link is dead, so i reuploaded.
http://www.sendspace.com/file/k2n7hc