The [VENDORINFORMATION] Section Of The Vendor INI File

Table entries in light blue/light green shading are optional. All other fields are mandatory and must be entered, or the VDA is not RP 1210-compliant.

[VendorInformation]	Indicates the start of the VendorInformation section. Field must not be empty.
Name=[string]	Name of vendor, and VDA being supported. Field must not be empty.
Addressl=[string]	First line of vendor mailing address. Field must not be empty.
Address2=[string]	Second line of vendor mailing address. Field must not be empty.
City=[string]	City of vendor mailing address. Field must not be empty.
State=[string]	State of vendor mailing address. Field must not be empty.
Country=[string]	Country of vendor mailing address. Field must not be empty.
Postal=[string]	Postal or zipcode of vendor mailing address. Field must not be empty.
Telephone=[string]	Telephone number to reach support. Field must not be empty.
Fax=[string]	Fax number of vendor. Field can be empty.
VendorURL=[string]	HTML link to vendor web site. Field can be empty.
MessageString=[string]	unique message string for the vendor DLL. Field can be empty.
ErrorString=[string]	unique error string for the vendor DLL. Field can be empty.
TimestampWeight=[number]	Weight, per bit, in microseconds of the timestamp. Field must not be empty.
AutoDetectCapable=[yes/no]	If API were capable of validating that the devices in this INI file are physically attached to the computer, the string would be "yes". Most APIs are capable of this feature. Field must not be empty.
Version=[string]	Where string reports the API version installed. This is in any format that the VDA vendor wants (i.e. Major.Minor.Subrelease-Build). This does not mark the version of RP1210 supported. Not being able to "mark" or "version" an INI file has resulted in incompatibility problems. Field must not be empty.
RP1210=[string]	Where string denotes the latest version of RP1210 supported [0, A, B, C, D]. If this parameter is present, -he developer can assume at least RP1210B is supported. Field must not be empty.
DebugLevel=[number]	This is an optional feature for a DLL provider. If the DLL does not have the capability of initializing in debugging mode, then DebugLevel=-l would be stated or this variable would not exist. This allows the API to be initialized in debugging/logging mode without having to re-compile and re-link source code for an application. This is very useful when an application seems to be misbehaving. The values to be logged depend on the #: -1 = Debugging is not supported by this API. 0 = No debugging to be accomplished. 1 = Only Connect/Disconnect/Error Messages 2 = Add RP1210_SendCommand calls 3 = Add all Sent Messages (with filtering) 4 = Add all Received Messages (with filtering) See the RP1210 section on Debug File Format. This field is optional; however, if this field exists, the Debug-File, DebugMode, and DebugFileSize variables must also exist.

DebugFile=[string]	When DebugLevel is greater than zero, the API will write debugging/log information to the file mentioned in this variable. The absolute path (disk/directory) for this file will be included in this variable. The file name should be unique as not to overwrite the log file of any other VDA vendors. Field can be empty if DebugLevel is set to -1 or does not exist
DebugMode=[number]	When DebugLevel is greater than zero, this variable describes how the DebugFile is to be written to: 0 = Overwrite (completely destroying previous contents) 1 = Append (write to the end of the file, keeping any previous contents) Field can be empty if DebugLevel is set to -1 or does not exist.
DebugFileSize=[X]	Maximum size in kilobytes that the debug file should be. The default shall be 1024 (1 megabyte) if this variable is not defined. Field can be empty if DebugLevel is set to -1 or does not exist.
NumberOfRTSCTSSessions=[X]	An integer representing the number of concurrent RTS/CTS transport sessions that the API supports per client. This is above and beyond the 1 BAM, 1 RTS/CTS that J1939 calls for. The default will be the J1939 default of 1. Field must not be empty unless the VDA does not support J1939.
CANFormatsSupport-ed=[l],[2],[3],[4],[5]	This adapter allows the user to connect to the CAN data bus using the connection formats as defined in RP1210_ClientConnect. Field must not be empty unless the VDA does not support CAN.
J1939FormatsSup-ported=[l],[2],[3],[4],[5]	This adapter allows the user to connect to the J1939 data bus using the connection formats as defined in RP1210 ClientConnect. Field must not be empty unless the VDA does not support J1939.
J1939Addresses=[X]	How many J1939 addresses does the API support. This must be a number from 1 to 16. If this variable does not exist, an application should assume the API can only support 1 J1939 address. Field must not be empty unless the VDA does not support J1939.
CANAutoBaud=[TRUE\|FALSE]	If the API is capable of handling CAN automatic bit rate detection using the RP1210_ClientConnect ("PROTOCOL:Baud=Auto") connect format. If this variable does not exist, the application should assume the API cannot detect baud rate and the app should query the user for what speed to connect at. Field must not be empty unless the VDA does not support CAN.
J1708FormatsSup-ported=[1],[2]	This adapter allows the user to connect to the J1708 data bus using the connection formats as defined in RP1210_ClientConnect. Field must not be empty unless the VDA does not support J1708.
ISO15765For-matsSupported=[1],[2]	This adapter allows the user to connect to the ISO15765 data bus using the connection formats as defined in RP1210_ClientConnect. Field must not be empty unless the VDA does not support ISO15765.
AutoBaudCANConnectTime-out=XXXX	This variable allows the user or technical support staff to adjust the automatic baud rate detection timeout on RP1210_ClientCon-nect () in the field. The default for all VDA vendors will be 3000 milliseconds (3 seconds) which is sufficient if the databus is active. This field is optional.
AutoBaudCANByDefault=[TRUE/FALSE] or [1/0] Where 1=TRUE, 0=FALSE	To solve potential connection issues with an application that is not using Baud=Auto, a VDA vendor can use this field to turn on "Baud=Auto" by default even if not asked specifically to do so. This field is optional. Changed from 1/0 to either TRUE/FALSE. Either acceptable.
Devices=[d1],[d2],...,[dn]	The d's represent the device IDs for the devices supported by this vendor API; each d is a number between 0 and 255; the device IDs are delimited by commas with no spaces in between. Field must not be empty. Each entry must point to a valid DeviceInformationXXX section.
Protocols=[p1],[p2],...,[pm]	The p's represents the identifiers for the protocols supported by this vendor; each protocol identifier is a number between 0 and 255; the protocol identifiers are delimited by commas with no spaces in between. Note that, unlike the device IDs, the protocol identifiers have no significance in the application software other than to concoct unique tokens for the different protocols supported by the vendor. Field must not be empty. Each entry must point to a valid Protocol InformationXXX section.