Can Auto Baud And Non-Auto-Baud Applications

Another discovery in mid-2016 showed that even though the automatic baud detection mechanism has been in place in the RP1210 document for several years prior to 2016, there are still applications out there that are not using it. There are also older applications that may exist that did not use the auto baud detect mechanism.

To solve the potential connection issue, there will be a new RP1210 INI file variable added that tells the API to auto baud on CAN channels, even if not asked specifically to do so.

With AutoBaudCANByDefault  turned OFF (0):

• RP1210_ClientConnect ("J1939")  results in RP1210_ClientConnect ("J1939"),  a 250k connection to CAN1.

With AutoBaudCANByDefault  turned ON (1):

• RP1210_ClientConnect ("J1939")  results in RP1210_ClientConnect ("J1939:Baud=Auto") 

The variable AutoBaudCANByDefault  does not have any effect on a call to connect at a specific baud rate (i.e., "J1939:Baud=500000"  . It only applies if the variable is on, and that the VDA DLL did not see "Baud=" in the connection string. Only on INI protocol variables that have "auto" in ProtocolSpeed  parameter.

If the variable is turned on, and the API does the automatic baud detection, the process for detecting the baud rate is exactly the same as is defined in the previous section.

This variable applies to ALL CAN-based-protocols (i.e. ISO15765, J1939, IESCAN, PTC AN, SWCAN, FT-CAN, etc.).