Upgraded to HiRes 10g
03-23-2010, 10:23 AM
#1
Elite Member
Thread Starter
iTrader: (11)
Join Date: Jun 2007
Location: Overland Park, Kansas
Posts: 5,360
Total Cats: 43
Upgraded to HiRes 10g
I just wanted to share my experiences.
Downloaded HiRes 10g and ran it through easytherm last night, copied my inc files over to TunerStudio and flashed. Funny enough, it was the first startup since Friday evening and I already noticed a difference! Checked a few things under the car then went for a 3 hour drive using TS 'autotune' feature. Still haven't replaced my fuel pump so my fuel table still sucks but the car has a ROCK SOLID 1000rpm idle @ ~ 14:1afr!
Since adding intercooler to the hotside M45 draw-through system I've had a good deal of trouble getting the car to idle for anything. I'm impressed and should have upgraded sooner.
Somehow I misunderstood something about the hires firmware, had the idea it was a 16x16 fuel table so was a little disappointed to see a 12x12. Guess we'll have to upgrade to MS3 soon.
Downloaded HiRes 10g and ran it through easytherm last night, copied my inc files over to TunerStudio and flashed. Funny enough, it was the first startup since Friday evening and I already noticed a difference! Checked a few things under the car then went for a 3 hour drive using TS 'autotune' feature. Still haven't replaced my fuel pump so my fuel table still sucks but the car has a ROCK SOLID 1000rpm idle @ ~ 14:1afr!
Since adding intercooler to the hotside M45 draw-through system I've had a good deal of trouble getting the car to idle for anything. I'm impressed and should have upgraded sooner.
Somehow I misunderstood something about the hires firmware, had the idea it was a 16x16 fuel table so was a little disappointed to see a 12x12. Guess we'll have to upgrade to MS3 soon.
Reply
0
0
03-23-2010, 10:57 AM
#3
Elite Member
iTrader: (1)
Join Date: Jun 2006
Location: Warrington/Birmingham
Posts: 2,642
Total Cats: 42
Why didn't you upgrade to the latest MS1 Hi_res Firmware? 11 has been out ages!
Also as Brain says it's finer injector control, not more bins in the table. (16x16 is a ballache anyway, don't get your panties twisted over it, it's not the be-all).
Also as Brain says it's finer injector control, not more bins in the table. (16x16 is a ballache anyway, don't get your panties twisted over it, it's not the be-all).
Reply
0
0
03-23-2010, 11:15 AM
#4
Elite Member
Thread Starter
iTrader: (11)
Join Date: Jun 2007
Location: Overland Park, Kansas
Posts: 5,360
Total Cats: 43
I'm not twisted over no 16x16, it was a misunderstanding. 
Uhm, There is a v11? The newest I could find on msextra site was 10g. Any substantial difference between 10g and 11?
Uhm, There is a v11? The newest I could find on msextra site was 10g. Any substantial difference between 10g and 11?
Reply
0
0
03-23-2010, 11:27 AM
#5
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,017
Total Cats: 6,587
The latest version, so far as I know, is 11d. Realistically, though, most of the changes that have occurred over the past couple years have been of no consequence to Miata owners. Just adding support for non-standard MAP sensors, odd wheel patterns, etc. I've run various builds from 10b all the way to 11c. Right now, I'm running 10d2, for no particular reason than it was what I had lying around the last time I did a major re-flash.
Reply
0
0
03-23-2010, 11:39 AM
#7
Senior Member
iTrader: (4)
Join Date: Jan 2008
Location: Falls Church, VA
Posts: 1,361
Total Cats: 17
This is the readme that explains the changes. I've seen no reason to upgrade to v11 on my car. The next time I monkey around with MS will be to upgrade to MSII.
Originally Posted by README
Notes for HiRes 11d
THe HiRes code has higher precison of PW calculation for injection. It has roughly 2.5 times the resolution of the LoRes code. The HiRes code as of HR_10g is feature compatible with the 029y4 with the exception of PWM control of Low Impedance (Lo-Z) injectors. If you want to run Lo-Z injectors you need to either run resistors or use a peak and hold board.
The HR_11d is a variant of the HiRes code. It adds a NGC Chrysler wheel (63-2+2), the ALS feature - Anti Lag System for turbos - Danger! and a feature to use a dwell capability for Saab DI whioch may also be useful to otehr CDI systems (pin pulled low at the spark event and held low for a time period determined by a table)
The ALS code is Baldur's turbo antilag code which was added to a variant of 025 in the past. This adds it to HR_10. This feature is highly untested and can do tremendous damage. Any questions should be directed to the forums. This feature addition caused the bugs found in 11c abd 11c1. These have been fixed in HR_11c2.
If there are any issues, problems or bugs, pelase report them to me on the msextra.com forum.
The initial intent of HR11 was to add % baro. This was removed from HR_11d because of incompatibilities with the nonstandars sensors. These incompatibilities were never resolved and eventually were removed from the code in the interest of functionality and consistency as there were some users trying the ALS code and we did not want this known bug out in code being used.
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 Chrysler wheel to the generic wheel capabilities. (36-2+2)
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.
HR_11c2 fixes a bug that showed up with the nonmissing wheel. Pin 10 was not being set at burn for ALS, but pin 11 was (2nd trigger).
HR_11c3 adds a 'dwell' for Saab DI cassette. It *must* be used with COP and the dwell must be set to 50% fixed before setting turning on the Saab DI settings.
HR_11d removes the % Baro code from HR11c3
KeithG
THe HiRes code has higher precison of PW calculation for injection. It has roughly 2.5 times the resolution of the LoRes code. The HiRes code as of HR_10g is feature compatible with the 029y4 with the exception of PWM control of Low Impedance (Lo-Z) injectors. If you want to run Lo-Z injectors you need to either run resistors or use a peak and hold board.
The HR_11d is a variant of the HiRes code. It adds a NGC Chrysler wheel (63-2+2), the ALS feature - Anti Lag System for turbos - Danger! and a feature to use a dwell capability for Saab DI whioch may also be useful to otehr CDI systems (pin pulled low at the spark event and held low for a time period determined by a table)
The ALS code is Baldur's turbo antilag code which was added to a variant of 025 in the past. This adds it to HR_10. This feature is highly untested and can do tremendous damage. Any questions should be directed to the forums. This feature addition caused the bugs found in 11c abd 11c1. These have been fixed in HR_11c2.
If there are any issues, problems or bugs, pelase report them to me on the msextra.com forum.
The initial intent of HR11 was to add % baro. This was removed from HR_11d because of incompatibilities with the nonstandars sensors. These incompatibilities were never resolved and eventually were removed from the code in the interest of functionality and consistency as there were some users trying the ALS code and we did not want this known bug out in code being used.
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 Chrysler wheel to the generic wheel capabilities. (36-2+2)
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.
HR_11c2 fixes a bug that showed up with the nonmissing wheel. Pin 10 was not being set at burn for ALS, but pin 11 was (2nd trigger).
HR_11c3 adds a 'dwell' for Saab DI cassette. It *must* be used with COP and the dwell must be set to 50% fixed before setting turning on the Saab DI settings.
HR_11d removes the % Baro code from HR11c3
KeithG
Reply
0
0
03-23-2010, 11:55 AM
#11
Elite Member
iTrader: (1)
Join Date: Jun 2006
Location: Warrington/Birmingham
Posts: 2,642
Total Cats: 42
That looks like the biggest ball ache....
Seriously I find a 16x16 table more of a pain to populate, and seeing as the numbers are all interpolated and the B6/BP motor is pretty linear with it's VE, I fail to see the point.
Is that for a Honda? It'd make a bit more sense due to the massive change in VE when VTEC switches over, still seems excessive to me though.
Seriously I find a 16x16 table more of a pain to populate, and seeing as the numbers are all interpolated and the B6/BP motor is pretty linear with it's VE, I fail to see the point.
Is that for a Honda? It'd make a bit more sense due to the massive change in VE when VTEC switches over, still seems excessive to me though.
Reply
0
0
03-23-2010, 12:33 PM
#13
Elite Member
iTrader: (1)
Join Date: May 2009
Location: Jacksonville, FL
Posts: 5,155
Total Cats: 406
But yah, for the most part the resolution isnt needed. But I wouldnt say it makes it hard, its easy to smooth out when looking at the 2D maps. And on the off chance that the resolution would be needed it can be very nice. Ive seen tunes that have very fine adjustments in them that require high resolution.
Reply
0
0
03-23-2010, 02:21 PM
#17
Boost Czar
iTrader: (62)
Join Date: May 2005
Location: Chantilly, VA
Posts: 79,488
Total Cats: 4,077
the .1uF cap is need to filter the second trigger input from the CAS for some reason on Hi_Res code it's needed else you have random misfires.
needed for PNP or not using Ms-I and hi_res
needed for PNP or not using Ms-I and hi_res
Reply
0
0
03-23-2010, 03:10 PM
#18
Elite Member
Thread Starter
iTrader: (11)
Join Date: Jun 2007
Location: Overland Park, Kansas
Posts: 5,360
Total Cats: 43
Ooooh..
I still have a sparse random misfire but I'm pretty sure its the plugs. When they were fresh it didn't happen but now they've got a few miles on 'em with my oil burnin motor..
Will add cap anyway.
I still have a sparse random misfire but I'm pretty sure its the plugs. When they were fresh it didn't happen but now they've got a few miles on 'em with my oil burnin motor..
Will add cap anyway.
Reply
0
0
