|
Voulunteer needed to run HR11c1
While building LostSoul's MS, I've run into an issue while testing it on the stim. I decided to try the latest HR build (11c1) and while it worked on first load, after I set it up for the 4/2 wheel, it started crashing every time I did a "burn to ECU" from certain screens. I've posted the issue at MSExtra, and KeithG inquired as to whether I'd run it on an actual car. Well, my CAS is in a landfill (36-1 wheel on my car) and I don't have the harness built for LS's car yet, so I'm only able to test it on the stim right now.
I wonder if anybody who is running a stock CAS might be willing to give the new code a try, just to verify that it crashes on your car the same as on my stim. Specifically, the screens that kill it are: • Accel/Decel mode • Accel Wizard • Codebase and Outputs • Rev Limiter Type • Rev Limits • Lambda Sensor Targets • OverRun Settings You don't even need to change anything in them, just open the screen and do a Burn. No permanent damage- you just power cycle the MS and it's mack to normal. |
link to the code and I'll try it tomorrow.
|
|
what is SUPPOSED to be better about it anyway?
|
I'll try it out tonight.
|
Originally Posted by paul
(Post 390894)
what is SUPPOSED to be better about it anyway?
|
Originally Posted by Joe Perez
(Post 390924)
The old version is 10. The new version is 11. That's one more, isn't it?
|
Here's what the readme says, poor spelling and all.
Originally Posted by HR_11c1
The default setting for this variable is 'map' which should perform exactly as all previous HR and LoRes codes in that MAP is used as the Y axis variable on the fuel and AFR maps. When it is set to '% Baro", the Y axis variable in the maps is Load = map*100/baro. It shoudl work just fone for all accepted map sensors. It does not matter if you have dual sensors or a single sensor, but with dual sensors, it will constantly adjust if this feature is enabled.
In addition, Baldur's turbo antilag code is added. THis is highly untested and can do tremendous damage. Any questions should be directed to the forums. This added feature differentiates the HiRes codes from the base 029 codes as the LoRes codes do not have this capability. The reasoning is that this feature makes it much easier to operate an engine in a wide range of altitudes. The load index on the tables takes into account the AFR desired regardless of barometric pressure. The Barometric correction featire shoudl operate more 'correctly'. If this needs to be adjusted for your installation, use EasyTherm v5 and edit the barometric correction table to suit your install. If there are any issues, problems or bugs, pelase report them to me on the msextra.com forum. HR_11b has a one line fix for a flaky PW when running % Baro. Also cleaned up a number of indents. HR_11c has the addition of the NGC Chrhsler wheel. HR_11C1 fixes an EGO problem introduced when ALS was added. Due to the logic of the test, If ALS was turned off, EGO correction of PW would always be bypassed. FIxed it for channel 1 and 2. This bug was in 11b and 11c. KeithG |
Well I fail, I cant even get it to install the new firmware...
|
Originally Posted by nicacus
(Post 391039)
Here's what the readme says, poor spelling and all.
|
does anyone here run a second sensor for baro correction? I've been thinking about adding one for when I drive through the mountains. I'd get the 4bar sensor, but I'll never get to 4bar, so I'd rather have the resolution on the 3bar. I'd be interested to know how well this new code works with that setup.
|
1 Attachment(s)
Originally Posted by Joe Perez
(Post 390924)
The old version is 10. The new version is 11. That's one more, isn't it?
|
I know what I was doing wrong when I tried installing it. Hopefully I can get it installed tonight. Maybe Brain will have gotten it installed by then though.
|
If you need another volunteer, I'm game, but can't get to it til Monday.
|
Originally Posted by TrickerZ
(Post 391090)
does anyone here run a second sensor for baro correction? I've been thinking about adding one for when I drive through the mountains. I'd get the 4bar sensor, but I'll never get to 4bar, so I'd rather have the resolution on the 3bar. I'd be interested to know how well this new code works with that setup.
|
Originally Posted by TrickerZ
(Post 391090)
does anyone here run a second sensor for baro correction? I've been thinking about adding one for when I drive through the mountains. I'd get the 4bar sensor, but I'll never get to 4bar, so I'd rather have the resolution on the 3bar. I'd be interested to know how well this new code works with that setup.
I do. All 94+ MSPNPs have dual MAP sensors. But I don't think I'll be trying out this firmware. |
Originally Posted by TrickerZ
(Post 391090)
does anyone here run a second sensor for baro correction? I've been thinking about adding one for when I drive through the mountains. I'd get the 4bar sensor, but I'll never get to 4bar, so I'd rather have the resolution on the 3bar. I'd be interested to know how well this new code works with that setup.
|
Originally Posted by Joe Perez
(Post 390924)
The old version is 10. The new version is 11. That's one more, isn't it?
|
|
| All times are GMT -4. The time now is 09:50 PM. |
© 2024 MH Sub I, LLC dba Internet Brands