Xbee3 connection to Remote Manager when DO Bit 0 (Remote Manager support) is disabled

Question

By default, the DO field on an Xbee3 is set to 1.

https://www.digi.com/resources/documentation/Digidocs/90002258/#reference/r_cmd_do_cellular.htm%3FTocPath%3DAT%2520commands%7CNetwork%2520commands%7C_____8

However, at the bottom of that page there is a note about power saving mode:
"Note We strongly recommend that you clear bit 0 (Enable Remote Manager) if you set bit 3. If not, the connection that the device retains with Remote Manager causes the cellular component to spend very little time in low power, negating the value of selecting that feature."

The consequences of disabling this bit are not clear though. If we do clear bit 0 for improved power savings, will we be able to use Remote Manager at all down the road?

Specifically, if there is a reason for us to need to update python files, or change settings, can we still use Remote Manager to send a RCI packet to enable this bit? Such as this:
https://www.digi.com/resources/documentation/Digidocs/90002258/#tasks/t_rm_restore_persistent_tcp.htm


Or, does disabling this completely remove any ability to use Remote Manager at all?

Thanks!

Answer 1

Disabling this bit will keep you from being able to use Digi Remote Manager. But if you set MO to 0, you should be able to use SMUDP to make a connection request from the Digi Remote Manager. Now as I have not tested this, I would suggest you do to make sure before you deploy.

Comments

Thanks for the response. Yes, I have been able to use Remote Manager to update settings / files remotely when MO bit 0 is cleared, and DO bit 0 is set (Remote Manager enabled).

I am more specifically asking if there is any mechanism I can use to remotely change the DO setting if Remote Manager has been disabled (DO bit 0 cleared)?

As an example, would it be possible to send a SMS CLI (or an SM/UDP CLI) message to change DO to enable Remote Manager?

---

No, if DO = 0 it will not work.