Bluetooth troubleshooting? (slow refresh!) [mac]

[Chiburbian]

I had been using a 2006 MacBook Pro as my tuning laptop for the past year or two. I had great throughput via USB and Bluetooth to my EFIanalytics supplied bluetooth module. The other day I had the hard drive crash in the laptop and I decided rather than repair it I would finally retire it. I may bring it back later but with a cheap 60gig SSD drive because I think the vibrations killed the hard drive over time.

Anyhow, I got everything set up and paired on the new machine (Macbook Air 1.4ghz) and drove home yesterday while running TS. Immediately I noticed that my gauge refresh was abysmal. I am getting less than 10 refreshes per second, perhaps even as low as four. I can actually count the refreshes audibly they are that slow.

This is the third laptop (and fourth computer) I have used to tune with and the only one to experience any issues with data throughput. The laptop is running MacOS Mavericks but then again so is my desktop iMac that I use when bench testing, and I have never seen any throughput issues with that machine. Unfortunately I cannot locate my USB cable so I can't test USB versus bluetooth until later today when I drive home (at the earliest).

I am assuming that the bluetooth module is set up to communicate at the proper speeds because I haven't touched it or done anything to it and it worked fine with my previous laptop.

This is a fresh installation of Tunerstudio on a factory fresh computer. I already changed the communication speed testing in the menu bar to 115200 (or whatever that was). No effect. I also changed the refresh to 50:1, still no effect.

Any ideas?

[LT401Vette]

Is the same project working normally with a USB cable?

I did a search for OS x bluetooth lag
and found quite a few people having trouble with this, mostly with BT a key board or mouse.
Some of the solutions were related to turning WiFi off, removing other BT devices and turning off broadcasting.

[Chiburbian]

On previous computers no problem with USB cable.

I will try turning off WiFi and see what happens. No other bluetooth devices connected.

[Chiburbian]

Added edited debug file from this mornings startup and drive.]

Edit: Also updated Java to latest v.7 version...

[LT401Vette]

I see no errors in there, but it does look like all Comms is going quite slow going by the interrogation times.


Have you tried unpairing and repairing? That might set some setting back to default? I'm grasping.

[Chiburbian]

I notice in my list I have /dev.cu.EFIANALYTICS01 and /dev.tty.EFIANALYTICS01...

Which should I be using? Should I be using RS232 protocol?

[LT401Vette]

You can use either. OS X does that for USB too, it makes a cu and a tty.

Yes, RS232 is correct.

I'm thinking the trouble is related to something with the BT on the laptop itself, not hardware, but something. I am really no OS X expert though.

[Chiburbian]

I used a USB cable on the way home and while it wasn't as bad it still had intermittent pauses. Basically every 2-5 seconds it would seem to pause for a half second or so.

[LT401Vette]

I used a USB cable on the way home and while it wasn't as bad it still had intermittent pauses. Basically every 2-5 seconds it would seem to pause for a half second or so.

Now that is interesting... Does CPU usage seem reasonable?
I would be interested in seeing an Comm Debug.txt

[Chiburbian]

Where would I get this comm.debug?

A guy got hurt at work so I am doing overnights in his place. Should be driving to work soon. Going to stick with USB for now so it's somewhat useful.

[Chiburbian]

I found the menu option for comm debug. Let me know if this worked:

[LT401Vette]

Nope, no COMM debug info in that file, but there are a lot of protocol errors.
Those will slow things down a lot as TS will keep waiting and retrying.

[Chiburbian]

How do I get the comm debug info then? What could be causing the protocol errors?

[Chiburbian]

I think I have the comm stuff in there this time.

The file was 29MB! I had to cut a whole bunch of stuff out to make it fit.

[Chiburbian]

Please help? I don't know what the next step is.

[LT401Vette]

When you had Comm Debug turned on, it appears you were using the USB cable. It looks like you were getting 25 reads / second when VE Analyze wasn't running and appeared to be TS throttling it. But there are protocol errors periodically causing the pause.

While VE Analyze was running, the protocol errors are very frequent.

By the looks of these protocol errors, it seems for some reason the full request is not making it to the MS3 in tact. Interestingly, there dosen't seem to be errors for TS reading, the data seems to get to TS ok.

Do you have any other laptop to try, just to rule out a problem with the cable or MS?

[Chiburbian]

I'll try running on my spare laptop tonight but it worked fine a day earlier when my previous tuning laptop died. That machine worked fine with USB and Bluetooth.

[Chiburbian]

After work today I used my spare tuning laptop to connect to the MS while driving home.

It appears I am seeing the same problems I have seen on the NEW tuning laptop (Macbook Air).

Either way, I am returning the computer tomorrow and just buying an SSD for my MAIN tuning laptop which has been fine up until the past couple days. It is appearing that perhaps my problems are not related to the software or the cables/bluetooth but rather it's related to the MS3 itself. Once I have my MAIN tuning laptop up and running I will try again.

I will include my latest debug comm file tonight when the laptop is finished syncing with my server. (my tunes are backed up on server when I get home every night). I am almost certain I am seeing the exact same problem as before.

[LT401Vette]

Is there any difference using the USB port on the MS3 from the db9?

[Chiburbian]

That will be my next test. I am going to guess no considering that the Bluetooth plugs up to that port, but I have been wrong several times already. I need to find my cable and give it a try.