MSPNP2 firmware upgrade 3.3.0 to 3.4.2...TERRIFIED!
06-09-2017, 04:42 PM
#1
Senior Member
Thread Starter
Join Date: Dec 2007
Location: ATL
Posts: 1,346
Total Cats: 128
MSPNP2 firmware upgrade 3.3.0 to 3.4.2...TERRIFIED!
I've been tweaking my tune for almost a year now...using more and more of the awesome capability of the MS platform (yes...even the lowly MSPNP). My latest adventure was to finally approach using EBC - not that the MBC I've been using hasn't served me well, I just want a finer degree of control.
Long story short, I've discovered that the built-in driver for the EBC solenoid is "dead" in my MS. So now my choices seem to be;
1) Take the unit to DIYAutotune and have them fix it (they're somewhat local to me so I can hopefully make an appointment, take it in, and have it repaired in a single day). Or...
2) Use the VICS output (as Matt suggested in a direct email to DIY) to drive the solenoid.
Unfortunately (for me) #2 - the quick-n-dirty approach - requires a firmware upgrade from 3.3.0 to 3.4.2. Reading up on that I've scared myself silly! I've read of people that have bricked their MS. Some that have come away with units that won't sync any more. Some with other horrific tales of angst and woe. I've got too much sweat 'n tears into this tune to have it all go to crap because of a failed firmware upgrade.
So....if it was you...#1, or #2?
Long story short, I've discovered that the built-in driver for the EBC solenoid is "dead" in my MS. So now my choices seem to be;
1) Take the unit to DIYAutotune and have them fix it (they're somewhat local to me so I can hopefully make an appointment, take it in, and have it repaired in a single day). Or...
2) Use the VICS output (as Matt suggested in a direct email to DIY) to drive the solenoid.
Unfortunately (for me) #2 - the quick-n-dirty approach - requires a firmware upgrade from 3.3.0 to 3.4.2. Reading up on that I've scared myself silly! I've read of people that have bricked their MS. Some that have come away with units that won't sync any more. Some with other horrific tales of angst and woe. I've got too much sweat 'n tears into this tune to have it all go to crap because of a failed firmware upgrade.
So....if it was you...#1, or #2?
Reply
0
0
06-10-2017, 08:20 AM
#2
Senior Member
Join Date: Apr 2011
Location: Hollywood, FL
Posts: 807
Total Cats: 163
#1 or #2 sounds awful. How about A or B?
B all the time. Save your tune and sanity check it once you upgrade. I'm not familiar with the differences in the firmware but reading up on it in MSExtra doesn't make it out to be a big deal.
B all the time. Save your tune and sanity check it once you upgrade. I'm not familiar with the differences in the firmware but reading up on it in MSExtra doesn't make it out to be a big deal.
Reply
0
0
