[Dmac @ BMS/DMD]

Originally Posted by Nugs

Downloaded the update and the issue of it randomly disconnecting is still there, in fact it rarely stays connected for more than a few minutes.

So far I have
-checked the connection of the usb cable with the JB4
-used two different lighter to USB adapters, and tried both of the lighter positions (armrest and ashtray).
Issue still happens.
Any tips on what I could try troubleshooting next?
Thanks.

At this point you'll need to test it on another device if you have access to one.

Originally Posted by volcom8190

can we get a checkbox to disable the warning after the first notice

Originally Posted by prelude2perfect

X2. I don't want to disable my wifi everytime I get into my car and it would be nice to just open the app and go

I actually debated adding that in before I submitted it to the App Store. I mean if you just REALLY don't want to turn wifi off, I'll add a toggle in the settings page on the next version. Expect the next version in 2-4 weeks.

[Dirty Dog]

Downloaded the latest version of the App on my Iphone 6 plus running the latest Apple iOS software and noticed that the Ignition gauge gets frozen on a set number until you press throttle. Tap the throttle and it changes to a different ignition degree and stays there. The Ignition value use to jump all over the place on previous version which I think is how it's suppose to be on the N54. Engine type is N54 E series.

[Dmac @ BMS/DMD]

Originally Posted by Dirty Dog

Downloaded the latest version of the App on my Iphone 6 plus running the latest Apple iOS software and noticed that the Ignition gauge gets frozen on a set number until you press throttle. Tap the throttle and it changes to a different ignition degree and stays there. The Ignition value use to jump all over the place on previous version which I think is how it's suppose to be on the N54. Engine type is N54 E series.

Are you either:

A) On map 0
B) Looking at Ign 2-6

[135isuff]

do u have the jb4 connect bluetooth kit for android in stock?

[Dmac @ BMS/DMD]

Originally Posted by 135isuff

do u have the jb4 connect bluetooth kit for android in stock?

I have a few left for now. Check the website for details.

Click Here!

[Ddang06]

Every time I launch the app I have to clear device history , it doesn't auto connect for some reason ? I had freezing using the app on my iPad mini , but deleting the app and downloading it again solved that issue .

[Dmac @ BMS/DMD]

Originally Posted by Ddang06

Every time I launch the app I have to clear device history , it doesn't auto connect for some reason ? I had freezing using the app on my iPad mini , but deleting the app and downloading it again solved that issue .

Please give me all of the info as requested in the first post.

[Spxxx]

Note 4
n54 e series
jb4 firmware for backend mhd flash

App will occasionally connext but usually gives me a serial port not available error.any testing done with the new firmware?

[The Die]

I'm showing them as out of stock. Any ETA on a restock?

[Spxxx]

Originally Posted by Spxxx

Note 4
n54 e series
jb4 firmware for backend mhd flash

App will occasionally connext but usually gives me a serial port not available error.any testing done with the new firmware?

Connects to my windows version as I had to flash the firmware a few times... Mobile app is the version causing issues

[Dmac @ BMS/DMD]

Originally Posted by Spxxx

Note 4
n54 e series
jb4 firmware for backend mhd flash

App will occasionally connext but usually gives me a serial port not available error.any testing done with the new firmware?

1) What's different about the JB4 firmware for use with MHD? That shouldn't make a difference at all.

2) These serial port not available issues are virtually always either a poor quality OTG cable or an issue with the user's device. You see that error because the OS is telling my app that it doesn't see a serial port.

[Spxxx]

Originally Posted by dmacpro91

1) What's different about the JB4 firmware for use with MHD? That shouldn't make a difference at all.

2) These serial port not available issues are virtually always either a poor quality OTG cable or an issue with the user's device. You see that error because the OS is telling my app that it doesn't see a serial port.

The flash firmware allows for fully passiveness of the jb4 for running standalone flash tunes or for using just the jb for gauges. Terre said there is no difference in the way the jb connects to the software (I thought he responded in this thread but I don't see his post anymore)

Tried 3 different otg cables and examined the jb4 USB wire for issues and all checked the board for bad connections to the USB port.

The device recognizes that there is an otg cable plugged in and the otg cable works fine when flashing through the MHD app from my same phone.

[Dmac @ BMS/DMD]

Originally Posted by Spxxx

The flash firmware allows for fully passiveness of the jb4 for running standalone flash tunes or for using just the jb for gauges. Terre said there is no difference in the way the jb connects to the software (I thought he responded in this thread but I don't see his post anymore)

Tried 3 different otg cables and examined the jb4 USB wire for issues and all checked the board for bad connections to the USB port.

The device recognizes that there is an otg cable plugged in and the otg cable works fine when flashing through the MHD app from my same phone.

Well apparently FTDI just recently released an update for their D2XX driver (http://www.ftdichip.com/Drivers/D2XX.htm). I'll include that in the next update and we'll see if that fixes anything.

[Dmac @ BMS/DMD]

Originally Posted by Spxxx

The flash firmware allows for fully passiveness of the jb4 for running standalone flash tunes or for using just the jb for gauges. Terre said there is no difference in the way the jb connects to the software (I thought he responded in this thread but I don't see his post anymore)

Tried 3 different otg cables and examined the jb4 USB wire for issues and all checked the board for bad connections to the USB port.

The device recognizes that there is an otg cable plugged in and the otg cable works fine when flashing through the MHD app from my same phone.

Just saw your posts on the other thread. So are you saying that you're now having trouble connecting to the Windows interface as well?

[Spxxx]

Yep, disregard my earlier comments... It was a hardware issue.

[Dmac @ BMS/DMD]

Originally Posted by Spxxx

Yep, disregard my earlier comments... It was a hardware issue.

Thanks, that confirmed my suspicions. I'll provide a better error message so people can try to better diagnose these issues themselves. Let me know when you get your new JB4 data cable.

[135isuff]

Hi DMAC, was about to order your bluetooth kit but says out of stock, but on this thread it says in stock and that stock status would be listed here. I know answering this question must b annoyin but if you could please I want to order it but be nice to get it soon

[The Die]

Originally Posted by 135isuff

Hi DMAC, was about to order your bluetooth kit but says out of stock, but on this thread it says in stock and that stock status would be listed here. I know answering this question must b annoyin but if you could please I want to order it but be nice to get it soon

Same here!

[Dmac @ BMS/DMD]

Originally Posted by 135isuff

Hi DMAC, was about to order your bluetooth kit but says out of stock, but on this thread it says in stock and that stock status would be listed here. I know answering this question must b annoyin but if you could please I want to order it but be nice to get it soon

Originally Posted by The Die

Same here!

Sold the last ones while I was asleep. I'll update this thread when I receive more parts. Sorry guys!

[prelude2perfect]

Device: Iphone 5s
OS: 8.1.2
Engine type: N54 E Series
App build: not sure where to find this but the app version is 2.1
Problem experienced: Sometimes when I open the app it will give me a message stating something about it not being able to find my saved bluetooth device. It's a simple fix by going in to settings and clearing the saved device so it can relearn it and works fine afterwards. It happens maybe once every 25 connects or so.

[Dmac @ BMS/DMD]

Originally Posted by prelude2perfect

Device: Iphone 5s
OS: 8.1.2
Engine type: N54 E Series
App build: not sure where to find this but the app version is 2.1
Problem experienced: Sometimes when I open the app it will give me a message stating something about it not being able to find my saved bluetooth device. It's a simple fix by going in to settings and clearing the saved device so it can relearn it and works fine afterwards. It happens maybe once every 25 connects or so.

Strange that you're experiencing that on 8.1.2. The way Apple handles the UUIDs for bluetooth devices means an app never sees the actual mac address. The UUIDs for these devices are *supposed* to be static inside each app, but it looks like that functionality isn't working properly. I'm going to be posting an update soon to address this. Basically in the next update, if it can't find your saved device, it will ask you if you want to connect to the nearest one. If you click yes, it will connect and that will be your new saved device.

[Peter @ Pure]

FYI I had that can't connect to saved device as well 1st time today. IOS 8.1.2 with latest JB4 mobile.

[ba114]

Originally Posted by dmacpro91

iOS or Android? Also, the 0-60 capability seems to be much less accurate on Android. I'm actually debating removing the feature entirely. Ideally if we could get the speed reading through the JB4 (on the other engine types not just the N54), we could have quite accurate 0-60 timing. The GPS refresh rate on mobile devices just isn't that great. I still want to look into some Bluetooth GPS devices, but that has been low on my priority list lately.

Couldnt you force users to set FUD = '4' they want to use timing features?
Would presumably be able to offer a whole wealth of other timing features then too such as 60-130 etc.

Only see this causing issues when users dont get traction.

[ac305]

Hi guys,

Could use some insight. I read the following codes yesterday from the JB4 mobile app:

102001 - Air Mass, plausibility -- tuner code, ignore
102A22 - No Description found

I sent them in to the BMS guys and they were unable to identify the codes, presumably due to the numbering convention used by the App. It appears that fault code numbering is standardized. The way are presented above by the mobile app does not align with that convention and I unfortunately don't have a BT cable.

Any idea what these codes translate to? As background, I had a Map 4 switch due to running lean (temporarily increased the failsafe running E85) and decided to see if there were any codes. I only spotted these after 'reading codes' immediately after a long pull. Shortly after, codes were gone (presumably erased by the JB4) and car ran fine after failsafe was lowered back down. Can I ignore these codes? The boards seem to indicate that codes that go away are not indicative of a real problem.

[Dmac @ BMS/DMD]

Originally Posted by ac305

Hi guys,

Could use some insight. I read the following codes yesterday from the JB4 mobile app:

102001 - Air Mass, plausibility -- tuner code, ignore
102A22 - No Description found

I sent them in to the BMS guys and they were unable to identify the codes, presumably due to the numbering convention used by the App. It appears that fault code numbering is standardized. The way are presented above by the mobile app does not align with that convention and I unfortunately don't have a BT cable.

Any idea what these codes translate to? As background, I had a Map 4 switch due to running lean (temporarily increased the failsafe running E85) and decided to see if there were any codes. I only spotted these after 'reading codes' immediately after a long pull. Shortly after, codes were gone (presumably erased by the JB4) and car ran fine after failsafe was lowered back down. Can I ignore these codes? The boards seem to indicate that codes that go away are not indicative of a real problem.

Please refer to the first post for info regarding support requests.