Inadequately Documented: Subscribe ALL Responses.

[awneil]

Looking at ADL User Guide v6.21:

The examples at the end of the “Outgoing Commands” section show “*” used to specify the subscribed responses

@ADL User Guide v6.21

// function 1
void function1(adl_InitType_e adlInitType)
{
  // We send ati and subscribe to its responses
  adl_atCmdSend("ati",
     (adl_atRspHandler_t)ATI_Response_Handler,
     "*",
     NULL);
}

The examples do not explain the meaning of “*” here, and the descriptions of the API calls don’t even mention it at all.

One is left to guess that it means, “all responses”

One is also left wondering whether it might be usable as a “wildcard” in match strings…?

[yuantuh]

I also guess “*” means all responses and it should be documented. ADL is throwing many black and white boxes to OAT app developers. It would be nice adding a global event hook, similar to Window32 WinProc. OAT is not a embedded real time operating system. It is impossiable for OAT to catch all events/responses. For example, Q26xx/ex, OAT suppresses part of ARM946 power and is hardly to use in real-time system from my posonal point of view.

[awneil]

https://forum.sierrawireless.com/t/cant-configure-uarts-in-7-4-0-a-and-above/4393/8

[awneil]

@awneil

The examples do not explain the meaning of “*” here, and the descriptions of the API calls don’t even mention it at all.

No change - one is still left to guess that it means, “all responses”

whether it might be usable as a “wildcard” in match strings…?

remains unanswered.