There should not be any problem relating to the response not being captured in the response handler for the command created using adl_atCmdCreate () API. Please ensure that you have specified the correct response handler and the command is created by specifying a “*” for the variable list (which represents the responses to be subscribed).
I have not experienced the problem when the response to the command created using adl_atCmdCreate () API is not received in the command handler. All the responses to the created command will be received in the command handler until a terminal response (for e.g. “OK”) is received.
If your command is such that it sends a response after sending a terminal response too, that response will not be received in the command handler.
For instance, let us assume that you have a SIM which fails (+CME ERROR :13) when you try to write to a particular location in it. To check this scenario, you create AT+CPBW command from within your Open-AT application and subscribe to all the responses (hoping to get a +CME ERROR: 13 response too when the SIM fails).
As you know, that response to the AT+CPBW command will be an immediate “OK”. THe actual write will be performed after some time. In other words, a terminal response (“OK”) is received before receiving a +CME ERROR: 13 response. However, a +CME ERROR : 13 will not be received by the Open- AT application. This is because, once you get a terminal response (e.g. OK), the response handler for the command is deregistered by ADL and it does not receives any more responses.
However, if the problem faced by you is not similar to this, then you should check the code where you are creating the command.
I think that must be the place where some error has creeped.