Script Editor and Tcl procedures
Custom scripts affect engine behavior using Tcl procedures. Configure these procedures to run at certain UPoCs (User Points of Control).
Tcl procedures within the engine
A Tcl Procedure Stream (TPS) lists Tcl procedures that are used in sequence. It uses the TPS binary to invoke the procedures in series with the correct arguments. This is the most prevalent form of UPoC Tcl code.
Trx ID determination decides a message’s transaction, as opposed to offset/length or variant. After determining the transaction ID, the translation thread translates and routes the message appropriately.
A XLT (translation) code fragment calls procedures that receive their input through a certain set of variables, and returns data through another set. Any values that parameters return are ignored.
Tcl procedures outside the engine
Two types of UPoC Tcl code are used outside of the engine for testing purposes:
- TPS-test end procedures
Uses end procedures to process messages produced by the Testing Tool. Used with hcitpstest.
- Route-test end procedures
Uses end procedures to process messages produced by the Testing Tool. Used with hciroutetest.