Example INI Files With Various Protocol Speeds And Auto Baud

Below is an INI file section showing that both 250k, 500k, 666, and 1 Mb speeds are supported for both CAN and J1939, and that the adapter is capable of doing automatic speed detection. Also shown is the example for CAN which supports 125, 250, 500 666, and 1 MB.

If an application knows that there is a possibility that it might be used on a vehicle with a 500k J1939 connection, that application should warn the user that connecting the VDA to a 500k databus may cause adverse affects f the keyword "Auto" is not in the CAN ProtocolSpeed parameter. The application would then prompt the user for the speed to connect at based on the speeds supported by that VDA (250k is the default baud rate for CAN and J1939).

NOTE: Applications should never issue a RP1210_ClientConnect ("Protocol:Baud=XXX") to a CAN/J1939 databus unless XXX is the known baud rate. Developers must be diligent in application coding when there is a possibility that an application could create CAN error frames. Using "Baud=Auto" is the desired method for connecting to an unknown CAN-based databus.

A new variable [VendorInformation]. CANAutoBaud=[TRUE/FALSE] has been created in the vendor INI file. This will allow applications to know if the VDA API supports auto baud detect.