Page History

...

When performing a 'get' operation UspPa attempts to get all specified parameters using a single RDK bus message. This is more efficient than requesting each parameter individually, however it has the downside that if the 'get' of any single parameter fails, all fail (the RDK response message does not provide a partial response in this case). So if you try to get all parameters of an object using a a partial path, and get the CCSP_ERR_INVALID_PARAMETER_NAME error, you need to determine which one is causing the error. You can use the GET_GROUPED_PARAMETERS_INDIVIDUALLY and SET_GROUPED_PARAMETERS_INDIVIDUALLY defines in vendor_defs.h to change the behaviour of UspPa to request parameters individually, and determine which parameter is actually causing the problem. You can then omit this parameter from usp_dm_params.conf. For problems with set, you can consult the logs (obtained with -p option enabled) to determine which parameter is causing problems.

For problems with get use:

...

ERROR: [error-code] retrieving [parameter-name] ([textual-error-message])

For problems with set, you can consult the logs (obtained with -p option enabled) to determine which parameter is causing problems, or use 'UspPa -c set', to try setting each parameter in turn.

WARNING: No instances in Device.LocalAgent.Controller

...