Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 15
Next »
01 - Objectives
Tips, Development Notes, Tricks, and other useful stuffs that come in handy are expected being here.
02 - Notes 2
| Item | Date | Keyword(s) | Comment |
|---|
| 02. Input Dialogs | | - Confirm_Input
- Confirm_Pic_Input
| Update Test Scripts
A. RunMode: Board1.
"Jig1-Current Consumption Check", 8810/8810P/6825, Board Level Test-Jig1
- Added Input Field for input current value.
Ex: typing "213.0", no unit(mA) required
B. RunMode: Board2, Long Wait Board Installation, + 20 seconds wait after Unify ID Input.
C.Run Mode: Production
a. Removed RS232 + Ethernet Test items. b. Printer Test: Fixed No Printed Patterns Issue |
01.Multiple Model Numbers but same instance | | Products.cs CreateModelNumberDictionary() |
// In case of Multiple nodes (name, name1, name2, ...+name(\d)*$), multiple aliases are allowed.
//Ex:
// < ModelNumber name = "5E.5BDA8.003" Qisda - prjcode - name2 = "9J.5BD03.0DQ" IDT_name3 = "ID88-8800" name4 = "80163002-003" >
// List : "5E.5BDA8.003" / "9J.5BD03.0DQ" / "ID88-8800" / "80163002-003"
// rule 01: 1st name string attribute "name=..." must have..
// rule 02: 2nd name and more attributes, " name#=..", optional. contain sub token "name"
// rule 03: based on rule 02, every attribute name must be exclusive to others.
//Ex:
// < ModelNumber name = "5E.5BDA8.003" Qisda - prjcode - name2 = "9J.5BD03.0DQ" IDT_name3 = "ID88-8800" name4 = "80163002-003" >
// Result: Automatically generate the nodes
// ModelNumber 1 = name ("5E.5BDA8.003")
// ModelNumber 2 = name ("9J.5BD03.0DQ"), aka name2, which contains "name".
// ModelNumber 3 = name ("ID88-8800"),aka IDT_name3, found "name" sub string.
//
|
| | Device Tree fm file with header From Limansa | |
