OBD2 Car Diagnostic Tool Share

Last month, I happened to got free BMW E-Sys 3.27.1 link from a car diagnostic forum: https://mega.nz/#F!E1YzzSxQ!DRr7BE8YL7GWEX8YqBbH9g and have been using E-Sys 3.27.1 with my old ENET cable (Chinese knock-off) a lot recently and I noticed that it crashes a lot due to a myriad of issues. Something as simple as having the MSM Updated turned on could crash E-Sys. The good news is that MSM update is the last process in coding, so the crash does not pose big problem when coding. It's just so annoying. Memory, or the lack thereof, could also crash E-Sys. So, when running on default memory settings and trying to code complex ECUs, like NBT, could crash it. I've never seen this happen to previous versions of E-Sys. It was pretty good at handling exceptions, but 3.27.1 seems different. Bonus Tip If you are forced to run E-Sys using default memory settings (512MB), you can help it by moving some PSdZData folders you never use. Some folders you can safely move, so long as ...

This might be helpful to those who use K+DCAN USB and ENET interface and do diagnosis and programming with ISTA-D, ISTA-P, or E-sys Windows 10 Home 64-bit. ** Background information: I did have ISTA-P (3.54.3) running nicely on Windows 8.1 64-bit with a K+DCAN USB lead (never tried ENET but I think it would have been fine). I was using loader V3.2 for ISTA-P. I also had Rheingold Standalone 3.47.3 running perfectly with K+DCAN USB and ENET cable . ** Setup on Windows 10 64-bit: After the Windows 10 update (which failed the first two attempts because it turned out the laptop BIOS needed an update first) most applications were fine. By simply revisiting the COM port settings for my USB K+DCAN to set back to COM9 , minimum buffer sizes and minimum latency Rheingold ran perfectly. Loader V3.2 and ISTA-P was a bit more tricky. I re-ran the Network Config Tool. I tried Loader V4.3. No joy. However I did eventually figure it out and now ISTA-P runs nicely too, and with the exc...

I just installed full version of ista along with icom emu 3.0.3. After some trying with the network settings, i finally got the icom to show in ista. I am trying to get ista to work with my k+dcan-usb cable with my BMW E87 1 series. I started up ista and and the icom emulator on my windows 8 computer with VMware Workstation 10 and connected the k+dcan cable to my car. It worked and made contact with the car and started reading out different values like my vin number and production date etc. But suddenly i got a pop-up window with 4 errors.. It says: "An error occurred on execution of the measure." 94201 Technical service initialisation failed (EDIABAS) - IFH-0009: ECU not connected or not responding 19 10007 (CIP) - Error during initialisation of EDIABAS 94020 Determination of the vehicle context failed Google and talked with some bmw users on forum. I was told that that this could be because the car had MOST connection but unfortunately i don't have...

Hello, all. Here I’d like to share my experience with INPA K+DCAN cable for my BMW E63. Just got INPA cable for months, shipped with my clone ICOM A2 package and as a gift. I would have thought that it was just a cheap gift couldn’t work well, so that I never thought to have a try. Last week, my friend Ken said he wanted to buy a K+DCAN cable, which reminded me of my old gift. Decided to try my INPA cable and give away to Ken if it works well still. You see my BMW cable, brand-new. K+dcan interface inside, looks good. After reading the PCB, I thought I might look down on this gift. International design, you know. Then I connect K+DCAN interface with my E63 and the USB port of the laptop. When INPA starts, the following screen is displayed: Press F2 for the E36 options. From the dialog, I select Body and then Airbag to have a try. The following menu is displayed: Pressing F2 shows the Airbag Ident screen: The part number 8374798 relates to the Airbag Co...