In Z-Wave, some examples of multichannel devices are 

• A power strip with multiple binary switches
• A multisensor device with, for example, temperature, light, heat sensor etc.
• A composite device with multiple functionality

In order to communicate with these devices with multiple endpoints, multichannel encapsulation is used. 

Note, when adding devices of this type in the PC controller, it is necessary to hit the "Node Info" button to see all the endpoints.

Typically, the root device is mapped to endpoint 1 to allow some functionality with controllers that do not support multichannel encapsulation.

When Z/IP gateway communicates with multichannel devices the source or destination end point fields are non-zero in the COMMAND_ZIP_PACKET command.

In depth information about multichannel communication can be found in: https://www.silabs.com/documents/login/application-notes/APL12955-Z-Wave-Multi-Channel-Basics.pdf

MicroRF Link can be used to debug background noise or power supply interference problems. It is the 500 series equivalent to RAIL on the 700 series.

Refer to https://www.silabs.com/documents/login/user-guides/INS12880-Micro-RF-Link-User-guide.pdf as a guide.

Once the MicroRF firmware is loaded to a 500 series device, the serial interface can be used to issue commands.

Some example use cases are:

1. Use the rxsweep command to do a spectrum analysis (refer to table 3 in the above document to set the correct frequencies). For example for EU frequencies, set start freq to 86800kHz, stop frequency to 87000kHz, and bandwidth to >1000kHz.

:rxsweep
Enter start freq?
868000kHz
Enter stop freq?
870000kHz
Enter step size?
1000

2. Receive/demod frames (like a crude Zniffer)

:f
Enter freq?
869850kHz (h)ighside/(l)owside? h Baudrate 40k(4), 9.6k(9), 40k & 9.6k(b), 100k(1)?1
:rx a 

3. Block a freq using the transmit carrier command

: tx c

The Z-Ware C API allows for OTA updates of devices. This article provides an example of how to use it.

zwif_fw_info_get() should first be called to find information about the device and then zwif_fw_updt_req() should be called to perform the update. Each of those functions has callbacks that must be implemented.

The example provided is based on the existing bin_switch demo. It finds the first binary switch node and then allows that node to be updated by adding an additional menu option to do so.

Two places in the code were modified from the plain bin_switch demo. Inside the bin_sw_intf_get() function an additional option to find the firmware update interface was added. The callbacks were added and the main function was modified to add menu option 3 to perform the update.

To run the demo make sure you have a firmware image (.gbl or .otz file) for the binary switch end device example in the same directory as the executable.

Or, on the Launcher panel, click the hammer icon next to your account. See pic below.

Regards,

Tony