• Click HERE to ask your JB4 Question!
  • Car enthusiast? Join us on Cars Connected! iOS | Android | Desktop

3.3T New Install Log Check - Map 1

I know how frustrating this process is but I have been through it and is the "price of admission".......not fun by no means but once you get it figured out, the satisfaction of knowing you figure it out will be priceless......
 
That one is fairly simple to remedy. Just unplug it and connect the wiring harness connectors back. No need to fully remove the jb4 but may want to make sure connectors/wiring are not in harm's way. Of course, no logging but I didn't see anything in the one you provided to say something major is wrong.

See how things run without the jb4 and you will know if it is contributing. Is the CEL clear? With that code, if the issue is correctable by the ecu, it will clear on it's own.

I cleared the code with the JB4 and let the car just run in my garage for 5 minutes and it didnt come back. But I would not expect it to without the car moving.

That is a good idea to just unplug everything and try it out. Would unplugging the OBD be sufficient for that? I would expect it is drawing power from the OBD, so if the OBD is unplugged, there would be now way for the unit to do anything.
 
Unplug the all the JB4 connections. Run from stock and see if the code comes back.
 
______________________________
Unplug the all the JB4 connections. Run from stock and see if the code comes back.
I am wondering if it is worth trying to run with everything connected tomorrow on map 0 tomorrow and seeing if it comes back when everything is dry.

I am surprised that there doesnt appear to be more instances of this fault. I have only been able to find a couple instances on here or the N54 forum. No one seems to really know what this fault is. The other instances from last year were related to JB4 and the mobile app version. They were fixed when they updated version/firmware. I checked and I am on the latest versions. I had to update when I first connected the unit.

One instance appeared to be fuel related, which is concerning to me a little bit because that would mean I am 0-2 with fuel since installing JB4. Even after attempting to find 'good' fuel. When I filled up on Friday there were 3 GTRs, a Supra and a modified S2k and 350z. So I felt good at that gas station if that is their usual spot.
 
Unplug the all the JB4 connections. Run from stock and see if the code comes back.
As stated, unplug the jb4 connectors in the engine bay as @ChaneRZ stated ( I may not have been clear enough)....lol.

Unplug the OBD2 as well. This way, the car will be TOTALLY stock and you can eliminate the jb4 altogether. If you still get issues after this, then it will be time to start working on the intakes or anything else you may have added.

As I said earlier, this not the fun part of troubleshooting but a necessary part.
 
From interior to exterior to high performance - everything you need for your Stinger awaits you...
Sure. Try running on map0. Code returns, disconnect them all. Go from there…
 
Thanks guys! I will try to report tomorrow. Hopefully it will work enough to get my kiddo to swim lessons.

I am cautiously optimistic that it will work, just because I think this was kind of a freak event, and I was running map 0. I was under the impression map 0 was JB4 disabled.

I will reach out to the support team at Burger as well and see if they have any ideas.
 
Thanks guys! I will try to report tomorrow. Hopefully it will work enough to get my kiddo to swim lessons.

I am cautiously optimistic that it will work, just because I think this was kind of a freak event, and I was running map 0. I was under the impression map 0 was JB4 disabled.

I will reach out to the support team at Burger as well and see if they have any ideas.
Do you still have the stock air boxes and filters. If removing the JB4 doesn’t work then I would put those stock boxes back in and take it back to as close to stock as possible. Then perhaps take it in for service if it is still throwing codes.
 
I wanted to post an update now that it has been a week. I have been in contact with Terry and another guy from Burger Motorsports. We are not sure what was causing the CEL. Terry mentioned he has only seen the fault occur due to the bluetooth module. I did not have any issues since the one occurrence. At this point I will have to chalk it up to a one off instance. I will post again if it does pop back up.

Terry also took a look at my logs. I now have logs from 3 different gas stations and all appear to be pulling similar amount of timing. I unplugged the battery at some point with each tank as well to reset timing. His recommendation is that it is perfectly safe to run map 1. In the future I can explore an E30 blend and attempt map 2 or map 3. I might give this a try at some point, but for now I will keep it in map 1 and fill at top tier stations.

I did take the car on a 600 mile round trip this past weekend and it was great. I kept it in Eco for the drive and got almost 30 mpg which was pleasantly surprising.

Also, last week I did gap a Jeep Grand Cherokee SRT (NOT trackhawk) pretty nicely. I was planning on moderately accelerating, so he got the hit and never got more than a nose ahead of me before I gapped him by a couple cars. At the next light I was completely stopped and he decided to roll through at 20+ mph and I slowly reeled him back in.
 
That’s good to hear. Ethanol is highly addictive haha.
 
From interior to exterior to high performance - everything you need for your Stinger awaits you...
Back
Top