Ok, so I can go into a bit more detail about the ZGW flashing. I bought a ZGW-02 HIGH from a F01 2011 model car. If you get one from a car that came with NBT, it will be much easier than the trouble I had to go through. So, how do you hook it up? Well, you need to get access to the wiring diagrams for the F10 so that you can see where the ethernet wires go on the ZGW and how the second set of ethernet wires from the ZGW go to the NBT. You basically are wiring the ZGW in front of the NBT as seen from your laptop. The ZGW effectively has 2 ethernet "ports", one for your laptop, and one for your NBT. Anyways, you wire an ethernet cable to the ZGW where it would normally go the the OBD2 port (you can wire it to the OBD2 port if you want and use a USB to ENET cable to connect, but it's easier to wire it to an RJ45 plug). You'll need the resistor on the Ethernet-A wire, like it's shown in the Carsystems diagram. Then you wire the 5 Ethernet wires from the ZGW to the NBT on the other "port" of the ZGW. You don't need a resistor on that Ethernet-A line though. Then you hook up the K-Can2 wires on the ZGW to the same CAN wires on the NBT and adapter, not the CAN lines that go to the cluster. Last is the 2 power wires and the ground. You can wire the 2 power wires together if you plan on just wiring it this way temporarily, but if you plan to keep it in the car, it won't let your NBT go to sleep, let alone your amps and your battery will die quickly. Best is to figure out which one is constant 12V and which is switched 12V and wire it that way.
In Esys, you should now be able to connect by VIN, instead of only the gateway method. If you can't, then you either don't have it wired correctly or you've set a static IP on your LAN port. The flashing procedure is pretty much the same as the Esys Flashing guide 1.01 says, unless you have an older ZGW that was pre-NBT like mine was. I'm actually kind of glad that I got an earlier one, because it's taught me how to get around the issue. So, the issue is that when you read the SVT from the ZGW, it is looking for a HU_CIC, not HU_NBT. To fix this, you'll need to flash the ZGW, since it cannot be coded. Follow the guide that I'm linking to (Esys Flashing Guide 1.01).
Start out by going to the TAL Calculation on the Comfort screen and clicking Read FA. Save the file and click Edit. You'll be taken to the FA Editor where you'll need to edit your VIN (the one in your NBT) and set your vehicle option codes. Make sure you at least include the ones that are already on your NBT, so you don't lose any functionality. Make sure the time criteria is reasonable for NBT in the series you're choosing. You'll have to keep changing it and re-calculating the FA to make sure it's a valid choice. You should also make sure the car series matches what you have in the NBT. Once you're finished, save the FA and go back to the TAL Calculation screen. Let it reload the FA. Double-click the FA folder to activate it.
Now read the SVTActual, save it as svt_ist.xml and then edit it. Scroll down to the ZGW module. If it says ZGW2, you're probably already good, so continue on with the guide. If it just says ZGW, then double-click on ZGW and go to BaseVariant and change it to ZGW2. Save the file again and go back to the TAL Calculation screen. Now go to KIS/SVT and check Complete Flash button. Change the I-Step (ship) to 13-03-500 (First I-Level with NBT for F10). You can leave the I-Step (target) as whatever it was pre-loaded as (That's the most current for your PSDzData files). Next click Calculate, then click HW-IDs from SVTactual. Save the file as SVT_soll.xml (you can click edit again and verify that ZGW2 is still shown, but I think it remembers it from the first edit). Next, under TAL, click Calculation and save the file as SVT_tal.xml. Use the default folders for the file locations by the way.
Ok, now go to Expert Mode and click TAL Processing. Under TAL, load the SVT_TAL.xml file you saved earlier. Under SVT, load the SVT_soll.xml file you saved earlier. Under FA, load the FA file you saved earlier. The VIN under that should show the VIN that you changed to in the FA editor.
Once you loaded the SVT_tal.xml file, you should have seen a bunch of ECUs populate the lower section of the window with a bunch of check boxes. Click the button that says All in the upper left to deselect all check boxes. Now, go to the ZGW2 (should be ZGW2 here if you did everything right before). Check the boxes for blflash, swDeploy, cdDeploy, and ibaDeploy.
Now, here's where it can get interesting if you don't have all the required files, or the correct loader for Esys. I use TokenMaster's Esys Lanucher Premium 2.0, which automatically loads the definitions for the latest PSDzData, and you'll need the full package to program all modules. I'm not sure if the smaller 9GB package has all the required files, but you can click the Check Software Availability button to make sure it has all the required files. If you've set up Esys properly, it should say all of the files are found and you can procede.
Ok, so click the Start button and you should get a window asking for the I-Steps. For I-Step (current), put the I-Step level that it should show in the lower right corner of Esys, but it's the same that would have shown in the I-Steps on the TAL Calculation page and is the one that showed as I-step (target). In the I-Step (last), put the I-Step you used as the I-Step (ship) (eg 13-03-500 for F10). You won't be able to actually set the 3rd box, but when you hit Next, it should fill it. Click Finish and hope that it starts flashing properly. For the ZGW only, it should take just a few minutes. You should see some progress percentage lines in the log (turn on "Events" checkbox). If you don't, something went wrong. Once it's complete, I suggest closing Esys and re-opening it. Now, when you connect, you should be able to connect to the VIN again, but it hopefully should have changed to the VIN used in your NBT. If so, go ahead and connect. If it asks you the I-Step levels, leave it blank. Now, you're going to do basically the same thing you did for flashing the ZGW, but when you read the SVTActual, scroll down the list to HU_NBT and see if the text is black. If it's red or blue or still says HU_CIC, something is not right. If the text is black, continue doing the same steps as before, but this time, when you get to the TAL Processing page, you'll select the same check boxes for the HU_NBT and not the ZGW2. Same I-steps are used again (eg 13-03-500 for shipment and whatever your latest for the target/current). I highly recommend hooking up a 10A+ charger to the car before hitting start, because this will take about 40 minutes or so. If you're doing this on the bench, you don't have to worry about the charger. In either case, all you need hooked up is the CarSystems or BimmerRetrofit adapter, ZGW, and NBT.
If you start getting the percentage progress updates, you're likely ok and you'll just be waiting for about 40 minutes or so while it flashes. Once it finishes, you should have the latest version installed. Your FDL coding should have remained, but if it didn't, you can VO code it, then FDL code your changes as required. I had one additional step since mine was a MINI NBT and I was flashing the BMW firmware and that was to FDL code the HMI_brand to BMW.
That's basically it. If anyone has any questions, let me know and I'll do my best to help you out. This has been a grueling knowledge collecting process, but I'm just glad it's done and that I remembered how to do it
Bookmarks