I have been trying to send remote AT commands using the API mode and XBee PRO with the latest Digimesh firmware and some previous versions (8062 and 8067).
While requested nodes are switched on and reachables, the remote AT command responses work like a charm. However, if the node is not reachable, the AT command error does not work properly. Although the error code is received indicating TX error (0x04), both Frame Id and AT command name in responses do not match with the requested parameters. Furthermore, these values change with every request (even if it is the same).
Is this proper behaviour documented elsewhere or it is just a bug in the Digimehs firmware? At following you can find an example of this weird behaviour (extracted from X-CTU program).
Frame sent: <frame_payload>7E000F17270013A20040078BC0FFFE006264B7</frame_payload>
Frame received: <frame_payload>7E000F97E70013A20040078BC0FFFE143F04E6</frame_payload>
Thanks in advance.