Copyright 2017. All rights reserved. Advantech Co. Ltd.
Page 63
For example, run DUI command with multiple parameters:
http://127.0.0.1:80/start?serv_id=4&func_id=2&bus=0000:02:00.0&vendor_id=0x
8086&device_id=0x1533&revision_id=0x03&
In the CFG folder, it’s suitable to create multiple configure files for different SKU or test sets.
The CFG file consists of two parts:
1
Common configuration area, including static info, FW version, IP and port number for
HTTP access.
2
Custom configuration area, each row is a diagnostic item. It can be interpreted as
following format:
[Item] [Prefix] [Action] [Serv_id] [Func_id] [Wait time]
["[Para1_name]=[Para1_value]"…]
. And each field is shown below:
[Item]
DUI_<test item number>, the start prefix string as "DUI_". The number
increases sequentially.
[Prefix]
DUI test item description in shorten name, and it is unique in CFG file. Note
that underline "_" is used instead of space word.
[Action]
Run - It will run this test.
No - It skip this test item during the total DUI diagnostic test.
[Serv_id]
DUI service id. Described in
Section 3.10.3.3.
[Func_id]
DUI function id. Described in
Section 3.10.3.3.
[Wait time]
Max waiting time for this run of test. In units of second. Fail verdict if
timeout.
[Parameter_name]:
DUI test parameter name (from 1~N, it depend on component verification
request). Please refer to
Section 3.10.3.10.
[Parameter_value]
DUI test parameter value (from 1~N, it depend on component verification
request). Please refer to
Section 3.10.3.10.
Here are some notes:
1
DUI daemon MUST run first, no matter in foreground or background. Please check
Section 3.10.5.1
2
If the strings contain a space character among them, please use “%20” instead of space
character “ ”.
