When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I replaced the nearly 5 year old battery (because it was dropping below starting voltage) with a new EverStart Maxx H5 and found the air bag light is now on. When ignition key is turned on the airbag light comes on with other check lights, briefly goes out, and then comes back on and stays on. The PO had added a 3 ohm resistor to the squib wiring in the boot because of a corroded squib, but said the squib had not fired, and that resistor had worked for the 5 years I've had it until this battery change. I was careful not to damage the resistor wiring or the disconnected squib connector, but still got the air bag warning light.
I have the Schwaben/Foxwell 510 code scanner with BMW/Mini software and it shows no BMW faults but the light stays on. It also shows no OBDII codes. I looked for, but have not found a way to reset the light in the scanner's menus. Is there a way to reset the air bag warning light with the Schwaben scanner?
Is there any difference in which battery terminal is connected first? I connected the positive first and got a pretty big spark when I connected the negative terminal. Also is there any downside with driving with the air bag warning light on?
If the light is on then there should be an error code stored somewhere. Are you sure this tool is capable of scanning the airbag module?
The squib wiring is suspicious but you won't know for sure until the codes are read. But the error could have been triggered by low voltage of the dying battery (I've seen this first hand before).
The order of disconnecting/reconnecting the cables shouldn't matter to the electrical system of the car. But it's good practice to disconnect the negative cable first and reconnect it last. This is done for safety reasons, while you're wrenching on the positive terminal and your wrench accidentally grounds out on the chassis you won't have to worry about causing a short circuit.
A few sparks when reconnecting the negative cable is normal - nothing to worry about there.
If the light is on then there should be an error code stored somewhere. Are you sure this tool is capable of scanning the airbag module?
The squib wiring is suspicious but you won't know for sure until the codes are read. But the error could have been triggered by low voltage of the dying battery (I've seen this first hand before).
The order of disconnecting/reconnecting the cables shouldn't matter to the electrical system of the car. But it's good practice to disconnect the negative cable first and reconnect it last. This is done for safety reasons, while you're wrenching on the positive terminal and your wrench accidentally grounds out on the chassis you won't have to worry about causing a short circuit.
A few sparks when reconnecting the negative cable is normal - nothing to worry about there.
I have disconnected the battery several times before and had it get very low a number of times before this last replacement, and never had the air bag light come on. Looking back in my notes it has always sparked when reconnecting the negative terminal.
When I first connected the Schwaben to check for faults I did see one in the DSC module of "5E19 not present" but it was not detected later so I must have done a general code or fault erasure.
You ask will the Schwaben read the air bag module? When I Auto scan for faults now I see just three modules left after it scans and The one fault it now finds is in the Engine DME module "132/present - O2 sensor voltage high" and that fault will not erase.The others show no fault when it is scanning them..
The scanner does not find my VIN in auto mode so I have to manually select the model and year and when I do it finds the manufacture date, the programming date, the correct Chassis number (VIN), and other information specific to this Mini. It also lists 16 different body modules including the "Airbag MRS Multi restraint system IV" but when I try to check them it says it cannot communicate with any of them, so I must be doing something wrong. I've tried with the key on #1 position, #2 position, and with the engine running and still no communication.
I am cleaning the mini for a British car show tomorrow, so further testing will have to wait until after. If anyone knows how to get a Shwaben/Foxwell scanner to communicate with body modules, I'd appreciate a tutorial.
Last edited by philwarner; Oct 8, 2021 at 03:12 PM.
The scanner does not find my VIN in auto mode so I have to manually select the model and year and when I do it finds the manufacture date, the programming date, the correct Chassis number (VIN), and other information specific to this Mini. It also lists 16 different body modules including the "Airbag MRS Multi restraint system IV" but when I try to check them it says it cannot communicate with any of them, so I must be doing something wrong. I've tried with the key on #1 position, #2 position, and with the engine running and still no communication.
I also have the Schwaben scanner, it will read and clear my air bag codes.
If your scanner will not read your VIN in auto mode...you might have to update the software, that is the little SD card for the program. If your scanner is not updated to the latest version, you might have scanning issues. If your scanner does not do updates from the manufacturer via your computer, then forget everything I typed above.
Also, do not try reading codes while the engine running, it will not work. Key must be in #2 position with everything turned off (radio, heater, lights, everything possible)
I also have the Schwaben scanner, it will read and clear my air bag codes.
If your scanner will not read your VIN in auto mode...you might have to update the software, that is the little SD card for the program. If your scanner is not updated to the latest version, you might have scanning issues. If your scanner does not do updates from the manufacturer via your computer, then forget everything I typed above.
Also, do not try reading codes while the engine running, it will not work. Key must be in #2 position with everything turned off (radio, heater, lights, everything possible)
Bryan
Thanks Bryan,
I checked the Schwaben's Setup, About, and the scanner says copyright 2012. I bought it in June 2018 from ECS Tuning. I believe there is an update available, so I'll look into downloading it after the car show this week end.. I had assumed the update was mostly to include newer models, but maybe it will help with older ones too. Good to know yours will clear your airbag codes; I assume on the 06 JCW drop top?
My scanner WAS able to read all kinds of info from my buddy's BMW Z4, things like the brakes got hot once last year, but I am not having good luck with my 04 Mini, except that it did reset my brake pad warning light after I replaced the front pads and sensor when none of the other routines folks suggested extinguished it.
Yes, I am using the scanner on the '06 R52 JCW car.....I bought my scanner from ECS around 2018 as well, shortly after I got the car. I have probably done about 7-8 updates on the program files on the SD card....so that might be one of your problems.
Also, there was a recall on the passenger seat mat if I remember, mine was covered under warranty, I don't know if your car has that seat mat or not.
I would suggest to get the latest updates for your scanner card and then try to clear the codes again.....other than that....I'm only guessing here
Yes, I am using the scanner on the '06 R52 JCW car.....I bought my scanner from ECS around 2018 as well, shortly after I got the car. I have probably done about 7-8 updates on the program files on the SD card....so that might be one of your problems.
Also, there was a recall on the passenger seat mat if I remember, mine was covered under warranty, I don't know if your car has that seat mat or not.
I would suggest to get the latest updates for your scanner card and then try to clear the codes again.....other than that....I'm only guessing here
Bryan
At https://www.foxwelltech.us/support-tools.html I see a download for a Foxwell NT510elite, but not a Foxwell NT510 which I believe is what the Schwaben is. Is the NT510elite the one I need to use?
At https://www.foxwelltech.us/support-tools.html I see a download for a Foxwell NT510elite, but not a Foxwell NT510 which I believe is what the Schwaben is. Is the NT510elite the one I need to use?
I'm not sure....I was having issues trying to update my scanner a while back.....through several emails, thery sent me this link to update my scanner, have not had any issues since.
I'm not sure....I was having issues trying to update my scanner a while back.....through several emails, thery sent me this link to update my scanner, have not had any issues since.
If that doesn't help you, you will have to probably email them here support@foxwelltech.com and ask them to direct you to the correct download.
I don't want to say "Yes, it will work" and then find out it's not the correct download.
Bryan
Thanks Bryan,
I looked back in my notes to when I bought the Schwaben 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." i had forgotten that advice and have recently done several "Erase Codes" or something similar with the Schwaben.
Have you ever heard of a limit on number of code erasures in Minis? The young man I met had worked at a BMW/Mini dealer.
I also had saved some update information to pdf files that I had forgotten about, so between them and your link maybe I can get an update and try extinguishing the air bag light. I also have a new problem in that after cleaning my Mini for a car show yesterday, I had a Service Engine Soon light in the Tachometer that I had not seen before. It might be related to the Engine-DME-Digital; 132/Present – O2 Voltage high fault the scanner found and that I tried to erase unsuccessfully.
I have never heard of the comment that codes can not be erased after a certain amount of time.....they will keep coming back if you don't fix the problem. But as far as clearing them over time, there is no set limit
Sounds like one of your O2 sensors is shorted to the heater voltage.....scanner should be able to tell you which one.
Bank 1, sensor 1 is before the catalytic converter
Bank 1, sensor 2 is after the cat
Curious if you can get your scanner updated....you may have to send an email to them per my link above
I have never heard of the comment that codes can not be erased after a certain amount of time.....they will keep coming back if you don't fix the problem. But as far as clearing them over time, there is no set limit
Sounds like one of your O2 sensors is shorted to the heater voltage.....scanner should be able to tell you which one.
Bank 1, sensor 1 is before the catalytic converter
Bank 1, sensor 2 is after the cat
Curious if you can get your scanner updated....you may have to send an email to them per my link above
Bryan
The message said the sensor before the cat, I believe. I did use a hose to wash parts of the engine bay, but you'd think an overnight dry and drive of 40 miles would alleviate any water problem.
I created a Foxwell account and tried to register my scanner but so far could not. I sent this message to support@foxwelltech.com.
Schwaben-Foxwell NT510 SN NV51712068124 won't register
I bought my scanner from ECS Tuning in June of 2018 and I need to update the software in it.
I created an account at https://www.foxwelltech.us/register.html using my email address and password ______.
Then I tried to register my Schwaben/Foxwell510 scanner at https://www.foxwelltech.us/member#/new-register using the serial number NV51712068124, but it returns a message “sequence number error”
How can I get my scanner registered and update the software?
What the young man said was not that there was a time limit but a limit on the actual number of times codes can be erased before something in the BWM software locks you out, kind of like limiting the number of log-in tries. OH, and I am sure I have the serial number correct because I had also recorded it in 2018 and 2020 in my notes. ( I've got to remember to read my previous notes next time ) I even tried using lower case and substituting an o for the 0 just in case, but no joy.
The account I created was at foxwelltech.us but that log-in does not work at the link you used. Rather confusing.
Update: received an email from foxwelltech that said to register at the other web site, not the .us web site, and I am now awaiting the circling dots to stop after submitting my registration: still circling after 10 minutes, so not sure what gives.
Update 2:
I started over from scratch clicking the link in their email and got a window that said the registration went through but got no confirming email. After several more tries sent this to foxwelltech:
I went to the site you listed and entered my information to register, but did not receive a validation email nor can I find the “verification link” it says to click on.. I tried to register again and it said my user name was already registered and when I try to sign in I get
"Your account has not been activated yet. Please sign in your registered email and click the verification link to validate your Foxwell ID."
Where is the verification link?
Must be something lost in the English to Chinese translation or visa versa.
Update3:
Tried to download the foxscanner file foxwelltech listed and while it is shown as FoxScanner Installer_V8.73_20190508.zip on the web site, it downloads as a pdf file that Adobe cannot open. rather frustrating.
Update 4:
i renamed the downloaded pdf file to a zip file and was able to unzip it into an exe file and install FoxScanner 8.73 but guess what. When I run it it opens a window that wants me to sign in and then tells me that my account has not been validated. I just love the Chinese.
Last edited by philwarner; Oct 11, 2021 at 11:44 AM.
I have never heard of the comment that codes can not be erased after a certain amount of time.....they will keep coming back if you don't fix the problem. But as far as clearing them over time, there is no set limit
...Curious if you can get your scanner updated....you may have to send an email to them per my link above. Bryan
Had an email from Foxwelltech this a.m. that said they had registered my scanner for me and reset the password so I was able to log in. It took half a day to discover that the FoxScanner will do nothing until the SD card is connected to my computer and that the card reader that came with the scanner did not work. Finally tried another card reader and was able to work through the BMW and OBDII updates and even purchase the Honda module for our Odyesseys and I am about to go try that module out. My head still hurts from all the resets and vague instructions, but it seems to have finally worked.
I'll report back if the update can auto read the Mini VIN now, but the last update was in 2019 so I assume it still won't be able to read my buddy's later Beemer SUV. I just hope the Honda module is easier to navigate.
Update: After updating the NT510 Pro scanner it still cannot Automatically read my Mini's VIN in BMW/Mini diagnostic mode, but it can read the VIN in OBDII diagnostic mode. 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 the same "Engine DME Digital 132.not present - DME O2 sensor Bank 1 before cat voltage high" it had before. I did an erase codes and afterward it said no codes. However, if I go to Control Units/Body it still says it cannot communicate with any of the 16 units it lists and if I back out and go to Maintenance/Service Function/Body all the functions except Transport Mode say they are not supported; it will delete or reinstate transport mode.
The only up side is that when I started the engine after an hour or more of messing with the scanner, the Service Engine Soon light was not on, so the erasure of the O2 sensor fault must have worked for now. However my air bag warning light is still on and I have no way to get at the air bag system using the NT510 scanner. Maybe the fellow was correct about a limited number of fault erasures after which BMW locks you out?
I may start a new thread about the NT510 scanner to see if anyone else has experienced the same lack of communication with body modules or if it is just me.
Last edited by philwarner; Oct 12, 2021 at 03:12 PM.
Reason: update
To update this thread, I was finally able to get my NT510 scanner to communicate with the airbag-MRS module by plugging it directly into the OBDII recepticle rather than into a one-into-two OBDII cable I had used to keep my Ultra Gauge connected and have an easier place to plug the scanner. It had worked with this cable in the past, but for some reason now it can scan for errors but can not communicate with body modules through that cable.
However, there are several things about this scanner I find confusing. If I enter the VIN manually, a choice which only comes up if I click to read the VIN automatically and wait for it to fail, It says my model is year 2003_12 and it lists 33 modules in the control units/body section, but if I select one of the years in its manual list, 2003_9 or 2004_3, it lists just 16 modules in the control units/body section.
Also, If I select a saved vehicle (I saved one after entering the VIN manually), I get a list of just three modules, none of which have any errors, and there is no choice to look at any of the Control Units. Does anyone know how to get to the control units list from selecting a saved vehicle? The only way I have found to get there is to start a "new session" and go through the auto VIN read and fail and laboriously enter the VIN or to manually select from the list of models and model years that does not include my 2003_12 year.
And it seems odd to me that in OBDII mode the scanner can read my Mini's VIN, but in BMW/MINI mode it can not.
BTW, the reason I wanted to access the airbag-MRS module, the airbag light being on, was resolved when I found that a cold solder joint on the PO installed BST wiring 3.6 Ohm resistor had cause a higher than spec resistance causing the light to turn on and after re-soldering the resistor I was able to erase the fault with the scanner plugged directly to the OBDII recepticle..
Last edited by philwarner; Oct 20, 2021 at 06:51 AM.