Things you can do with K-DCAN ??

[RAFiK - BMWClubUAE]

Well this is for the experts...

I've bought a K-DCAN cable and an OTG cable as well, along with Torque (Android) and Carly for BMW (Android). I've noticed you can pretty much code anything in the car and play around with BMW options.

What other things can be useful and things probably that I don't know I can play with or alter using the K-DCAN? What laptop software should I be using for instance and what can I do more than Carly for BMW (formerly BMWWhat)?

[jdamore]

I'd like to know more also.. specifically for logging.

Carly for BMW is constantly releasing new updates with additional coding options but, for the less common codings (or custom values), NCSExpert and NCSdummy is available.

RAFik- have you tried engine "parameters" using the cable? I am wondering how fast the refresh rates are..? The wireless OBD adaptors typically used with Carly are slow!

[RAFiK - BMWClubUAE]

I have the ELM wireless adapter but I use the Cable for coding to make sure i don't mess things up. Haven't tried how fast it reads the engine parameters.

[330iToy]

What coding options are available? Anything great? Thanks guys

[Helmsman]

Originally Posted by 330iToy

What coding options are available? Anything great? Thanks guys

Plenty things possible with "Carly for BMW". Here you go mate: http://support.mycarly.com/knowledge..._campaign=home

[mkPOTO]

the things we can do with our phones!

[RAFiK - BMWClubUAE]

Now from what I learnt, as I've been practicing on this for the past 2 months, K-DCAN can only work with E Chassis cars, while F Chassis cars net a cable called E-NET Cable.

Happy Coding!

[emil55]

KDCAN may be used upto 2013 model.
There are plenty of BMW software available on net for laptop like Rheingold Ista-D or Ista-P, Inpa. I have installed them on my laptop,but still have a problem with chinese KDCAN cable,so far I can not connect to my car.

[TboneS54]

BUMP - Can anyone knowledgable tell me specifically what can be done with a regular k+dcan cable with green pcb? It seems like you need one of these cables loaded with ediabas firmware to safely flash the ECU with an egine tune, but does that also apply to using winkfp to update DCT with GTS tune? Can you use a basic cable to code with NCS?

Just trying to figure out what I can accomplish with my basic cable and what I'd need a $50 cable with ediabas firmware for.

Thanks

[TboneS54]

Seems like all you can do is read. So at least you could verify that a BMW tool install worked and is communicating with the car, and maybe see DTCs

But not any sort of flashing to the ECU or a module. If anyone has anything to add, please do thanks.

[RocketyMan]

Originally Posted by TboneS54

BUMP - Can anyone knowledgable tell me specifically what can be done with a regular k+dcan cable with green pcb? It seems like you need one of these cables loaded with ediabas firmware to safely flash the ECU with an egine tune, but does that also apply to using winkfp to update DCT with GTS tune? Can you use a basic cable to code with NCS?

Just trying to figure out what I can accomplish with my basic cable and what I'd need a $50 cable with ediabas firmware for.

Thanks

"Green PCB" is irrelevant. That's not the defining point of getting a K+D CAN cable. What you're looking for is the FTDI chip (FT232) and being able to terminate pin 7/8. The issue arises with the fake FTDI chips. But in my experience, I just made sure to update to the latest FTDI driver, and I haven't had a problem as of yet.

I've done everything else except flash a module with it. In the event I want to flash a module, I use ICOM for that.

[TboneS54]

Only mentioned green as that was a quick way to tell if a cable probably had the FTDI chipset. Irrelevant, however, as I already know I have a good ftdi chipped dcan cable. My question is purely what can safely be done with that cable versus the same cable loaded with ediabas firmware that is safe for Engine ECU flashing.

I still haven't gotten a direct answer, but it's seeming to be only safe to read/connect to the car, not flash. But maybe it's safe to get into some modules besides the engine ecu? I'm not sure. I know it's best to play it safe. This was more to satiate my curiosity as I have a good dcan cable, but not the updated/safe one yet.

[RocketyMan]

Originally Posted by TboneS54

Only mentioned green as that was a quick way to tell if a cable probably had the FTDI chipset. Irrelevant, however, as I already know I have a good ftdi chipped dcan cable. My question is purely what can safely be done with that cable versus the same cable loaded with ediabas firmware that is safe for Engine ECU flashing.

I still haven't gotten a direct answer, but it's seeming to be only safe to read/connect to the car, not flash. But maybe it's safe to get into some modules besides the engine ecu? I'm not sure. I know it's best to play it safe. This was more to satiate my curiosity as I have a good dcan cable, but not the updated/safe one yet.

The direct answer was, verify the proper FTDI chip (which you did), use the latest FTDI drivers, do everything aside from flashing ECUs--use ICOM to flash ECUs reliably.

[TboneS54]

I'll be using a k+ dcan loaded with ediabas firmware (like what bimmergeeks or ecuwerx sells for ~$50), no ICOM, but I appreciate your input thanks.