In the "Replacement Firmware for ELM327" page, in "Programming of the Processor:"

The source for the firmware could be found in the subdirectory CanAdapterElm. In this subdirectory there is also a flash tool (subdirectory UpdateLoader) that allows firmware updates using the bootstrap loader once the firmware is programed. The latest firmware version will be always included in Deep OBD for BMW and VAG.

In the current binary release, there are three folders in the CanAdapterElm subdirectory: bc04, hc04, and default. There is no UpdateLoader folder -- that is in the CanAdapter folder, not CanAdapterElm. No guidance is given for what the difference is for the bc04, hc04 and default folders. Also no clarity as to the "unified" and "non-unified" within those folders.

The files in the CanAdapter folder match up much better to the descriptions on the firmware page (and on the page "Build a Bluetooth - D-CAN/K-Line Adapter" which I tried to use for help as well), but they are in the wrong folder according to the instructions and are also over a year older, so I imagine they are not the ones to use? But one can't really be certain with the instructions as they are, I think.

Hello,

I have a BMW E46 330i (2004), I would like to use the android application, but my OBDLink LX, and ELM327 clone device is not working.

There is a link for bluetooth adapters on this documentation page, but it's a dead link:
https://github.com/uholeschak/ediabaslib/blob/master/docs/Replacement_firmware_for_ELM327.md

Can you provide a proper ebay link to get one of these adapters? Thanks.

Hi,

I have been using Ediabaslib.dll successfully in a number of my projects, however I believe I may have stumbled upon a bug. I can successfully execute the job in question using identical parameters using Tool32 and the stock api32.dll, however when I execute the job with the ediabaslib api32.dll I get an error. The same error occurs if I repeat the test using EdibasTest.exe too.

I am running the job "FLASH_LOESCHEN" from the SMG2.prg file and passing the parameter "010100000000000000FF0000006000600010200300FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF03".

The errors I receive are "DATATRANSMISSION TO INTERFACE DISTURBED" or "ERROR_ECU_PARAMETER".

Attached are trace logs from the working api32.dll and tool32, along with the traces from the non working ediabaslib api32.dll.
ediabaslib_logs.zip

Many thanks,

Martyn

Hi,
this is more like a nice-to-have improvement than an issue: In INPA the IGN and BATT dots dont work (in ADS mode). The IGN line is connected to the RI pin. I looked through your code and I think that you only use the DSR pin. Just wanted to report that here, pretty low priority problem :)

Hallo Herr Holeschak,
Wann stellen Sie wieder Adapter in ebay ein? Vielen Dank.

Since this is open source, it'd be great if the Android app could be installed via F-Droid.

Is the modified firmware compatible with this?

Timestamp resolution in data logs is 1 second while actual read interval can be much lower.

On my 2007 E91, connected with FTDI chip, with configuration reading few variables with STATUS_MESSWERTBLOCK_LESEN I get up to 6 samples with same timestamp.

Date    motor_air_mass  motor_air_mass_act      motor_throttle  motor_ambient_press     motor_air_mass_set      motor_boost_press_act   motor_bat_voltage       motor_refrig_temp       motor_torque_act        motor_torque_set        motor_fuel_cons motor_rpm       motor_ambient_temp      motor_intake_air_temp   motor_inject_act        motor_inject_set        motor_oil_temp  motor_boost_press_set   motor_rail_press_act    motor_rail_press_set    motor_speed
2018-04-22 17:20:59       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.35  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  315.19    0.00
2018-04-22 17:20:59       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.15  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  314.58    0.00
2018-04-22 17:21:00       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.15  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  315.19    0.00
2018-04-22 17:21:00       0.01    0.01    0.00  994.89  444.11  1005.89  12.37   78.15  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  315.19    0.00
2018-04-22 17:21:00       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.35  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  315.19    0.00
2018-04-22 17:21:00       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.35  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  314.58    0.00
2018-04-22 17:21:00       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.15  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  314.58    0.00
2018-04-22 17:21:00       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.15  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  315.19    0.00
2018-04-22 17:21:01       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.35  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  315.19    0.00
2018-04-22 17:21:01       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.15  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  314.58    0.00
2018-04-22 17:21:01       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.15  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  315.19    0.00
2018-04-22 17:21:01       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.15  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  315.19    0.00
2018-04-22 17:21:01       0.01    0.01    0.00  993.89  444.11  1005.89  12.39   78.15  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  315.19    0.00
2018-04-22 17:21:01       0.01    0.01    0.00  994.89  444.11  1005.89  12.39   78.15  -23.58    5.49    0.00    0.00   19.95  -50.14    0.01    0.01  114.84  989.89    4.27  315.19    0.00

My suggestion is to add milliseconds value to Date column.

I have successfully diagnosing, coding with this adapter many cars.
But I can't code or read code with NCS expert E39 DSC5.7 module.
I can make diagnosis with ISTA, INPA that module, but can't code.
I have tried different INPA installation, re installed daten files etc.
I can code other modules in same NCS expert session.
I tried with INPA-cable, no problem.
I can provide more info if needed.
Ediabas Version:
7.3.0_Package_1.1
and
7.3.0_Package_1.0
NCS-expert v4.0.1
CoAPI V3.13.2
KrAPI 3.0.2

NCS expert error file:
[16:05:10.105] [2018-02-17] [SERIE] 2000 Error LFCDHDIA.CPP (A_DSC57.IPS/IPO) CDHapiResultText 1 [16:05:10.105] [2018-02-17] [SERIE] Error in EDIABAS or in ECU description file (SGBD) SYS-0000: Internal error C_DSC57 [16:05:10.105] [2018-02-17] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6 [16:05:10.105] [2018-02-17] [SERIE] Error in EDIABAS or in ECU description file (SGBD) CODIERINDEX_LESEN [16:05:10.105] [2018-02-17] [SERIE] 2000 Error COAPI.CPP coapiReadCodierIndexFromSg 5 [16:05:10.105] [2018-02-17] [SERIE] Error in EDIABAS or in ECU description file (SGBD) CODIERINDEX_LESEN: A_DSC57 [16:05:10.277] [2018-02-17] [SERIE] 2000 Error LFCDHDIA.CPP (A_DSC57.IPS/IPO) CDHapiResultText 1 [16:05:10.277] [2018-02-17] [SERIE] Error in EDIABAS or in ECU description file (SGBD) SYS-0000: Internal error C_DSC57 [16:05:10.277] [2018-02-17] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6 [16:05:10.277] [2018-02-17] [SERIE] Error in EDIABAS or in ECU description file (SGBD) CODIERDATEN_LESEN

I have an ELM327 Bluetooth adapter that reports version 1.5 but doesn't actually support anything above 1.4 (I checked with ELM327 Identifier). When I connect with the Deep OBD android app, the connection just drops every couple of minutes for a minute or so. Is this the adapter's fault?
Also if I switch to another app and come back it always says there have been errors and wants to send a log file. Should I do it each time?

Hi, i don`t know is it a error or not but i thought when INPA/Ediabas/Tool32/NCS Expert and DeepOBD work with the Bluetooth Adapter, it work with DIS because DIS use the Ediabas for Connection?!?

Did anyone try this connection before or managed it to work ?

Sorry for my bad english
I`m from Germany and had only 4years English in School..

Good day sir. I am a graphic designer and i am interested in designing a logo for your good project. I will be doing it as a gift for free. I just need your permission first before I begin my design. Hoping for your positive feedback. Thanks

Custom firmware is technically Not required - Carista can do it without custom firmware
What would be required is changing hte program to have deepodb work with unrecognised firnwares/devices.

Carista can do custom VAG settings using standard ELM327
Not many, the ones with discrete CPU and EEPROM matching original ELM327 hardware would be best. The cheap ones are implemented to work for standard ODB2 packets, probably having specification based on sniffing/reverse engineering standard ODB2 protocol converstion only.

If carista can do it with PP2145, standard firmware, then why do you need custome firmware.

In fact, since its hard to find the elm327's that can be customised with the EEPROM/PIC programmer thing, better to work with whats available ? such as carista's list or the jaycar one

Hi. I'm not super proficient with programming and compiling. But would it be possible to get this working on the stn1100 chip?

Hello
First congratulate you for this project, it's a great job and I thank you for sharing it.
I have a problem with an ESP8266ex ELM WiFi adapter, in which I have modified both the ESP (esp-link Release 2.2.3) and the PIC18f25k80 firmware (115200bps esp8266 firmware), and now I can not connect using the Deep OBD for app BMW and VAG, the adapter seems not to receive the data, I think it is because the application does not try to connect by the ip 192.168.4.1 port 23, if so it is possible that it is included, or can be selected in the settings of the app
Greetings and thank you

Hi, I'm trying to patch my MaxiScam OBDII 901 using EdiabasLib.exe however I get an error:
Connected
Read firmware version failed

Any idea? A bug in a program? I have Skoda Superb 2014 FL 2.0 diesel. Please advise

I was made aware that a bug in how I was arraying the bytes could cause the bytes to be output in correct decompressed / compressed length but result in every byte potentially being null since zlib.managed v1.1.2. I plan to release a v1.1.4 to attempt to fix this issue.

Sorry for any potential inconvenience this has caused.

Is possible to battery adaptation using this app, after replacing a new similar battery for Skoda cars etc. If not, any chance to do it?

Is BK3231 firmware compatibility with BK3432 chip?

I've noticed that EdiabasLib doesn't handle jobs where some of the arguments are left empty. Below I've attached examples of the Ediabas vs EdiabasLib behavior in tool32:

EdiabasLib

apiJob("08MSV70","diagnose_mode","default;PC115200","")

Satz : 0
  VARIANTE                        = 08MSV70
  OBJECT                          = 08msv70
  JOBNAME                         = DIAGNOSE_MODE
  SAETZE                          = 1
  JOBSTATUS                       = 
  UBATTCURRENT                    = -1
  UBATTHISTORY                    = -1
  IGNITIONCURRENT                 = -1
  IGNITIONHISTORY                 = -1
Satz : 1
  JOB_STATUS                      = OKAY
  _TEL_AUFTRAG                    = 7 Bytes
    0000 : B8 12 F1 03 10 81 05                               ¸.ñ..�.
  _TEL_ANTWORT                    = 8 Bytes
    0000 : B8 F1 12 03 50 81 05 8C                            ¸ñ..P�.?  

apiJob("08MSV70","set_parameter",";115200","")

EDIABAS Error 16 : IFH-0006: COMMAND NOT ACCEPTED


apiJob("08MSV70","set_parameter",";115200;;15","")

EDIABAS Error 16 : IFH-0006: COMMAND NOT ACCEPTED

Ediabas 7.3.0

apiJob("08MSV70","diagnose_mode","default;PC115200","")

Satz : 0
  OBJECT                          = 08msv70
  SAETZE                          = 1
  JOBNAME                         = diagnose_mode
  VARIANTE                        = 08MSV70
  JOBSTATUS                       = 
  UBATTCURRENT                    = -1
  UBATTHISTORY                    = -1
  IGNITIONCURRENT                 = -1
  IGNITIONHISTORY                 = -1
Satz : 1
  JOB_STATUS                      = OKAY
  _TEL_AUFTRAG                    = 7 Bytes
    0000 : B8 12 F1 03 10 81 05                               ¸.ñ..�.
  _TEL_ANTWORT                    = 8 Bytes
    0000 : B8 F1 12 03 50 81 05 8C                            ¸ñ..P�.?  

apiJob("08MSV70","set_parameter",";115200","")

Satz : 0
  OBJECT                          = 08msv70
  SAETZE                          = 1
  JOBNAME                         = set_parameter
  VARIANTE                        = 08MSV70
  JOBSTATUS                       = 
  UBATTCURRENT                    = -1
  UBATTHISTORY                    = -1
  IGNITIONCURRENT                 = -1
  IGNITIONHISTORY                 = -1
Satz : 1
  JOB_STATUS                      = OKAY

apiJob("08MSV70","set_parameter",";115200;;15","")

Satz : 0
  OBJECT                          = 08msv70
  SAETZE                          = 1
  JOBNAME                         = set_parameter
  VARIANTE                        = 08MSV70
  JOBSTATUS                       = 
  UBATTCURRENT                    = -1
  UBATTHISTORY                    = -1
  IGNITIONCURRENT                 = -1
  IGNITIONHISTORY                 = -1
Satz : 1
  JOB_STATUS                      = OKAY

Sporadic issue.
Steps:

1. Open application
2. Open General Settings, Change any settings item (i usually set Keep Screen Bright to keep screen unlocked)
3. After successful connection and communication - disconnect.
4. Open application after some time (usually after several hours in my case)
5. General settings are reset to its defaults

Hallo, ich habe einen ELM327 WIFI Adapter von Carly

ip: 192.168.0.10
Port: 35000
Version 1.4b

Wird leider von der Ediabaslib nicht erkannt. Hätte es mit Ista benutzt.

Was muss ich an dem Adapter ändern, damit es funktioniert. lg

I have used it with large variety of cars.
Mainly it works fine and very easy to connect (compared to ENET). But sometimes it lost connection after succesful identification to some modules (example DDE). Also Fault memory delete not work, because new ISTA+ want's to control ignition voltage terminal change during memory delete. 99% times terminal change fail with wlan adapter and also memory delete fail then.
With ICOM it works every time, ISTA turn car off and back ON and continue delete.
Sorry I dont have any trace logs now, but I can arrange on some day.

I cannot find the value for the meters traveled since the last Diesel Particulate Filter regeneration. I have found exhaust temperature before DPF, pressure and other items related, but this one doesn't seem to be there and I can't understand German well. Can you point me in the right direction?
It is the 6th from the bottom in this screenshot you made:

Thanks

I have selected all jobs in the ecu and it worked but it takes ~5 sec to refresh, is it normal?

Hi, First I have to say thanks from all of this...
But I have also problem with programming bc-04 to elm327.
Elm chip is the pic18f25k80 and BT BK3231, I use Pickit3.
With bc-04 firmware it was unworking state, no elm, no DeepOBD. But with Default unified firmware it worked right away and also received firmware update after that.
It's already superior with the DeepOBD/inpa/ista, I also made the k-line switch.
But what I doing wrong with the programming?
What I miss with this firmware, speed, stability, configurability?

Is there any way to use that with other PC software as a INPA adapter, like Siemens MS43 flash tool, Romrider logger, they need a standard Com port. If I pair that BT-device with Windows 10, I got two Bluetooth Com ports, PC&adapter side openable ports. But those ports not work with any other app what I have tried. Maybe they need FTDI driver?

Sorry if this isn't the appropriate place to ask this. But basically I'm working on an flashing application for the MSS6x series DMEs. It works very well with EdiabasLib along with a D-CAN cable flashed with your firmware. On a standard cable, a brick is all but guaranteed.

Is there a way to detect if a D-CAN cable is flashed with your firmware? That would make me a lot more comfortable about releasing since I'm sure there's someone who won't listen to my warnings.

After flashing blue elm327 with elmV1.5e , adapter some times has a ATZ command error. And now stop working with openDiag application.
UPD: Adapter needs car for first protocol detection.

First of all, thanks for a great app, which is very helpful in finding problems with my car.

I've been taking a lot of logs lately (tracking down an issue) and I have had several occasions where the logs did not get written.
I found sometimes the checkmark next to logging gets reset and no logging gets written. Also always writing the data to the same file can be problematic for me.

I'd propose to create an option to always log the data (never automatically reset this option) and to create a new logfile with timestamp in the filename each time the app connects to the dongle.

Also (unrelated), in case a job result contains newlines, the CSV file is not (easily) readable anymore. I'd propose to replace any newline characters in job results with ; or something similar.

Best regards
Daniel

Hello,
I got EdiabasTest running on mono on an raspberry pi. I sometimes get the problem, that I cannot execute the job STATUS_MESSWERTBLOCK_0. Other Jobs are running f.ex. STATUS_DIGITAL_0. I am using a maxDiag1 USB adapter for my BMW Z4 E85 with MS45 ECU. I get an ERROR_ECU_CONDITIONS_NOT_CORRECT_OR_REQUEST_SEQUENCE_ERROR
for job status.
See here my commands I executed.
osmc@BMW:~/ediabaslib/EdiabasLib/EdiabasTest/bin/Debug$ sudo mono EdiabasTest.exe --alltypes -s ms450ds0.prg -j STATUS_MESSWERTBLOCK_0 -p /dev/ttyUSB1
API Version: 7.3.0
JOB: STATUS_MESSWERTBLOCK_0
Variant: MS450DS0
DATASET: 0
IGNITIONCURRENT: I: -1 0xFFFF ALL: -1 255 -1 65535 -1 4294967295 -1
IGNITIONHISTORY: I: -1 0xFFFF ALL: -1 255 -1 65535 -1 4294967295 -1
JOBNAME: STATUS_MESSWERTBLOCK_0
JOBSTATUS:
OBJECT: ms450ds0
SAETZE: W: 1 0x0001 ALL: 1 1 1 1 1 1 1
UBATTCURRENT: I: -1 0xFFFF ALL: -1 255 -1 65535 -1 4294967295 -1
UBATTHISTORY: I: -1 0xFFFF ALL: -1 255 -1 65535 -1 4294967295 -1
VARIANTE: MS450DS0
DATASET: 1
_TEL_ANTWORT: B8 F1 12 03 7F 21 22 24
_TEL_AUFTRAG: B8 12 F1 02 21 F0
JOB_STATUS: ERROR_ECU_CONDITIONS_NOT_CORRECT_OR_REQUEST_SEQUENCE_ERROR

osmc@BMW:~/ediabaslib/EdiabasLib/EdiabasTest/bin/Debug$ sudo mono EdiabasTest.exe --alltypes -s ms450ds0.prg -j STATUS_DIGITAL_0 -p /dev/ttyUSB1
API Version: 7.3.0
JOB: STATUS_DIGITAL_0
Variant: MS450DS0
DATASET: 0
IGNITIONCURRENT: I: -1 0xFFFF ALL: -1 255 -1 65535 -1 4294967295 -1
IGNITIONHISTORY: I: -1 0xFFFF ALL: -1 255 -1 65535 -1 4294967295 -1
JOBNAME: STATUS_DIGITAL_0
JOBSTATUS:
OBJECT: ms450ds0
SAETZE: W: 1 0x0001 ALL: 1 1 1 1 1 1 1
UBATTCURRENT: I: -1 0xFFFF ALL: -1 255 -1 65535 -1 4294967295 -1
UBATTHISTORY: I: -1 0xFFFF ALL: -1 255 -1 65535 -1 4294967295 -1
VARIANTE: MS450DS0
DATASET: 1
_TEL_ANTWORT: 62 40 07 00 00 08 42 1B F5
_TEL_AUFTRAG: B8 12 F1 03 22 40 07
JOB_STATUS: OKAY
STAT_LL_EIN: I: 0 0x0000 ALL: 0 0 0 0 0 0 0
STAT_SBBHK: I: 0 0x0000 ALL: 0 0 0 0 0 0 0
STAT_SBBHK2: I: 0 0x0000 ALL: 0 0 0 0 0 0 0
STAT_SBBVK: I: 0 0x0000 ALL: 0 0 0 0 0 0 0
STAT_SBBVK2: I: 0 0x0000 ALL: 0 0 0 0 0 0 0

Do you have any idea why this happens?
With the same setup it is sometimes possible to read STATUS_MESSWERTBLOCK_0 and sometimes not.
Is there any job I have to run before it is possible to run STATUS_MESSWERTBLOCK_0?

I can connect using INPA without any problems with the same interface.

Thank you BR
Martin

Hello, I'm using DeepOBD on a Huawei P10lite with Tacklife AOBD1W WiFi-Adapter on BMW E87.
Many thanks for this powerful App.
My issue is that the autogeneration find many ECUs and when connected I could see the failures on the errors-page but the ECU-sheets are empty (see screenshots). What am I doing wrong ?

I designed a logo for the deep OBD application. I was inspired by the letter "D". Color options, whether you want a single color or dual color as you want to send the format you want to prepare. I think the new logo of the application will be more noticeable. I hope you like it.

Hi,

I have got an adapter (WiFi OBD2), which I use for communication for Carly. Unfortunately DeepOBD Android App on my Samsung S7 cannot establish connection via this adapter. S7 is connected to the adapter via WLAN.

Thanks for the help in advance.

Maris

Hi I have some issues to read the ecus, i have an vgate icar2 tool. I tried to read the ecus on an bmw e61 lci build in late 2007.
I take an screenshot, i pretty sure that my car dont have k-line, because its an lci.
With the vgate tool and "bimmercode" its works quit fine also with the apps "torque" or "car scanner".

With an other tool i have i can work without any problems with inpa and tool32 via usb and my notebook.

Maybe, you have any ideas where my mistake is.

Greetz Tim

Hi @uholeschak,

thx for your great work! I'm very thankful for it.

I'm struggling a bit with one of my page specifications which shows values of multiple ECUs and hence has multiple Job nodes. My problem is that i want to show some values from engine ECU then some of gear box ECU and then again from engine ECU which leads to the first engine ECU values not showing up. I'm using user defined code to format the values.
Do you by any chance have a mock OBD adapter to be able to test the page without having a real OBD interface connected?

Thx in advance

I'm using DeepODB on a Nexus 5X with 16 GB flash. On this phone in reality 16 GB becomes 14.5GB and of that about 4 GB is used by the Android system. After installing some apps typically only a few GB is left for data. In this situation, it seems a pity that I need to extract the complete 2.3 GB of ECU files.

I was thinking it could be interesting to add an option to only extract the modules that are used in the installed page configs or even only the current page config. What do you think?

I replicated your E60 config pages for my E46 N42 (EK924) but only the Error tab is working. The other tabs are empty.
I only want a second tab named: Monitor with the following info:

• Battery Voltage
• LTFT Bank1
• LTFT Bank 2
• STFT Bank 1
• STFT Bank2
• RPM
• Coolant Temperature in C°

How can I properly do it?
Thanks for your response.

Hello,

I found this repo while i was searching for new firmwares for the elm327, actually i don't have a bmw.
may i ask you from which version of the elm327 did you started for your improvements? and from where did you found it?
thanks

Hi @uholeschak,

i am testing your project thx about but a little issue VS give me errors when i build the project
/EDIABASLIB/ediabaslib-master/EdiabasLib/CanAdapterElm/CanAdapterElm.X/dist/default/production/CanAdapterElm.X.production.hex".' (CS1566) (BmwDeepObd)
missing a file here on github?

Hi,

I would like to clarify whether is it possible to use DeepOBD on my Windows Laptop. If yes, what I shall install and from what source.

Regards
Maris

pretty old and slow GT P 5110
https://en.wikipedia.org/wiki/Samsung_Galaxy_Tab_2_10.1
latest Deep OBD
connected with gender changer to FTDI USB cable
Android 5.1.1 custom (https://slimroms.org/) witch is probably rooted and has extended debug settings.

Deep OBD starts and extracts fine, but whether I use the config generator or ediabas tool and choose USB/FTDI it does simply nothing. No warning / error. I am also unable to create trace files or similar. So hard to provide better info for this...

How could I check whether it can talk to the FTDI at all?

I'm trying to find a bluetooth adapater for the E46. I can see that this falls under DS2 - however the current link in the README is for an expired auction and I'm not clear if the pin 7+8 connection is something I can buy off the shelf or requires some input from me? It would be good to improve the readme to include this detail. Thanks.

The reason for looking for a different adapter is because I received this message:

Hi

I did replace the api32.dll in ediabs/bin path with yours.
Needed to install vcredist 2015 runtimes.
Paired the bluetooth dongle and got com6 and com7.
Edited obd.ini to com6.
Inpa is loading.
Battery and Ignotion stays off.
After selecting my e39 and the lcm i get the error about an interface error.
The same with an usual usb interface.
Windows 7 Pro 32bit

How to get it working?

Hi,
I bought this: http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItemVersion&item=262933669196&view=all&tid=2034755812016

Which was FAKE! (BK3231)

Please advice about a seller which has genuine ediabaslib compatible PIC18F25K80.

First off, thank you for providing this, it has been a VERY helpful tool!

I just started playing around with the Deep OBD BMW app on my USA E61 and noticed many of the values from the sample E61 config were not being read on the "motor" tab. Is there something else I need to do or could it be a difference in the E61 build (USA vs Euro, year, etc)?

ELM327 comes with a PIC18F2480 but the provided Microchip project is configured for a PIC18F25K80.

I need to set it up again bcs pc swap, can you help with files for Ista-D ?

Hallo Herr Holeschak

Gibt es eine Möglichkeit vor dem Kauf eines "noName" ELM327 den Chipsatz rauszufinden? Es geht im wesentlichen dadrum, das ich einen ELM Adapter mit BC-417 erwerben möchte. Pickit3 ist vorhanden und ich weiß wie man solche Devices flasht.

Auf den gängigen Seiten fand ich genau einen Händler, der eine "genauere" Beschreibung ink PCB-Bilder hatte. Ich habe mal seine Bilder kopiert - eventuell können sie mir ja sagen welcher Chipsatz was ist. Es gibt bei ihm 2 verschiedene Varianten. Eine mit grünem PCB, und eine mit rotem:

Ich gehe davon aus, das auf dem roten PCB ein HC05 Chip verbaut ist(dadrauf deutet die Markierung des Chips:m160309). Dieser sollte Pin sowie Software-Kompatibel zu HC04 sein. Wissen die Open-Source Firmware auch damit läuft?

Vielen Dank im Voraus,
Grüße aus München
Elias

https://gist.github.com/brandonros/3e4eb6b39d77e2e7469abdf44ab4c7f3

There are no executables supplied with the repository (e.g. EdiabasTest.exe). Could you supply them?
It would save the VS Studio setup and compilation.