Specifications

4 Message Reference
26
phy_id
The physical ID for the DSI SPCI Board. This field must be set to the same value as the
board_id. (i.e., 0 … one less than the number of boards supported).
code_file
Null terminated string giving the filename of the code file to be downloaded to the
board.
run_mode
Number taken from the following table to indicate which protocols are to be run.
Note: It is only possible to activate protocols that have been licensed to run on the board by use
of a suitable license button.
Run Mode
Value
Run Mode
Mnemonic
Protocols selected to run on the board
1
DTI
Digital Trunk Interface only, no protocol software. This
mode does NOT require the use of a software license
button.
2
MTP2
MTP2 protocol only.
3
MTP
MTP3 plus MTP2 protocols.
25
ISUP-S
ISUP, small version, plus all MTP.
4
ISUP
ISUP, regular version, plus all MTP.
5
ISUP-L
ISUP, large version, plus all MTP.
26
TUP-S
TUP, small version, plus all MTP.
6
TUP
TUP, regular version, plus all MTP.
7
TUP-L
TUP, large version, plus all MTP.
See section 2.3.2 Capacity for details of the capacity for modules running on the DSI
SPCI Boards.
Status Response
The confirmation message (if requested) indicates success by status of zero.
No status values indicating errors are defined.
4.2.3 MGT_MSG_CONFIG0 - Board Configuration Request
Synopsis
Message sent to a board immediately after starting the code running to provide
protocol configuration parameters.
Note: When using s7_mgt, this message is generated by s7_mgt and must not be generated by
the user.