Usually the controlling device function (ECSC) for the ECSP gets hosted on two redundant devices. As of now in the TRDP library, the only option for the user application is to completely perform the tau_initEcspCtrl() or tau_terminateEcspCtrl() in case there is a redundancy switchover. This is needed because currently the publishing of the PD comId 120 is done with redId 0 and we cannot allow the "follower" controlling device to continue sending the PD comId 120 with possible outdated payload.
The proposal is that the tau_initEcspCtrl() could be extended with an argument of "redId". If the user wants to host the controlling function on redundant devices, user can call the tau_initEcspCtrl() on both the devices with non-zero "redId" argument. Whenever any redundancy switch-over happens, the user anyway calls the tlp_setRedundant() to control it, and hence the PD 120 could also be controlled that way indirectly. The user need not do complete init and terminate of the ECSP control function on every redundancy switchover.
Committed the updates for this in r2385