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!

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.

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...

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.

install latest release. update map.

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.

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.

ok, that makes much more sense from an error-proofing standpoint. Here's the error report I need to wade through:


40 Warnings:
Warning: MSQ Units Mismatch for amap_table1! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for amap_table2! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:IdleCtl_out equal to the proposed Normal
Warning: MSQ Units Mismatch for IACcrankxt! s found in current configuration, sec found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for ego_startdelay! s found in current configuration, sec found in MSQ, values were not converted to new units.
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:flexport equal to the proposed LAUNCH
Warning: MSQ Units Mismatch for knk_trtd! s found in current configuration, sec found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for knk_tadv! s found in current configuration, sec found in MSQ, values were not converted to new units.
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:knkport equal to the proposed MS2 AD7/JS4
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:rtbaroport equal to the proposed Baro
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:ego2port equal to the proposed Baro
Warning: MSQ Units Mismatch for pwmidle_close_delay! s found in current configuration, sec found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for pwmidle_pid_wait_timer! s found in current configuration, sec found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for pwmidle_targ_ramptime! s found in current configuration, sec found in MSQ, values were not converted to new units.
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:boost_ctl_pins equal to the proposed BOOST
Warning: MSQ Units Mismatch for smap_injadv3! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fc_ego_delay! s found in current configuration, seconds found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for pwmidle_shift_open_time! s found in current configuration, sec found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for smap_table1! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:launch_opt_pins equal to the proposed Launch
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:N2Oopt_pins equal to the proposed Launch
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:N2Oopt_pins2 equal to the proposed InjectorD+C
Warning: MSQ Units Mismatch for RotarySplitLoad! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for smap_table3! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for idleadvance_delay! s found in current configuration, sec found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for smap_injadv1! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for smap_injadv2! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_trim1! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_trim1doz! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_table1! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_table3! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_table1doz! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_table3doz! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_trim2! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_trim3! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_trim4! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_trim2doz! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_trim3doz! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: MSQ Units Mismatch for fmap_trim4doz! kPa found in current configuration, % found in MSQ, values were not converted to new units.
Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:shift_cut_in equal to the proposed Tableswitch

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

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

Could please give more details on this. I am about to update firmware and think it might help me.

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.

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?

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.