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.
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
Your reference tooth table was wrong and also h2 had bad values. Fixed in here http://kotisivu.dnainternet.net/sakrkorh/vems/fw1143/testrun1gunnifixed.msq (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.
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?
Quote from: gunni
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.
Quote from: gunni
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.
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.
Is this because the dwell voltage compensation is now automatic?
since 1.1.32
# 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).
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
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.
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?
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
Sure I can Rob. Some of the test cases I did are avaible here http://kotisivu.dnainternet.net/sakrkorh/vems/fw1143/ (http://kotisivu.dnainternet.net/sakrkorh/vems/fw1143/). Tables and outputs might be messy, but trigger related setting should be correct for all cases.
Quote from: Sambas on October 30, 2008, 03:46:16 PM
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.
Can you give us some sort of description of the method that you used?
Quote from: gunni on October 30, 2008, 11:01:08 AM
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.
Can you upload your configs and tables?
I have 1.1.43 on bench. I like it!
Many very usable features since 1.1.27:
Boost scaling from TPS works (alternate settings) helps control over car on slippery road!
IAC valve slope from IAC - it is for traffic jams! (I want 2x or even 3x bigger maximal value)
MAT enrichment table (I have Jaguar 4.2L engine with 1.1.41 on the street - I like this table)
Reasonable acceleration enrichment! Why there is no deceleration?
More friendly trigger settings.
switchable configurations. Seems it works! I use 215 (D7) and 199 (C7) in Megatune. Now I see the way to stabilize boost at launch: http://www.vems.co.uk/forum/index.php?topic=573.msg5887#msg5887
Improved shift-cut (ability to spool-up turbo during long gearshift!)
Boost limiting from IAT and EGT!
Improved Misc output sources!
Boostgauge for Audi
Dwell from MAP (be careful!)
Something like Check Engine.
AIM (today customer independently ask me question about AIM compatibility!)
Try it on bench with Audi trigger and 60-2 w/ and w/o camsync. Seems OK.
what I miss:
lost warmup wizard. IAC reference position wizard.
Something with bat scripts or communications. Frequently messages <i>no halo from AVR</i> in firmware-uploader.bat No matter 9600 or 19200 chosen.
something wrong with serial communications at power-up. Frequently reads bad signature from board and mess up channels -if logging, datalog in MLV becomes unusable: 54000Rpm and so on...
I use Prolific old-chip adapter from webshop. FIFO disabled, flow control - none.
100% Gego when LSU is disconnected!!!
Sometimes on small engines and BOSCH valve I want better IAC strategy when trottle leaves idle position. IAC valve momentary goes to 0% or reference position (config dependent). Both can give rough step.
CLT range over 102C.
Gints
If AIM stream is enabled it causes those communication problems.
:D Yes! It was cause!
Now I have good chance test 1.1.43 on real car tomorrow!
60-2 no camsync, wasted spark, turbo.
No 36-1 to hand at the moment :(
Rob
Quote from: MWfire on October 30, 2008, 06:44:24 PM
Quote from: gunni on October 30, 2008, 11:01:08 AM
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.
Can you upload your configs and tables?
http://www.vems.hu/wiki/index.php?page=MembersPage%2FGunnarReynisson
:-\ I put this config and tables to my board. It seems weird to me. I think AE amount (maximal or base duration) must be more ar low rpm and scaling...
also config lacks proper MAT table; and angular width of tooth is off.
Here my corrections:
http://www.vems.hu/files/GintsK/AEsample1.1.43_01.msq
Why is angular width off?
I have 60 teeth
360/60 = 6degrees
I have all the AE at 1ms with no regards to rpm as I havenÃ,´t spent any time messing with it.
What corrections did you put in?
Sorry. Forget about my previous post. I can't generate config.mtt from your config.txt
I get erroneous config with 18-1 disc and wrong tooth angle of 2000deg...
Here my AE starting point:
http://www.vems.hu/files/GintsK/AEsample1.1.43_02.msq
I have always used "IAC reference position wizard" to adjust the idle, so i also miss this, but if i can be left out, then it dosenÃ,´t matter
/Skassa
What do you guys mean by this "IAC reference position wizard"?
idle air control valve pwm that determines itÃ,´s opening.
We're not sure what the Wizard part was though... Can you tell us what version it was in and what menu in MegaTune?
Cheers
Rob
(http://img.photobucket.com/albums/v41/Denmark/idlepwmtable.jpg)
(http://img.photobucket.com/albums/v41/Denmark/idlepwmtable1.jpg)
This is from 1.0.73
/Skassa
But that thing is still there. Only big things that got removed are velearn and user adjustable temperature bins.
Forgot to mention, testers should check MAP filter in Alpha-N page, some info avaible in wiki FirmwareChanges page.
Ups, sorry,
I have just seen that it can only be seen when there is a file loaded, sorry
/Skassa
If no one else gets to test this on 36-1, i'll do it, but not before I get it running correctly on 1.0.78
No point in trying 1.0.78, this one replaces it.
Rob please ::) I need to get this somewhere right with a firmware we know works ;D you said so :D ;) ;)
I will see where I get tomorrow. I flooded the engine last week rushing to get it running and this cold weather hasnt helped dry it out. I found where I went wrong and have re configured, so hopefuly tomorrow when I get some external heat on the head, I will do a better job :D
Yeah, I guess so, I do tell people a lot of things mate, so I may end up contradicting myself. I try to be accurate, but I never claimed to be consistent ;) :D
Sorry again! Not "wizard" but graphical Curve Editor! New version lost warmup graphical editor. But additional for IAC postion should be helpful too.
Today I load 1.1.43 on real car. Got it running with ease, check timing. Perfect.
But engine had some mechanical problem: we get sky-high EGT. Reason can be wrong timing mark or camshaft timing.
What I note: IAC valve closes slowly when throttle leaves idle position. Good feature!
More ests on next week.
Gints
Quote from: GintsK on October 31, 2008, 10:11:41 PM
Sorry again! Not "wizard" but graphical Curve Editor! New version lost warmup graphical editor. But additional for IAC postion should be helpful too.
Today I load 1.1.43 on real car. Got it running with ease, check timing. Perfect.
But engine had some mechanical problem: we get sky-high EGT. Reason can be wrong timing mark or camshaft timing.
What I note: IAC valve closes slowly when throttle leaves idle position. Good feature!
More ests on next week.
Gints
Just edit the vems3.ini file to get the curve editors working
MAT table, is this biased at 100%??
Quote from: Sprocket on October 31, 2008, 10:59:46 PM
MAT table, is this biased at 100%??
yes 100% is zero enrichment.
Graphical editor was lost when temperature bins got locked. Haven't found solution in megatune if I can use locked constants as x-axis.
edit. Digged into megatune source and found a way to make it work. Stay tuned, I'll release vemsv3.ini fixes today
edit2. updated the alpha2 zip with new vemsv3.ini, new curve editors have only coolant bins [0..9] because of megatune limitations.
Throttle response is great, idle is much better(especially when mat is above 40C)..
But LCD is slow(it takes more than 1s to refresh page), ego correction has lag(1-1.5s).
Did somebody tried dual configs? I have problem with dual configs.
http://www.vems.hu/files/DamirMuha/1.1.43/config.txt
http://www.vems.hu/files/DamirMuha/1.1.43/tables.txt
http://www.vems.hu/files/DamirMuha/1.1.43/megasquirt200811011542.msq
edit: trigger wheel is 60-2
I didn't note more lag on LCD than all previous firmwares. Except at power on, where something is changed.
On my test car ego control looks fast as usual.
Quote from: MWfire on November 01, 2008, 03:28:41 PM
Throttle response is great, idle is much better(especially when mat is above 40C)..
But LCD is slow(it takes more than 1s to refresh page), ego correction has lag(1-1.5s).
Did somebody tried dual configs? I have problem with dual configs.
http://www.vems.hu/files/DamirMuha/1.1.43/config.txt
http://www.vems.hu/files/DamirMuha/1.1.43/tables.txt
http://www.vems.hu/files/DamirMuha/1.1.43/megasquirt200811011542.msq
edit: trigger wheel is 60-2
Just load your msq on my test board.
My ego step size is always 1%, yours is 25%. Any specific reason?
Also from discussion about new AE - idea is allow more AE at low rpm, but curve is contrariwise in this configuration.
Also dotrate - here is full 100% AE at smallest throttle move of 1 dV/dt. 100% in
dotrate vs scale table means direct value from
RPM vs amount table...
Dual config. Open your msq with any text editor (I use Notepad++), find
confswitch and save two different copies of msq: one with value 199, other - with 215. Power up board and burn msq with 199. When switch MCP3208 chip ADC input 7 (pin8 in fact, also make sure you have pullup resistor soldered on board) to analog ground and now burn msq with 215. Restart megatune is good idea, but not strictly necesarry - just type Alt_F on every opened dialog. IRC it was how I get this feature working.
Quote from: GintsK on November 02, 2008, 04:09:17 PM
Just load your msq on my test board.
My ego step size is always 1%, yours is 25%. Any specific reason?
Also from discussion about new AE - idea is allow more AE at low rpm, but curve is contrariwise in this configuration.
Also dotrate - here is full 100% AE at smallest throttle move of 1 dV/dt. 100% in dotrate vs scale table means direct value from RPM vs amount table...
Dual config. Open your msq with any text editor (I use Notepad++), find confswitch and save two different copies of msq: one with value 199, other - with 215. Power up board and burn msq with 199. When switch MCP3208 chip ADC input 7 (pin8 in fact, also make sure you have pullup resistor soldered on board) to analog ground and now burn msq with 215. Restart megatune is good idea, but not strictly necesarry - just type Alt_F on every opened dialog. IRC it was how I get this feature working.
On 1.0.73 when step size is big, then ego correction is faster. On 1.1.43 is same speed, but lag is 2-3s(like i put 90 in engine cycles before changing corection).
For AE dotrate i didn't change anytingh, just copy/paste:).
I tried this
http://www.vems.hu/wiki/index.php?page=MembersPage%2FDamirMuha%2FDualConfigs
I will try tomorow dual configs.
Tnx for advice.
Config switch is not fully completed yet, only some of the tables can be swapped for now. Switchable tables include ve, lambda, kpa and rpm arrays, spark and boost.
Please help with my understanding of a few things, making it much easier for me to correct, adjust and tune
EGO
EGO Lean or Rich limits, is % of what value? Is it % of active VE bin?
EGO step size in %, is % of what value? Is it % of Active VE bin?
EGOC on LCD is what? It maxes out at +-51. its not percent. Is this affected by EGO step size, IE, if step size is 1% and LCD EGOC indicates -50, that equates to -50% of the active VE bin, or, if the step size is 2% and LCD EGOC indicates -25, that also equates to -50% of the active VE bin? What does the EGOC value on the LCD actualy tell me other than the VE table is rich or lean, I have no idea by how much, other than 51 is miles out!
Quote from: Sambas on November 02, 2008, 04:49:36 PM
Config switch is not fully completed yet, only some of the tables can be swapped for now. Switchable tables include ve, lambda, kpa and rpm arrays, spark and boost.
I tested on primepuls >:(
Can you put in config switch injectors setings? I have high ohm injectors for petrol(no pwm) and low ohm for LPG(pwm).
EGOC on lcd is 2.56*ego
Again, an explanation that, to me, means nothing.
wen you say 2.56* EGO, what value is the EGO
Do you mean the Rich limit and Lean limit?
I have the lean limit set high at 20% and the rich limit set at 5%. If you multiply 2.56 with 20 it gives the 51 i see on the LCD?
Still doesnt explain what the rich or lean limits are a percentage of
Okay, uploaded the firmware and configs, then got the whole AiM datastream.
So do I set lcd_c0=40 to turn it all off?
Quote from: [email protected] on November 05, 2008, 06:55:34 PM
So do I set lcd_c0=40 to turn it all off?
lcd_c0 bit 2 is aim enable so that should disable it yes
When it is enabled I can't get MegaTune to work, it just sits and gets pounded by the out coming data.
turn megatune off and on again, it should work then.
as the inital startup of the megatune stops the stream,
but you have to disconnect from the port and reconnect with the MT
to get to the unit.
thatÃ,´s how itÃ,´s been working for me.
and make sure that megatune is set for 19200 speed, in terminal commands 'A', 'D', 'S', 'Q' and "Man" disables the aim stream
I'm just thinking of a way of writing a how-to, and disabling the LCD and AiM features in order to get MegaTune up to do various tests seems like a good thing to suggest.
Rob
Okay...
There are issues with MegaTune. When you start up MT in the usual manner the combination of AiM protocol and the fact its now 19200baud causes
My tables are all screwed, every other value in the tables is wrong - I think this is because the wideband learning values are no longer printed out when an mct is done, and they are still in the original tables file.
My ignition and injector outputs were all wrong. The ignition entries were all blank, the injector entries seemed to contain random numbers.
When cranking I found the RPM was spot on, but when I'd set the ignition and injection outputs correctly the engine would catch and kick back against the starter - this would suggest that the base timing has shifted. My cranking advance is still correct at 4oBTDC. Could this be a setting that is incorrect with the new trigger config settings?
Here is my new msq file
http://www.vems.co.uk/VEMSConfigs/SR20DE/SR20DEAfterSomeCleaning.msq
I suggest the following actions:
* Create a UpgradeDefaults.txt configlet that sets the values correctly - notably AiM disabled, switching all new features off.
* Update the make tables to cope with the original and new mct formats.
* Create a suitable .cfg file that defaults to the correct baud rate.
* Write a how-to upgrade document.
I am happy to do the make tables executable as I wrote it in the first place, the rest needs further discussion.
Quote from: [email protected] on November 06, 2008, 11:00:31 PM
Okay...
There are issues with MegaTune. When you start up MT in the usual manner the combination of AiM protocol and the fact its now 19200baud causes
My tables are all screwed, every other value in the tables is wrong - I think this is because the wideband learning values are no longer printed out when an mct is done, and they are still in the original tables file.
My ignition and injector outputs were all wrong. The ignition entries were all blank, the injector entries seemed to contain random numbers.
Just twice time upload config(upload config.bat) and then tables are right.
Rob, did you use the config and tables I made? Because there is nothing right with that msq. For example I did set confswitch=00 but in msq it's 5 and Toothwheelwidth is also wrong (i think original value). This looks like either you uploaded your old config or something else gone wrong.
I re-downloaded the config and tables files you did for me and found that the final line contained a load of entries without CR+LF.
Editied, remade, uploaded - car started :D
Running very rich, but even so I managed to get some nice acceleration response from an engine that was in all other respects very flat.
I was able perform some additional tests on real car. Due very high EGT I checked timing for every cylinder - perfect match! Also I check AFR using Tech Edge unit - perfect match! Also playing with EGO control - did not find any lag comparing to 1.1.27.
Engine - old VOLVO B200ET. 60-2. No camsync. RC 550cc injectors using Peak-hold mode. GT28R. G-reddy w-gate solenoid. 1.5bar boost.
log
http://www.vems.hu/files/DamirMuha/1.1.43/egodatalog200811101429.xls
at 193.9s is throtle stady and 11%. At 194.4s ego start coreting. i don't know why i have 1-1.5s lag.
Here is my config
http://www.vems.hu/files/DamirMuha/1.1.43/megasquirt200811101507.msq
http://uk.youtube.com/watch?v=tg9Fjd0HwYc
On 1.0.73 lcd was much faster
Are you find EGO correction laggy here? Lambda in this case is close to target and controller do changes slower. If faster response desired, rise up speed limit and lower engine cycles. I do not knew anything about step size: do not see any significant changes in range 1...30 ??? Ego correction here is interrupted by AE too.
My typical settings when sensor is located ~70cm after valves is 64 for speed limit and 5cycles when tuning and 10-15 when already tuned.
LCD is slow at start up. Did you see any lag after that? I don't.
Loock lambda.It's 0.9x, but on lcd is 1.9x.It's a bit scary to see lambda 1.8 on wot:).
http://uk.youtube.com/watch?v=_N4FbCQTmE0
This is a bug! 1.95 is 0.95.
I notice something similar!
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 ).
Quote from: Sambas on November 20, 2008, 11:28:24 AM
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 ).
Cable is 2m utp(unshilded). I don't thing it's interference problem, becouse on LPG(low ohm injectors) i drive whit pwm and i don't have this problem(firmware 1.0.73). This film is made on petrol(high ohm injectors).
Does the boost switch work in this firmware?
When Boost alternate settings enabled..
IÃ,´ve got this on a bench and making air temp colder makes boost target higher....
I canÃ,´t find anything that suggest a connection between the two?
This is closed loop setup
Analog input works to lower maximum allowed DutyCycle as expected.
TPS voltage also changes duty cycle by using the Boost vs. TPS scaling as expected.
Open loop boost, open loop DC adjustment channel enabled
If the DC is 10% in the map, maximum possible is 20% duty cycle and minimum is 0%
If map is 20% , max is 40% duty and minimum 9% duty
if map is 30% then max is 60% duty and min 14%.
and so on, everything above 50% in the map allows for 100% max via the switch,
if DC adjustment channel disabled, then DC is same as the DC map.
If Alternate settings disabled.
DC changes to chase the boost target.
but air temp also contributes to the boost target.
But lowers the boost target, that is if target is MAP-target.
If "boost target" then DC is always 0%
Why is MAT making such a mess of things?
If MAT goes above 30C then boost target is lower then 100kpa
Quote from: gunni on November 30, 2008, 12:36:07 AM
Does the boost switch work in this firmware?
When Boost alternate settings enabled..
IÃ,´ve got this on a bench and making air temp colder makes boost target higher....
I canÃ,´t find anything that suggest a connection between the two?
This is closed loop setup
Analog input works to lower maximum allowed DutyCycle as expected.
TPS voltage also changes duty cycle by using the Boost vs. TPS scaling as expected.
Open loop boost, open loop DC adjustment channel enabled
If the DC is 10% in the map, maximum possible is 20% duty cycle and minimum is 0%
If map is 20% , max is 40% duty and minimum 9% duty
if map is 30% then max is 60% duty and min 14%.
and so on, everything above 50% in the map allows for 100% max via the switch,
if DC adjustment channel disabled, then DC is same as the DC map.
If Alternate settings disabled.
DC changes to chase the boost target.
but air temp also contributes to the boost target.
But lowers the boost target, that is if target is MAP-target.
If "boost target" then DC is always 0%
Why is MAT making such a mess of things?
If MAT goes above 30C then boost target is lower then 100kpa
Maybe this?
uint8_t boost_matdec; // boost decrease -4kPa/C above this MAT [ F-40 ]
Thanks but why isnÃ,´t that in the Megatune software then?
ItÃ,´s a pretty clever control mechanism, I spot EGT boost retard as well.
Those are placed in shiftcut page as they don't fit on main boostcontrol page. I'll put them to boost alternate page.
IÃ,´m upgrading to 1.1.44 anyway
so no need to upgrade 1.1.43 as .44 is logical upgrade from other fwÃ,´s
Quote from: gunni on November 30, 2008, 12:06:34 PM
IÃ,´m upgrading to 1.1.44 anyway
so no need to upgrade 1.1.43 as .44 is logical upgrade from other fwÃ,´s
But Experimental features have disappeared on 1.1.44? I'd like to test some of them (like wheel speed input) but didn't find them on 1.1.44.
Quote from: PeepPaadam on December 18, 2008, 01:58:03 PM
Quote from: gunni on November 30, 2008, 12:06:34 PM
IÃ,´m upgrading to 1.1.44 anyway
so no need to upgrade 1.1.43 as .44 is logical upgrade from other fwÃ,´s
But Experimental features have disappeared on 1.1.44? I'd like to test some of them (like wheel speed input) but didn't find them on 1.1.44.
You need difrent vems.hex. This is my_make for 12x12 with speed sensor enabled.
http://www.vems.hu/files/DamirMuha/1.1.46/my_make.txt
How stable is this firmware?