and then use the AT command as “AT+T2RUSR=1234,abc,123”, i get ERROR. I think it is because first and third parameters are numeric only (if I mix the numbers with letters, I get an OK). I put those values into “ascii var[50]” variables using
I have discovered a new fact about this thing. I have one command which uses 1 parameter, an another one which uses 3. If I use a numeric value on the first one, I get an error. If I use at least one non numeric value on the second one, I get an OK. The second one is just fine, because one of the fields I want to store must have a few chars. But the first one is still a problem. Could someone help me with the adl_atCmdSubscribe and its handler? Thanks again
After a few days, i have found the answer to part of the problem. The trouble with the command using 1 parameter is solved using 0x0011 as an option. It’s subscription would be as follows:
The 3 parameters one is still giving some trouble. I have tried using 0x0033, but that is far from solving the problem. Instead, it does not accept any number of parameters (I have tried from 1 to 6 or 7). I have also tried to use 0x0031 and 0x0032 but the same problem appers. Anyone has an answer for this part? The subscription I’m using is like this:
Then, if there are any non-numeric parameters, they have to be quoted:
That should do it, I hope.
I’m using the ADL_CMD_TYPE_ROOT more and more often for exactly these reasons… the quotes required around negative numbers and strings are pretty annoying, and I always forget to change subscription when adding new, optional, parameters to my AT commands.