Announcement
Collapse
No announcement yet.
MSS6x Flasher - Now released!
Collapse
This is a sticky topic.
X
X
-
Hello , first of all thank you for this amazing app, i was able to read full data out of my damaged mss60 . Question , if i write this full data to other dme with same part number will it be full clone of my dme ?
-
Originally posted by tdott View PostAre there any limits to number of times you can flash a MSS6x ecu?
Leave a comment:
-
Originally posted by 1984M3 View Post
Thanks Terra for your response. It reflashed in WinKFP. I should note that I was using version 1.0.0.2. Should I update to 1.0.0.3 and try again flashing the RSA bypass fast?
- Likes 1
Leave a comment:
-
Originally posted by terra View PostDoes the dme respond at all in tool32 or inpa or WinKFP? If so try reflashing with WinKFP. I’d just use the update function - it’ll figure out the VIN and such from there on its own.
If it doesn’t send me the backup file you made and I’ll clone it onto my dme and overnight that to you.
I don’t think it is bricked if it got to the step you’re at.
Leave a comment:
-
Update to my post above: Reflashed the ECU with WinKFP. Put in my vin. Reflashed without a problem. Started the car up without any issues at all.
Used the program to identify the ECU afterwards as well.
Leave a comment:
-
Does the dme respond at all in tool32 or inpa or WinKFP? If so try reflashing with WinKFP. I’d just use the update function - it’ll figure out the VIN and such from there on its own.
If it doesn’t send me the backup file you made and I’ll clone it onto my dme and overnight that to you.
I don’t think it is bricked if it got to the step you’re at.
- Likes 1
Leave a comment:
-
Had an error trying to flash the RSA Bypass fast. Using Bimmergeeks cable just bought. What should I do to recover or is my ecu permanently bricked? Should I try WinKFP to reprogram the ECU? Do I enter my full VIN in WinKFP or just the abbreviation?Last edited by 1984M3; 05-05-2020, 05:27 PM.
Leave a comment:
-
Originally posted by terra View PostMinor Update (Now Version 1.0.0.3)
Changes:- The application will now default to using the D2XX Driver instead of the Virtual COM Port. This seems to be more stable for K-line mode communications, should not cause any regressions for other cars
- In this mode, the settings you have in device manager (COM port, latency, etc) shouldn't matter.
- If you wish to go back to the Virtual COM Mode, Edit the "MSS6x Flasher.exe.config" so that "Port" is set to the COM port you desire (default is now "FTDI0")
- Note: This will probably not work properly if you have multiple FTDI devices connected at the same time. If you have multiple FTDI devices, you can try to select the specific device you want using the instructions under "FTDI D2XX Properties" here
- Eliminated the slow RSA bypass. Just seemed to create confusion.
- Made some changes so that if one of the stages during a flash process fails, the program doesn't try to perform the subsequent steps.
Leave a comment:
- The application will now default to using the D2XX Driver instead of the Virtual COM Port. This seems to be more stable for K-line mode communications, should not cause any regressions for other cars
Leave a comment: