When configuring your Signature for a deployment by using custom commands, the configuration is verified when sending the SAVE command. If SAVE is not used, the deployment plan will be validated when sending the START or DEPLOY command. If there is anything wrong with the deployment plan, i.e. some of the parameters are entered with values outside their specific range, an ERROR will be returned. To get more details about why the error occurred, use the GETERROR command. Invalid configurations return the error with limits directly, so that each subsequent error can be handled until a valid configuration is achieved.
For example, if entering SETPLAN,MIAVG=5000, you will receive an OK. But when saving or deploying, you will receive an ERROR. When following up with the GETERROR command, you will receive the following:
134,"Invalid setting: Plan Profile Interval","GETPLANLIM,MIAVG=([1;3600])"
which indicates that the measurement interval must be within 1:3600 seconds and you have to go back and reconfigure this before you can proceed.
The valid range for the various arguments can also be retrieved by using the GETxxxLIM commands where xxx is the command you want the limits for. For example, if you need the limits for all arguments associated with the SETAVG command, you send the GETAVGLIM command. You can also retrieve the limits for one specific argument by including this when sending the GETxxxLIM command. As in the example above when you are configuring the measurement interval for the average measurements, you can get the valid range beforehand by sending the command GETPLANLIM,MIAVG.
More details can be found in the AD2CP Integrator's Guide.