cjernigan

iTrader: (13)

Actually the 2nd one you listed is good to 85*C or around 175*F. I think it will be ok. :fm:

compy

Are you referring to http://www.radioshack.com/product/in...&tab=techSpecs ?
That is the second one I posted, Part # 272-1069.

Here is the Table:
Miscellaneous Features

Min Operating Temperature -40 Fahrenheit


Max Operating Temperature 85 Fahrenheit


Supported Languages English


The table indicates that the 85 degrees is in Fahrenheit, not Celsius. Is there some other link that you read that indicated otherwise?

cjernigan

iTrader: (13)

Considering my left nut can handle temps warmer than 85F i'm going to assume the tech specs part of that page is wrong. The main page says otherwise.

compy

Who knows then...

MikeRiv87

iTrader: (12)

I have the package for the 272-1069 .1 UF capacitor that i put in yesterday. The rating on the back says -40 F to +185 F. That is well within the range of a car interior, well in New jersey at least.

On a side note you can try these if space is an issue:
http://www.radioshack.com/product/in...tId=2062365&cp

I have a set of these that i bought too. They are much smaller and temp rating is -13F to +185F so if space is an issue you could try these.

compy

I should have checked out the other one when I purchased mine. FWIW the one I purchased (first link), the temperatures on the back were in C.

I wish we could just stop being so ignorant and switch to metric already.

timk

I used EasyTherm to create a modified firmware with the GM IAT and MX-5 CLT sensors and it gave me some weird side effects. I had a rev limit of 2500rpm and I was crazy rich all over the table. I flashed back to the MSPNP no AFM firmware and the problems went away. Maybe I didn't choose the right offset in EasyTherm or something. Anyway I thought I'd let you all know in case anyone else has this problem. I'll try to EasyTherm the HighRes firmware again on the weekend and see what happens.

timk

I tried this again and had the same problem, so instead of using EasyTherm I put the .inc files in the src folder and compiled a new msns-extra.s19 by running compile.bat. Guess what? Same problem! I tried this with both HR10d2 and HR10e.

Last time I had HR10d2 running with both the stock Miata sensors, and used EasyTherm to make the changes. Now I have a GM IAT sensor and a stock CLT sensor. When I flash back to the standard firmware, everything is great, but when I flash to either HR10d2 or HR10e (using the same MSQ) the ~2500rpm limit is back.

This is really doing my head in!

FoundSoul

iTrader: (5)

Alright guys-- a great thing happened today... I had installed some new coils on my red car which I haven't driven much since I put Hi-res on it, took it for a spin, and it started acting up just like Saboteur is reporting! It wasn't bad at first, barely noticeable when cold and could be dismissed as maybe needing some fine tuning on the hi-res code, but after the car was fully warm is was nearly undriveable-- I wasn't sure if I would make it back to the shop and then I figured out that if I babied it I 'could' get it to rev on past where it was having a problem, and if I held it high in the revs I could get home that way-- so I cruised home in 2nd and 3rd gear . When I had tested it on this car before I didn't notice a problem, but I only took a short drive, just enough to see I'd need to do some retuning, and parked it. This time I let it heat up and noticed it clearly... FWIW, I know of other cars running HiRes with no issues, on MSPNP MM9697 cars, so it's not the code.

Put the car on the dyno which I needed to do anyways, and got to work.

Sure enough, right at 2500 it was falling on it's face. This would happen when free-revving with no load, and when loaded up. Felt like a rev limiter like Sab has been describing. RumRumRumRumRum, right at 2500 ish.

I started working through things--

Reflashed the easythermed 10d2 firmware and reloaded my base map, no luck.

Reflashed to base 10d2 firmware and reloaded my base map, no luck.

Reflashed to base 10d2 an tried to get it to fire up without reloading my map and without taking any real time to copy over much more than base ignition settings and req_fuel. Car didn't run good enough to test and I aborted for another test.

Reflashed to base 10d2, and hand-copied every single setting from my old configuration over into the new. No .msq involved. I did export the VE, Spark, AFR Target, and EBC Duty Cycle tables to .vex files and import those, but everything else was a hand copy procedure. Works like a champ.

Reflashed to easythermed 10d2 in case that was creating the problem somehow. Still works like a champ.

No more issues- and it also appears that most of the previously apparent need to retune was another symptom of this .msq corruption/incompatibility between the two codebases. I'm still going through and touching up the tuning on my car just to be safe, as I previously had things a bit richer than I'm going to run them now. I also made a couple more changes to the car-- crazy hot coil packs that should allow me to run whatever boost I care to with no chance of blowout (they've been run, in competition, at 42psi of boost with no blowout when an M*D box couldn't hang), hence I may up the boost a lb or two when I'm done here... Car is sitting on the dyno now, I'll finish tomorrow.

So--

Unplug your coils/ignitors.
Reflash fresh firmware to make sure no leftover corruption is hanging around...
HAND COPY all of your settings. While disconnected from the ECU, open your old .msq and you can use ALT-PRTSCRN to copy each page to memory (yes there are alot of them), then CTRL-V to paste them into a wordpad document. Then use then when creating a new .msq in hi-res.
Save the new .msq!
Plug in your ignitors.

Test! Fine Tune!


Hope this works for you guys like it has me....

timk

Awesome! I'll give it a try tonight. Thanks dude!

cjernigan

iTrader: (13)

I've actually had to do the same hand copy deal before. Had some corrupted MSQ from transferring it between computers and accidentally saving it while running a different firmware blah blah something like that. A fresh MSQ solved that problem.
Glad to know this is a good fix for that.

cheesecow1

Correct?

FoundSoul

iTrader: (5)

Almost, but not quite--- that 'second from the top' hole would be JS11. You want to use the 'second from the bottom' hole, which is JS8.

If you want to send it our way we'll be glad to do it for you man...

cjernigan

iTrader: (13)

Cheese, as easy as it is to modify the PNP. A warranty is worth it to maintain. You sure you want to kill it by soldering that in yourself?

cheesecow1

im comfy as a dung beetle in a pile o poo soldering myself and i cant wait to ship it off and come back my car is a daily driver and I bum rides off of my friends far too often.

MikeRiv87

iTrader: (12)

Same Exact symptoms i was getting the other day before i re-flashed back to the non-hires code. I had to drive on the highway so what i did was short shift thru fifth get up to about 45 or so and then go back to 3rd and i would be past the 2500 rev limit thing. Then i could get to about 65 or so and not get ran over while driving on the highway. So you saying that i should hand copy every table into a new .msq after i have my MS flashed into hi-res and megatune reading my MS in Hi-Res. Im glad to here i'm not the only one out there with same problem, not that I'm wishing this problem on to any else or anything.

bbrbob

iTrader: (1)

I went Hi Res a month or so ago and this (or something very much like it) has popped up a few times. Is there any way that this problem could be intermittent? Now for the dumb question... I printed off all of my existing settings with a view to creating a new .MSQ. I thought that all I'd have to do is open Megatune, not load a file and then start filling in the fields until complete and then save to a file. So I get to setting the required fuel area and the "number of cylinders" cell is greyed out and I can't change it.. What is the process then?? Help.

FoundSoul

iTrader: (5)

I'd recommend flashing your box fresh with hi-res, then connect to the ECU so that you have the base map that's in it to begin with, and while connected go through and fill in each page of settings with your settings from your old config, one page at a time, remembering to burn each page.

cjernigan

iTrader: (13)

Anyone upgrade to the new 10e version?
Supposedly fixes the overboost protection for people using 3 and 4 bar map sensors.

FoundSoul

iTrader: (5)

I've tested it on the bench and the fix works there-- I've got a 2.5bar sensor in my MiataT so I haven't tested in the wild yet. If ya'll bump into KeithG (and this effected you) on the MS forums say thanks- he of course did this for everyone really and for the good of the project, but originally stepped up to bat on this at my request for the MSPNP guys as that's an advertised feature that was broken and this will correct it, and of course I knew it would help the DIY guys as well. The same fix will work it's way into the standard MS1E code too I believe, just hasn't happened quite yet.

There's no other change with HR10e AFAIK.