Project

General

Profile

Actions

Bug #456

closed

champs PA_BIA_ON_OFF AND al de TM_LFR_SCIENCE_NORMAL_BP*_F* ne sont pas mis à jour / TC_LFR_UPDATE_INFO

Added by Veronique bouzid over 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
-
Start date:
02/07/2015
Due date:
% Done:

0%

Estimated time:
revision:
r0

Description

Bug signalé depuis dans JIRA :
https://jira-lesia.obspm.fr/browse/RPWMEB-508
-------------------------
Si on change la valeur du paramètre CP_PDU_BIAS_ON_OFF ( 0 vers 1) dans TC_LFR_UPDATE_INFO, on s'attend à voir ce parametre mis à jour dans les TM_LFR_SCIENCE
produite après la prise en compte de la TC_LFR_UPDATE_INFO. Le champ se nomme PA_BIA_ON_OFF dans TM_LFR_SCIENCE_NORMAL_BP* .

hors ce n'est pas le cas.

les logs
09:36:47.673516, TC_LFR_ENTER_MODE (CP_LFR_MODE=1)
09:36:47.695604, TM_LFR_TC_EXE_SUCCESS, TIME=0x80000009fae2
09:36:48.696052, TC_LFR_UPDATE_INFO,*CP_PDU_BIAS_ON_OFF: ON = 1*
09:36:48.909631, TM_LFR_HK,HK_LFR_UPDATE_INFO_TC_CNT=1 --> prise en compte de TC_LFR_UPDATE_INFO

le premier BP ne voit rien, ce qui peut s'explique car l acquisition a pu commence avant la prise en compte deTC_LFR_UPDATe_INFO
09:36:51.738856, TM_LFR_SCIENCE_NORMAL_BP1_F0, TIME=0x80000009fadf, PA_BIA_MODE_MUX_SET: SET_0 = 0, PA_BIA_MODE_HV_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS1_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS2_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS3_ENABLED: DISABLED = 0, PA_BIA_ON_OFF: OFF = 0, SPARE=0x0, SY_LFR_BW=1, SY_LFR_SP0=0, SY_LFR_SP1=0, SY_LFR_R0=0, SY_LFR_R1=0, SY_LFR_R2=0, PA_LFR_ACQUISITION_TIME=0x80000009fadf, SPARE=0x0, PA_LFR_N_BP1_BLK_NR_F0=11

malheureusement il n est jamais pris en compte aussi bien sur les BP1 que sur les BP2

09:36:55.738969, TM_LFR_SCIENCE_NORMAL_BP1_F0, TIME=0x8000000dfade, PA_LFR_SID_PKT: SC_N_BP1_F0 = 14, PA_BIA_MODE_MUX_SET: SET_0 = 0, PA_BIA_MODE_HV_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS1_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS2_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS3_ENABLED: DISABLED = 0, PA_BIA_ON_OFF: OFF = 0

09:36:55.751354, TM_LFR_SCIENCE_NORMAL_BP1_F1, TIME=0x8000000dfaeb, PA_BIA_MODE_MUX_SET: SET_0 = 0, PA_BIA_MODE_HV_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS1_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS2_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS3_ENABLED: DISABLED = 0, PA_BIA_ON_OFF: OFF = 0,

09:36:55.764467, TM_LFR_SCIENCE_NORMAL_BP1_F2, TIME=0x8000000dfbd0, PA_BIA_MODE_MUX_SET: SET_0 = 0, PA_BIA_MODE_HV_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS1_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS2_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS3_ENABLED: DISABLED = 0, PA_BIA_ON_OFF: OFF = 0,

BP2
09:37:07.755408, TM_LFR_SCIENCE_NORMAL_BP2_F0, TIME=0x80000019fad9, PA_BIA_MODE_MUX_SET: SET_0 = 0, PA_BIA_MODE_HV_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS1_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS2_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS3_ENABLED: DISABLED = 0, PA_BIA_ON_OFF: OFF = 0

09:37:07.75807, TM_LFR_SCIENCE_NORMAL_BP2_F1,*TIME=0x80000019fae6*, PA_BIA_MODE_MUX_SET: SET_0 = 0, PA_BIA_MODE_HV_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS1_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS2_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS3_ENABLED: DISABLED = 0, PA_BIA_ON_OFF: OFF = 0

09:37:07.781859, TM_LFR_SCIENCE_NORMAL_BP2_F2, TIME=0x80000019fbcc, PA_BIA_MODE_MUX_SET: SET_0 = 0, PA_BIA_MODE_HV_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS1_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS2_ENABLED: DISABLED = 0, PA_BIA_MODE_BIAS3_ENABLED: DISABLED = 0, PA_BIA_ON_OFF: OFF = 0

Idem pour les parametres
CP_BIA_MODE_MUX_SET, CP_BIA_MODE_HV_ENABLED, CP_BIA_MODE_BIAS1_ENABLED, CP_BIA_MODE_BIAS2_ENABLED, CP_BIA_MODE_BIAS3_ENABLED
correspondant à
PA_BIA_MODE_MUX_SET, PA_BIA_MODE_HV_ENABLED, PA_BIA_MODE_BIAS1_ENABLED, PA_BIA_MODE_BIAS2_ENABLED, PA_BIA_MODE_BIAS3_ENABLED.

le script utilisé se nomme /opt/VALIDATION_R3/lfrverif/LFR_SVS/SVS-0077/update_info_cnt_normal.py

les fichiers de log (2015_07_02-09_42_14*) se trouvent dans /home/validation/data/R3/3.0.0.7/SVS-0077/normal.

Pour l'instant le script n'a testé que les BP en Normal mode. Reste à verifier les autres produits ....

Ce comportement n'est pas en conformité avec ce que Paul écrit dans sa doc SDD p35 req-lfr-srs-55_ed1

Contexte du test
----------------
FSW 3.0.0.7
VHDL 1.1.83 (_c car chgt de contrainte sur timing)
EM sans Timegen
SocExplorerEngine.getSocExplorer: Version = 0.6.2, Branch = default, Changeset = 819d0376d481
StarDundee


Related issues

Related to Bug #531: champs PA_BIA_ON_OFF AND al de TM_LFR_SCIENCE_BURST_BP*_F* ne sont pas mis à jour / TC_LFR_UPDATE_INFOClosedVeronique bouzid04/10/2015

Actions
Related to Bug #532: champs PA_BIA_ON_OFF AND al de toutes les TM_LFR_SCIENCE_SBM1_* ne sont pas mis à jour / TC_LFR_UPDATE_INFOClosedVeronique bouzid04/10/2015

Actions
Actions

Also available in: Atom PDF