Quality bmw k dcan cable for z4 manuals#
Quality bmw k dcan cable for z4 software#

Please find my handmade sketch for the circuit attached. May be some one more experienced in BMW diagnose can shed some light on this.

Expect BMW soft has similar functions like that. After the timer expires the instruction is given to switch Ignition ON, detects that and the program continues.

Quality bmw k dcan cable for z4 software#

I'm not an expert in BMW, but for Mercedes the software instructs to switch ignition OFF at a certain moment, detects that and starts a timer. I expect the software requires the info that power and ignition is on, hence the option to have the error detection ON or OFF in Ediabas.ini. There are entries to instruct EDIABAS to flag an error or not if the Ubatt/Ignition are not sensed by the soft. Must say that I have not found any entry yet in Ediabas.ini which will cause the dots to be black without an interface connected. Just start Inpa without the interface connected to the OBD2 in the car or the USB.

You can easily find out if it is the interface or soft setup the reason for the black dots. I don't know if I have a software problem or if I need to modify the cable.ДЄlso, can you clarify the BC547/1K/10K connections? (02-06-2015, 01:33 AM)vespa Wrote: Nice work Max! I have a dumb question, is this needed for proper operation or is it just to correct the display of the battery and ignition dots? I have the same cable with the same behavior, it shows battery/ignition all the time but won't do anything else. Happy now with the interface and Inpa setup! So, I lifted the pin (UBatt_1.jpg) and used a transistor BC547/1K/10K as inverter to pull this pin to GND if the interface gets +12V on pin 16 of the OBD2 connector (UBatt_2.jpg). That is why the UBatt dot is always black. Seems the RI pin on the FTD232RL is directly connected to GND on the board.

See picture 'Ignition.jpg' resistors R5 & R6. That solved the Ignition ON indication problem. These were not the proper values to get ~5V at the junction between both resistors. However the values and connections were as: Traced back the tracks from OBD2 pin 1 and found 2 resistors mounted on the board as voltage dividers. Interface connected to OBD2 or not.Дecided to try to fix this and started to read.ДЇound that RI from TTL-USB converter is used to indicate UBatt and DSR/DTR is used to indicate Ignition ON. While connecting and testing the interface I found the UBatt and Ignition dots were always black. Installed BMW Standard Tools 2.12 as per instructions of our friend Bimmer with all software he provided in his thread. Interface looks very well designed and has a nice PCB, all components soldered properly on the board. Since log files do not include any personal information, please note date and time of the log to help us find the correct log file.So, got my self a high quality INPA K+DCAN Interface from China. Please send us an email when you have uploaded the debug log file. The debug log is uploaded to our server and we can investigate the reason of connection problems.

Go back to Debug Settings, check that your debug log size is at least 5kb.

Let the adapter make connection attempts for a minute or so.

Go back to dashboard, and let the adapter make connection attempts for a minute or so.

It is disabled by default since it will slow down connection time on older (Application->Debug Settings and enable debug logging feature.

The 'Use Multipid Request' will increase the data rate on newer vehicles that have a CAN bus.

Go to 'Garage->Connections' and select your OBD2 connection settings.

You can try to improve the performance by enabling two optimizations for OBD connection.

Probably just something stupid in the configuration process, but I'll report back what they advise. I'm fairly sure we're not the first N54's to try the app, or E82 N54 specifically, so I followed their OBD2 'new connection fails' process from the faq and sent logs per their instructions. The RD connection config options are limited, but should be sufficient for the task at hand. My Google-Fu was unable to come up with anything helpful despite my best efforts. Heck, I even tried several connection settings/combinations- alas, all in vain.

Quality bmw k dcan cable for z4 manuals#

I used the RD online faq and manuals to be sure that I had configured my OBD connection correctly. Same as you iminhell1 I simply couldn't get it to connect.ДЇirst I verified my tablet is compatible with RD- yep, it is (Samsung Galaxy Tab S2 10 (SM-T810)). Finally got the chance to play with RealDash for a bit today.