Foxwell NT510 can't communicate with body modules
 

I was finally able to download the updates to my Schwaben/ Foxwell NT510 Pro scanner but after the updating, the scanner still cannot Automatically read my 2004 Mini Cooper S's VIN in BMW/Mini diagnostic mode, (although it can read the VIN in OBDII diagnostic mode) and the update erased all saved vehicle information and I had to start a new session manually selecting the model and year. I did an auto scan and it found one O2 sensor high voltage fault it had before and I did an "erase codes" and afterward it said no codes.

However, if I go to Control Units & Body it lists 16 body units but says it cannot communicate with any of the 16 units it lists. If I back out and go to Maintenance/Service Function/Body, all the functions say they are not supported except Transport Mode; it will delete or restore transport mode but all of the other listed functions say they are not supported. I wrote in my notes that I had used the Schwaben "Active test/component activation/power windows" test and when set to "activate" each window gave a double click but no movement” so I was able to access an active test for the windows before, but now when I try to open the ZKE Body Electronics (where I think the power windows reside) under Control Units and Body, it tells me it can't communicate so there is no active test I can find again for the windows. (The window motors were replaced several years ago BTW).

I need to access the multiple restraint system to find out why my air bag warning light came on after I replaced the battery, but the scanner is no help if it cannot communicate with the airbag MRS system and it is not much more help than an OBDII scanner at this point.

Now here's the kicker question. I looked back in my notes to when I bought the Schwaben version from ECS Tuning and first used it to find codes for my inoperative window motors and found this comment I had written: " I didn’t erase any of the codes the Schwaben found because of the advice of the young man at the GOBMC British Car Show that there is a set limit on the number of times codes can be erased." He said that BMW had set a limit on the number of times you can erase codes in the main module, which he called the footwell module because of its location, and that if code erasures exceed that limit they can no longer be erased and the only solution is to buy a new module from Mini for big $$$. The young man said he had worked at a BMW/Mini dealer. i had forgotten that advice and have done a number of "Erase Codes" over the last three years with the Schwaben...

So... has anyone ever heard of a limit on the number of code erasures in Minis or BMWs? And can anyone verify if this NT510 scanner is able to communicate with the 16 body modules on your Mini? And is it possible that the failure to communicate is specific to my Mini now that some set number of code erasures have occurred?

With my Foxwell, I’ll sometimes auto scan the VIN but will only pick up about 5 modules. If I go in manually by year and quarter of manufacture then I have 17 modules (06) but only not all read. It’s wired. Also my sons 04 has like 23 modules and my son-in-laws 06 has 18 or 19 modules.

I like the foxwell but it does read modules consistently. To get to the engine module I have to always do it manually.

The last auto scan I did after manually choosing the model and year left only three modules displayed after the scan,
1 Engine-DME Digital
2 ABS/ASC/DSC
3 EHPS Steering Assist

None of these three had any faults and no other modules were shown after the scan, although a number of them were displayed briefly while it said they were being scanned. I don't understand why not all of the modules that are scanned remain in the display and many are then inaccessible.

Also, my Mini's Manufacture date is 11/9/2003 and the Programming date is 1/12/2004 but the two closest choices for manual selection are 2003_09 and 2004_03. I have tried both and gotten similar results but I don't know which is correct for my Mini. The scanner manual is pretty generic and does not help. It would be so much easier if the Mini Mode could read the VIN automatically as the OBDII mode is able to do..

Guy from BMW dealer talk about FRM module used for R56 model, not for R53, because R53 is equiped with BC -Body control- not with FRM, even both make same job.
Anyway you can try just to rewrite the BC file,using INPA cable and NCSExpert software.

I am not familiar with the INPA cable, but I did look up the NCSExpert software. It seems a bit scary to try re-writing a module in the car unless you really know what you are doing or unless the software can safely walk you through it with 100% assurance.

I received this Reply from Matt at ECS Tuning:
Thank you for getting back to me. I spoke to our MINI product specialist on this one to make sure I have all of the information absolutely correct. There is no limit on how many times you can erase/clear codes on a BMW/MINI. This is a misconception that is not true.
The NT510 scanner can communicate with all 16 body modules. It cannot program all of them but it can read them for codes. If it cannot communicate that likely means there is an issue with a connection somewhere within the car. In the early 2000s MINIs like yours, it is common for moisture to find its way into the footwell module. When the moisture gets in corrosion can occur in the footwell module and can cause the errors you are having. He recommends you pull the footwell module and take a look inside of it to make sure there is no corrosion. I hope this helps. Please let me know if you have any more questions and I will see what I can find. Matt M VW/Audi Product Specialist

So can someone tell me how to access the "footwell module"? Are there any you tube videos on checking/cleaning this for our Gen 1 Mini's?

This link shows you where it is and how to remove it. You’ll have to remove the door entry trim along the step over of the passenger door. It’s just held in with pop out clips.

There was a mod in the later Gen 1s to put a water shield over the top of the BCM. You may not have that. Water comes in from sunroof, window or even under hood around brake module and gets in the floor and floods the BCM.

Thanks for that link. Good to know it is on the right side in our Minis and not on the driver side as later ones. Is it best to disconnect the battery first or does it make any difference?

Oops, I meant US driver side, not UK.
BTW, everyone on You Tube seems to wear gloves, but I find them very hard to work in. They are either too heavy or if the thin plastic kind my hands sweat and drip out of the gloves onto whatever I am trying to do. Maybe it's a Southern thing other don't experience.

I would suggest you disconnect the battery. Not sure if it’s mandatory. Better safe than sorry.

I was surprised that none of the You Tube videos mention disconnecting the battery first; most are usually pretty thorough about such things, maybe for liability reasons.

Raining right now and the Mini is under a car cover in the driveway, so removal of the BCM will have to come later. At least I have something else to try now besides cursing the scanner.

I get more modules when i do the manual with a later build then the auto vin which gives me less modules. Have not looked into why.

I just got the foxwell nr510 elite scanner. I see "transmission control unit EGS" but the device cannot communicate with it. Has anyone had any luck with this device to communicate with egs on a 2005 mini cooper r50?

Best,
Mike

I realized this thread is regarding the body module. Sorry.

Mike, when you got the scanner, did you register it and download the latest updates?

Yes, I updated all the modules, including mini. I also created an account with foxwell from which I tried to register the device but it failed for some reason.

I have a foxwell 510 - ( it’s an ECS Schwaben branded one ). It works fine on body modules with the e46 ( 01 330 vert ). I last used it on the r53 about a year ago, and it saw body modules and reported on them. Nothing I needed to reset, so I can’t say what happens.

When I first bought my Foxwell NT510 Elite, I did some reading about it online. The one thing that stuck with me was reading enough users accounts as to updating the firmware had bricked their device/Foxwell.
I have a 04 pre-facelift R53 wich has been mentioned that updating the Foxwell NT510 software is unnecessary since much of the updates didn't apply to the early ECU's. True or false...
That's just my understanding - from what I've read.

Thanks for the replies. I haven't updated the firmware. The scanner is not able to connect to the DME module as well. By car battery is at 12.7V. Going to return the scanner.

When working with electrics or electronics, ALWAYS disconnect the battery first. For instance, removing the seat and disconnecting the lines under it without disconnecting the battery will set your airbag light and require programming to reset.

Sorry to hear you may have gotten a dud and have to return it.
From my novice experience with the Foxwell NT510 Elite; Since I've had mine - the only time I received the "Unable to communicate dialogue" was scanning for fault codes whilst the engine was running. Scanning and revealing fault codes/diagnostic worked fine when engine was running.
But in order to clear the fault codes the engine had to be off. Just the key turned to the second position.

I can imagine some of the more seasoned are rolling their eyes right now:)....but as I've already conceded to - I'm pretty much a novice:nod:

Tried both with engine off and on. Same result.

Ecu

If you disconnect the seat / airbag when the battery is still connected, you will trigger the airbag light - which is all in the airbag module / ecu - not engine, transmission or body module / ecu. I have used foxwell 510 to reset that - twice on the e46 - interior swap.

inpa will reset airbag light if the condition has been fixed.

with the srs, the lights dont reset on their own. once there is an error you have to reset it manually. some safety kind of logic

. I think the Foxwell 510 is the same as the Swaben Elite but, I wasn’t aware it could reset the airbag module , Thanks …