...
| No Format |
|---|
radioTest app, ver 1.2.0.1
SmartMesh IP stack, ver 1.4.1.8
> testtx
Usage: testtx <testType> <chanMask> <power> <stationId> <repeatCnt> ...
... <numSubtests> {<pkLen> <delay> ...}
> testtx 0 0x0001 8 255 100 1 100 1000
Test started...
>Tx completed
> testrx
Usage: testrx <chanMask> <time (s)> <stationId>
Channel mask is in hex, e.g. 0x0001 selects channel 0 (IEEE ch 11)
>testrx 0x0001 100 255
Starting rx on channel 0
Rx completed
> stat
Radio Test Statistics:
OkCnt : 99
FailCnt : 1
> mshow rstat
OkCnt : 99
FailCnt : 1
AveRSSI : -55
AveLQI : 0
|
...
The 03-radioTest sample application uses the Helper Modules to initialize the CLI Module and for interaction with the local interface. It passes JOIN_NO in the fJoin flag when initializing the local module in the loc_task_init() to prevent the local module from attempting to join, as the radio can only be tested when the mote is in either the idle or radioTest state. It has a single dummy task that does nothing but wait. The CLI command handlers parse the command arguments and call helper functions to run the receive and transmit tests. It contains a function to check if the mote is idle - all radiotest functions will return an error if called while the mote is in an incorrect state, so errors can be handled inline if desired.