Specifications

mcastRpc(6, 2, 'reboot') will ask all nodes within 2 hops and belonging to group 2 (0x0002
or 0000000000000010b) or group 3 (0x0004 or 0000000000000100b) to do a reboot().
This function normally returns True. It returns False only if it was unable to attempt the Remote
Procedure Call (for example, if the node is low on memory, or the RPC was too large to send).
If this function returns True, it does not mean your RPC request was successfully received (SNAP
multicast messages are unacknowledged).
If you need confirmation that the remote node executed your request, it needs to come from the remote
node. Refer to the callback() function for one method of doing this.
mcastSerial(destGroups, ttl) – Setup TRANSPARENT MODE
SNAP TRANSPARENT MODE is covered in section 5.
When you want the outbound data to be sent to multiple nodes, use this function.
Parameter destGroups specifies the multicast groups that are eligible to receive this data. Parameter ttl
specifies the maximum number of hops the data will be re-transmitted (in search of interested nodes).
Note that because the received serial characters will be sent using (unacknowledged) multicast
messages, multicast TRANSPARENT MODE is less reliable than unicast TRANSPARENT MODE.
If you want the received serial characters to go to only one specific node, you should use function
ucastSerial() instead.
This function does not return a value.
monitorPin(pin, isMonitored) – Enable/disable monitoring of a pin
This function can be used as an alternative to function readPin(), or in addition to it.
Parameter pin specifies which IO pin to monitor. Parameter isMonitored makes the pin be monitored
when True, or ignored when False.
“Monitoring” in this context means “sampled periodically in the background,” and only makes sense
with pins previously configured as digital inputs via setPinDir().
You could monitor an output pin, but the changes you got notified about would be changes that you
caused (via writePin()).
When monitored pins change state, a HOOK_GPIN event is sent to the SNAPpy virtual machine. If
you have assigned a HOOK_GPIN handler (using the “set hook” capability described in section 5),
Page 62 of 202 SNAP Reference Manual Document Number 600-0007K