Your vehicle for sure would still qualify as its MG1 based and pre 2021. I would however doublecheck the label on the ECU to get the exact production date. Also, you can reach out directly to us for tech support at "support@missiontuning.com"
The RS functionality is part of your OBD flashing, and this is the Backup/Unlock/Flashback physical device. For RS questions, I would reach out to your tuner.
Same answer as above. This is not a "tune" but a device to perform the unlock/flashback/backup functions. Throttle pedal questions should be addressed with your tuner.
Leaving a good question for last for today: That is a very interesting and good question you bring up. There is more than just restore functionality that goes into the Flashback (and even more to come!), however, Flashback was built on top of our EEPROM Recovery technology we released somewhere in 2019 with initial M340i offerings. Even though we have not publicized it much, over the years this offering has saved countless of customers at the dealer, and was pretty much the first product we offered that was complimentary to both our own platform and competitors. Recently, there has been more and more talk about it on these boards with people giving their real-life dealer experiences after doing our restoration service so it might be good to read over those and see what they came out with (not flagged for warranty work, etc). Also, it's worth mentioning that inconsistent data is NOT a ground for denial and flag, however concrete detection is. Below, ill put the summarized flagging functionality as well as two extreme examples:
Functionality
During the initial scan, a function AG9999 known as 'Tuning Detection" reads the vehicle data and extracts info including "plug and play variante suspected ", "plug and play DTCs suspected", and "tuning DTCs detected". With 11 of such parameters (was 9 just few months ago), the tool decides to either mark that DME is "Suspected of Tampering" or not.
Example Customer A: Comes in for turbo replacement to a dealer. The initial scan is ran, detecting "Plug And Play variant", aka any piggyback. The flag is set off only internally (since PnP is a level 2 detection currently). Now that data is transmitted to BMW warranty sector that will take that into account when issuing warranty repair orders. Since PnP flag can be set off ONLY by having actual piggyback (ok resistor trick with basic board can set it off as well), the warranty is denied even though the car looks fully stock. Why? Well because this specific flash has only one trigger function, that takes into account acceleration! So if you accelerated much faster then stock (letes hope you did, otherwsie the piggy-back did not actually function) and function detected other key parameters, this will be set off. BMW will also have access to "blackbox" data that outlines what performance paramaters (new one added is RPM/s, or RPM acceleration rate) were taken into account. To summrazie, you are screwed.
Example Customer B: Comes in with an identical car setup and the same complaint. The scan is ran, and no Flags aside from small chance of "low-Ilevel" is triggered (also level2). At this point, by perfoming Flashback, you lowered your detection chances from Flash to Piggyback, as to say. Now, this is where it gets very interesting: Unlike "pnp detection" that has only 1 trigger point, "low-Ilevel" has MULTIPLE with no "logs" as to what set it off as to say. So BMW now has a huge burden of proof to state that you performed some monipulation OR you had the car repaired somewhere else aside from their authroized dealer network (which you have full right to).
- You took the car to get repaired at an independent shop. During repair, the car failed update 1, 2 or 3 times causing "low-Ilevel" error to be triggered. Based on "Right To Repair", you the user have all the right to take your car outside of BMW Dealer, so you are all in the clear.
- You updated your car yourself using esys or ista at which time it failed few times but finally succesfully finished. Technically speaking, you actually did NOT violate your warrnty agreement as no aftermarket accessories were installed, and software in the car is authrozed by BMW, though potential flag registered a false positive.
Just with that above, you minimized your flagging risk from pretty serious to barelly any. Now, we enter a 3rd and most interesting aspect: The way it sits, M-Link has ability of performing backup unlimited number of times on your vehicle. With our upcoming updates, Version Control will be relased, and part of functionality will be lowering above mentioned risks even more. This function will alllow you to backup and restore to specific Verson so you have no way to even set off "low-Ilevel". Flow/Scenario:
- Perform initial backup before any modification.
- Modify and enjoy your car.
- Before going to dealer for software update (or even OTA updates), restore your DME's image to the initial backup.
- Go to dealer, get updatd to new version and drive home (or do this in the field if you like infront of dealer).
- Perform another backup. Now you have mirror image of your DME, still never modfieid, but of the same iLevel as BMW thinks you have
- Retune with platform of your choice.
- Boom goes the turbo.
- Restore the LAST backed-up image of your DME and go to dealership.
- "low-Ilevel" will not be set since your FW level matches exactly to what you left dealer with.