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

**URL:** <https://forums.digi.com/t/what-are-the-reasons-an-api-remote-at-request-to-toggle-dox-state-gets-status-error-01-response/16951>\
**Category:** XBee & XBee Gateway\
**Tags:** response, xbee-pro, api\
**Created:** [June 19, 2016, 12:36pm UTC](https://forums.digi.com/t/what-are-the-reasons-an-api-remote-at-request-to-toggle-dox-state-gets-status-error-01-response/16951 "2016-06-19T12:36:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![BallardHill](https://avatars.discourse-cdn.com/v4/letter/b/c37758/32.png) [@BallardHill](https://forums.digi.com/u/BallardHill)\
**Post date:** [June 19, 2016, 12:36pm UTC](https://forums.digi.com/t/what-are-the-reasons-an-api-remote-at-request-to-toggle-dox-state-gets-status-error-01-response/16951/1 "2016-06-19T12:36:14Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [June 20, 2016, 9:29am UTC](https://forums.digi.com/t/what-are-the-reasons-an-api-remote-at-request-to-toggle-dox-state-gets-status-error-01-response/16951/2 "2016-06-20T09:29:21Z")

</div>

Look at the value you are trying to set it to. The value “35” is an invalid. That is why you got Error.

---

<div class="post-metadata">

**Author:** ![BallardHill](https://avatars.discourse-cdn.com/v4/letter/b/c37758/32.png) [@BallardHill](https://forums.digi.com/u/BallardHill)\
**Post date:** [June 29, 2016, 9:02am UTC](https://forums.digi.com/t/what-are-the-reasons-an-api-remote-at-request-to-toggle-dox-state-gets-status-error-01-response/16951/3 "2016-06-29T09:02:37Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![BallardHill](https://avatars.discourse-cdn.com/v4/letter/b/c37758/32.png) [@BallardHill](https://forums.digi.com/u/BallardHill)\
**Post date:** [June 29, 2016, 8:58am UTC](https://forums.digi.com/t/what-are-the-reasons-an-api-remote-at-request-to-toggle-dox-state-gets-status-error-01-response/16951/4 "2016-06-29T08:58:31Z")

</div>

Also TX Failure using Hex values of 00 and 01