PSA: BtSsm OBDII Gauges, Logging & LV for Android devices

[Daemos]

I can't be bothered on a $10 vagcom cable haha...

I will just install a USB extension and unplug and plug back in...wonder if there are any good condition nexus 7s still available.

*edit*

well I just tried it in the car, it's super intermittent and cuts out all the time requiring the vagcom to be unplugged and plugged back in.

I think it's RIP Nexus 7

[JohnSub2013STI]

Bumping this

Device: OBDLink MX+ r3.1 Firmware: STN2255 v5.8.0 [2022.11.16]
Device: Samsung Galaxy S22 latest's version on android
Mfr: OBD Solutions LLC Serial #: 225510380364 BL
Ver: 3.6 IC ID/Rev: 0x0210, 0x1BC8, 0x4003 BT
Modem: BT24H, R15, 200915E_Scantool, 00043E5A4A15, 001F00 BT



Does anyone ever get random bad lines of data logging? (Using MX+ over Bluetooth)
&& If so, how do I fix it

I've tried using an OP2.0 and it doesn't return the bad lines

Eg : Target boost 10000000, AFR 300

[bigBADbenny]

Have you tried your Btssm app connection settings options?

Bt is convenient but usb/otg has a much faster data rate.

Also read up on hardware compatibility in the Btssm online manual?

[JohnSub2013STI]

I've tried a OP2.0 and don't have the issue with it. But the Bluetooth is so much safer considering I use the logger every time I drive.

I actually get faster rates with the MX+ though ~50ms. What do you get with OP2.0 ?

& Yes have read everything there is to read on there site

[bigBADbenny]

Share your datalogs from both the tactrix and obdlink here?

My vagcom data rate is around 10 samples per second, with 80% parameter load.

Maybe try Perscitus on LGT forum, for advice?
https://www.legacygt.com/topic/132039-f ... er-models/

Correct hardware rev?

Prerequisite: to use CAN mode with MX adapter: check label for hardware rev, only 2.2/R4 or higher will work. Otherwise contact scantool.net for new model

[JohnSub2013STI]

Here's the MX +
https://datazap.me/u/johnsub2013sti/log ... ata=2-8-18

If you click on fuel learn you can see the spike to 300 (which is the bad data

Here is the OP2.0
https://datazap.me/u/johnsub2013sti/log ... &data=2-18

I might have been mistaken about the read rates. For these logs I was 17 samples a second on the MX+ and 20 samples a second on the OP2.0

I will check the hardware rev at lunch. I'm pretty sure I have an up-to-date model though.
I talked with the dev and he said he could implement a data check to filter out bad lines. (If theres ever an update)

As far as why the issue is happening who knows. I did a reinstall of BTssm and the issue seems less frequent now. But i might even chalk it up to the fact that its been warm outside. This issue is weird.

Appreciate the feedback

[bigBADbenny]

Gotcha, I’ll take a look and get back…

[bigBADbenny]

Yes that looks inconsistent between parameters, but the dataset is far to short to make any further comment possible, apart from saying some values drop, others rise and some eg time stay the same.

You might also connect the obdlink bt plug to Romraider logger to isolate the issue to the plug or the software?