LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Mercedes Benz >> 2025 >> eSprinter Base, _NA_ >> Repair and Diagnosis (Single Page) >> TMC Recommended Practices >> Onboard Vehicle Electronics >> RP 1210D - Windows (TM) Communication API >> RP 1210D - Windows(TM) Communication API >> RP1210_GETHARD WA RESTATUSEX () >> Notes
April 5, 2026: LEMON Manuals is launched! Read the announcement.

RP1210_GETHARD WA RESTATUSEX (): Notes

This function was added to address the inadequacies of the RP1210_GetHardwareStatus  function when it came to generic CAN and other hardware channels. The RP1210_GetHardwareStatus  function was "protocol centric" meaning the user application asked information about a specific protocol without regards to the channel it was attached. With the RP1210_GetHardwareStatus  function, there was no way to find out the correct status of (as an example) J1939 if it were connected to more than one CAN channel.

Vehicle networks are starting to use more than one CAN channel and TMC expects this trend to continue. Any CAN-based protocol could be connected to any CAN channel, and at any speed. To accommodate this, there was no easy way to "add" to RP1210_GetHardwareStatus  to get the desired result; therefore, this function was added.

An application must have at least one successful connection to the VDA before the function will return valid values.