dialin

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'staging'

Merge branch 'DENBUG-126-usage-record-crc-override-failed' into staging

Merge branch 'DENBUG-126-usage-record-crc-override-failed' into develop

DENBUG-126: fixed versioning string.

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

Merge branch 'DEN-16454-UI-VD-S106_fix_update_test_pt1' into develop

Merge remote-tracking branch 'origin/DEN-16454-UI-VD-S106_fix_update_test_pt1' into staging

Merge branch 'DENBUG-126-usage-record-crc-override-failed' into develop

DENBUG-126: updated NV ops enums to be in sync with FW values.

DIALIN-DENBUG-126_Usage Record Crc Override Failed
DIALIN-DENBUG-126_Usage Record Crc Override Failed
Merge branch 'staging'

Resolved.

Resolved.

Resolved.

Resolved.

Resolved.

Resolved.

Done.

Done.

All set. I have reverted it

All set. I have reverted it

DEN-16465: Updated - TestSuites:Integration testing update

Re-add the parameters removed based on CR comment

Remove extra newline

good point. Vy will fix it.

good point.
Vy will fix it.

Michael Garthwaite Ui code is frozen and we cannot change the UI code, so matched with what currently exists in UI. The attempt was to fix the integration tests, and we did not go over all the mess...

Michael Garthwaite
Ui code is frozen and we cannot change the UI code, so matched with what currently exists in UI.
The attempt was to fix the integration tests, and we did not go over all the messages API to fix them.
We can have it done later when have more time.

If the UI can ignore the fields, then why does dialin need to match the UI?

If the UI can ignore the fields, then why does dialin need to match the UI?

UI will ignore the last two values, which is not using it. FW can add extra fields, but for now if UI don't use it or does not have to use it will just ignore.

UI will ignore the last two values, which is not using it.
FW can add extra fields, but for now if UI don't use it or does not have to use it will just ignore.

this message structure is in Release FW. What is the UI going to with the incorrect message size?

this message structure is in Release FW. What is the UI going to with the incorrect message size?

Michael Garthwaite we needed to match it with UI and since UI code is freeze.

Michael Garthwaite
we needed to match it with UI and since UI code is freeze.

Missing two fields. Current DG FW has MSG_ID_DG_HEATERS_DATA = 0x2C as /// Heaters data structure. typedef struct F32 mainPrimayHeaterDC; ///< Main primary heater DC F32 smallPrimaryHeaterDC; ///...

Missing two fields. Current DG FW has MSG_ID_DG_HEATERS_DATA = 0x2C as

/// Heaters data structure.
typedef struct

F32 mainPrimayHeaterDC; ///< Main primary heater DC
F32 smallPrimaryHeaterDC; ///< Small primary heater DC
F32 trimmerHeaterDC; ///< Trimmer heater DC
F32 primaryTargetTemp; ///< Primary heater target temperature
F32 trimmerTargetTemp; ///< Trimmer heater target temperature
U32 primaryHeaterState; ///< Primary heater state
U32 trimmerHeaterState; ///< Trimmer heater state
F32 primaryEfficiency; ///< Primary heater efficiency
F32 primaryCalcTargetTemp; ///< Primary heater calculated target temperature
F32 trimmerCalcCurrentTemp; ///< Trimmer heater calculated current temperature
U32 trimmerUseLastDC; ///< Trimmer heater use last duty cycle
F32 previsouFlow; ///< Trimmer heater previous flow L/min
U32 controlCounter; ///< Trimmer heater control count

HEATERS_DATA_T;