Let me rephrase.
I did reprogram a key.
My car is an Alfa Romeo Giulia, and “luckily” programming keys is rather straightforward given an interface supporting proprietary CAN protocols and adequate software (the AlfaOBD Android app, in my case).
“Luckily” because my car also has a “feature”: the CAN bus can be accessed by unscrewing the front radar. Thieves know this, program a key and steal the car in 5 minutes. Maybe this is the reason for the great drop of key prices on AliExpress lately, they really come “at a steal”.
As an aside, sourcing the key from the official network costs €350, I paid about €90 for mine on Aliexpress. Programming costs €50, more than the license for the software.
I’m guessing not the 105 Is yours one of the 2015 models? Just curious. I grew up with old car restoration guys (I was the ‘pass the wrench guy’). I’d love to find a 1960s Giulia to restore.
105s do not have electronic keys. It’s a 952, model year 2016. If you have the room and the time, that would be a great and highly rewarding activity.
The time is probably going to be available when I’m not longer able I helped work on an AC Cobra
File:Shelby Cobra 427 (539467867).jpg - Wikipedia many years ago and my second fave after that was the GTC Spider:
File:1966 Alfa Romeo Giulia GTC Spider front.jpg - Wikipedia
I have to admit, with the amount of software work I’ve piled up, It’s not looking like I’ll get to this before I’m too old to do the lifting.
I have the KONNWEI OBDII Diagnosegerät KW902 Android Bluetooth Auto Diagnostic Scan Werkzeug ELM327 OBD2 V1.5.
It was working with the 32bit-Version on my old Sony X Compact with OBDFish | OpenRepos.net — Community Repository System
The 64Bit-Version of OBD-Fish (OBDFish (Fork) | OpenRepos.net — Community Repository System) crashes on my XZ2 Comapct (64Bit SFOS) when enabling the BT-Connection to the ELM327-Device.
Addendum:
I recovered a new 64Bit-Build here and will test ist:
https://openrepos.net/content/kan/obdfish-aarch64
The comments say “Installing qt5-qtconnectivity-qtbluetooth fixed it”. I will try it.
A bit confusing to have several releases.
You do not need to connect bluetooth before connecting via OBDFish. Once paired, use OBDFish straightforward.
Once paired! I can’t pair, it disconnecting after try to connect. OBDFish says “Connect error” in this way, when i tap on OBDII device in the list of devices available in OBDFish.
Should you cannot pair it, this is not OBDFish issue but Bluetooth itself.
Did you try plain Bluetooth pairing BEFORE you added udev rules? Just trying to understand the steps you took?
Yep, sure, i tried before. But disconnect after 2 sec of connect too. But i didn’t do it in Terminal, so i don’t know now the log of error.
Why RFCOMM TTY can’t create, can you help?
hmmm. I don’t know how I can help without the device. I always have a number of generations of SFOS around (3.4, 4.4, 4.5) on different devices for testing.
The only thing I can suggest is to try logging while pairing. Either doing logcat or following the systemd logs. For instance:
/usr/libexec/droid-hybris/system/bin/logcat > $MYHOME/sailfish-logs.txt
It’s a verbose log. maybe: Collect logs for a specific systemd unit journalctl -u <unitname>
and or look here: Collect Bluetooth Logs | Sailfish OS Documentation
OBDFish offers logging functionality, which can be enabled in the ‘Options’ menu. The log file is saved to:
$HOME/Documents/obd_log.txt
Good day. I have installed Obdfish app from Aurora OS and now it tries to connect to adapter! And as other man with working combination of OS-Obdfish-ELM327 adapter said - Adapter don’t need to connect via BT in Sailfish OS settings. It need to be connected from Obdfish app only. Here we go)
But… On 1/11 stage it fails with next error:
[defaultuser@XperiaXA2-DualSIM ~]$ org.harbour.obdfish
[D] unknown:0 - Profile registered
[D] unknown:0 - Using Wayland-EGL
[D] onStatusChanged:51 - sGetPIDsPage1
[D] onStatusChanged:52 - sGetPIDsPage2
[D] onStatusChanged:53 - sGetPIDsPage3
[D] onCompleted:53 - Manager operational: false
[W] unknown:419 - file:///usr/share/org.harbour.obdfish/
qml/pages/MainPage.qml:419: TypeError: Cannot read prope
rty ‘discovering’ of null
[W] unknown:433 - file:///usr/share/org.harbour.obdfish/
qml/pages/MainPage.qml:433: TypeError: Cannot read prope
rty ‘discovering’ of null
[W] unknown:445 - file:///usr/share/org.harbour.obdfish/
qml/pages/MainPage.qml:445: TypeError: Cannot read prope
rty ‘discovering’ of null
[D] expression for onOperationalChanged:58 - Manager ope
rational2: true
[D] unknown:0 - Connect “OBDII” QMap()
[D] fncStartCommand:86 - fncStartCommand, sCommand: ATZ
[D] fncStartCommand:103 - fncStartCommand, sPID: ATZ
[D] unknown:0 - Writing: “41545a0d”
[D] unknown:0 - Write returned: 4
[D] unknown:0 - Entering readData…
[D] unknown:0 - Data size: 1
[D] unknown:0 - Data[ 46 ]: “7d”
[D] unknown:0 - Text: “}”
[D] fncGetData:144 - fncGetData, sReceiveBuffer: }
[D] unknown:0 - Entering readData…
[D] unknown:0 - Data size: 1
[D] unknown:0 - Data[ 46 ]: “54”
[D] unknown:0 - Text: “T”
[D] fncGetData:144 - fncGetData, sReceiveBuffer: }T
[D] unknown:0 - Entering readData…
[D] unknown:0 - Data size: 1
[D] unknown:0 - Data[ 46 ]: “5a”
[D] unknown:0 - Text: “Z”
[D] fncGetData:144 - fncGetData, sReceiveBuffer: }TZ
[D] unknown:0 - Entering readData…
[D] unknown:0 - Data size: 1
[D] unknown:0 - Data[ 46 ]: “8d”
[D] unknown:0 - Text: “\x8D”
[D] fncGetData:144 - fncGetData, sReceiveBuffer: }TZ�
[W] unknown:379 - file:///usr/share/org.harbour.obdfish/
qml/pages/MainPage.qml:379: Error: Cannot assign to non-
existent property “id_GlassItem_Reddimmed”
[W] Unknown:379 - file:///usr/share/org.harbour.obdfish/
qml/pages/MainPage.qml:379: Error: Cannot assign to non-
existent property “id_GlassItem_Reddimmed”
… Repeats 20 times…
…
[W] unknown:379 - file:///usr/share/org.harbour.obdfish/
qml/pages/MainPage.qml:379: Error: Cannot assign to non-
existent property “id_GlassItem_Reddimmed”
[D] unknown:0 - Disconnect “OBDII”
Who knows what else to do?..
ELM327 is sometimes ELM327. Sometimes it is just crap.My second adapter worked flawlessly on my Saab.
It also depends on the version. v1.5 works fine with old cars, while v2.1 is required for the newer. Between €12 and €4 ELM327 from China, I did not found crap but different version and surprisingly the cheaper was the newer. Why? The manufacturing not only of the PCB but also the enclosure united to the production volume. Customization or extension, might also play a role.
Yea, i know, there are different ELM327’s. But this adapter successfully connects on android phones, on different auto’s. But not on Sailfish. … Eh.
For those are interested in seeing a smartphone running SFOS as a diagnostic tool for OBD2 readers, they can check this website linked below. It is a Chinese automotive ODB2 diagnostic tools producer on Alibaba market since 4 years ago, at least.
Why care about this website and their offer? Well, if you like to have fun in hacking things probably you can save your time and carrying on your way. Instead, those wish to see a business opportunity need to compare their expectations / ideas with a competitive existing provider like this.
Changed Obd adapter to new and ObdFish works! But to tell the all, old obd adapter seems to be damaged after this fail connection. Now old adapter not works even with android. It sees BT, accepts code on connection, but it’s all - eternal lag on “Automatic protocol connection” (Torque app).