EM357-MOD-RF-T datasheet(39/43 Pages) SILABS

39 / 43 page

8-1

EM35x Development Kit User Guide

120-4030-000E

8 Software Tools Overview

8.1

Using the EM357 Nodetest Application

The Nodetest Application replaces the Rangetest Application provided with earlier releases. This new

application supports a more advanced command parser and provides results in a more consistent, easy to parse

format.

The Nodetest application is pre-programmed on to the Radio Communication Modules (RCMs) included with your

EM35x Development Kit. The pre-built application image is also located at {stack installation

directory}\app\nodetest\nodetest.s37.

You may communicate with the serial interface of the Nodetest application using the methods described in

Chapter 6. Ensure that the serial port is configured for 115200 baud, 8 data bits, No parity, and 1 stop bit. By

default the InSight Adapter (ISA3) is configured in this way, but it can be adjusted in this manner:

•

Connect to the admin interface of the ISA3.

•

Issue the baud rate configuration comment for the pass-through UART (port 1): port 1 115200

The Nodetest application provides on-line help about the available commands that can be viewed by executing

the command “help”. All input parameters to Nodetest are specified in hexadecimal.

8.2

Running a Packet Error Test

A typical usage scenario for the Nodetest application is measurement of Packet Error Rate (PER). PER is defined

in 802.15.4 as the percentage of transmitted packets that are not detected correctly. The Nodetest application

provides two commands "rx" and "tx" that are designed to interoperate with the "receive" and "transmit"

commands from the EM250 Rangetest application.

PER measurement procedure:

Load the Nodetest application on two EM357 nodes.

Set the radio to the desired channel on both nodes with the "setchannel n" command where "n" is the

desired channel number in hex.

Issue the "rx" command on the first node.

Issue the "tx a" command on the second node. (This command will transmit 10 (hex a) packets of the

form required for PER analysis. For actual PER analysis, send 1000 or more packets.)

Observe the PER result in the third column of the "rx" command output, for example1:

> rx

{{(rx)} test start ('e'nd)}

#{{(rx)}

{num}

{seq}

{per} {lqi}

{rssi}{gain} {status} {time}

{length}}

{ {

1} {

0} {0x00} {-22} {0x31} {0x4000} {0x000F3716} {0x12}

}

{ {

2} {

0} {0x00} {-22} {0x31} {0x4000} {0x000F9FE6} {0x12}

}

{ {

3} {

0} {0x00} {-22} {0x31} {0x4000} {0x000008B6} {0x12}

}

1 This example may show different length packets than you see.

EM357-MOD-RF-T Datasheet(PDF) 39 Page - Silicon Laboratories

EM357-MOD-RF-T Datasheet(HTML) 39 Page - Silicon Laboratories

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43

Datasheet Download

Link URL