OK update, same thing with the car running. Auto detection does not work, same message, and manual doesn't do anything either. Fail Sauce.

I also figured out the admin part. Test the head, it said that its connected and communicating. IP is coo126 192.168.68.31. I also disconnected it, and reconnected successfully. So I don't think there is an issue with the gt1/DIS.

What should I try now? Should I bother disconnecting the battery and reconnecting it?

This may sound silly but make sure the OBD2 connector is in good shape and connected properly to the car, if all is good... I am stomped too..

Success.

Ok so here is the sequence tried today.

Connected the laptop to car via the obd connector while car was running (and off but key in position 2), and laptop was on. Fail

Connected to car via lan wire, while car was running (and off but key in position 2) and gt1 on, FAIL

GT1 turned on nothing pressed on screen.
Connect gt1 to car via the OBD connector.
Put car key in, not in any position, just the hole, don't turn.
Click Diagnosis in DIS
Screen goes blank and takes about a min
Message pops up that the there is a low voltage problem.
Turn key to position 2 (ignition), pop up box goes away by itself in about 20 seconds.
Message pops up saying that the car has been AUTO-DETECTED.
Click OK.

DIS FULLY FUNCTIONAL NOW. Thank you all. I'll keep you all posted if there are any other issues.

P.S. After this process, the GT1 seems to know the car, and disconnecting and reconnecting seems to be no problem, but this could be because there is some sort of memory in the program. My parts should be here Tuesday, so hopefully next weekend I will get to try this all again.

Are you running DIS on VMware or native?

DIS Native.

So happy it works. Don't want to do the trans oil without this. Not sure if I will need this for the PDC, but deff will need it this to encode a new Seat Occupancy Sensor.

Sorry for the late reply. Note: I use DIS not SSS.

Battery Charger Specs:
Read from the link below (and several posts onwards) about charger requirements. The discussion talks about voltage requirements. Others can chime in on their experience but I have the charger with a power supply mode.

Generally you need to have more voltage than required because of voltage drain. IIRC, voltage output should be around 14v.

http://www.xoutpost.com/bmw-sav-foru...op-gt1-22.html

Battery charger while coding:
I cannot speak about using a regular charger when coding. I use the PS mode when I use my charger. Hopefully others can speak-up. I don't want to assume 100% of others, who may use a regular charger, have not experienced any problems.

USB ODB Cable:
I have no experience with that cable. I use the cable thats made to work directly with the DK (yellow unit). That looks like a cable made to be used with another system I'm not familiar with. Sorry can't help you on this.

Thanks, TwinsPoppa http://www.xoutpost.com/images/members/premier.ico for your valuable information.


Anyone know how to reset transmission adaptation and how long it will take?

In the fact, you do not need a battery charger when using SSS. Just start the engine when starting SSS, most of modules can be coded or programed when the engine is running (battery voltage over 14v). When coding/programing DME, EGS (facelift) and VTG (facelift), you need to start the engine when SSS checking battery voltage, and swith off the engine and turn to position 2 after SSS checking battery voltage, SSS can complete the whole coding/programing without any problem. However, make sure your battery voltage is over 11v during the coding/programing, if your battery's condition is ok, it should keep at 11v or above. I just updated software of my DME, EGS, VTG and DSC by using this method without any problem.

When you coding/programing EGS and VTG, SSS will reset the adaptation itself. Or you may select EGS or VTG (I don't remember which one), and you will see 'reset adaptation' (something like that) to select.

Yes, I saw this fault in my x too. You need to re-code your IKE.