OSD modes
To set a OSD mode, enter PT/MR equal to the desired mode number. Below is a list defining what the label field of the active provider will display for each OSD mode. Default mode after reset is 2.
Mode 0: Label mode. The label of the providers as edited in the eeprom file is displayed for all providers.
Mode 1: Version Mode. Slipstream version string is displayed, e.g. "Slipstream 1.00"
Mode 2: Key in use mode. Displays the hexadecimal key representation of the used key on the last active provider. Hence, if active channel on the STB is coded and decrypted the key in use will be shown. If the channel is coded but not decrypted the string "Key 0x unknown" will be displayed, where x is the hexadecimal representation of the key index (8,9,A,..,F).
Mode 3: Entities in use mode. Displays the identity of the active issuer and provider entities, e.g. "FFF400-010C30".
Mode 8-15: Specific key mode. Displays the specific key stored in eeprom selected by the mode number. The key is displayed regardless of if it's a correct key or not. Please note that all numbers are decimal. Dec relates to hex as: 8=8,9=9,10=A,11=B,12=C,13=D,14=E and 15=F.
For all OSD modes except for mode 0, the Subscription Information menu will present key history and information about how opkeys have been updated. When the card is taken in use it is advised to first perform a formatting of the eeprom section containing the information about the opkeys, the metadata section. This is described in Commands below.
The Subscription Information screen for the selected provider will contain a list of 8 rows that will look something like in this example:
START DATE
STOP DATE CLASS THEME LEVEL
01/01/1980 01/01/1980 - 77 08
01/01/1980 01/01/1980 - 77 09
09/02/2003 10/02/2003 - 115 110
01/01/1980 01/01/1980 - 77 11
10/02/2003 01/01/1980 - 115 12
01/01/1980 01/01/1980 - 77 13
21/01/2003 24/01/2003 - 200 14
01/01/1980 01/01/1980 - 77 15
START DATE => The date at which the opkey was first updated.
STOP DATE => The date when the opkey was last used. If START DATE > STOP DATE this means the updated key is a "next" key.
CLASS => not used.
THEME => Information about how the opkey was updated. Look at THEME as a three digit number "xyz":
Digit Information Description/encoding
x : Update method 0 => AU using SA addressing, 1 => AU using UA addressing, 2 => Remote update
y : Issuer/provider 0 => AU over provider, 1 => AU over issuer. Only relevant for AU updates.
z : mkey Key index of used mkey. Only relevant for AU updates.
LEVEL => Index of the opkey about which the row gives information. Also, if the opkey is in use by the active channel, either 100 or 200 is added to the key index. 100 + index mean that key is in use and the key is correct. 200 + index mean that key is in use but the key stored in card is not correct.
So, looking back at the example screen above with the 8 rows of key information data we can tell that:
The key in use by the active channel is opkey 10, and it is successfully used for the decryption of the picture. As opkey 10 is in use now the STOP DATE tells us today's date is the 10:th of February.
Opkey 10 was AU updated the 9:th of February using UA updates over issuer with mkey 5.
Opkey 12 was AU updated the 10:th of February (today) using same method as for opkey 10. Since START DATE > STOP DATE for opkey 12, this means it's a "next key" not taken in use yet.
Opkey 14 was updated by remote control.
Some STBs sort the rows on basis of dates. This means that the order in which the rows is presented may differ from this example and when the dates changes. Remember to check the LEVEL value to be certain for which opkey each row applies to.
Ursprungligen postat av pepsi_badder
Tack för koderna T-Bird, dom funkar alldeles utmärkt även i Nässjö.
Behörigheter för att posta
Svara med citat
