That is really odd. Usually with ISTA the modules that it can't speak to are shown but in red. In your case it just isn't showing them at all, and you are right there should be at least a DME.

I can only suggest you need a different lead. From my distant memory with BMW's of this era you need an adapter with the K and L lines linked together and many don't.

 

Yes I have a K+dcan cable and it is linked. Some say the cables are hit or miss but before I buy another cable or I start reinstalling ista again I was wondering if a driver update or something would help.

 

My experience of these cables relates to BMWs, and a long time ago, but a slightly different cable was needed before 2007. You may have a BMW cable for post 2007.

 

I think you're talking about an ENET cable, yes I cannot use those. But K+Dcan can be used on r50 minis.

 

I wasn't talking about ENET, that's even later. However your lead does seem to be functional.

First just to clarify on the leads. I use a K-line OBD2 lead on my Mini at it works perfectly. The K-Line lead suits BMWs 1998 to 2007 and had pins 7 and 8 shorted. You need a DCAN lead for BMWs 2007 to 2016. After than you need the ENET cable.

A non-switchable K+DCAN cable only works in some BMWs. Because on those cars you need to be able to physically switch whether Pin 7 and 8 are shorted or not. It seems from your success that the R50 does indeed work with a non-switched K+DCAN lead.

Back to your problem, go to COM1 Port settings. Set to 38400 baud, 8, N, 1 and the smallest buffer and latency settings allowed. See how this works.

 

It is a switched k+dcan lead, and I do have pin 7 and 8 shorted. Look at my other reply everything seems to be working, unsure why those modules go to sleep, starting the engine scanning it and then leaving it on pos 2 worked. COM1 Port settings were already set to those.