Discussions avec Thomas Chust : SY_LFR_N_ASM_P devrait être minimum à 4 et un multiple de 4.
Or il est possible de demander SY_LFR_N_ASM_P = 0, SY_LFR_N_ASM_P=1 et SY_LFR_N_ASM_P=2 qui sont acceptés :
15:02:49.807246, TM_LFR_PARAMETER_DUMP, CCSDS_VERSION_NUMBER = 0, PACKET_TYPE: TM_PACKET = 0, DATA_FIELD_HEADER_FLAG: WITH_HEADER = 1, PROCESS_ID: RPW_PID_2 = 76, PACKET_CATEGORY: DUMP = 9, (PACKET_ID=0xcc9), SEGMENTATION_GROUPING_FLAG: STANDALONE_PACKET = 3, SEQUENCE_CNT=7, (PACKET_SEQUENCE_CONTROL=0xc007), PACKET_LENGTH=29, SPARE_1=0, PUS_VERSION = 1, SPARE_2=0, SERVICE_TYPE: HOUSEKEEPING_AND_DIAGNOSTIC_DATA_REPORTING = 3, SERVICE_SUBTYPE: HK_PARAMETER_REPORT = 25, DESTINATION_ID: GROUND = 0, TIME=0x800004d9750c, PA_LFR_HK_SID: LFR_DUMP_SID = 10, SPARE=0x0, SY_LFR_BW=1, SY_LFR_SP0=0, SY_LFR_SP1=0, SY_LFR_R0=0, SY_LFR_R1=0, SY_LFR_N_SWF_L=2048, SY_LFR_N_SWF_P=16(s), SY_LFR_N_ASM_P=0(s), SY_LFR_N_BP_P0=1(s), SY_LFR_N_BP_P1=1(s), SPARE=0x0, SY_LFR_N_CWF_LONG_F3=0, SPARE=0x0, SY_LFR_B_BP_P0=1(s), SY_LFR_B_BP_P1=5(s), SY_LFR_S1_BP_P0=0.25(s), SY_LFR_S1_BP_P1=1(s), SY_LFR_S2_BP_P0=1(s), SY_LFR_S2_BP_P1=5(s), SPARE=0x0
14:46:25.392409, TM_LFR_PARAMETER_DUMP, CCSDS_VERSION_NUMBER = 0, PACKET_TYPE: TM_PACKET = 0, DATA_FIELD_HEADER_FLAG: WITH_HEADER = 1, PROCESS_ID: RPW_PID_2 = 76, PACKET_CATEGORY: DUMP = 9, (PACKET_ID=0xcc9), SEGMENTATION_GROUPING_FLAG: STANDALONE_PACKET = 3, SEQUENCE_CNT=4, (PACKET_SEQUENCE_CONTROL=0xc004), PACKET_LENGTH=29, SPARE_1=0, PUS_VERSION = 1, SPARE_2=0, SERVICE_TYPE: HOUSEKEEPING_AND_DIAGNOSTIC_DATA_REPORTING = 3, SERVICE_SUBTYPE: HK_PARAMETER_REPORT = 25, DESTINATION_ID: GROUND = 0, TIME=0x8000010108c8, PA_LFR_HK_SID: LFR_DUMP_SID = 10, SPARE=0x0, SY_LFR_BW=1, SY_LFR_SP0=0, SY_LFR_SP1=0, SY_LFR_R0=0, SY_LFR_R1=0, SY_LFR_N_SWF_L=2048, SY_LFR_N_SWF_P=16(s), SY_LFR_N_ASM_P=1(s), SY_LFR_N_BP_P0=1(s), SY_LFR_N_BP_P1=1(s), SPARE=0x0, SY_LFR_N_CWF_LONG_F3=0, SPARE=0x0, SY_LFR_B_BP_P0=1(s), SY_LFR_B_BP_P1=5(s), SY_LFR_S1_BP_P0=0.25(s), SY_LFR_S1_BP_P1=1(s), SY_LFR_S2_BP_P0=1(s), SY_LFR_S2_BP_P1=5(s), SPARE=0x0
MAIS ces valeurs sont refusés si demandées via LPPMON : 0 et 1 sont impossibles à entrer dans l'IHM et la valeur 2 génère un TM_LFR_TC INCONSISTENT :
Détail en csv de l'ack :
2014 6 10 14:51:48:650 1 2 0 0 12 193 192 20 0 19 16 1 8 254 128 0 2 68 75 127 0 5 28 204 192 0 181 13 14 2
Est-il normal d'avoir cette différence de comportement.
--------------------------------------------
Contexte:
LPPMON: Version=0.2.2 Branch=default Changeset=835955994d5f
Carte mini-LFR: LFR-172200 dev V1.0; No série 5
Vhdl: mini-lfr_0.1.9
Brique Star-Dundee S/N 46120065
Soft:1.0.0.7 (variante sur carte finale)
TEST CASE = SVS-0019
script : just_mode_counter_loop.py
RPW-SYS-IDB-00067-LES_Issue2_Rev2
RPW-SYS-MEB-LFR-ICD-00097 Issue2_Rev2
RPW-SYS-SSS-00013-LES + Annex_Release_Definition Issue2_rev2
Updated by 
Updated by