Unexpected Vehicle Interface Adapter Disconnect

There have been differences in how a VDA disconnect was managed among VDA vendors. RP1210 indicates that the API should return Error Code "142 ERR_HARDWARE_NOT_RESPONDING" to the calling application whenever a hardware error occurs. However, the reaction of VDAAPI's differ greatly when hardware is accidentally disconnected.

In severe cases the client application may be required to do the following:

• Notify the user of the problem and ask the user to re-instate the hardware.
• Disconnect from the API by using RP1210_ClientDisconnect (  ).
• Continue calling RP1210_ClientConnect ()  until successful.
  • Or allowing the user to click Connect when the hardware is reinstated.
• Set up all RP1210 variables and filters again.
• Reclaim J1939 addresses (if using J1939).
• Other protocol specific setup procedures such as filters required, etc.

Vendor APIs that require no intervention retain all client identification and filter states and will verify ownership of all previously J1939-claimed addresses upon correction of the disconnect. This type of API does not require the recovery method described above. See also the RP1210 function RP1210_GetLastErrorMsg ()  and Section 10.2.