Home/Support/Support Forum/What are the reasons an API Remote AT Request to toggle DOx state gets Status Error 01 response?

What are the reasons an API Remote AT Request to toggle DOx state gets Status Error 01 response?

0 votes
Units are XBP24

In XCTU Version: 6.3.0 Build ID: 20151110-8

toggling the DOx via Radio Configuration works fine.

Using the Packet (Frame) Send in Terminal Mode results in the below:

RQS: Remote AT Command Request (API 1)

7E 00 10 17 01 00 13 A2 00 40 BB 3F 74 FF FE 02 44 30 35 DC

Start delimiter: 7E
Length: 00 10 (16)
Frame type: 17 (Remote AT Command Request)
Frame ID: 01 (1)
64-bit dest. address: 00 13 A2 00 40 BB 3F 74
16-bit dest. address: FF FE
Command options: 02
AT Command: 44 30 (D0)
Parameter: 35
Checksum: DC

RSP: Remote Command Response (API 1)

7E 00 0F 97 01 00 13 A2 00 40 BB 3F 74 FF FE 44 30 01 92

Start delimiter: 7E
Length: 00 0F (15)
Frame type: 97 (Remote Command Response)
Frame ID: 01 (1)
64-bit source address: 00 13 A2 00 40 BB 3F 74
16-bit source address: FF FE
AT Command: 44 30 (D0)
Status: 01 (Status Error)
Checksum: 92
asked Jun 19, 2016 in RF Solutions and XBee by BallardHill New to the Community (3 points)
edited Jun 19, 2016 by BallardHill

Please log in or register to answer this question.

1 Answer

0 votes
 
Best answer
Look at the value you are trying to set it to. The value "35" is an invalid. That is why you got Error.
answered Jun 20, 2016 by mvut Veteran of the Digi Community (12,657 points)
selected Jun 29, 2016 by BallardHill
Also TX Failure using Hex values of 00 and 01
mvut, thank you for your response!

Set in the ASCII panel of the Frames Generator as "5" (without the double quotes), this is intended to denote the DO High [5] value

Using the Hex Panel and testing with 35, 34, 31, 30, 01, and 00 results in same TX Failure.

What would be an example valid Hex Value?

Remember - toggling the DOx via Radio Configuration works fine.

DOH!  Using Hex 04 and 05 works ...

Missed where that's documented in the Packet Definitions
...