[Sylow]

I installed a JB4 along with the bluetooth unit in my 2013 F30 335i M sport approximately three weeks ago. The unit ran fine until recently when I started to get the following codes

102001 Air mass, Plausibility - Tuner code, ignore
121001 TMAP sensor,short circuit to +
120408 Reduced Power Mode
104401 MAP sensor, intake pipe, electrical: Short to circuit to B+

I removed the unit and vehicle runs fine, so I believe the TMAP and intake MAP sensor sensor are not damaged and hence the short may be in the JB4 unit itself. The car battery was disconnected during both the installation and removal. I realize that the TMAP sensor issue is common but I received a code for both the TMAP and intake MAP sensor, and the vehicle does NOT throw a code with the JB4 removed. I also find it worrying that the code suspects a tuner code despite the JB4 being advertised as nearly undetectable.

Anyone have recommendations? I purchased the unit from Mike at n54tuning and emailed him. At the moment I'm open to a exchange or refund. But I'm wondering if I should cut my loses, escalate a refund claim through Paypal, and go with either a Dinan Stage 2 or MPPK.

Edit: Codes were caused by incorrectly connecting the red power wire from the BT Rev3 dongle to the red 12 volt line instead of the 5 volt red wire in the main JB4 wiring harness.

[Jadar]

Originally Posted by Sylow

I installed a JB4 along with the bluetooth unit in my 2013 F30 335i M sport approximately three weeks ago. The unit ran fine until recently when I started to get the following codes

102001 Air mass, Plausibility - Tuner code, ignore
121001 TMAP sensor,short circuit to +
120408 Reduced Power Mode
104401 MAP sensor, intake pipe, electrical: Short to circuit to B+

I removed the unit and vehicle runs fine, so I believe the TMAP and intake MAP sensor sensor are not damaged and hence the short may be in the JB4 unit itself. The car battery was disconnected during both the installation and removal. I realize that the TMAP sensor issue is common but I received a code for both the TMAP and intake MAP sensor, and the vehicle does NOT throw a code with the JB4 removed. I also find it worrying that the code suspects a tuner code despite the JB4 being advertised as nearly undetectable.

Anyone have recommendations? I purchased the unit from Mike at n54tuning and emailed him. At the moment I'm open to a exchange or refund. But I'm wondering if I should cut my loses, escalate a refund claim through Paypal, and go with either a Dinan Stage 2 or MPPK.

I'll elaborate and these are my views, experiences and some of the things I've found out through reading and searching for answeres.

I'll start with I use to run JB4 and with the Bluetooth rev. 3.
I no longer run JB4 since in all honestly it started to give me the same issues. All the same issues you listed. I'm not going to get into great detail but i ditched JB4 and went to bootmod3 and never been happier.

Now, I found that for running JB4 in the 2 years it was best on earlier revisions. 2.hex and 5.hex files worked relatively well. I noticed more problems when I updated to newer files.

Also this is what I found...folks started having these short circuit faults when they added the Bluetooth device. I've ran across 2 people that took it off and ran the lap top with data cable and it stopped. Coincidence? Perhaps...I can't confirm or say that's a fix. But it's what I've seen.

I've heard there's a revision 4 Bluetooth coming and maybe this is why. But I'm not paying another $140 to find out for a BT dongle.

I worked with terry and in the end I dialed it in but still had a mysterious drivetrain fault that threw no codes and the only way to clear it was disconnect the battery. Pretty annoying every 9-10 days.

Took JB4 off never had another issue. Just saying.

JB4 has awesome support and a lot of users and that helps a ton plus countless parameters that nothing else can adjust such as fueling at the moment especially meth and PI control. So it does come with great benefits as well.

Good luck man.

[Sylow]

Thanks for the reply. I should of added that I initially got the fault last weekend but a clear and restart got rid of the issue. Today the issue persisted through the clear but I did not disconnect the battery today other than to remove the JB4.

[Jadar]

Originally Posted by Sylow

Thanks for the reply. I should of added that I initially got the fault last weekend but a clear and restart got rid of the issue. Today the issue persisted through the clear but I did not disconnect the battery today other than to remove the JB4.

I would try and set a map you want, then unplug the battery, take off the Bluetooth dongle reattached the battery and see how it does.

It's the ups and downs of JB4 life...good days bad days.

[Sylow]

Originally Posted by Dejan_

I would try and set a map you want, then unplug the battery, take off the Bluetooth dongle reattached the battery and see how it does.

It's the ups and downs of JB4 life...good days bad days.

Thanks. I originally ran the JB4 for one week without rev3 BT dongle as Mike forgot to ship it together. The first code appeared within a few days of attaching the bluetooth dongle and again today. I'll try running it without it and see how it goes for a week.

[Jadar]

Originally Posted by Sylow

Thanks. I originally ran the JB4 for one week without rev3 BT dongle as Mike forgot to ship it together. The first code appeared within a few days of attaching the bluetooth dongle and again today. I'll try running it without it and see how it goes for a week.

That's when my issues began as well man. Try it and report back. You'd be doing us a solid.

[M-terkait]

Originally Posted by Dejan_

I'll elaborate and these are my views, experiences and some of the things I've found out through reading and searching for answeres.

I'll start with I use to run JB4 and with the Bluetooth rev. 3.
I no longer run JB4 since in all honestly it started to give me the same issues. All the same issues you listed. I'm not going to get into great detail but i ditched JB4 and went to bootmod3 and never been happier.

Now, I found that for running JB4 in the 2 years it was best on earlier revisions. 2.hex and 5.hex files worked relatively well. I noticed more problems when I updated to newer files.

Also this is what I found...folks started having these short circuit faults when they added the Bluetooth device. I've ran across 2 people that took it off and ran the lap top with data cable and it stopped. Coincidence? Perhaps...I can't confirm or say that's a fix. But it's what I've seen.

I've heard there's a revision 4 Bluetooth coming and maybe this is why. But I'm not paying another $140 to find out for a BT dongle.

I worked with terry and in the end I dialed it in but still had a mysterious drivetrain fault that threw no codes and the only way to clear it was disconnect the battery. Pretty annoying every 9-10 days.

Took JB4 off never had another issue. Just saying.

JB4 has awesome support and a lot of users and that helps a ton plus countless parameters that nothing else can adjust such as fueling at the moment especially meth and PI control. So it does come with great benefits as well.

Good luck man.

Same shit here bluetooth had problems and none was listening to me many emails but no solution was found.. So i gave up on it.

[mike@x-ph.com]

OP did you contact BMS technical support?

[Sylow]

Originally Posted by mike@x-ph.com

OP did you contact BMS technical support?

Today is Saturday so I didn't try them yet. I reconnected the JB4 without the Bluetooth and went on a 50 mile ride through the Malibu canyons and it seems to be running fine. I'll wait a week to see if another CEL pops up.

I'll be happy if the main JB4 unit runs without the bluetooth module but it's a shame. The Bluetooth module was $139 and another $36 for the JB4 Mobile app and I doubt i'll get a refund on either. The app worked really well and I really did like it. Luckily I do have another code reading tool available to me if another warning pops up.

[mike@x-ph.com]

Originally Posted by Sylow

Today is Saturday so I didn't try them yet. I reconnected the JB4 without the Bluetooth and went on a 50 mile ride through the Malibu canyons and it seems to be running fine. I'll wait a week to see if another CEL pops up.

I'll be happy if the main JB4 unit runs without the bluetooth module but it's a shame. The Bluetooth module was $139 and another $36 for the JB4 Mobile app and I doubt i'll get a refund on either. The app worked really well and I really did like it. Luckily I do have another code reading tool available to me if another warning pops up.

If the bluetooth is the defective you will get a refund on it for sure

[Jadar]

Originally Posted by Sylow

Today is Saturday so I didn't try them yet. I reconnected the JB4 without the Bluetooth and went on a 50 mile ride through the Malibu canyons and it seems to be running fine. I'll wait a week to see if another CEL pops up.

I'll be happy if the main JB4 unit runs without the bluetooth module but it's a shame. The Bluetooth module was $139 and another $36 for the JB4 Mobile app and I doubt i'll get a refund on either. The app worked really well and I really did like it. Luckily I do have another code reading tool available to me if another warning pops up.

You can still clear codes with the jb4 but hooking it up the the lap top using the data cable.

[Sylow]

I received a response from Jon at BMS. I was very surprised to get a response to an email sent on Saturday night. Turns out I incorrectly tapped the Rev3 Connect Kit to the lone 12v red wire (the one connected to the battery rail from the JB4) INSTEAD the 5v red (CORRECT) within the main wiring harness. Bit confusing but my fault. I'll reconnect the Rev3 kit and report back.

[yoandry]

4 days now. Updated please.
Thinking on going jb4+bt or bootmode3.

[Sylow]

Originally Posted by yoandry

4 days now. Updated please.
Thinking on going jb4+bt or bootmode3.

So far no problem after fixing the wiring. Just be careful to disconnect the battery whenever you do ANY wiring work with the JB4 and make sure the red wire from the BT Dongle is connected to the 5 volt red wire within the main harness bundle and NOT the lone 12 volt red wire going to the battery rail. Support from BMS has been great and they even replied quickly to an email on a Saturday.

[yoandry]

Originally Posted by Sylow

So far no problem after fixing the wiring. Just be careful to disconnect the battery whenever you do ANY wiring work with the JB4 and make sure the red wire from the BT Dongle is connected to the 5 volt red wire within the main harness bundle and NOT the lone 12 volt red wire going to the battery rail. Support from BMS has been great and they even replied quickly to an email on a Saturday.

[Bigmo93]

Originally Posted by Sylow

So far no problem after fixing the wiring. Just be careful to disconnect the battery whenever you do ANY wiring work with the JB4 and make sure the red wire from the BT Dongle is connected to the 5 volt red wire within the main harness bundle and NOT the lone 12 volt red wire going to the battery rail. Support from BMS has been great and they even replied quickly to an email on a Saturday.

Any update on this? Literally ran into the same problem! Wondering if I should keep the jb4 or not. NOT dissing BMS or anything. The setup might just not be for me.

Thanks

[jgoens]

Originally Posted by Bigmo93

Any update on this? Literally ran into the same problem! Wondering if I should keep the jb4 or not. NOT dissing BMS or anything. The setup might just not be for me.

Thanks

You know looking at the response the guy got from Jon@bms it seems like the BT has to be connected to the right red wire or you get the faults like you have.

[anom3]

Just want to mention...

Jb4 for 1.5 months here.

Bt rev3 module for 2 weeks now.

No issues what so ever. Posi tapped the red harness cable for the 5v+ the way the the bt install pdf calls 'more stealth install method'.

Only code ever thrown by the jb4 was on first ever start after install. Didnt read it as it cleared right away after ignition cycle. Did pop up as drive train fault on idrove though. Most likely was the tune detect code.

[Bigmo93]

Originally Posted by jgoens

You know looking at the response the guy got from Jon@bms it seems like the BT has to be connected to the right red wire or you get the faults like you have.

Yup! That's what it sounds like. Kinda frustrating 😰

[anom3]

Well yea...

I mean this in the most un-aggresive way possible... But it clearly states the BT kit is 5V... The red wire you have connected to the + post of the vehicle is 12V.

That alone should be enough to make anyone stop and think things over.

[Bigmo93]

Originally Posted by anom3

Well yea...

I mean this in the most un-aggresive way possible... But it clearly states the BT kit is 5V... The red wire you have connected to the + post of the vehicle is 12V.

That alone should be enough to make anyone stop and think things over.

I'm offended!!!
Kidding, but yeah after looking at the instructions I admit it was 100% my fault and was clearly a install error.

[lens]

Originally Posted by anom3

Well yea...

I mean this in the most un-aggresive way possible... But it clearly states the BT kit is 5V... The red wire you have connected to the + post of the vehicle is 12V.

That alone should be enough to make anyone stop and think things over.

Actually kind of strange. Mine didn't come with a posi-tap but that metal fork, which I connected straight to the 12V rail without any problems.