DIYPNP firmware/base map compatibility - Miata Turbo Forum - Boost cars, acquire cats.

Welcome to Miataturbo.net   Members
 


MEGAsquirt A place to collectively sort out this megasquirt gizmo

Reply
 
 
 
LinkBack Thread Tools
Old 11-13-2015, 07:43 PM   #1
Senior Member
Thread Starter
iTrader: (1)
 
wackbards's Avatar
 
Join Date: Nov 2015
Location: Seattle
Posts: 613
Total Cats: 63
Default DIYPNP firmware/base map compatibility

Hi all, first post to the forum, so please don't assume I actually know what I'm talking about here...

I've built a DIYPNP (v1.5B/v2.2M), and I'm unsure how to proceed with the firmware & base map install.

based on the firmware installation instructions, it sounds like the firmware & base map versions must be identical for them to play together nice like. buuut, I can't find identical versions of each. I see firmware versions 3.4.0, 3.3.3, 3.2.5, and 2.1.0e here. I found base maps for versions 3.3.1a and 3.2.1 here.

so my questions to the comunity are:

1) does version compatibility matter given my YMM?
2) if so, can anyone point me towards compatible firmware & base map?


for reference, the car is a normally aspirated '91 USDM 1.6 with basic I/H/E mods, GM IAT, & LC-2 WBo2.

Thanks!
wackbards is offline   Reply With Quote
Old 11-13-2015, 08:15 PM   #2
Senior Member
iTrader: (3)
 
Join Date: Sep 2011
Location: Plano TX
Posts: 595
Total Cats: 2
Default

I am guessing you have already seen the base map for a 1.6 at the end of the diypnp instructions. I believe that is very old firmware.
But it's what I used to start the 1.6 3 years ago just turn off electronic boost control it's turned on in the base map and cause a major error that stops the car from starting.

Remember to unplug coils and ignitor when flashing firm ware.

I am sure someone with more knowledge of the newer firmware will chime in.
90 Turbo is offline   Reply With Quote
Old 11-13-2015, 08:24 PM   #3
Senior Member
Thread Starter
iTrader: (1)
 
wackbards's Avatar
 
Join Date: Nov 2015
Location: Seattle
Posts: 613
Total Cats: 63
Default

Quote:
Originally Posted by 90 Turbo View Post
I am guessing you have already seen the base map for a 1.6 at the end of the diypnp instructions. I believe that is very old firmware.
But it's what I used to start the 1.6 3 years ago just turn off electronic boost control it's turned on in the base map and cause a major error that stops the car from starting.

Remember to unplug coils and ignitor when flashing firm ware.
yeah, I did download that base map. There are actually two maps contained for two different injector sizes. It says it's for a turbo build, and tunerstudio identified it as version 3.0.3s. I guess that's another option to add to the pile, but it didn't seem like a good one. I couldn't find a firmware version to support that map either.

I'm loading the software off-vehicle with a 12v power supply to reduce the changes of frying anything...
wackbards is offline   Reply With Quote
Old 11-14-2015, 07:34 AM   #4
Senior Member
 
Join Date: Apr 2011
Location: Hollywood, FL
Posts: 525
Total Cats: 18
Default

I see what you are trying to accomplish but unless you get someone to give you a basemap for your particular engine from the latest firmware, you are SOL. If you bought it from DIYAutotune, send them an email. They might just have one.

Otherwise you just load the latest firmware and change every setting to what you need. Forget the errors and whatever else it says at the beginning. Just go setting by setting until it matches the basemap or your needs.

The other option is to load the older firmware that you have a basemap for. I seem to remember the option to do so on the firmware download page. Of course once you do this you will have to go and change setting by setting when you go to the current firmware. There is no easy button here.
hector is offline   Reply With Quote
Old 11-14-2015, 10:13 AM   #5
Boost Czar
iTrader: (61)
 
Braineack's Avatar
 
Join Date: May 2005
Location: Chantilly, VA
Posts: 72,900
Total Cats: 1,793
Default

install latest release. update map.
Braineack is offline   Reply With Quote
Old 11-14-2015, 04:08 PM   #6
Senior Member
Thread Starter
iTrader: (1)
 
wackbards's Avatar
 
Join Date: Nov 2015
Location: Seattle
Posts: 613
Total Cats: 63
Default

ok, I've loaded v3.4.0 firmware onto the ECU, and Tunerstudio is recognizing the ECU & format. I grabbed screenshots of every setting on the 3.3.1a base map, and I'm manually imputing the settings & values into a new v3.4.0 map. The tunerstudio menus and options appear different when viewing each map, so I'm discovering that it's not quite just a plug & play operation. I'm grinding away at the manual here.

thanks for the help, and I'm sure I'll have more pointed questions as I bumble through this.
wackbards is offline   Reply With Quote
Old 11-14-2015, 06:48 PM   #7
SADFab Destructive Testing Engineer
iTrader: (5)
 
aidandj's Avatar
 
Join Date: Apr 2014
Location: Beaverton, USA
Posts: 17,999
Total Cats: 1,466
Default

Load map onto new firmware. Copy all error messages. Go fix all error messages. Problem solved. Dont start from scratch you will forget a setting.
aidandj is offline   Reply With Quote
Old 11-14-2015, 10:58 PM   #8
Senior Member
Thread Starter
iTrader: (1)
 
wackbards's Avatar
 
Join Date: Nov 2015
Location: Seattle
Posts: 613
Total Cats: 63
Default

Done. 40 errors. Posted them here, but looks like it needed admin approval. I'll be wading through the error report next.
wackbards is offline   Reply With Quote
Old 11-14-2015, 11:00 PM   #9
SADFab Destructive Testing Engineer
iTrader: (5)
 
aidandj's Avatar
 
Join Date: Apr 2014
Location: Beaverton, USA
Posts: 17,999
Total Cats: 1,466
Default

Quote:
Originally Posted by wackbards View Post
Done. 40 errors. Posted them here, but looks like it needed admin approval. I'll be wading through the error report next.
Most will be inconsequential
aidandj is offline   Reply With Quote
Old 11-15-2015, 01:51 AM   #10
Senior Member
Thread Starter
iTrader: (1)
 
wackbards's Avatar
 
Join Date: Nov 2015
Location: Seattle
Posts: 613
Total Cats: 63
Default

looks like I got it working.

errors sorted into three basic statements:
1) units have changed from kpa to %
2) units have changed from s to sec
3) parameter in msq but not valid for current firmware

these seemed like the above mentioned "inconsequential" errors. I tried tricking the software by iterating the tune file through once again: saving/importing 3.3.1a-->3.4.0-->3.4.0. this cleaned up every single error except one for barometric correction. it was set to "2 independent sensors", and I changed it to "initial map reading".

well, nothing caught on fire, and the ECU seems to be swallowing the software load so to speak... I guess the next step is to see what happens when I plug it into the car.

thanks for the assist,
-wacky
wackbards is offline   Reply With Quote
Old 11-15-2015, 11:13 AM   #11
Senior Member
iTrader: (3)
 
Join Date: Sep 2011
Location: Plano TX
Posts: 595
Total Cats: 2
Default

Quote:
Originally Posted by wackbards View Post
I tried tricking the software by iterating the tune file through once again: saving/importing 3.3.1a-->3.4.0-->3.4.0.
-wacky
Could please give more details on this. I am about to update firmware and think it might help me.
90 Turbo is offline   Reply With Quote
Old 11-15-2015, 04:11 PM   #12
Senior Member
Thread Starter
iTrader: (1)
 
wackbards's Avatar
 
Join Date: Nov 2015
Location: Seattle
Posts: 613
Total Cats: 63
Default

When you load a map for an old version of firmware into an ECU with a new firmware version, tunerstudio spits out an error report & asks which dataset you want to burn. I went with the dataset that came with the outdated base map. Then I saved this file to the desktop. It's now a 3.4.0 map, with cell values from the 3.3.1a map, but variable names from the 3.4.0 format. Then I shut everything down & cycled it back on. I opened the map I had just saved to the desktop & burned it to the ECU. This time, I only got the one error for the barometric settings, which I then changed & burned. I copy & pasted the error report for posterity in case the map doesn't actually work.

This is the first time I've ever done this, so I don't know if this is the right way. Seems to have worked though.
wackbards is offline   Reply With Quote
Old 11-24-2015, 07:30 PM   #13
Senior Member
Thread Starter
iTrader: (1)
 
wackbards's Avatar
 
Join Date: Nov 2015
Location: Seattle
Posts: 613
Total Cats: 63
Default

Under the engine & sequential settings, my map has required fuel values populated, but the engine size is set to 2000cc, and injector size to 0. Am I correct in understanding that these two values are used to calculate required fuel? If the required fuel values are already populated by importing/updating my 3.3.1a base map, should I just leave the values for engine & injector size alone?
wackbards is offline   Reply With Quote
Old 11-25-2015, 07:13 AM   #14
Senior Member
 
Join Date: Apr 2011
Location: Hollywood, FL
Posts: 525
Total Cats: 18
Default

Input actual engine size and actual injector flow. Don't overthink it.

When updating firmware you lose quite a bit of settings although your fuel and ignition maps may stay the same. Things like ignition settings and injector firing strategy and even o2 preferences tend to get wiped away by a firmware update. You must go through everything.
hector is offline   Reply With Quote
 
 
Reply

Related Topics
Thread Thread Starter Forum Replies Last Post
New to Miatas, new to cars. dickamusmaxamus Meet and Greet 35 07-29-2016 02:50 PM
MSPNP Pro Bad MAP sensor? abenson100 MSPNP 7 01-31-2016 09:03 PM
fm throttle body adapter & 1.6 coolant reroute charlie7337 WTB 4 12-19-2015 12:28 AM
Part Out Sale! 1.6 BEGi S2 GT2560R kit, injectors, MSPNP, full 3" exhaust and more. Trent Miata parts for sale/trade 12 11-25-2015 07:47 PM


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



All times are GMT -4. The time now is 07:12 AM.