Turning transmitter on/off

[advantage-tim]

It would be great if you could turn the transmitter off, but keep the receiver on so that one base station could send a "wake-up" signal OTA.

[kbanks]

I think you misunderstand how SNAP Pro uses the radio...

Unlike some other 802.15.4 based wireless protocols, SNAP does not use any sort of "beacon". If a node has nothing to say, then it is not transmitting anything at all.

So if you do not want to transmit, don't make a rpc() or mcastRpc() call in your script.

In addition to sending its own messages (rpc calls), a node might need to transmit for the benefit of other nodes, but this can be turned off too.

If you do not want a node to forward multicast messages, clear the appropriate bits in the "forwarding" parameter.

If you do not want a node to participate in Mesh Routing, then set the "Mesh Override" parameter.

(These two options support scenarios like "mostly battery powered nodes, with a few wall-powered nodes acting as repeaters")

So, there is no need for a "tx off" command, you already have control over what gets sent.

We do have a function called rx(True/False), which allows you to turn the receiver off.

You are correct that we have no "wake up via radio signal" capability (and are not the first to request it). My point is that the nodes are probably not transmitting as much as you think.

Thank you for your suggestion.

[advantage-tim]

I was kind of thinking that's what it did, and a tech here made the suggestion and I was unsure of how the transmissions worked.

Thank you