Hello,
I copied everything. Only the pins I could not connect from "cd4053be". I do not understand, there are 16 pins .. on the pdf is at pin 1 -> 11 why? I am sorry for my English
Is the number 11 on the Picture Pin nummer 1 and:
14 - pin2
10 - pin3
15 - pin4
9 - pin5
4 - pin6
12 - pin9
13 - pin10
2 - pin11
1 - pin12
5 - pin13
3 - pin14
????
Last edited by Asker06; 12-31-2018 at 08:39 AM.
I dont understand with the chip "cd4053be".
Is number 11 - pin1? number 12 - Pin 9?
number 5 - pin2? number 13 - Pin 10?
number 10 - pin3? number 2 - Pin 11?
number 15 - pin4? number 1 - pin 12?
number 9 - pin5? number 5 - pin 13?
number 4 - pin6? number 3 - pin 14?
! . , ? , .
! . , ? , .
#Edit: Solved , I re-build that HansVMKII Board , and now it talking to my e34 530 RHD non EWS via DIS v44
WhatsApp Image 2019-02-19 at 20.56.33.jpeg
Need Help , sorry my english is not really good.
with help of my friend we re-create board schematic in eagle and build it. when i plug in to the car it light up right away , connect to battery and ignition dot in INPA ( from ediabas-6.4.3-full), but it got same problem again IFH-0009: NO RESPONSE FROM CONTROL UNIT Car is E34 530i M60B30 RHD. My installation folder is in C drive and a fresh windows xp 32bit on pentium 4. i also follow up the instruction from klaas :
a- execute instprog.exe
b- Installed with rectification program UK and selected ADS (not OBD), and installed just EDIABAS and INPA
c- Set the environment variable PATH: addes C:\EDIABAS\BIN
d- restarted laptop
e- Executed ADSSETUP.exe and restarted again
Ediabas.ini Files is like this , or maybe i should try using DIS ? anybody have the link to download it ?:
Thank You
;-----------------------------------------------------------------------------
; Interface
; Description : Connected diagnosis interface
; Default = EDIC
Interface =ADS
; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein!
Here is my error picture and my stock COM1 Setting,
Attachment 644681Attachment 644682Attachment 644684
Last edited by boy2nd; 02-20-2019 at 04:11 AM. Reason: SOLVED Thanks!
I built a case for my interface, maybe its useful for other people: https://www.thingiverse.com/thing:3438136
It has a 5mm hole for a power led and a D-SUB 9 cutout
[QUOTE=klaas;30145951]Sorry for the confusion im maybe creating.. i think this instruction might be wrong (but still try it 2nd if you cant get it to work):
----WRONG
- Rename existing SGDAT\DM331K20.PRG ---> SGDAT\DM331K20_WITHAWS.PRG
- Copy mistreku DME331.PRG -> SGDAT\DM331K20.PRG (rename it to this after copy)
----
RIGHT, just do this:
- Copy mistreku DME331.PRG -> SGDAT\DM331.PRG
The DM331K20.PRG.. ive renamed it to DM331K20_WITHAWS.PRG just to make sure EDIBIAS/INPA is not using that
- - - Updated - - -
[QUOTE=TRF434;30147762]Sorry i have not repied..
Strange that that fixed it..
I think i gave the wrong instructions:
----WRONG
- Rename existing SGDAT\DM331K20.PRG ---> SGDAT\DM331K20_WITHAWS.PRG
- Copy mistreku DME331.PRG -> SGDAT\DM331K20.PRG (rename it to this after copy)
----
RIGHT, just do this:
- Copy mistreku DME331.PRG -> SGDAT\DM331.PRG
This was right i believe:
- Rename existing \Ecu\DME331.IPO ---> \Ecu\DME331_WITHAWS.IPO
- Copy mistreku DME331.IPO --> \Ecu\DME331.IPO (same name)
The DM331K20.PRG.. ive renamed it to DM331K20_WITHAWS.PRG just to make sure EDIBIAS/INPA is not using it.
Last edited by klaas; 02-24-2019 at 05:02 PM.
Hi there!
So i built my own diagnostic ADS interface from here:
https://www.bimmerforums.com/forum/s...terface/page21
POST #508
thanks for these for E36328Coupe!
so after that, it's working very well with Inpa and NCS, i can code my car and read out oll of my modules, but now i decided to use DIS.
yes. DIS.... i know a littlebit about DIS and i also know about this, this is a "hard understand" software instead Inpa.
so i can't connect my car with DIS via owned ADS interface.
can anybody help me? what coud be wrong with that? Thanks a lot!
Hello,
i am looking for the latest gerber file for hannsv mk2 interface. Could somebody help me?
Thanks!
Lets see if this thread is still active..
I made the circuit and it works somewhat. The indicators work, and I can access at least 2 modules; the EWS and Instrument Cluster. But when I choose "DME 1.7 for M42 / M43" I get an 0009 error in INPA 5.0.2
I checked the cables between the 20 pin and DME and everything is connected.
Hi there!
Couse its not working with this ecu. I cant acces too. You have to look around in this ecu with tool32.
Every other ecu is worked for me except this. I dont know why
Just wanna say, I made it work, I mirrored the ground cable on the DB9. Everything is working and I just reprogrammed the EWS to work with and Ebay chip tune
can you kick off the EWS? if you say yes, HOW? and what with? can you point me? thanks a lot!
I didnt see an option to just "turn it off", but when you go back, read the DME and look for the ISN code(for me it was 3 characters, can be "c4t" or "cat") and write it down. Go back to main menu, scan the EWS and there is an option to code in the ISN overthere. When you type it in you see "0xdog", leave the "0x" and replace "dog" with your ISN from the DME. I hope this helps.
Thanks. Is it in the Inpa software? Or NCS or something else? Or do you know any guide for it?
You can find it all in INPA. I used INPA 5.0.2. Basicaly my previous message was a short "guide"
Hi i made this ADS interface from #1 post and works well with INPA and my old laptop with rs232 and windows xp. But i have i issue with ncsexpert. I can't read ZCS and VIN. I tried did that in DIS v44 too but without success. And i have question what line would belong to "coding things", wchich element on scheme i must check or how to check the correct work of the entire interface? With INPA i can connect to engine ecu, airbags and nothing more. Car is euro e36 m52 '97 coupe
hi there!
i built a few boards, which are fun, but i wondering to build another one with less components. So i took Hans's circuit, and tried to transfer it to the simple strip board. i didn't test it yet, what are you think about guys? Is it good, or absolutley wrong? Or anybody has a layout with this circuit to strip board? I also know, there is a layout for this, but i can't make my own board, i can just work with strip boards. So Hans, if you read it, pls check out my new board
And one more thing, now here is winter time in my country, and my boards just broked down. WTF??? the cold is very very bad for these boards, it's about -10C. 141551340_5351541401587854_295427655536605382_n.jpg141747697_263074191864238_1034684624304698842_n.jpg142143675_396528638309933_9081546115083502951_n.jpg
Kevin you mention you know DME3.3.1. Are you able to help me? Simply cannot get INPA to talk to my DME. Starting to think it cant be done. Happy to PM?
Hi,
If other modules are working (i always try to KOMBI first as its fast), then you probably are missing the DME331.IPO and DME331.PRG modified files by mistreku
Make sure that your wiring is proper: I built the basic interface from post 1, but could not make it work... upon recheck, I had awrong resistor 4.7K instead of 47K, upon recheck 2 some wiring was missing and upon recheck 3 I had built the DB9 plug reversed, most of us will be using a female DB9 to go into the PC male serial port. Check this site:
https://www.codrey.com/embedded-syst...communication/
and this schematic toward the middle:
I still have issues but managed to get some basic infos. I am using ediabas 6.4.3 which install INPA 3.0.1, Compag NC8430, with XPsp2, real serial port
Last edited by letank; 09-12-2022 at 04:57 PM.
Hello there!
First of all, a big Thanks to everyone that has helped/contributed to this thread. After reading tons of pages and forums about how to fully diagnose my e36 318i (M43) 1997, I decided to build the ADS interface as described in post #1. I am using a newly installed INPA known to work on ADS mode, according to the page 7 of the "z3 diagnostic forum". The laptop I am using is a Panasonic cf-18 with a physical serial port, running windows xp 32 bit.
I have triple checked the schematics and connections but I am still unable to access any module. Power and ignition (INPA black dots) work as intended, and INPA loads without errors, indicating to me that probably the INPA is configured correctly, but still getting errors when trying to access a module. Serial port is set to com1, ediabas.ini configured correctly.
I am running out of ideas what might be wrong.
Any help is greatly appreciated.
Thanks,
Kostgeor
Nice work!
Can i get your pcb layout? Both sides, and the component values pls
Thanks a lot
Hi there,
I'm struggling to get my interface working, I've checked my pcb a few times and pretty sure I've got everything connected correctly, but who knows (MKII design).
Currently I can get dis and Inpa to recognise my ignition, they also start to communicate seemingly, but when I choose a module i.e. dme, it tells me I have an m62 engine and the chassis data etc seems corrupt (The car is actually a 1994 e36 318is m42).
When I plug my interface into the 20 pin and my laptop serial port, all the leds turn on which seems incorrect according to KevinMullins video. Ignition does get brighter when turned on, but I would assume dtr should be off as well as k line. When I start a job the K and DTR lines are the only ones that flicker, the rest remain on.
Is there anything you recommend I check?
Thanks
IMG-20231229-WA0018.jpg
Last edited by MARHD; 12-29-2023 at 04:51 PM.
Bookmarks