OBD Fusion Dashboard Swappin' Thread

Since this thread is active I'll ask here: what kind of sampling rates are you guys getting with your logging and what obd adapter are you using? I've just tried an innova brand one that I borrowed from a local and it wasn't compatible with obd fusion but it also has a really low sampling rate of about 3-5Hz. Wondering if it's just inferior for data capture it if that is typical for this ECU/obd2 protocol. Thanks for any info

 

I’m still trying to figure this out myself. At one point I had pretty quick sampling. I’ve been thinking about doing some testing. I have about six dashboards, but I don’t know if it’s polling for all of them. When I log, it appears that I get about 0.3-0.5 Hz. But I have 15 PIDs.

There are differences in adaptspers though. I’ve been happy with my kiwi3.

 

You get less than one data point per second? Like one every two seconds? What dongle do you use? How much faster does it get with fewer parameters? Have you tried with only 3 or 4?

 

That’s what I’m thinking of testing. But yes, I’m only updating every second or so. Would love to find out I’m missing something. I did have a fast poll at one point, but after scanning additional networks it really slowed down. There really isn’t a lot of forum support fore these apps, here or elsewhere.

 

Anyone got updated instructions to importing dashboards?

version 5.15.0.1223

 

Let me sniff around a little.

 

Seems to work the same as before: Settings | Menu | Import Settings | Select Dropbox

 

You have to have a Dropbox account and a sub folder called import

 

Ah... if it’s a first time setup, see the first post. There’s some info there about how to setup.

 

Had to install the Taco extras first. Got it now.

 

Thanks for your info here. It was very helpful getting logs from a guy that is having some vibration issues.

 

Out of curiosity, what was the frequency of data logging, and when you look at the logs, what was the frequency of updates? They are not the same.

 

Yeah. That was problematic. On both my ancient 7yr old adapter and the guy's new VeePeak BT 4.0 adapter, the fastest that we got was a pathetic 1/sec. We were trying to diagnose an estimated 10hz vibration. Both adapters did not puke when we tried the higher data rate settings, but the logs were still 1/sec.


Regardless, getting a dashboard set up easily for this new user and getting info out, it was very helpful. We were also able to visually monitor the SLU and TC Locked states in person, which I believe was enough to rule out a TC issue.

The problem is that we are now stumped. Tried a few good suggestions like needle bearing diag, deleting SLU, and a few other things. Either no change to the vibes or made them intolerably worse. Fully stock 2021 that I'm leaning in on a bad MAF or ETB. I've seen a few other post about this Stutter / Rumble Strip vibration on 2021s.

Considering these are about 6sec to 7sec slices, that is just fucked:

 

Try this: generate a dashboard that *only* has the items you want to log. Even if you are only logging 3 of 10 dashboard items, the refresh rate is a function of how many PIDs are on the dashboard.

What about OV logging? Or Techstream. .

 

PS. There are OBDFusion settings for logging and refresh frequencies.

 

Great tip! I didn't know that.

I got crossed up with the Fusion thing and vF not having the TC PIDs, so TS was completely forgotten until I was leaving. Just a brain fart. But, the log posted above was from vF. It is logging at about 10hz. That was Version 1.2.9.9.4. 1.2.9.9.5 dropped when I got home that day.

 

Yes. We both tried the fast logging option. While it didn't freak out, it didn't log any faster either. We were using a lot of PIDs like you noted in your last post.

Thankfully, even my older adapter didn't choke.

 

If that was 10hz, I don’t think OBDFusion is going to match that. Even with low dash widget counts.

 

It’s an ask-receive system. So you can have as many widgets as you want. It just slows down the total refresh rate.

 

The adapter likely sees the same amount of traffic no matter how many widgets. The software just cycles through the existing widgets (PIDs) and asks for the next once it gets the last answer. At least that’s my understanding of how it collects.