Applications Doing Auto-VDA-Detection (Not Recommended)

Some application vendors have attempted, and failed, in algorithms to automatically detect the adapter that is physically attached to the computer. The logical (versus physical) connection to a VDA has resulted in VDA vendor technical support calls. Some API's are just not capable of validating a specific device is connected to the PC and some require that the VDA be powered up and connected to the vehicle prior to performing an RP1210_ClientConnect (  ).

• A new variable will be present in a vendor INI file that will tell the application developer whether or not that the associated API devices in that INI file are capable of being "auto-detected". See the "Auto-DetectCapable"  variable in the INI file section of this document. This was an RP 1210B addition.
• If you are writing an application and this variable is not present in an INI file, then it is highly recommended not trying to go through the auto-detect process with devices from that INI file.
• Auto-detection is strongly discouraged and it should only happen at the explicit action of a user. Query messages sent by auto detect functions scanning all interfaces can upset unrelated devices connected to the computer, such as USB printers, USB keyboards, and USB mice.