Home/Support/Support Forum/Remote WR command locks up remote DigiMesh modem until it is power cycled.

Remote WR command locks up remote DigiMesh modem until it is power cycled.

0 votes
"Function": XBee Pro DigiMesh 2.4
Firmware Version: 8073

I have been trying to set the channel number of remote devices using remote AT frames, i.e. 0x17 type frames in API mode. Having had many problems with many combinations of remote CH, WR, using the "apply changes" flag, and AC itself, I settled on doing the following:
Send remote CH without the "apply changes" flag;
Send remote AC;
Put the local modem on the new channel;
Send remote WR without the "apply changes" flag;

I was finding that very often (but not every single time) no acknowledgement was received back from the remote modem when the remote WR command was sent. Since then, I've done further testing using X-CTU. I find I can happily send many remote AT commands (PL to get the power level, PL to set the power level, AC) and all works well until I send a remote WR. Sometimes "Status OK" is returned, but very often no response is received. Then when I send any remote AT command, a status of 0x04 "TX failure" is returned. This continues until I power cycle the modem by removing it from the board and replacing it.

I've not seen any pattern to when the remote WR command fails and when it succeeds.

The configuration for the local and remote modems are the same except for the Node ID. It is:
<setting command="CH">C</setting>
<setting command="ID">7255</setting>
<setting command="MT">3</setting>
<setting command="PL">0</setting>
<setting command="RR">3</setting>
<setting command="CA">0</setting>
<setting command="CE">0</setting>
<setting command="BH">0</setting>
<setting command="NH">5</setting>
<setting command="MR">2</setting>
<setting command="NN">3</setting>
<setting command="DH">0</setting>
<setting command="DL">0</setting>
<setting command="NI">T307 Hub</setting>
<setting command="NT">82</setting>
<setting command="NO">2</setting>
<setting command="CI">11</setting>
<setting command="EE">0</setting>
<setting command="KY"/>
<setting command="BD">3</setting>
<setting command="NB">0</setting>
<setting command="RO">3</setting>
<setting command="FT">BE</setting>
<setting command="AP">1</setting>
<setting command="AO">0</setting>
<setting command="D0">2</setting>
<setting command="D1">0</setting>
<setting command="D2">0</setting>
<setting command="D3">0</setting>
<setting command="D4">0</setting>
<setting command="D5">0</setting>
<setting command="D6">0</setting>
<setting command="D7">1</setting>
<setting command="D8">0</setting>
<setting command="D9">0</setting>
<setting command="P0">0</setting>
<setting command="P1">0</setting>
<setting command="P2">0</setting>
<setting command="PR">BF</setting>
<setting command="M0">0</setting>
<setting command="M1">0</setting>
<setting command="LT">0</setting>
<setting command="RP">28</setting>
<setting command="IC">0</setting>
<setting command="IF">1</setting>
<setting command="IR">0</setting>
<setting command="SM">1</setting>
<setting command="SO">0</setting>
<setting command="SN">1</setting>
<setting command="SP">C8</setting>
<setting command="ST">1388</setting>
<setting command="WH">0</setting>
<setting command="CC">2B</setting>
<setting command="CT">64</setting>
<setting command="GT">3E8</setting>
<setting command="DD">1</setting>

asked Sep 30, 2015 in RF Solutions and XBee by Graham Banks New to the Community (0 points)

Please log in or register to answer this question.