Configuring the Communications Database for the DUT Tutorial

This topic describes how to configure the communications database for the Device Under Test (DUT).

The Communications Database for the DUT measures the delays on the communications framework. To create a Communications Database configuration it is necessary to know:

  • the device to test

  • the bearer to use as a test channel

  • the bearer to use for the control channel, if the control channel is in use.

It is not necessary to change the configuration of Communications Database if it is already configured by a previous test run on the DUT and an existing test channel is in use.

  1. To configure the hardware reference board, the NetPerftest suite is distributed with a set of sample communications database. This sample configuration is stored in %EPOCROOT%epoc32\tools\netperf\data. The configuration file can be in one of the two formats, XML or CFG. An XML file is a standard Communications Database configuration file. This file is recommended for ced, as the XML interface performs more validation than the CFG interface.

  2. To adapt the communications database configuration to your device, use the export command ceddump on the DUT.

  3. To insert the NetPerf Delay Plug-in, declare the delaymeter protocol in the protocol table:
    
    ############################################################
    ## ProtocolTable
    ## 
    [ProtocolTable]
    ## .. existing sections...
    
    ADD_SECTION
    # COMMDB_ID = 11   [ the ID should be 1 more than the highest existing value ]
        Id=11
        Name=delaymeter
        ProtocolUid=271003463
        FIELD_COUNT=3
    END_ADD
    

  4. To configure the communications database manually, use the ced utility:
    
    ced -I <config_file_name>
    
    The command ced creates a log file c:\ced.log. The argument config_file_name is the full path to the configuration file. This is done with the XML or CFG interface. To confirm the successful configuration, check the log file that contains the word "SUCCESS " in the last line. If a ROM is built for the automated tests, then it replaces the Communications Database settings automatically.

  5. To set up a connection on the Test Controller PCrequires administration rights. The sample configuration files that contains the common connection types NT-RAS and Ethernet needs to be configured on the Test Controller PC and Net Monitor PC.

  6. To establish a connection, use the "ping " command. Ping the Test Controller PC from the DUT first and ping the DUT from the Test Controller PC.
Related concepts
Network Performance Test