Otherwise, the app works well on even ancient Android devices and Android versions eg Samsung SGSi900 for example.
Of course Btssm also works with BT connection using specific BT OBDII plugs as discussed on the Btssm website: http://www.btssm.com. ... However the Bluetooth data rate is much slower than with the more affordable Vagcom KKL 409.1 usb obdii interface…
Introducing the BtSsm, an app that utilizes SSM K-line data on your BlueTooth or OTG capable Android device.
Yes you will require both the btSsm app AND the btSsm OBDII adapter for BlueTooth wireless logging on your Android device. (Because ELM327 adapters are incompatible with the SSM protocol.)
Or the btSsm app and either a Tactrix 2.0 or kkl USB2 cable for wired logging via Android OTG. (if your device is compatible with OTG)
Recent updates to btSsm have massively increased the versatility of the app and the potential customer base. The app is now comptible with the Tactrix and kkl cables via usb2 OTG and the btSsm plug can be used with a laptop for RomRaider logging via BlueTooth virtual ports.
This app bridges the gap between ELM327 BlueTooth devices and their apps, and laptop PC logging using a Tactrix. The speed of the logging has been confirmed to be on par with a Tactrix, and far better than a Tactrix in standalone logging mode. Logging is super convenient, and the rear defroster button can optionally be used to start and stop logging.
A key feature of BtSsm is the "Learned Values" output, effectively being able to obtain an LV and email it without having to resort to using a laptop or having to settle for much slower standalone Tactrix logging.
Whether logging or not, users can display high quality gauges or values, displaying their cars vital statistics.
The device can be left plugged in the car if the car is used weekly, the adapter uses about 6mA when the car is off. The OBDII socket has constant power so if the car is not used weekly, simply remove the btSsm to preserve your battery voltage.
Please subscribe this topic to stay in the loop regarding BtSsm
That's an actual BtSsm screenshot attached above, my dashboard. Of course the gauges can be resized and moved to your preference, see below for a demo video from the developer. Given progress so far I'm sure there are more, very useful features on the way.
BtSsm features change log: the V1.0.1: Displays realtime data on your Android phone/tablet using the SSM protocol (which gets the good Subaru-specific data) Logs the above data, which can then be emailed/shared/etc Allows you to place and resize gauges of your choice on the display Monitors for knock events (when app is running), and captures all of your selected fields at that point in time (great for tweaking timing tables) Shows you Learned Values that your ECU is applying to fuel/timing, as well as the current IAM value Since this uses the SSM protocol in continuous-push mode, the logging rate is much better than "generic OBD2" solutions
V1.0.2: added a Record button for logging (in addition to supporting car's rear-defrost button) logging mode will no longer suppress display of real-time data added a couple of fueling fields minor enhancements
V1.0.3: Graphing of logs added to the app itself. added reset to min/max values (thanks snow05gtRI!). Just long-press the min or max column, and the values will reset. logging when rear defrost button is on is now an OPTION...
V1.0.4: Error code retrieval feature has just been added to BtSsm On the main menu click "Codes".
V1.0.9: added option to auto-hide ActionBar changed background of gauge area from dark gray to black added metric unit support added to settings: "snap-to-grid" gauge movement added to log graph: share button miscellaneous enhancements
V1.1.0: added speed correction option in settings (affects only BtSsm app) when sharing LV, it is now an image rather than text (improved appearance) renamed VVT fields to include "int" or "exh" as needed
V1.1.1: To protect gauges from inadvertent movement, a long-press is now needed to move them (please let me know if you'd like to see this become an option - for now, it's the new behavior) expanded model-year coverage to 2009 revised existing LGT-style gauge appearance.
BT Virtual Com Port Logging: use your BtSsm adapter to do RomRaider logging from your laptop (provided that your laptop has bluetooth support, which can usually be added if it doesn't have it already). You need to create an outgoing BT connection from your laptop, pair it with your BtSsm device, assign a virtual com port, then you should be able to use that com port in RR.
V1.1.2: Adapter price drop to USD$100 new feature: throttle-triggered logging via long press of rec button (suggested by snow05gtRI) enhancement: added Car/ECU info to LV (suggested by xt2005bonbon) enhanced appearance of LV append log filenames with "_knock" when a knock is detected during a log (suggested by snow05gtRI) enhanced knock notification logic (bug found by xt2005bonbon) added field VVT-Exhaust to ADM 2.0 GT (suggested by bigBADbenny)
V1.1.3: Added widgets for 0-60mph and 0-100kmh. Located at bottom of field list. Added field for Fuel pump duty cycle (%). Located in field list. Field "Fuel Learn (%)" is now based on a higher resolution value Formatting enhancements when sharing an LV Also made it an option to have the recently added "glow" effect to the gauges (since it seems as though it doesn't display properly on some devices. Located in "Settings/Gauge glow effect")
V1.1.4: updated to be compatible with Android 5 (Lollipop) updated to support 2002+ WRX with 16-bit ecu bug fixed where sometimes switching vehicles could reset field selections (discovered by xt2005bonbon)
V1.1.5: now optionally supports wired ecu connection (pyro, fibble) wiring: android device->*usb/otg adapter->*kkl cable->obd port (*=additional hardware reqd) to enable, go to Settings/ECU interface, select as appropriate LV images are now retained in a list for review like logs (xt2005bonbon) added multiselect to logs dialog for delete/share (fibble) also added multiselect to new LV list bug fix for new android version 5.0.1 (xt2005bonbon)
V1.1.6: A bug was fixed for certain devices using android 5.0.1 Also included is a new feature to allow custom ecu firmware in some cases. Before the app would just say "Unsupported ECU found. ID=xxxx" and close. The new feature offers a new button "Create Alias" that, if clicked, will ask you to "Enter original ECU ID for alias". Entering that will use that ECU ID instead going forward. Note that this only works if the custom ecu firmware has all the same address mapping as the original firmware.
V1.1.7: added a hands-free feature if touch screen not avail: key-on, engine-off, floor throttle for LV. Floor again to close attempt to handle OTG cable made by winchiphead
V1.1.8: new: multiple car profiles can be created for same ecu id (jif) (click car/select a profile/click new) new: now supports multi-windows for samsung devices having it (djpast) enhancement: preserves gauge stacking order/z-axis (bigBADbenny) enhancement: saves gauge layout after gauges are moved, rather than in other app events enhancement: added green WRX gauge (djpast)
V1.1.9: bug fix: speed widgets not rendering on android v5.0.1+ (Hardware BoB) bug fix: more than one speed widget selected would cause crash (Hardware BoB) fix attempt for isolated logging bug (satogixxer) slight tweak to recent support of ch340-based kkl usb cable
V1.2.0: new feature: supports Tactrix OP 2.0 USB cable w/OTG adapter (you can check if your Android device supports OTG with this free app) new feature: alerts can be set for each field - when value becomes greater/less than x, a dialog will display and notification will sound (xt2005bonbon)
V1.2.1: added field "Throttle Pedal (%)" (Hardware BoB) added more vehicle definitions added #ynansb to a couple error codes (MrTris)
V1.2.2: added field "Throttle Pedal (%)" (Hardware BoB) added more vehicle definitions added #ynansb to a couple error codes (MrTris)
V1.2.9: new feature: added backup/restore for vehicles/fields/gauges for all profiles. In Settings, see Backup & Restore fix: IAM gauge for 16 bit ECUs had incorrect range (djpast)
V1.3.0:
for 6 cyl vehicles: added misfire fields for cyl5 and cyl6 (Perscitus) bug fix: new backup feature could say "backup failed" (bigBADbenny)
V1.3.1:
new feature: added digital gauge option. to access, tap field name in field chooser, choose gauge type (djpast) bug fix: occasionally a small log file would get created when vehicle turned off but app still connected (djpast)
V1.3.4:
changed recent field alert feature to play an alarm sound and change gauge color to red, as popup was too disruptive (djpast, xt2005bonbon) enhancement for H6 vehicles: LV will contain 2nd row for fuel correction that represents bank 2 (Perscitus, satogixxer) bug fix: FKC and FLKC gauges (both analog/digital) now display decimals (xt2005bonbon) More info on alarms settings.
For the latest developments check the btSsm thread on LGT (link below).
Last edited by bigBADbenny on Sat Jan 07, 2023 2:29 pm, edited 55 times in total.
My current setup, for the MY03-07 low res C1 nav disc OEM navigation is:
$20 clear blue case local eBay vendor VagCom with USB A plug > $25 BtSsm app hosted on $60 TX2 Android TV box (no power button, 3.5mm composite video and audio out) > 4 pole 3.5mm to RCA adaptor > RCA lead (shielded) > rear of stock nav.
I can also split the TV box audio via an adapter to my Grom BT3 3.5mm stereo input, but this need a ground loop isolator added.
For setup and transferring log files, I use a laptop with dropbox, a second android tablet, and the Dropsync app on my in-car TV box to synchronise the Btssm folder.
This means I can tweak my setup at home, view logs and LV's on my laptop, and sync it all to and from the car, automatically or manually.
or
btSsm > BT > Android mini PC w/ HDMI out > ebay HDMI to AV video converter > Nav screen AV video input (on rear of screen unit). Need one or the other nav hacks to use it on the move, at your own risk...
or
btSsm > BT > Android Phone w/ HDMI out > ebay HDMI to AV video converter > Nav screen AV video input (on rear of screen unit). Need one or the other nav hacks to use it on the move, at your own risk...
For the latter two a mini keyboard/trackpad will be needed for control.
or
btSsm > BT > Android SGS i9000 in tv-out mode > DIY i9000 headphone adapter (different pinout to the usual... see below) > Nav screen AV video input (on rear of screen unit). Need one or the other nav hacks to use it on the move, at your own risk...
Screen Shot 2014-11-26 at 6.58.42 pm.jpg (31.35 KiB) Viewed 33999 times
Here's a BOM from a working install that was parted out: Nexus 7 tablet rooted with Timur's USB ROM already mounted to a JDM 7" sat nav bezel with associated hardware, Cubby clock relocation kit (Rev A-C for pre FL ref D-F for post-FL) OTG Y-Cable, DCDC USB mini box power supply, 4 port USB 2.0 hub, Behringer UCA-202, 2ch RCA cable, Paid apps: Poweramp pro music player, Tasker, Sygic offline navigation with traffic updates, Tasker, Greenify, Titanium Backup, BtSsm... Optional: wired or wireless reverse cam...
I suppose the benefit of the i9000 is a sim card for mobile data, plus a battery for standby power... but these units are ancient and can barely use eg the btSsm graphing function. I have the i9000 currently but might upgrade to android mini pc soon or a newer Android phone.
I get the feeling that HDMI to AV video option might provide a slightly crisper display on the low res Nav screen... (?)
Long term my plan is to have btSsm working with automatic LV and log uploads, plus GPS tracking with logging and security functions enabled.
Last edited by bigBADbenny on Fri Jan 17, 2020 8:46 pm, edited 8 times in total.
Yes it requires the btSsm obdii to BT adaptor. (Bt elm327 is incompatible with ssm protocol) New: adapter price drop to USD$99 plus post, exhaust vvt field for adm prefl gt, auto logging options etc...
Do you require a special definition for your Tactrix? Edit: it's being discussed on LGT see link above. An ecu labs user is planning to get one when his motor is built...